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 help topic identifies the key parts and options that are applicable to the record type you are creating.
Create a new flow by selecting Flow from the Process category.
Key parts:
A flow has two key parts:
Field
|
Description
|
|
Apply to
|
For a starter flow rule, select or enter a class that derives from the Work- base class.
For a flow that is to be started from a Subprocess shape  , Split For Each shape  , or a Spinoff shape  , you can select or enter a class derived from the Data- or Embed- 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.
|
|
Identifier
|
Enter a name for this flow. Begin the name with a letter and follow the rules for a Java identifier, but do not include dash characters. See How to enter a Java identifier.
|
Additional creation options
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
|
Select a template rule to provide a starting set of shapes and capabilities for the new flow:
- (none) — To create a flow using Process Modeler.
ScreenFlow — To create a screen flow rule using Process Modeler. To present assignments at runtime as form tabs, set the harness referenced in the Start shape to TabbedScreenFlow.
|
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 rule
About Flows
Open topic with navigation
