Req Unrelease Options

 3 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
mark.cook
Veteran Member
Posts: 444
Veteran Member

    In our current Process Flow, we have the ability to approve, reject or unrelease Req's. Once a req is unreleased, we want to code for the  process flow to pick up the approval from the person who made the change and continue to completion of the flow. Has anyone done something similar to make the req approval more like a true work flow?

    Shari
    Veteran Member
    Posts: 78
    Veteran Member
      Yes, we have. For us, we have 2 points where they can unrelease. The first point, they can unrelease to make changes to the req. We then require it to go through the approval process again entirely as we don't know the changes. The other point that it can be unreleased is the very last approver (we have a finance reviewer), who can unrelease, code, and then re-release. At that point in the flow, after it's unreleased, we set a flag somewhere on the req itself - in a user field. Once the flow is re-released, the first thing our flow does it to look for that flag. If it sees the flag, it goes straight through to the approve AGS call and ends the flow. If it doesn't see the flag, then it goes through the approval process as normal.

      -Shari
      Gary Davies
      Veteran Member
      Posts: 248
      Veteran Member
        Another option if you do not want to deal with user fields would be to query the LOGAN tables, first finding the workunit for the Req using WFVARIABLE (where workunit status is Completed), then if that exists query the WFMETRIC to find who took last action. Of course this solution is dependant on when and if you purge workunits on a regular basis.
        mark.cook
        Veteran Member
        Posts: 444
        Veteran Member
          Perfect, looks like we have a couple of options. Thank you for your replies.