That should be driven by the Increment Revision action inside the transition to released, if it's missing that would explain it.
Hi Chris the "set variable" actions and "increment revision" actions are two quite different things.
During a workflow transition both are needed to correctly update the revision for a file.
The "set variable" action set the Revision variable on a file's data card to the next value.
The "increment revision" action increment a internal revision counter within the EPDM database.
So as an example, a file with no revision is checked in to the vault.
Once it goes through a workflow transition where these two actions are defined, two things happen:
1. The set variable action updates the field on the data card linked to the Revision variable (usually called Revision) E.g A
2. The Increment revision action increments the Revision counter inside the EPDM database.
This is done to ensure that the EPDM database and the file's revision property are always kept in Sync.
You might ask why a increment revision action is provided in the first place. This is to help deal with legacy data. As legacy data is moved into the vault, Administrators can use the increment revision action a number of times to get the database in sync with the file's revision property. For example, if a file comes into the vault at Revision C, an admin might increment the revision on it 3 times to bring the database in sync.
I hope this makes sense