4. Best Practices: CIMPLICITY Version Changes

1 CIMPLICITY version upgrade.
2 CIMPLICITY version downgrade.

CIMPLICITY Version Upgrade

  1. Follow the Change Management project management recommended procedure to ensure the managed project is up to date.
  2. Apply the CIMPLICITY upgrade.
  3. 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

  1. Follow the Change Management project management recommended procedure to ensure the managed project is up to date on the Change Management server.
  2. Right-click Project in the Workbench.
  3. Select Manage>Show History on the Popup menu.
  4. Select the current project and the labeled project that corresponds to the previous version of CIMPLICITY.
  5. Identify the configuration changes.
  6. Stop the project.
  7. Right-click Project in the Workbench.
  8. Click Manage>Show History on the Popup menu.
  9. Select the labeled version of the project that was running successfully.
  10. Click Get to get that version.
  11. Delete any files that were added from the local project.
  12. 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).

  1. Apply any desired/application configuration changes from the new project
  2. Use project management best practices to ensure that the current version of the managed project matches the production system project.