Upgrade guide for SchedulerPro v7.2.0

Prevent silencing resolved scheduling issues

Since this release the SchedulerPro does not silence changes made by the Engine on data loading if there was a conflict, cycle or other scheduling issue which was resolved. This fixes the problem when applications could not persist changes after resolving a scheduling on data loading (happens because of silenceInitialCommit config enabled by default).

This is controlled by the ProjectModelpreventSilencingOnIssueResolve config. Which can be disabled back like this:

new SchedulerPro({
    ...
    project  : {
        // silence initial commit event if there was a conflict resolved
        preventSilencingOnIssueResolve : false,