Version 3.5.10 of the ITP/MDK Repository introduced the status [published] for object revisions. This status is used by default to determine which revisions of dynamic objects are used in a model run.
A compatibility option "Handle accepted revisions as published" was also introduced. If this option is set, the ITP/MDK Repository reverts to its previous behavior of returning [accepted] revisions for dynamic objects, instead of revisions with the new [published] status. This allows customers that already are using the [accepted] status in their processes and configuration to postpone the transition to using the [published] status. When a pre-3.5.10 version is upgraded, this option is turned on. New installations will have the option turned off.
Note
Do not to turn on the option when the status [published] on objects is already introduced. In this case, the runtime behavior of which revision will be selected for the production run is not defined.
The dialog under the Installation properties menu allows you to change the value of this option. The ITP/MDK Repository Server and Clients have to be restarted to make the change fully effective.
Note
The checked option "Handle Accepted revisions as Published revisions" even takes charge if ITP/Server is configured to select runtime objects with the status published from the ITP/MDK Repository. Refer to the topic about the General tab in the Administrator's Help for more information about the configuration setting that can be used to set the status of the runtime objects that are retrieved from the ITP/MDK Repository, i.e., RepositoryObjectStatus.