Deprecated Collection form - Completing the Basic / Advanced Collection tab

Complete this tab to identify the rules in the collection, the sequence in which they run, and preconditions. Rows on this tab are called steps, similar to the steps in an activity.

Basic and Advanced layouts

This tab has two alternate layouts: Basic Collection and Advanced Collection . You toggle them by selecting the Show Advanced Options? check box in the Preamble and Stop tab.

Basic Collection (default) — Use this tab to execute a decision tree, decision table, or map value in a step. Step pages are not enabled. Only when rules can be used as preconditions.

Field	Description
Define Collection Specifications	Complete the rows of this array to identify the rules that form the collection. Order is significant; at run time, rows are evaluated starting at the top. To reorder the rows of this array, hold the mouse pointer over a number. Click and drag to another row. To duplicate or move a row, hold the mouse pointer over a number. Or, right-click to access a context menu with `Cut`, `Copy`, and `Insert` options.
Description	Optional. Enter a brief text description of this step.
When	Optional. Select a when condition rule, or an expression that must evaluate to true for the step to execute.
Execute	Identify the type of decision rule to execute: `Decision Tree` — A decision tree. `Decision Table` — A decision table. `Map Value` — A map value.
Rule	Specify the name — second key part — of the rule to be executed in this step. This is a rule of the type identified in the Execute field.
Rule Resolution Qualifiers	Optional. The following describe the qualifiers available for decision trees, decision tables, or map values that are available in the Rule Resolution dialog. To open the dialog, click the Open icon . When you select the check box and enter a property reference or literal value in the adjacent text field, rule resolution selects one of the following: A circumstance-qualified rule of that name rather than an unqualified rule. A time-qualified rule with a date range that doesn't include "now". These temporary values do not affect rule resolution for preconditions.
Override Circumstance Property Value?	Select to indicate that while rule resolution searches for the decision tree, decision table, or map value identified in this row, a replacement value is temporarily used for the Circumstance Property . The original property value is restored after the step completes (unless the value is changed again during the course of the step).
(no label)	Enter an expression that at run time provides the temporary Circumstance Property value. The system evaluates replacement value only once at run time, before any other collection processing (including mixins) is performed.
Override Circumstance Date Property Value?	Select to indicate that while rule resolution searches for the decision tree, decision table, or map value identified in this row, a replacement value is temporarily used for the Circumstance Date Property . The original property value is restored after the step completes (unless the value is changed again during the course of the step).
(no label)	Enter an expression that at run time provides the temporary Circumstance Date Property value. The system evaluates this expression only once at run time, before any other collection processing (including mixins) is performed.
Override Rule Resolution Date?	Select to indicate that while rule resolution searches for the decision tree, decision table, or map value identified in this row, a replacement value is used rather than the true current date and time. This can cause a time-qualified rule to be selected that otherwise would not be selected with the true current date and time.
	Enter a literal `DateTime` constant or an expression that at run time provides the date and time to be used during rule resolution. The system evaluates this expression only once at run time, before any other collection processing (including mixins) is performed.

Advanced Collection — Use this tab to execute a collection, list view, activity, or Declare Expression rule (in addition to the basic decision rules described above). You can specify a step page for the rule. The following table describes fields that are unique to the Advanced Collection tab:

Field	Description
Precondition Type	Optional. To cause the rule in this row to execute only when certain conditions are met, specify the type of rule, or `None`. Click the check box icon to expand the row and display the fields: `None` — No precondition. `When` — A when condition rule, or an expression that evaluates to true or false. `Decision Tree` — A decision tree that evaluates to true or false. `Decision Table` — A decision table that evaluates to true or false. `Map Value` — A map value that evaluates to true or false. If the Execute field for this row has the value `Other Collection`, choose a precondition that does not depend on the results of other rules on this tab.
Step Page	Specify the name of a page for the precondition and the rule in this step. Include this page name and a class for the page on the Pages and Classes tab. If blank, the system uses the primary page corresponding to the Applies To key part of the collection rule as the step page when evaluating the precondition.
Execute	Identify the type of the rule to execute in the context of the Step Page page. `Another Collection` — A collection rule. At runtime, the steps in the Basic / Advanced Collection tab of the specified collection rule are appended to those on this rule's tab and run in sequence. `Activity` — An activity. `Declare Expression` — A Declare Expression rule that meets certain criteria. `List View` — A list view rule that returns the keys of other rules. Decision Tree, Decision Table, and Map Value are also available on this tab as described previously.
Rule	Specify the name of the rule to be executed in this step. This is a rule of the type identified in the Execute field. The system uses the class of the page in the Step Page field to locate this rule at run time.
	The name — second key part — of the collection rule to be executed in this step. The system uses the class of the page in the Step Page field to locate this rule at run time. You can specify how duplicate rules are handled and modify input parameters by clicking the Open icon to open the Collections Parameter dialog. Duplicate Handling — By default, all rules are executed in both collections. You can control how the system consolidates rules already encountered with rules of the other collection rule at runtime. In the Duplicate Handling field, select one of the following: `Include All` (default) — No consolidation is necessary. If a rule appears more than once, it executes each time in the ordinary sequence. `Remove Rules with Same Name` — If the rule with this name ( pxInsID property) is already in the list, it is removed. If it is in the list multiple times, then all occurrences are removed. `Remove Identical Rules` — If the rule with this handle ( pzInsKey property) is already in the list, it is removed. If it appears in the list multiple times, then all occurrences are removed. Optional: Use the Collection fields to modify the rule you specified in the Execute field. Parameters — Use this section to modify the parameter values (if any) specified in the collection rule (not the one identified in the Execute field).
	Identify a property reference that may be computed by a Declare Expression rule that has `When applied by a Rule Collection` as the value of the Calculate Value field on the Change Tracking tab. The system uses the class of the step page for this step as the Applies To key part to find this Declare Expression rule.
	Identify the second key part of a list view rule that returns the keys of other rules that are to execute as part of this collection. Reference a list view rule that meets either of two conditions: The Applies To class of the list view rule is Data-Rule-Summary and the list view returns the pyClass and pxInsID properties or, The Applies To class is a subclass of the Rule- base class and it returns the pxInsID, and pxObjClass properties. (If the list view rule returns other list view rules, include the pyClassName property in the results too.) The system uses `ALL` as the third key part to locate the list view rule at runtime. Each `pxResults()` page that identifies a rule of one of the rule types that can appear in this Execute field becomes a new step; `pxResults()` pages that identify rules of other types are ignored. The order of results pages is significant. Click the Open icon to open the Rule Resolution Qualifiers dialog to specify: How duplicate rules are handled at run time. See Duplicate Handling above. The class of the list view whose results are executed for this step.
	Identify here the second key part of the activity that is executed in this step. Click the Open icon to open the Activity Parameters dialog and modify the parameters (if any).

Switching between Basic and Advanced Collection tabs

Because there are fields in the Advanced Collection tab that do not appear in the Basic Collection tab, entered (saved or unsaved) values will change when switching between tabs.

Basic to Advanced:

Decision Tree, Map Value, and Decision Table Execute and Rule values remain.
The When rule appears in the Precondition Type fields.

Advanced to Basic:

Description remains.
Step Page values do not appear.
Activity, declarative expression, another collection, and list view Execute and Rule values do not appear. The Execute value defaults to Decision Table.
When rules in the Precondition Type field appear in the When field for the basic decision rule types. All other precondition types do not appear.

Values entered in the Step Page , Precondition Type , Execute , and Rule fields persist when you switch between tab formats.