Decision TablesCompleting the Create, Save As, or Specialization form

You are here: Reference > Rule types > Decision Tables > Decision Tables - Completing the New or Save As form

Decision Tables Completing the Create, Save As, or Specialization form
About New Table Results Parameters Pages & Classes Test Cases
History More...

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.

Create a decision table by selecting Decision Table from the Decision category.

Key parts:

A decision table has two key parts:

Field

Description

Apply to

Select the class to which this decision table applies.

Decision table rules can apply to an embedded page. On the Decision Table form, you can use the keywords Top and Parent in property references to navigate to pages above and outside the embedded page. If you use these keywords, include the class and absolute name — or a symbolic name using Top or Parent — on the Pages & Classes tab.

Identifier

Choose a unique name that indicates the purpose of the rule. Begin the name with a letter, and use only letters, numbers, and a hyphen.

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

In addition, this rule type supports rule redirection.

Related information

Open topic with navigation