This page was last edited on July 2, 2013, at 13:34.
Comments or questions about this documentation? Contact us for support!
Instructs URS to route the interaction to the default destination, as specified by the default DNs at the Routing Point or by the URS configuration option default_destination. When you use the Default Route block in a strategy, it sends the interaction to that destination. Once set this will be applicable for the entire duration of the strategy unless overridden by a Set Default Route block in the workflow execution.
The Default Route block has the following properties:
Find this property's details under Property Common Properties.
Find this property's details under Common Properties.
Find this property's details under Property Common Properties.
This property is for future use by Orchestration Server. Its use will be described in various action elements referenced in the Orchestration Server wiki.
Set to a meaningful value or keep the default value, which is the system variable InteractionId.
Can be used for interaction-less processing for scenarios where the InteractionId variable is not automatically initialized, but instead must wait for an event. An example would be an SCXML application triggered by a Web Service that does not add an interaction.
Background: Previous to 8.1.1, Composer did not expose an Interaction ID property. Instead, when ORS started processing an interaction, a generated SCXML application automatically initialized the system variable, InteractionId. This variable was then used internally by Routing and certain eServices blocks when interacting with ORS.
With the introduction of support for Interaction-less processing, you can now define a specific event (IPD Diagram Wait_For_Event_Property) to initialize InteractionId, or not define an event at all.
For scenarios with an interaction (IPD Diagram/Wait For Event=interaction.present for example), you may keep the default value for the Interaction ID property. The default value is the system variable InteractionId, which is initialized automatically in this case.
For other scenarios (any scenario where the system variable InteractionId is not set), you may choose to:
Use for multi-site routing. Controls whether the Orchestration Platform should <detach> an interaction from the current session before routing to the specified targets. When this property is set to true, the interaction is detached from the current session.
Use to specify how long to attempt to <detach> if an initial attempt fails with an invalidstate error. Specify the timeout in milliseconds. If set to 0, no further attempt to detach is made. After the timeout, if the <detach> is not successful, no further attempts will be made and the block will attempt to reclaim the interaction back into the current session using <attach>.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
Find this property's details under Common Properties.
This property accepts true/false values. When set to true and Detach is also true: