Automate

 View Only
  • 1.  Limiting later swim lanes and approvals to exclude requester

    Posted 05-24-2023 12:50

    Hello,

    We are looking into if it is possible to have a swim lane that uses the same general pool of originators or a pool of other approvers where overlap may happen as the next step in the approval process but want to exclude the original originator.  Is there way to do this?  Currently using Evolve 20.1.



    ------------------------------
    Scott Fouss
    Leprino Foods
    ------------------------------


  • 2.  RE: Limiting later swim lanes and approvals to exclude requester

    Posted 05-25-2023 08:52

    Hello Scott,

    in the Properties of the Swimlane, under the Advanced section (this is the last section), there is a property to Include Self: True/False. If you set it to False, than the Originator should be excluded from the list of people receiving the approval assignment. In the below printscreen I used TeamFromRole type swimlane, where the resolver group comes from y Data Connection pointing to the Originator user group.

    I hope this helps, let me know the result.

    Best regards,
    Zoltán Dobszai
    Novacon



    ------------------------------
    Zoltan Dobszai
    Novacon Zrt.
    Törökbálint
    ------------------------------



  • 3.  RE: Limiting later swim lanes and approvals to exclude requester

    Posted 05-26-2023 11:34

    Hi Zoltán,

    This worked perfectly.  I was looking into the wrong spot in the individual node but the swimlane level does exactly what we need.

    Thank you. 



    ------------------------------
    Scott Fouss
    Leprino Foods
    ------------------------------