4. Best Practices: CIMPLICITY Version Changes
1 | CIMPLICITY version upgrade. |
2 | CIMPLICITY version downgrade. |
CIMPLICITY Version Upgrade
- Follow the Change Management project management recommended procedure to ensure the managed project is up to date.
- Apply the CIMPLICITY upgrade.
- Follow the Change Management project management recommended procedure to ensure the managed project is up to date.
CIMPLICITY Version Downgrade
Important:
Make sure that all configuration applications are closed and remain closed through this process.
Procedure
- Follow the Change Management project management recommended procedure to ensure the managed project is up to date on the Change Management server.
- Right-click Project in the Workbench.
- Select Manage>Show History on the Popup menu.
- Select the current project and the labeled project that corresponds to the previous version of CIMPLICITY.
- Identify the configuration changes.
- Stop the project.
- Right-click Project in the Workbench.
- Click Manage>Show History on the Popup menu.
- Select the labeled version of the project that was running successfully.
- Click Get to get that version.
- Delete any files that were added from the local project.
- Modify any non-CIMPLICITY configuration changes that were made to support the requirements change
Note: You may need to delete saved runtime information (e.g. SAVED_POINT files).
- Apply any desired/application configuration changes from the new project
- Use project management best practices to ensure that the current version of the managed project matches the production system project.