Enable Management of Change (MoC) permissive mode

When Management of Change (MoC) permissive mode is disabled, MoC restricts permissive mode aware processes (listed below) from modifying configuration fields when you have not supplied a changeset. When MoC permissive mode is enabled, permissive mode aware processes can modify configuration fields when you have not supplied a changeset. These untracked configuration changes will be logged in a process-specific log and stored by the MOCOrchestrator service in the AuditLogEntries table of the ManagementOfChange Database.

Note: By default, MoC permissive mode is disabled.

The following is a current list of permissive mode aware processes:

• Advanced Database Editor (ADE)

• Application Calculation Engine (ACE) Editor

• Batch Tracking Compiler (BTC)

• LMSDel

• DBPut

• DBDel

If permissive mode is disabled when you run permissive mode aware processes (that is, BTC, LMSDel, DBPut, and DBDel) from Windows PowerShell without supplying a changeset, you will receive an error message indicating the change is not permitted in the current mode. When you are using ADE and ACE code editors and do not supply a changeset (that is, Read-Only Mode), the toolbar Save buttons and menu items will be disabled.

To enable MoC permissive mode

Note: For information on overriding default configuration settings, refer to Modify configuration settings.

1. Create or open the ManagementOfChange.json file found in the following locations:

   • %DNADataRoot%\RealTime\config\Settings\ManagementOfChange.json

   • %DNADataRoot%\ManagementOfChange\config\Settings\ManagementOfChange.json

2. Set the ManagementOfChangePermissiveMode value to true.

   The following example shows the default content of the configuration settings JSON file:

   {

   "ManagementOfChange": {

   "ManagementOfChangePermissiveMode": false,

   }

   }