Flow Actions - Completing the New or Save As form
Flow Actions - Completing the Create, Save As, or Specialization form
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 can copy data instances but they do not support specialization because they are not versioned.
Create a flow action by selecting
Flow Action
from the
Process Category.
Key parts:
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
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. |
Additional creation options
| Field | Description |
|---|---|
| Template |
To mark the new rule as JSR 168 compliant, select the name of a template rule to copy.
Specify
|
Rule resolution
When searching for instances of this rule type, the system uses full rule resolution which:
- Filters candidate rules based on a requestor's ruleset list of rulesets and versions
- Searches through ancestor classes in the class hierarchy for candidates when no matching rule is found in the starting class
- Finds circumstance-qualified rules that override base rules
- Finds time-qualified rules that override base rules