Process Engine assets

Process Engine: object store assets

Workflow definition

Description

Provides an electronic representation of the activities and resources required to accomplish a business process. A workflow definition acts as a processing template that Process Engine uses each time the workflow runs, routing the work to the specified participants, along with data, attachments, and other information they will need to complete the activities.

Deployment Mechanism
  1. Enterprise Manager export tool: See Create export files.
  2. FileNet Deployment Manager conversion tool: See Convert objects for import.
  3. Enterprise Manager import tool: See Import converted objects.
Dependencies
  • If a workflow definition contains references to attachments, then those attachments must exist in the specified object store in the destination environment by the time the workflow is processed. You are responsible for deploying the attachments.
  • If a workflow definition is used in a workflow subscription, the workflow subscription will be invalid in the new P8 system.
  • If a workflow definition contains user-defined queues, rosters, event logs, they need to be deployed as well.
  • If a workflow definition contains specific LDAP user name and groups, they need to be available in the system.

See Common dependencies between objects.

Environment-specific data References to attachments identify the object store in which the attachments are found. FileNet Deployment Manager converts these object store references when converting the workflow definition.

Any object exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information identifying users and groups. For more information, see Permission.

Notes The workflow definition contains the data required to create an executable workflow. Before you can run the workflow in the destination environment, you must transfer the workflow definition into the Process Engine database to create the executable workflow. For more information, see About transfer.

Workflow subscription

Description Provides an association between a class or an object and a workflow definition. The subscription can specify which events trigger an automatic launch of the workflow or if a user must launch the workflow manually.
Deployment Mechanism

There is no automated mechanism for export and import of workflow subscriptions.

Dependencies

Not applicable

Environment-specific data Not applicable
Notes

The workflow subscription requires the version ID of executable workflow that is created when you transfer the workflow definition to the Process Engine database.

Process Engine: database assets

Application space

Description Provides a mechanism for organizing the resources for a mashup application or other custom application that uses a workflow.
Deployment Mechanism

Exported and imported as part of the isolated region configuration using either Process Configuration Manager or the Process Engine Export/Import Utilities.

For more information, see the following topics:

Dependencies None
Environment-specific data If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.
Notes Application spaces need to exist in the destination environment for the workflow definitions to work.

Event log

Description Contains a record of system or workflow events for each isolated region. This type of logging is useful for tracking workflow activity. Each event that is logged is part of an event category, and has an associated event number.
Deployment Mechanism

Workflow events in an event logs are not deployed. However, event log configuration is exported and imported as part of the isolated region configuration using either Process Configuration Manager or the Process Engine Export/Import Utilities.

For more information, see the following topics:

Dependencies None
Environment-specific data If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.
Notes Event logs need to exist in the destination environment for the workflow definitions to work..

Queue

Description Provides a workflow database table to contain work items. There are four types of queues: user queues, work queues, component queues, and system queues.
Deployment Mechanism

Work items in a queue are not deployed. However, the queue configuration is exported and imported as part of the isolated region configuration using either Process Configuration Manager or the Process Engine Export/Import Utilities.

For more information, see the following topics:

Dependencies None
Environment-specific data If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.
Notes Queues must exist in the destination environment for workflow definitions to work.

Roster

Description Provides a database table that contains the current location of and other information about all workflows.
Deployment Mechanism

Roster items are not deployed. However, the roster configuration is exported and imported as part of the isolated region configuration using either Process Configuration Manager or the Process Engine Export/Import Utilities.

For more information, see the following topics:

Dependencies None
Environment-specific data If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.
Notes Rosters must exist in the destination environment for workflow definitions to work.

User preferences

Description Contains user preferences such as e-mail addresses, notification flags, and proxy user information.
Deployment Mechanism

Exported and imported as part of the isolated region configuration using either Process Configuration Manager or the Process Engine Export/Import Utilities.

For more information, see the following topics:

Dependencies None
Environment-specific data If the destination environment does not use the same LDAP provider as the source environment, you must edit the security settings in the exported isolated region configuration data before you import the data.
Notes None