Flow form
Process Modeler — Editing Assignment shapes
 

Field

Description

Assign a name, no longer than 128 characters, 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.

When you begin building your application, it is customary to make this name the same as the name of the assignment activity. Later when your flow is more complete, you can change this to a more descriptive name.

Select an assignment activity. Use SmartPrompt to see a list of activities with an AssignActivity Type that are available.

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.) XXXXX What about ArchiveQueueList? Bill checking with Matt Sartin.

• Work-.WorkList — Causes the assignment to be placed on the worklist of the current operator (or of another operator identified by a Router shape). Creates an instance of the Assign-Worklist class.
• Work-.WorkBasket — Causes the assignment to be placed in a workbasket, determined by an associated Router shape. Creates an instance of the Assign-Workbasket class.
• Work-.External — Starts the directed Web access feature, sending a temporary assignment by email to a party identified in the work object who is not an interactive Process Commander user. Creates an instance of the Assign-External class. SR-5767 B-22707
• Work-.Agent — Sends the assignment to a background process rather than to a person (rarely used, similar to WorkBasketMARIK 3/17/06).

(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.)MARIK 3/17/06 poss bug6Why does it show up then?

The activity you select may accept input parameters. Supply a value for each parameter. See Completing activity parameters for guidance on common parameters. B-16680 Process Commander validates these parameter values when you exit from Visio editing (unless the flow in is Draft mode). 5.5 GRP-405 XXXXX As of 2/7 - doesn't appear to validate when you click ok - closes whether or not something is in the fields with no error or complaint - and is there a difference if you are in Draft mode?

Optional. Select a service level rule to apply to this assignment. See Associating a service level rule with an assignment task.

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 standard Declare Expression rule records this sum as the value of property Work-.pyTotalFlowActionCost.

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. 5.2

This checkbox works with Perform harness rules that include a breadcrumbs display and with assignments that offer the Previous flow action. In other cases, the checkbox has no effect.

This checkbox appears only when you select the Entry Point checkbox. Select to restrict users at runtime from jumping ahead to this step without having completed the preceding steps. After having completed this step, users may jump back to it from steps that follow it.

Leave unselected to allow users to select this entry point from anywhere within the flow. They can complete or visit an earlier or later step.

For maximum user flexibility, leave this checkbox unselected if your flow accepts inputs in any order. However, this approach is typically not workable for flows that contain fork and decision shapesa fork is a decision shape now, or that have intermediate tasks that are not entry points.

This checkbox appears only when you select the Entry Point checkbox. Select to run flow action post-processing when you click away from this entry point.

Field

Description

Optional. Select one or more local flow actions that are to be available at runtime from this assignment. Use SmartPrompt to display all flow actions available to flows in this class.

At runtime, local actions appear in the order listed here. Click to insert a row, or to add a row. Click to delete a row.

Optional. Select a use case application to use with this local flow action. Use SmartPrompt to display all use case applications available to flows in this class.

Optional. Select a use case work type to use with this local flow action. Use SmartPrompt to display all use case work types available to flows in this class.

Optional. Select a use case to associate with this local flow action. Use SmartPrompt to display all use cases available to flows in this class.

Field

Description

Optional. You can select a notify activity here, as an alternative to a separate Notify shape.

Some developers prefer this approach, to simplify the flow diagram. The system adds an envelope icon () to the assignment shape to indicate that correspondence is created as the assignment is created. XXXXX get new icon

Field

Description

Optional. You can select a router activity here, as an alternative to a separate Router shape, to simplify the flow diagram.

You can't specify a router activity if this assignment is within a swim lane. check now that routers are handled differently - no shape and no icon

Field

Description

Optional. Select one or more tickets that are to be available at runtime from this assignment. Add a row for each ticket. Use SmartPrompt to display all tickets available to flows in this work type.

Creating ticket rules is recommended but not required. You can enter here a name that does not correspond to a ticket rule.

If a shape has more than one ticket associated with it, then processing continues with that task only after all tickets are set.check

Example

Processing is connected to a ticket to respond to an exception, error flow or event. For example, if a mortgage application is withdrawn after some, but not all, of the application processing is completed, a mortgage processing flow can:

• Include a ticket named Withdrawn
• Connect this ticketed shape since there is not a 'ticket' shape? to a utility task that computes the fees due for work done so far, and any refund amount
• Follow the utility task with another that produces correspondence, to alert all parties working on the mortgage that it was withdrawn
• Connect to external systems to back out (rollback) changes or void accounting entries as appropriate

Field

Description

Select a field value rule for the worklist column Instructions that describes the task that users perform to complete the assignment. Click the pencil icon ( ) to review the field value rule or define a new field value rule. The SmartPrompt lists field value rules with an Applies To key part equal to the work type of the flow rule (or a parent class) and a Field Name key part of pyInstructions.

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.

When you plan to localize the application using this rule, so the application can support users in various languages or locales, choose the text carefully and limit text length to 64 characters. A field value rule with this text as the final key part is needed for each locale. When practical, choose a caption already included in a language pack, to simplify later localization. See About the Localization wizard.

If this parameter appears, you can enter a work object status value that displays when the assignment first appears on the worklist or in the workbasket. If you leave this blank, the status value is unchanged when this assignment is created.

Don't confuse the work object status value (the Work-.pyStatusWork property), which controls many aspects of processing, with the assignment status value. See Status.

Don't use this feature to set .pyStatusWork to a resolved value. Always use the standard utility Work-.Resolve to resolve a work object.

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.

Optional. Enter text to display in a confirmation form presented to the user when the flow action is complete.

When you plan to localize the application using this rule, so the application can support users in various languages or locales, choose the text carefully and limit text length to 64 characters. A field value rule with this text as the final key part is needed for each locale. When practical, choose a caption already included in a language pack, to simplify later localization. See About the Localization wizard.

Identify the Purpose key part of a harness rule the system is to use to present this assignment. (The system uses the Applies To key part of this flow rule as the first key part of the harness rule.)

By convention, the Purpose key part has the value Perform, or another name starting with the word Perform.

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.

WorkBasket activity. Select to redirect the assignment to the current operator if the workbasket is not defined. (This parameter is used by the Work-.WorkBasket activity.)

WorkList or WorkBasket activities. Select to prevent the activities from overwriting the newAssignPage page, allowing a pre-existing page to be performed instead. This option is useful for performing an assignment on a spun-off work object. (This parameter is used by Work-.WorkBasket and Work-.WorkList activities.)

External activity. Identify the Operator ID that serves as a model for the external operator. (This parameter is used by the Work-.External activity.)

External activity. 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.)

External activity. 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.)

External activity. Enter text to become the subject line of the email message sent to the external party. (This parameter is used by the Work-.External activity.)

External activity. Optional. Enter a phrase or sentence to appear in the body of the email message sent to the external party, above the system-generated URL link. (This parameter is used by the Work-.External activity.)

External activity. Optional. Identify the Corr Name key part of a correspondence rule to appear in the body of the email 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.