Ticket Not Routing to required SubFlow
I am trying to make a ticket route correctly from a reject process and route back to the relevant flow to allow changes to be made.
I am using a utility shape and the SetTicket Rule, the Ticket has been created and added to the sub flow that it needs to go on and the naming in consistent to the utility shape, ticket name and flow.
In tracing, it is setting the ticket, and name, but not routing to where it should, it just carry's on back to the previous flow, and undertakes the next task (which is a resolved-completed).
The really confusing aspect is that in the initial reject flow there is another utility, with a SetTicket, that goes to a different sub flow, and this works OK.
The only difference is that this sub flow, where the ticket shape is, is on the flow when the previous one completes, whereas the one that is not working, it 2 further sub flows down. I tried attaching a ticket shape to each of the flows to get to the assignment that I want to, but this did not help.
If anyone could let me know what I am missing I would be grateful
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Keep up to date on this post and subscribe to comments
- Routing to subflows based on pre-defined condition
- The significance of Required checkbox when skills are added in the assignment shape property for skilled based routing
- Assignment Routing- more than one user available with the required skill level
- Sending Assignment from one SubFlow to another Sub
- calling subflow