Please note that the Skipping functionality detailed in this section is superseded by the Rules Engine Skipping consumer.
It is possible to configure Skipping Rules so that Transport Forms bypass certain control points in the ActiveControl path.
This can either be done using the Rules Engine Skipping consumer (from ActiveControl 8.0 onwards) detailed earlier in this Administration Guide, or using the legacy Skipping capability described in this section of the Administration Guide.
These rules can be created based on the following fields.
- Transport form group
- Transport form type
- Business Task group
- Business Task type
- Business Task priority
- Any custom fields
- Project Phases
Example scenarios of where Skipping might be useful include where you do not require Merge TOC 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
Skipping is setup via configuration table /BTI/TE_SKIPCP in the Domain Controller, by adding rows for the relevant task/form fields that you want to skip CPs for along with the targets/locations.
| Field | Description |
|---|---|
| CLASS | Either REQUEST or TASK or METADATA |
| 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 | (optional) 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. |
Post your comment on this topic.