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.
A flow action has two key parts:
Select the name of a class, typically a class derived from the Work- base
The list of available class names depends on the ruleset that 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 action. Begin the name with a letter and follow the rules for a Java identifier.|
Additional creation options
To mark the new rule as JSR 168 compliant, select the name of a template rule to copy.
The rule type Service Portlet is deprecated. Use Pega Web Mashup instead.
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
To create a Flow Action:
- In the header of Dev Studio, click .
- On the Create form, enter values in the fields to define the
context of the flow.
- In the Label field, enter text that describes the purpose of the circumstance definition.
- Optional: To change the default identifier for the circumstance definition, click Edit, and then provide a unique value in the Identifier field.
- Optional: Click View additional configuration options to include all other configuration options supported by this record type on the form. These options vary by record type and appear for only records that support Quick Create options.
- Select a Context to specify where the record will reside in your application ruleset stack and how it may be reused in the class hierarchy.
- In the Apply to field, press the Down Arrow key and select the class that defines the scope of the circumstance definition.
- In the Add to ruleset field, select the name and version of a ruleset that stores the circumstance definition.
- Optional: To override the default work item that your application
associates with this development change, press the Down arrow key in the Work
item to associate field, and then select a work item.For more information about your default work item, see Setting your current work item.
- Click Create and open.