|
![]() |
Add an assignment task for each place in the business process that requires human judgment and input. Flow processing of a work object normally pauses when it reaches an assignment shape until a user completes the assignments.
Add an assignment task for each place in the business process that requires human judgment and input.
For every assignment, add at least one flow action. The assignment normally appears on the worklist of the user who executes the flow.
1. Drag the assignment shape () and
drop it onto the flow.
2. If this flow is a screen flow, special rules apply. Continue with Flow Rules — Editing in Visio — Creating and Editing a Screen Flow.
3. When the Assignment Properties panel appears, complete these fields. (To edit the shape properties after you save the Flow form, open the Diagram tab, right-click the shape, and select the Edit tab on the pop-up window.)
Field |
Description |
Name |
Assign a name to this Assignment task. Choose a name meaningful to application users who see this on the work object history display, the breadcrumbs control (for entry points), and the Where-Am-I? diagram. The task name is only descriptive; it does not affect runtime execution. This name also appears inside the assignment shape on the Diagram tab.
|
Rule |
Four standard activities defined with Work- as the Applies To class are always choices in this field. (Your application may include others or override these standard activities.)
(Another standard assignment activity Assign-.Connect activity is used internally when creating an instance of the Assign-Connect class and to support BPEL processing. Do not use this for assignments directly.) |
Parameters |
The activity you select may accept input parameters. Supply a value for each parameter. See Parameters for guidance on common parameters. Process Commander validates these parameter values when you exit from Visio editing (unless the flow in is Draft mode). |
Service Level |
|
Local Actions |
At runtime, local actions appear in the order listed here. Click Click
See below for guidance on choosing local flow actions. |
Effort Cost |
Optional. You can associate a cost value (in any units) with this assignment. For each work object, the system computes the sum of these cost values for the specific path it takes through the flow rule. A Declare Expression rule records this in property Work-.pyTotalFlowActionCost. |
Notify |
Some developers prefer this approach, to simplify the flow diagram. The system add an envelope icon ( |
Router |
Some developers prefer this approach, to simplify the flow diagram. You can't specify a router activity if this assignment is within a swim lane. |
Entry Point? |
Select to indicate that this assignment task is an entry point, which a user can return to using the breadcrumbs control or the standard flow action Work-.Previous. The default is selected. This check box works with Perform harness rules that include a breadcrumbs display and with assignments that offer the Previous flow action. In other cases, the check box has no effect. |
Only going back? |
This check box appears only when you select the Entry Point? check box. Select to restrict users at runtime who are at this entry point to choose only those entry points (on the breadcrumbs display) that identify earlier steps in the flow. Leave unselected to allow users to select any entry point of the flow when at this entry point. They can click the breadcrumbs control or tab to complete or visit an earlier or later step.
|
4. Click Apply when finished.
5. Connect at least one incoming connector to the assignment shape.
6. Connect one or more outgoing connectors from the assignment shape, corresponding to flow actions.
Completing activity parameters
The parameters you supply depend on the activity you select. These are common:
Field |
Description |
Instructions |
Examples of instructions are "Evaluate and accept or reject" and "Fulfill as soon as possible." Use wording that clearly states what users are expected to accomplish.
|
Status (or StatusWork) |
|
StatusAssign |
If this parameter appears, you can enter an assignment status value (not a work object status value). If you leave this blank, the assignment has no status. |
Confirmation Note |
Optional. Enter text to appear in a confirmation form presented to the user when the flow action is complete.
|
HarnessPurpose |
By convention, the Purpose key part
has the value The action section in the harness rule you identify affects the presentation of flow action choices at runtime. The most appropriate choice depends on user skills, the complexity of the actions, and likelihood values. See Presenting flow actions — Comparing three approaches. |
Use Cur Oper |
Select to redirect the assignment to the current operator if the workbasket is not defined. (This parameter is used by the Work-.WorkBasket activity.) |
Operator Model |
Identify the Operator ID that serves as a model for the external operator. (This parameter is used by the Work-.External activity.) |
Days to Expiration |
Enter a positive integer for a number of calendar days after which the external assignment expires, unless completed. (This parameter is used by the Work-.External activity.) |
Party |
Identify the party role (such as Customer, Originator, or another role) of the party within the work object who is to receive the external assignment. (This parameter is used by the Work-.External activity.) |
Subject |
Enter text to become the subject line of the e-mail message sent to the external party. (This parameter is used by the Work-.External activity.) |
Message |
Optional. Enter a phrase or sentence to appear in the body of the e-mail message sent to the external party, above the system-generated URL link. (This parameter is used by the Work-.External activity.) |
Corr Name |
Optional. Identify the Corr Name key part of a correspondence rule to appear in the body of the e-mail message sent to the external party. The resulting output appears above the system-generated URL link. (This parameter is used by the Work-.External activity.) Process Commander validates this value when you exit from Visio editing. |
Tips: Plan for flexibility by
including local actions
Strive to
anticipate and include all the local flow actions that users
may ever need. Some local actions let users respond to
conditions that happen rarely but are important when truly
necessary.
For example, you may want to define and include local flow actions that let users bypass approvals, exceed normal limits, cancel assignments, and so on. Remember that such local flow actions may be restricted through privileges that are available to only some users, and that user selections of flow actions are recorded in work object history.
Neglecting to allow for such real-world situations may make your application seem rigid and unforgiving to users and managers.