Tidy Instances of Procedures

Each time you edit and save a version of a procedure, a new instance of the procedure version is created. By default, all the instances of a procedure are kept. If you want to limit the amount of old instances that are kept for each procedure (for example, in order to save space in the iProcess database), you need to set the PROC_VER_NUM_INSTANCES attribute.

Note: Even if you have set the PROC_VER_NUM_INSTANCES attribute, the most recent instance of a procedure version is always kept. See the Example .

The first time you set the PROC_VER_NUM_INSTANCES attribute, you can use the swadm tidy_instances command to tidy up the old instances of a procedure so that they match the value you have set for the PROC_VER_NUM_INSTANCES attribute. Otherwise, the instances of a procedure are tidied up as and when a procedure is saved. This is because a tidy operation is performed each time a procedure is saved.

To tidy up the instances of a procedure defined on iProcess Engine, use the following command:

swadm tidy_instances machine_ID proc_ID

where:

• machine_ID is the unique identifier for the server. If you specify a value of 0, the command will apply to all servers in iProcess Engine.
• proc_ID is the unique identifier for the procedure. If you specify a value of 0, the command will apply to all procedures in iProcess Engine.
Draft comments: **APH 30-Apr: The example doesn’t make sense because no entries are highlighted in red - and don’t appear to have ever been so in previous doclibs! :-~ Checked with KJT and he wasn’t sure of the behaviour i.e. whether PROC_VER_NUM_INSTANCES keeps n instances INCLUDING the last one or PLUS the last one. Don’t have time to sort this now so I am commenting this section out and have raised CR 30133 to sort this out and re-instate the example in 10.7.