ActiveControls “Dynamic/Defined Locking Solution” ensures that only authorized changes are made to specific objects or keys, preventing unintended overwrites or conflicts. It dynamically evaluates whether a change should be allowed based on predefined rules and lists.
When a change is initiated, the system checks if the object is within the scope list to determine if locking rules apply.
- If a change request matches the scope list but also matches the allow list, it proceeds without triggering a lock.
- If a change request matches the scope and is not in the allow list, the system checks to determine if the object is currently locked.
- If locked the change is blocked.
- If not locked the change proceeds and the Locking Table is updated to reflect the new lock status.
Benefits of Dynamic Locking Process
- Prevents unauthorized or conflicting changes
- Supports governance and auditability
- Enables safe parallel development and configuration
- Reduces risk of system instability
The matrix below details the expected behaviour of the dynamic/defined object and key locking.
| In Scope List | In Allow List | In Lock List | Lock List Behaviour | Development Allowed/Denied | Reason |
|---|---|---|---|---|---|
| ✅ | ❌ | ❌ | Added | Allowed | In-Scope, not currently locked |
| ✅ | ❌ | ✅ | No Change | Denied | Locked, Not in Allow List |
| ✅ | ✅ | ❌ | Added | Allowed | In-Scope, In Allow List |
| ✅ | ✅ | ✅ | No Change | Allowed | Locked, in Allow List |
| ❌ | ❌ | ✅ | No Change | Denied | Locked, Not in Allow List |
| ❌ | ❌ | ❌ | No Change | Allowed | Not In-Scope or Lock List |
| ❌ | ✅ | ❌ | No Change | Allowed | In Allow List |
| ❌ | ✅ | ✅ | No Change | Allowed | Locked, in Allow List |


Post your comment on this topic.