Control Point Skipping

It is possible to configure certain Transport Forms to skip certain control points in the path, based on the following fields.

• Transport form group
• Transport form type
• Task group
• Task type
• Task priority
• Any custom fields
• Project Phases

Example scenarios of where this functionality might be useful include where you do not require Merge BAU transports to be approved through every step of your Project landscape process, or similarly, where you do not want Maintenance changes to skip certain control points because they do not need the same level of approval as other changes being delivered.

Configuration of Control Point Skipping

The configuration of the skip capability is done within the Domain Controller backend, and is a two step exercise:

1. Switching on the Skip user exit by adding a row in table /BTI/TE_EXITC for */BTI/TE_EXIT_SAMPLE_0710 *

(You can either use this sample FM in /BTI/TE_EXITC or create a Z version)

2. Setting up the skipping you require in your process via configuration table /BTI/TE_SKIPCP

(by adding rows for the relevant task/form fields that you want to skip CPs for along with the targets/locations)

Please note the following information when configuring the table:

FIELD: either GROUPID or TYPEID or PRIORITY or [Custom Field Number] or PHASEID

ID: If skipping on Group, should be long serial number from /BTI/TE_GROUPS If skipping on Type, should be long serial number from /BTI/TE_TYPE If skipping on Priority, should be 1,2,3,4 If skipping on Custom Field, should be the custom field value.

TARGET: Target ID from within ActiveControl Windows GUI

LOCATION: (I = Inbox , Q = Import Queue , T = Test Queue , O = Outbox )

RISKGROUP: Only required for the (rare) scenario where you want objects defined in a certain Risk Group to stop or otherwise skip an approval point.

SKIP: “Skip”, or “Do not skip” or “Delete from branch”, depending on the requirement.

CUSTOM_FIELD: check this box if defining skipping rules based on custom fields. If doing so, the custom field number should be entered in [FIELD]

RISKLEVEL: Again, only required for the (rare) scenario where you want objects defined in a certain Risk Group to stop or otherwise skip an approval point.

Notes:

(i) Please refer to online Forum for details of Project Phase based skipping.
(ii) Please refer to online Forum for details of Critical Objects based skipping.
(iii) if you want client independent transports to skip a control point, the field is CLIDEP. (Client Dependent = “X”, Client Independent = Blank)
(iii) As of ActiveControl 7.20 – it is NOT possible to skip based on Project values. (however it possible to skip based on Project Phase dates)