Workflows
The TCM application integrates with workflows created with FileNet Process Designer. To associate a workflow with a teamspace object, the workflow designer defines subscriptions to associate documents, folders, or teamspaces with a workflow definition.
Launching a workflow from within TCM
From within the TCM application you can start a workflow from a teamspace, a teamspace folder, or a teamspace document. When you use the start workflow action button to launch a workflow, a new browser window opens, and Workplace displays a list of workflow subscriptions associated with the document, folder, or teamspace class.
- When you start a workflow designed to use an initiating attachment from a folder or document, the folder or document is attached to the workflow.
- Workflows that you start from a teamspace do not use an initiating attachment.
Creating and modifying teamspace objects with a workflow
You can launch a workflow outside of the TCM application that will create, modify, or use teamspace objects.
- If a workflow is to be used with the TCM application, it must use the Collaboration Integration workflow as its base workflow. The Collaboration Integration base workflow is provided with TCM. (By default, it is installed at C:\Program Files\FileNet\Collaboration\Workflow\CollaborationIntegration.pep.) See the Team Collaboration Manager Installation Guide for more information.
- If you use a workflow to create a task, the designer of the workflow determines whether or not to make the created task a workflow-aware task. When a workflow creates a workflow-aware task, the workflow will not proceed until the task is complete. Once a workflow-aware task is complete, it cannot be reopened.
The TCM application can add targets to workflow attachments. TCM uses the following rules for adding targets to attachments and working with attachment arrays:
- If the workflow does not have any assigned or unassigned attachments, TCM adds the appropriate target (such as a teamspace folder or document) as the first assigned attachment in the attachment array.
- If the workflow already has one or more assigned attachments, TCM adds targets to the end of the attachment array. This is the case even when there are unassigned attachments in the attachment array.
- If a workflow contains only a single unassigned attachment, TCM replaces the unassigned attachment if it is adding other items. If there is more than one attachment (any combination of assigned and unassigned) TCM does not delete any attachments.