AR – Approval Rules

The following figure shows the approval rules that are used to determine a list of approver names in set processing. This places a restriction on the execution of the set until the approvers have authorized it. See Set-Processing for details.

Approval Rules

Approval Rules Definition Screen

The following figure is a list of Approval Rules. It is the first screen displayed after entering option AR and selecting a version.

Approval Rules Definition Screen

Detail Screen

The following figure shows the details displayed when a specific Approval Rule is selected from the Approval Rule List screen.

Detail Screen

Field Descriptions

The following table describes each field for an Approval Rule definition:

Field Descriptions

Field Name	Description
Appl Group	The Application Group covered by this approval rule.
Appl	The Application covered by this approval rule. Valid values: * – An asterisk indicates all applications. An existing ApplicationID.
Stream	The Stream covered by the rule. Valid values: * – An asterisk indicates all Streams. An existing Stream code.
Level	The level to be protected. For a promote operation, the target level is used. Valid values: * – An asterisk indicates all levels. An existing level.
Type	The component type to be protected. Valid values: * – An asterisk indicates all component types. An existing component type.
Change Type	The change type of the set. Valid values: * – An asterisk indicates all change types. S – Standard. E – Emergency. I – Incidental. User-defined change type – as defined in M.CH.
Approver	The approver name. See Set-Processing for details of the approval process. Valid values: A value that is defined in M.AN (Approver Names). This name maps to a resource in the external security product.
Criteria	This field is available for customized site-specific values.
Approval Required	Indicates whether approval is required before the set can be executed. If approvals are required, the approver has a restrictive role over the change. If approvals are not required, the approver has more of an auditing role over the change. Valid values: Y – Approvals are required before the set can be executed. N – Approvals are not required before the set can be executed.
Quorum	Indicates that multiple UserIDs must grant approval for this approver name. Valid values: A number from 1-9.
Usage	The Usage flag can have the following valid values: blank – Regular Rule. I – Impact Approvals Only. This rule is to enable approvals of Sets that have components in them affecting this Application. Approvals will not be required if the component is from the same Application Owning Group, nor when a version of the component already exists in the level being promoted to. This is based upon both Static and Dynamic relationships found in the Component Reference. S – SQL Rule. This rule is to enable approvals of Sets that have components with the SQL Flag set to “Y”. A – All Rules. This rule is for all of the above.

How Approval Rules Work

When a Set is Locked, ISPW uses the entries defined here to determine what approvals are required for the Set. ISPW looks at each Task in the Set, and if there is a matching Approval Rule, the Approval is added to the Set.