Chapter 3: Interaction Routing Designer Functions Force Functions
UTCToString
Parameters:
UTC representing coordinated universal time:
INTEGER.
For
information on UTC, see the note on
.
Return value type:
STRING
This function takes coordinated universal time (UTC) in seconds and converts it into a string with the format
YYYY-MM-DDTHH:MM:SSZ
.
Use this function when setting the scheduled time for submitting interactions in queues to routing strategies in IRD’s
Interaction Design window as described in the Universal Routing 7.6 Business Process User’s Guide.
Specifically, see the section on View object configuration,
Scheduling tab, in the chapter on creating business process objects.
Use this function with the Assign object (see
) or directly as a value of some other function parameter. Example:
Attach['ScheduledAt', UTCToString[…]]
The View object Scheduling tab description in the Universal Routing 7.6
Business Process User’s Guide contains a sample strategy that uses this function.
Note:
If UTC input is less than zero, then 0 (zero) will be used.
Force Functions
shows the
Function Properties
dialog box with
Force
selected.
Reference Manual
Figure 193: Function Properties Dialog Box, Force Functions
419
Chapter 3: Interaction Routing Designer Functions Force Functions
This section presents functions in the Force category (see Table 99 on
).
Force
Parameters: none
Return value type:
VOID
This function instructs URS to perform forced interaction routing, under which calls are routed regardless of the target’s current state. Targets for forced routing must have a format of
DN@Switchname
or merely
DN.
(The latter format will route the interaction to the corresponding DN on the current switch.) The target is ignored if assigned a type.
The target to which the interaction will be forcibly routed is one of the targets listed in the properties of the first Routing object following the Force object.
After the Force object, it is advisable to place only a single Routing object.
The effect of the Force object cannot be annulled after the function is called. If, under some conditions, ordinary routing still needs to be performed after Force is invoked, use a combination of the functions SelectDN, SuspendForDN, and
RouteCall, described on pages
,
, and
, respectively.
Note:
Force was retained in URS for the sake of compatibility with earlier versions. When building new strategies, use the forced-routing function TRoute, described on
, since the explicit specification of the parameters of TRoute makes its operation more transparent and decreases the risk of errors.
TRoute
Parameters:
Destination
:
STRING
or variable (representing a string for the destination)
Location
:
STRING
or variable (representing a string for the destination)
Route Type: RouteTypeUnknown, RouteTypeDefault,
RouteTypeLabel, RouteTypeOverwriteDNIS, RouteTypeDDD,
RouteTypeIDDD, RouteTypeDirect, RouteTypeReject,
RouteTypeAnnouncement, RouteTypePostFeature,
RouteTypeDirectAgent, RouteTypePriority,
RouteTypeDirectPriority
, or variable
DNIS
:
STRING
or variable (representing a string for the destination)
Return value type:
VOID
420 Universal Routing 7.6
