Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Avesh Ganodwala
    Requistion Approval Flow
    Topic posted May 24, 2019 by Avesh GanodwalaSilver Medal: 2,000+ Points, tagged Approvals/Notification, Create Requisition, Requisition Processing, Setup 
    64 Views, 3 Comments
    Title:
    Requistion Approval Flow
    Summary:
    How to configure requisition approval flow
    Content:

    We are planning to setup Approval's for Requisition Creation process as below.

    Groups Created:

    GR1: User1, User2

    GR2: User3, User4

    GR3: User5, User6

     

    The way approval should flow is ,1st it should go to all the members of GR1 (User1 and User2).

    Once one of the members of the group approves it , it should go to all the members of next group GR2 (User3, User4).

    Once one of the members of the group approves it, it should go to all the members of the next group GR3 (User5, user6)

    Once it is approved by any member of the GR3, the supplier should get approved.

    If I am using parallel approval with first responder wins, it is going to all the approvals at once.

    If I am using Serial approval, it is going to every person of the serially E.g (User1 first and then to User2)

    COuld you please help how to acheive this requirement.

    Version:
    19A

    Comment

     

    • Sumana Sarkar

      As i understand, the requirement is to have parallel approval between two groups. That is, when any one member from Group 1 approves, the approval flow should move to the next stage (in your case assigned to Group 2). Then when any one member from Group 2 approves, the approval flow should move to the next stage (in your case assigned to Group 3), and so on.

      Please note that using approval groups and consensus/first responder type of participant you won't be able achieve the desired behavior.

      One way to achieve the requirement is to use Application Role based routing in a header consensus type of participant.
      When task is assigned to an application role, all members holding the role will be able to see the task, but only one member from the role needs to approve. Because of consensus participant, both roles will need to approve.

      Please note that rules based on application role can be created from BPM Worklist app only. So if you are currently using FSM Rules UI, before using BPM Worklista app, you would need to click the button "Edit Rules in BPM" on the manage requisition approvals UI and clean up FSM Rules db.

    • Jim Van Tongerloo

      Hi,

      Please use the Parallel node with First responder wins, one in every stage.

      Meaning:

      Preapproval stage: first responder wins (GROUP1)
      Header stage: first responder wins (GROUP2)
      Postapproval stage: first reponder wins (GROUP3)

      Doing this within 1 and the same stage, everyone will be involved indeed.

      Note that this heavily depends on the number of stages available and the number of times you want to use a first responder wins parallel type.

      Jim

       

    • Ashok

      This post appears related to Self Service Procurement. Moving it here so customers can take a look and share in the solution proposed.