IBM FileNet P8, Version 5.2.1            

Preferences - workflow

The Preferences for workflows options apply to all workflows in the workflow collection.

Validate Workflow Before Transfer/Launch

It is helpful and efficient to validate a workflow definition (or all of the workflow definitions in the collection that are specified to be validated) prior to transferring it to the workflow database. This is because the Process Designer validation tool not only lists errors, but also links directly to the step or route where the error exists.

To disable automatic validation in Process Designer in the transfer process

  1. Select Preferences on the Settings menu.
  2. On the Workflows tab, select or clear Validate Before Transfer/Launch.

TIP Even if you disable workflow validation in Process Designer in the transfer process, validation occurs automatically by workflow system when you transfer a workflow.

Add/Check In Before Transfer/Launch

To launch a workflow outside of Process Designer—for example, from a workflow subscription—a workflow definition or collection must be checked into your object store or library. To expedite the check in, both the transfer and launch actions include an automatic FileNet® Add or FileNet Check in. However, if you are testing a workflow and want to save the workflow definition or workflow collection in your local file system and launch the workflow multiple times, you can disable automatic Add or Check in to the object store or library during the development phase.

  1. Select Preferences on the Settings menu.
  2. On the Workflows tab, select or clear Add/Check in Before Transfer/Launch.  

When Add/Check In Before Transfer/Launch is enabled:

When Add/Check In Before Transfer/Launch is not enabled, you can transfer or launch either the current workflow definition or the workflow collection without checking it in to your object store.

Enable Inheritance

You can show or hide inheritance functionality in Process Designer.

  1. Select Preferences on the Settings menu.
  2. On the Workflows tab, select or clear Enable Inheritance.

When workflow inheritance is enabled, you can choose an existing workflow definition or collection (transferred to workflow system) as a base workflow from which to inherit maps, fields, rule sets, milestones, and so on. Inherited items are read only in the current workflow unless you override them.

When workflow inheritance is not enabled, the IBM® FileNet-provided WorkObjectEx is the base workflow and the inheritance functionality is not available in Process Designer.

NOTE   If you disable workflow inheritance in a workflow that inherits maps, fields, and other properties from another workflow, the base map of that workflow will be reset to WorkObjectEx and all items inherited and not overwritten from the previous base workflow will no longer be available. If these items are referenced, such as by a submap step, validation errors will occur.



Last updated: March 2016
bpfdh035.htm

© Copyright IBM Corporation 2016.