Batch Process rulesCompleting the Create, Save As, or Specialization form

You are here: Reference > Rule types > Batch Processes > Batch Process rules - Completing the New or Save As form

Batch Process rules Completing the Create, Save As, or Specialization form
About New General Parameters Pages & Classes History

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 using the following Developer Help topics:

Completing the Create form Designer Studio – Completing the Create form
Completing the Save As form Completing the Save As form
Completing the Specialization form Completing the Specialization form

This help topic help topic identifies the key parts and options that are applicable to the record type you are creating.

This rule form is reserved for future use.

Create a new batch process by selecting Batch Process from the Technical category.

Key parts:

Field

Description

Apply to

Specify the class that this batch process applies to.

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 activity, starting with a letter and containing only letters, numbers, and hyphens. Choose a name that is unique within the Apply to class. The name must be a valid Java identifier; see How to enter a Java identifier.

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

Related information

Open topic with navigation