Save Configuration Changes
Configuration changes can be saved without actually checking-in the
rule. Use the Save 
button to save the configuration changes
in a file or use the Save All 
button to save changes
made in all open files. The changes are saved locally
to the computer being used, but not written to the database. If
the configuration is complex and takes several days to complete, then
this is a useful option, as configuration can be saved and the user can
log-off the computer without checking-in the rule. Remember
to come back to the same computer where the configuration was saved since
the Save and Save All buttons only save changes locally.
Other users may view the rule that is checked-out, but they will only see the configuration that is stored in the database. They will not see any configuration changes that were saved locally.
Save All saves all of the rules that are open and validation errors will be presented for each of the open rules. Any validation errors need to be resolved and Save All should be done again.
Local changes won't be saved from session to session on rules that have not been saved to the database initially, because new rules need to either be checked in or discarded when logging out of the Palette.
Copyright © 2009, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices