I had good behavior until just recently. I was operating on Manual versioning because of the inability to properly view prior revisions and generations with default behavior of only seeing the most recent revision. (We have prior revisions that are still active, despite being superseded.)
In this scenario, I was able to manually create revisions properly. I modified the PE_CreateNewRevision function to check my current life cycle state to determine if a revision can be created. No problems... working fine.
Then, yesterday I added the major rev to the Keyed name order for displaying in tabs and also set the sort order on that column (guessing this is non issue). I then switched my version control back to automatic so I could play with some custom queries and the generation feature. I now cannot get the major rev to increment using the same modified CreateNewRevision function. Throwing no errors.
I'm not even sure where to start here given that this.apply("version") called in the method and appears to be getting called directly.
Hi,
You are currently hard-coding the Lifecycle states into the Method to check if they are released, you will have to modify the code to match the new state names of the released states.
string[] ReleasedStates ={“In Design”,”Prototype”,”Active”, “Inactive”, “Obsolete”, “Discontinued”};
The second option would require more work, but you may be able to look at the Item property "status" and retrieve the released property that way.
Hi,
You are currently hard-coding the Lifecycle states into the Method to check if they are released, you will have to modify the code to match the new state names of the released states.
string[] ReleasedStates ={“In Design”,”Prototype”,”Active”, “Inactive”, “Obsolete”, “Discontinued”};
The second option would require more work, but you may be able to look at the Item property "status" and retrieve the released property that way.