Table of Contents

Navigate easier across business logic-based routing cards (8.5)

In both App Studio and Dev Studio, you now have the option to change the order of business logic-based routing cards so that their sequence conforms to your changing business needs. Instead of changing the order by deleting a condition and then creating a new one, you can now conveniently reshuffle the cards. For example, you create a business logic-based routing condition for situations in which the case ID is empty. You then configure business logic-based routing for the case to reach Operator 1, Operator 2, and Operator 3 respectively. If you then need the case to reach Operator 2 first, you can change the order of the conditions by reshuffling the cards, as in the following example: 

Changing the order of the routing cards
"Changing the order of the routing cards"
Changing the order of the routing cards

To help you navigate across multiple business logic-based routing cards, the system automatically collapses the cards when you have more than three cards. If you need to change the routing condition for one specific card, you can expand the routing card by clicking the arrow. For example, if you need to route an assignment to Operator 7 instead of Operator 2, you open the business logic-based routing, click the card that routes the assignment to Operator 2, and change the value to Operator 7, as in the following example:

Collapsing and expanding the cards
"Collapsing and expanding the cards"
Collapsing and expanding the cards

With improved business-logic based routing, you can now better prioritize the importance of individual routing cards, as well as navigate across them in an effortless way.

For more information, see Assigning users automatically at run time.

Did you find this content helpful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.