Setting the save mode in IBM® Process Designer

You can set the option that determines how changes in the editor are saved in the web Process Designer by adding the collaboration-mode configuration setting to the 100Custom.xml files.

About this task

When the collaboration-mode configuration setting is set to the value TP, explicit save is enabled. In this mode, when you edit an artifact in Process Designer, you must click Save to persist your changes. After you save your changes, the artifacts become available to other users for editing. When the collaboration-mode is set to the value HYBRID, changes in the editor are saved as you make them; however, other users can view them only in read-only mode. To make the artifacts available to others for editing, you must click Finish Editing after you complete your changes. The HYBRID option is available only for the web Process Designer. By default, the collaboration-mode is HYBRID. For more information, see Saving your changes in Process Designer.

Procedure

To add and enable the collaboration-mode configuration setting in the 100Custom.xml file, complete the following steps:

  1. Stop the server for Process Center.
  2. Open each 100Custom.xml file. For information about the individual 100Custom.xml files that need to be updated and their locations, see the topic Location of 100Custom configuration files.
  3. In each 100Custom.xml file, add the collaboration-mode setting and associated elements under the <properties> element, as shown in the following example:
    <web-pd>        
    <collaboration-mode merge="replace">HYBRID</collaboration-mode>
    </web-pd>
    (If you want to switch modes, change the value to TP.)
  4. In each 100Custom.xml file, save your changes.
  5. In a browser, open each 100Custom.xml file to ensure that it contains no special characters.
  6. Complete one of the following steps:
    • In a clustered environment, ensure that the changes are propagated to the nodes by forcing a synchronization and restarting the deployment environment.
    • In a stand-alone server environment, restart the server.