![]() ![]() |
|
Help for Process Designer | |
Search | Index | |
![]() |
|
![]() |
![]() |
![]() |
About attachmentsAn attachment is a link to information a participant uses to complete a step in a workflow. For example, in a workflow for processing insurance claims, the submitted claim form and associated medical reports could be attachments. In the workflow definition, the author defines attachments and indicates the steps at which each attachment is used. In the insurance claims processing example, the medical reports are used in the medical review step but not in the policy verification step. The specific item an attachment links to is referred to in the Process Engine documentation as a target. The most common target is a document stored in a a Content Engine object store, or in a Content Services (CS) or Image Services (IS) library; however, document arrays, stored searches, folders, URLs, or files located on a shared disk can also be targets. Assigning a target to an attachmentTo provide flexibility, the workflow author can either assign a target to an attachment in the workflow definition or allow the target to be assigned when the workflow is launched or in progress. The following scenarios illustrate each case:
Specifying the participant's access to an attachmentFor each step in a workflow, the workflow author specifies the following:
Note the difference between access to an attachment and access to a target. The participant's access privileges for the target determine the operations he or she can perform on the target (such as opening or modifying). Access privileges on the target are not part of the workflow definition; if the target is a document in an object store or library, for example, the user's access to that document is specified in object store or library.
|
![]() |
|
![]() |
|