Run Definition Versioning

For an Authorizer:

When you create a new run, its version will be 0. When you edit an existing run and try to save, you are prompted whether to save it as a new version or not. If you click Yes, a new Run is created with version as 0 and the Run having version as 0 will be saved with version as maximum version +1. If you click No, the existing run is overwritten and the version will be as it is.

For a Non-Authorizer:

When you create a new run, its version will be -1. After the Run is approved by an Authorizer, the version becomes 0. When you edit an existing Run and try to save, you are prompted whether to save it as a new version or not. If you click Yes, a new Run is created with version as -1. Once the Run is approved, its version becomes 0 and the Run having version as 0 will be saved with version as maximum version +1. If you click No, the existing Run is overwritten, and the Active flag of the Run becomes N (which you can view from the Summary window). The version remains the same. After the Run gets approved, its Active flag changes to Y.

Note:

• The run with version 0 is the latest one and it can have many versions say 1 to n, where 1 is the oldest Run and n is the next to latest.
• A run with version -1 will always be in an Inactive state.

You can view all the versions of a particular rule by providing the run’s name or code and clicking Search in the Search and Filter grid. (Ensure the Version field is cleared since it is auto populated with 0).