During flow rule design and development, you can promote intent-driven processing through careful naming, labelling, and and selection of flow actions available to users, and the Instruction field in assignments.

As a best practice, make the Short Description of a flow action start with an action verb and describe a goal or subgoal of the flow, using terms from the application domain that users will recognize.

For example, the following action labels convey the users' intent:

• Submit PO for approval
• Perform quality review
• Verify application

In contrast, offering users too many actions, or only vaguely labelled actions, only some of which are appropriate in specific contexts, forces the user to learn and decide which are meaningful in that context. This is a "toolbox" approach, rather than intent-driven.

	flow action, instruction
	About flow actions

Definitions — I