Revisions

In STEP, historical versions of objects are stored as revisions, providing a historical 'snapshot' of an object. All versions of a revisable object are automatically preserved. Each time a change is made by a different user, a numbered revision is created and logged. Revisions allow users to revert back to a previous version of a revisable object, identify who has made changes to an object (including what changed and when), and support overall auditing functionality within the system.

Revisions are maintained for the following object types: business rules, workflows, integration endpoints, products, entities, classifications, assets, standard standalone event queues, and Web UI configurations. Although each of these object types have their own unique features, the overall functionality of creating and maintaining revisions is universal across objects.

Revisions and Approvals

While revisions and approvals are related, they should not be confused.

Important: It is critical to consider revision handling for each system. Implement appropriate processes to purge old revisions and ensure that the number of revisions does not exceed the expected capacity of the system, which can cause performance issues.

The following topics explain how to work with revisions: