Add Warning Message on Items that become Locked when set as Active

What is the challenge?

Certain configuration items such as Questionnaires, Risk and Control Matrices, and certain Custom Fields become restricted from editing once they are marked as Active.

While copies of these items can be created, administrators are not always aware of the consequences of activation. In many cases, if changes are required later, a new copy must be created and existing naming conventions cannot be reused because the original active item already exists. This can lead to confusion, the need to duplicate configurations, and inconsistent naming standards across the system.

The current behaviour is often only discovered after activation, by which point administrators may have already finalized naming standards, documentation, training materials, or references to the original item.

Introduce a warning or confirmation message whenever a user selects "Set as Active" for an item where activation will restrict future editing.

What is the impact?

• Administrators may activate configurations before they are fully finalized.

• Additional effort is required to create replacement copies when changes are needed.

• Naming conventions can become inconsistent as original names cannot always be reused for replacement items.

• Duplicate questionnaires, matrices, and other configuration items can accumulate over time.

• Increased support requests and implementation delays caused by unexpected configuration restrictions.

• Reduced administrator confidence due to the lack of visibility regarding the consequences of activation.

Describe your idea

Introduce a warning or confirmation message whenever a user selects "Set as Active" for an item where activation will restrict future editing.

The warning should clearly explain:

• That activating the item will prevent or limit future modifications.

• Which elements of the configuration will become locked.

• That future changes may require a copied version to be created.

• That the original naming convention may not be available for reuse once a replacement is created.

• Any downstream impacts on reporting, references, integrations, or existing records.