IBM FileNet P8, Version 5.2.1            

Committing changes

When you make configuration changes in Process Configuration Console, in most cases these changes are added to a list of pending changes. The pending changes exist only in memory until you choose to commit the changes.

Process Configuration Console lists each modified workflow database object in the pending changes pane. After you commit them, the changes are saved in the database.

Important: When you commit changes, you make changes to the workflow database structures. If you currently have data in your workflow database, back up all the servers in your workflow system before committal.

The Commit Changes action is context-sensitive. This means that the transactions to be committed depend on the current focus, or selection, in the scope pane.

To commit changes:

  1. Make sure that you have selected the appropriate node in the scope pane. The selected node determines the scope of the Commit Changes action.
  2. Click Commit Changes on the toolbar.
  3. Click Yes. Depending on the number of changes to be committed, this action can take several minutes to complete.
Important: The commit process suspends all other database transactions within the isolated region until it finishes. Accumulate all changes and commit them at the same time, or commit the changes when the isolated region is relatively inactive. Whenever possible, avoid committing changes after every modification.

If you have any pending changes when you disconnect from an isolated region or when you exit, Process Configuration Console prompts you to commit or discard your changes.

Tip: If you use File > Exit to close a workflow application (Process Administrator, Process Configuration Console, Process Designer, or Process Tracker), the application prompts you to save any unsaved changes before it closes. However, if you click Close in the upper right corner of the window, one of the following actions occurs:


Last updated: October 2015
bpfc010.htm

© Copyright IBM Corporation 2015.