Skip to Content

How to stop workflow item sliding down if multiple substitution is activated

Hi,

I have issue where several userd in one line organization is activating workflow substitution. User A is substituted by user B, User B is substituted by user C.

When a workflow item is generated for user A, it will goes to user C as well. It's unwanted situation. Can we setup so that in this case only user B will receive the item but user C will not receive the item?

Thanks

Hadi

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Sep 19, 2018 at 06:15 AM

    Unless something changed or broke, this is not how substitution used to work. I tested this and it was discussed a few times in the past, there is no inheritance.

    Can you verify that B is not an agent for A. If not, try to replicate the scenario with a simple example of a one-step workflow: Send a task to a specified, hardcoded agent. If the substitution is still inherited, I would suggest raising this with SAP. And please post back, because this is an important behavior.

    Add comment
    10|10000 characters needed characters exceeded

    • This would be a serious change so I tested it. Substitution is definitely NOT inherited. Not in 4.x when I first checked and still not in 7.5

      How did you verify? Here's my 2 minute test:

      1. Under my ID, set up an active substitution to USER1.
      2. Log on as USER1 and set up an active substitution to USER2.
      3. In my ID, run the verification workflow from SWU3.

      I can see the work item in my inbox, USER1 can see it too, but not USER2.
      Even if USER2 tries to explicitly adopt substitution, I can't see anything.

      Substitution is not inherited, there is something in your setup.

  • Sep 19, 2018 at 09:11 AM

    Hi,

    that is how substitution works.

    But you can model workflows to handle escalation, e.g. if workitem is not picked up in 1 working day it will go to agent B, if they don't pick it up it will go to agent C.

    Kind regards, Rob Dielemans

    Add comment
    10|10000 characters needed characters exceeded