4 Replies Latest reply on Nov 18, 2015 11:34 PM by Prasad Bhonsule

    How to get Revision to show up in History?  EPDM 2015

    Chris B.
    Chris B. Nov 17, 2015 8:00 PM

      Hi All,

       

      We used to get Revisions showing up as a new line in the history, after a part had gone into the "Released" state.

      Someone changed something, and now it doesn't do it.

       

      Does anyone know how to get this to work?

      Attaching a pic describing it

       

      Thanks

        • Re: How to get Revision to show up in History?  EPDM 2015
          Chris B.
          Chris B. Nov 17, 2015 8:17 PM (in response to Chris B.)

          Here is a clue

          Revision used to reference "Source Revision Number"

          Had to change to just "Revision" to get Revision to show up on the History

           

          Somehow lost the "Source Revision Number"

           

           

          • Re: How to get Revision to show up in History?  EPDM 2015
            Charley Saint
            Charley Saint Nov 18, 2015 12:29 AM (in response to Chris B.)

            Hey Chris,

             

            That should be driven by the Increment Revision action inside the transition to released, if it's missing that would explain it.

              • Re: How to get Revision to show up in History?  EPDM 2015
                Chris B.
                Chris B. Nov 18, 2015 10:49 PM (in response to Charley Saint)

                Thanks Charley.  That was a great clue.

                I think it's the difference between the "Set Variable" action using set Revision variable to the "next revision"

                and

                the "Increment Revision" action

                 

                shown in pics attached

                  • Re: How to get Revision to show up in History?  EPDM 2015
                    Prasad Bhonsule
                    Prasad Bhonsule Nov 18, 2015 11:34 PM (in response to Chris B.)

                    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

                     

                    Kind regards,

                     

                    Prasad