Configuration

To enable and manage enhanced governance changes, ActiveControl introduces dedicated configuration tables that allow administrators to define system behaviour and customize user messaging.
Configuration tables can be viewed and managed using transaction SE16 and accessing the tables:

System Configuration – /BTI/TE_TP_MGM
This table is used to configure the source and target development systems involved in locking. It allows administrators to:

• Define parent-child system relationships.
• Activate object/key locking for each system.
• Specify the type of message (either Error or Warning) that should be presented when a lock condition is triggered.
  

Custom Messaging – /BTI/TE_TP_MGMTX
This table enables the configuration of custom error and warning messages that are displayed to users when locking rules are applied. It supports tailored communication to improve clarity and user experience.

Activates systems – /BTI/TE_ACTIVE – All Source and Target systems that participate in Governance​
All Source and Target systems that participate in Governance must be added to this table to enable Governance on the Object level, on the Key level, or on both
Note: The Domain Controller doesn’t have to be added

Developers Domain Controller – /BTI/TE_CONTROL – To ensure that the developer user is pointing to the right domain controller.
To be checked in all sources and targets.

These configuration tables provide the flexibility to align locking behaviour with organizational policies, ensuring consistent governance while maintaining a user-friendly experience.

Tables used in the enhanced governance process
Lock List – /BTI/TE_TP_OLOCK – This provides visibility into currently locked objects and allows authorized users to unlock them when necessary.​

Scope List – /BTI/TE_TP_SCOPE – Object and Keys to be that should be considered for Dynamic Locking​

Allow List – /BTI/TE_TP_ALLOW – Object and Keys where development will always be allowed