About Flow Actions
Flow Actions
|
|
Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You may copy data instances but they do not support specialization as they are not versioned.
Based on your use case, the Create, Save As or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:
This
Create a flow action by selecting Flow Action from the Process Category.
A flow action has two key parts:
Field |
Description |
|
Apply to |
Select the name of a class, typically a class derived from the Work- base class. The list of available class names depends on the ruleset you select. Each class can restrict applying rules to an explicit set of rulesets as specified on the Advanced tab of the class form. NOTE: When work items in your application contain an embedded page or pages that can be any one of multiple Data- classes, choosing a Data- class for the Apply to key part of a flow action can be beneficial. See PDN article 21030 How to create flows that operate on embedded pages of a work item. |
|
Identifier |
Enter a name for this flow action. Begin the name with a letter and follow the rules for a Java identifier. See How to enter a Java identifier. |
Referred to as Quick Create options, the fields presented in this area of the Create form are optional. Selections made here can be used as a starting point for the rule you are creating:
Field |
Description |
| Template |
To mark the new rule as JSR 168 compliant, select the name of a template rule to copy. Specify |
When searching for instances of this rule type, the system uses full rule resolution which: