• The redline feature has been introduced to enable parallel development, allowing to perform concurrent changes. BOM changes can be planned with inserted parts, replaced parts, modified usage and occurrences, and removed parts.

• The global workflow variable isRedlineSupported must be enabled to activate the redline actions for upgrading or enhancing the custom workflow.

• A new Start Execution action has been introduced to formally separate the planning stage for change notices from the implementation stage. This action will provide better control over the sequencing of change notices that are ready for implementation.

• New action control preferences have been introduced to control when resulting objects can be applied to the change task. Actions like revise, save as, new one-off version, and search/paste/collect resulting objects can be controlled.

• The resulting object revisions that are released by a change notice will become the affected object revision on other open change notices that have the same affected objects. In addition, BOM changes that are released by the change notice are synchronized with other open redlines that are planning concurrent changes. The Object Release States mapping rule must be defined to trigger this synchronization.

• The mapping rules have been introduced to define the eligible values for change intent, release target, and state of the released object. The mapping rules facilitate the configuration of the change management process.