This content has been marked as final. Show 5 replies
I'm not sure I understand the issue properly. If you select the "Initialize task with route name" option under Routes and Priority, then you should see the name of the route that goes to the end of the gateway in the workspace interface.
If that really doesn't work, then you can add an intermediate "Decision Point" service and have a route go from the User service to that Decision Point. Then have the Decision Point go to the end of the gateway.
Let me know if I misunderstood the issue.
Hi again Jasmin,
You understand the issue correctly. I used a "Set Value" activity instead of an "Decision Point" and then it worked perfectly. However I don't understand why the User Assignment cannot "see" the end branch/join gateway. In short, I don't think it should be necessary with an extra activity, is this a known bug or just a glitch?
Thanks for the help by the way
That looks like a bug to me. It's minor, but still a bug.
I have similar problem. My process has a decision point in the gateway. There are two options on decision point. When i set the conditions on these routes workbench creates another route to the end of gateway automatically?
What can i do?
Thanks in advance
Workbench automatically creates routes to the end of the gateway according to the logic in the conditions. This happens so that a route that exits the gateway is guaranteed. The following topic explains the logic behind it (hope it helps):
Do you want an operation inside the gateway to be a final operation in the process?