Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Configuration Console
  Search  |  Index
Process Reference  
Process Configuration Console
Getting Started
  Process Configuration Console toolbar
  Symbols in Process Configuration Console
  Security considerations
  Saving or discarding your changes
    Commit changes
    Discard changes
  The configuration hierarchy
  Multiple isolated regions and multiple VWServices
Isolated regions
Queues
Rosters
VWServices
Process Engines
Workflow database
Events and Statistics
   

Commit changes

The Process Configuration Console lists each modified workflow database object in the pending changes pane. In order to apply these changes to the database, you must commit them. Until you commit the changes, they exist only in memory. Once you commit them, the changes are saved in the database.

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.

  • If the focus is on the top level (Root), the Process Configuration Console commits all pending changes.
  • If the focus is on a VWService folder, the Process Configuration Console commits only the VWService changes.
  • If the focus is anywhere within an isolated region, the Process Configuration Console commits only those changes that apply to the selected isolated region.

The commit process suspends all other database transactions within the isolated region until it finishes. FileNet strongly recommends that you accumulate all changes and commit them at the same time, or that you commit 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, the Process Configuration Console prompts you to commit or discard your changes.

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 can take several minutes to complete.
   

NOTE When you commit changes, you make changes to the workflow database structures. If you currently have data in your workflow database, FileNet recommends backing up all the servers in your VWService prior to committal.

CAUTION The following actions do not require the Commit Changes action. These changes take place in the database as soon as you click OK. There is no ability to undo these changes later.

  • Removing the workflow database
  • Removing all isolated regions
  • Removing a single isolated region
  • Initializing an isolated region
Related topics

Discard changes