Variable approver routing

Home Forum WorkFlow Variable approver routing

This topic contains 5 replies, has 0 voices, and was last updated by  Anonymous 9 years, 6 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #197

    Anonymous

    What is the best approach to do variable approver routing? Scenario is during the approval routing, depend upon where the product will be sold, the approval may only go to 1 regional manager for approval or up to 5. For example, the regions are US, Asia, Europe, and Africa. So the approvers could be US only, or US and Asia, or Asia, Europe and Africa, or US and Africa, etc.

    #4543

    ijobling
    Participant

    within your workflow diagram, where you define the notification actions would probably be the best place for such a scenario, where you can encompass the notification rules within a conditional script (simple or multiple branch actions depending on your specific requirements)

    #4547

    Anonymous

    given the example of 5 regions, wouldn’t the number of possible conditions be enormous?

    #4551

    ijobling
    Participant

    that is entirely possible of course, but all depends on your rule. if the driver is the location where the product is sold and you have 5 location involved, then you would only need to have 5 conditions.. and under each is a notification action that is set to send out the emails appropriate for that selection. One notification action can be set up to send out as many notification as you need

    #4552

    Anonymous

    Sorry for the confusion, the number of approval combination scenarios depend upon what region(s) the product is being sold to. For example, the regions are US, Asia, Europe, and Africa.

    Scenario 1) If the product is being sold only in US, only the US manager needs to approve.

    Scenario 2) If the product is being sold in US and Asia, only the managers from those two regions need to approve.

    Scenario 3) If the product is being sold in US and Africa, only the managers from those two regions need to approve.

    Scenario 4) If the product is being sold in Europe and Africa, only the managers from those two regions need to approve.

    Scenario 5) If the product is being sold in US, Europe and Africa, only the managers from those three regions need to approve.

    Scenario 6) If the product is being sold in US and Africa, only the managers from those two regions need to approve.

    With that said, it could have lots of conditions and I’m looking to see if Perfectforms has a better way to handle this rather than setting up hundred of routing conditions.

    Thanks for you help.

    James

    #4553

    ijobling
    Participant

    James

    still wouldn’t see this as necessarily complex but key probably I’m not seeing is how you are able to identify what regions a specific product is sold in. If each product has a defined ‘sold in’ set of regions, do you have that information stored anywhere? in a database table for instance. if so, then as a product is selected on the form, you could then write back this information to a field on the form with a ‘connect’ action and then use that data in your branch condition. then you only need 6 options in the branch.

    if you are looking though at having to control the routing with the condition based on the product itself, yes, I could see this would be not as easy

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.