Flow form
Editing the Spin-off shape properties

Field

Description

Enter a text name for this shape . 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. For example, Begin Contract Processing.

The task name is only descriptive; it does not affect runtime execution of the flow. This name also appears inside the Spin-off shape on the Diagram tab.

Identify the objects the flow rule is to update. Select:

• On Current Work Item to continue processing on the current (unresolved) work object in the next flow.
• On Another Work Item to start processing on a different work object.
• On Embedded Page to apply this flow to an embedded page.

Optional. Select the name of the application that you want to link to the flow shape. The value of this field is referenced with the flow diagram in application documents.

Optional. Select the name of the work type for the application that you want to link to the flow shape. The value of this field is referenced with the flow diagram in application documents.

Optional. Select the name of the use case for the application and work type that details the implementation requirements for the flow shape. The value of this field is referenced with the flow diagram in application documents and on the Implementation tab of the corresponding Rule-Application-UseCase instance.

Field

Description

Assign a name to the new flow, an arbitrary text string containing no spaces. This name appears in the Visio diagram and in your flow form.

When first building, it is simplest to make this name the same as the name of your flow. Later when your flow is more complete, you can change the name to be more descriptive.

Identify the objects the flow rule is to update. Select:

• On Current Work Item to continue processing on the current (unresolved) work object in the next flow.
• Choose On Another Work Item to start processing on a different work object.
• Choose On Embedded Page to apply this flow to an object on an embedded page.

Select Regular or Screen Flow. Select Screen Flow if the flow for the other work objects is to consist only of a sequence of assignments (questions) and flow actions (responses).

(for On Current Work Item) Select a flow rule by Flow Type, the second key part of the flow rule branched to.

Some flow rules have input parameters. Enter parameters for the selected flow rule.

Optional. Text entered here appears as a history instance for the work object, recording that this flow was initiated.

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.

Select to indicate that this Spin-off 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 cleared.

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

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

For maximum user flexibility, clear this check box if your flow accepts inputs in any order. However, this approach is typically not workable for flows that contain fork and decision shapes, or that have intermediate tasks that are not entry points.

Field

Completing the Field

Optional. Enter a property reference in the current work object that identifies the key of the other work object.

Optional. Select the class (work type) of the other work object.

Optional. Identify the page containing the other work object, or a property reference holding the pzInsKey value of the other work object.

Select Regular or Screen Flow. Select Screen Flow if the flow for the other work objects is to consist only of a sequence of assignments (questions) and flow actions (responses).

Select the Flow Type, the second key part of the flow to be started for the other work object.

Optional. Text entered here appears as a history instance for the work object, recording that this flow was initiated.

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.

Select to indicate that this Spin-off 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 cleared.

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

Field

Completing the Field

Identify the embedded page on which the spin-off flow is to run; for example, .pyWorkParty("Originator").

Select the work type of the "other" work objects.

Select Regular or Screen Flow. Select Screen Flow if the flow for the other work objects is to consist only of a sequence of assignments (questions) and flow actions (responses).

Select the Flow Type, the second key part of the flow to be started for the other work object.

Optional. Text entered here appears as a history instance for the work object, recording that this flow was initiated.

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.

Select to indicate that this Spin-off 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 cleared.

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