When the Enforce mode is activated, the Changeset will operate in a declarative manner similar to CI tools, such as Puppet and Ansible. 

For example consider there is an Create Application action within the Changeset, but the Application already exists as the Changeset was previously executed. Normally this would cause a validation error. Within Enforcing mode the existing object will be detected and the Create action will be converted into an Update action. Any changed parameters will then be updated to the new values.

Enforcing mode allow you to manage the lifecycle of Genesys features via the Changeset, long past the initial deployment. The same Changeset can be used to deploy a feature set within Development and Production environments can also be used to maintain it. Upgrades and fixes can be added into the Changeset and executed again with minimal effort.

With the Enforce mode, it is important to review the change control documentation generated from the Changeset to confirm the actions that will be taken. This can also be achieved via the “Simulate Run” feature.

The Enforce mode should always be used when running Changesets from Puppet or Ansible.