See this link.
1. If you import the old data into EPDM,It is suggested to use epdm's Revision management system.
2 .To increment rev of old file use the above method and other related posts.
3. If you force the revision using a dispatch or manually adding it,EPDM's Rev managment system w ont recognise it i.e ,even if you put the revision to C, if file goes through EPDMs workflow where revision is incremented at state change it will come back to A as C rev was not registered.
4. by the obove method, u can get the revision in history as well.
We did import everything into EPDM with the revision managemnt system. I'm just trying to eliminate the need to have 30,40 transitions in the workflow, that is why i setup the dispatch to prompt for a rev.
I guess i'll setup a workflow to do this.
Thanks for the info.
With dispatch you can write the a value to revision variable. But not actually increment it.
When the file goes through the transition the dispatch may write the value as A and actually doesn't increment it to B for the next time usage.
Hence you need to have the ladder workflow with automatic conditions and increments to the next revision automatically.
Hope this helps !