This page was last edited on January 23, 2017, at 21:33.
Comments or questions about this documentation? Contact us for support!
Note:
|
A List object contains strings of any nature (for example, DNIS or ANI strings), which can be used in strategies. The strings can be as simple as 800 numbers or as complex as routing conditions.
For example, you may use a List object to create lists of toll-free numbers. Rather than reference each individual 800 number in a strategy, you can logically group numbers together and name the group. Then, when you need to add new numbers or edit numbers, you do not need to edit the strategy, but only the List object properties.
Providing key-value pairs for a List element enables you to store information in the Configuration Server Database and then retrieve it from the strategy.
You can specify a List Object variable when specifying targets in the Target selection block.
Composer supplies a List Objects Manager view to create List objects. To bring up the view and create a List object:
Besides individual items, parts of expressions (or an entire expression) can be stored outside of a strategy inside a List object. The sample below is a List object that contains routing information that URS can use to decide when to borrow and lend agents among business lines.
In this sample:
In Expression Builder, two URS functions can be used to access List Objects:
Refer to Universal Routing SCXML API Reference help file for details on these functions (Help > Contents).