Jump to: navigation, search

Composer Compared to IRD

Here is a short video on the advantages of moving to Composer from Interaction Routing Designer as well as an interface comparison.

Composer Compared to IRD

Integrated Development Environment

  • Composer is a single Integrated Development Environment (IDE) for creating applications to routing interactions as well as to orchestrate the entire customer experience. Composer-created voice and routing applications can command and control the customer experience through all channels (IVR, voice, e-services, and so on).
  • Composer's open framework enables widely-available, existing competencies to be used to create reusable components that manage the customer experience. The IDE allows both customers and integrators to utilize existing code sets (HTML, VXML, java, perl, REST and others) to control the customer experience.
  • The open framework also allows simplified integration into all Enterprise applications to harness the information within the Enterprise to drive and personalize the customer experience.

Session-Based Versus Interaction-Based

Composer works with the Orchestration Server platform, which is session-based as compared to the Universal Routing Server (URS) platform, which is "interaction based.' A session can last for the length of the customer journey, across multiple interactions. URS only executes strategies (workflows) that interact on a single interaction. In contrast, ORS does not need to have an interaction to perform useful functionality. All ORS requires is an API call in order to execute. In this manner, the ORS platform can be thought of as a general purpose workflow platform to control the workflow regardless of whether or not you have an interaction (email, SMS, mobile, social, voice, and so on).

Differences from IRD

In the past, Universal Routing's Interaction Routing Designer was the only Genesys tool to create routing applications. Genesys Composer is now the tool of choice for creating both routing and voice self-service applications.

A few of the differences between Composer and Interaction Routing Designer are listed below.

Composer Routing Application Types

You can use Composer's predefined blocks and/or write your own SCXML code to create routing applications that route based on various criteria such as:

The above list is by no means complete. It represents only a few types of routing applications that can be created in Composer. Since Composer uses open languages (SCXML and ECMAScript), you are not limited to its pre-defined blocks, but are free to create many types of routing applications.

Composer Blocks Mapped to IRD Objects

Composer refers to the fundamental element of a workflow as a block whereas in IRD documentation, this element is referred to as an object. A few IRD object/Composer block equivalents are presented below. The tables group IRD objects based on their IRD toolbar category name and point to the corresponding functionality in Composer.  

For a complete list of Composer blocks, including all those without an IRD equivalent, see RoutingBlockPaletteReference.

IRD Data & Services

IRD Object Name Composer Block Name Description
Database Wizard DB Data DB Data retrieves information from the database. Uses a Query Builder.
Web Service Web Service Invokes Web Services. GET, POST and SOAP over HTTPS are supported.
  Web Request Invoke any supported HTTP web request or REST-style web Service. See sample: Routing Based on Web Request.

IRD Miscellaneous

IRD Object Name Composer Block Name Description


Assign Assigns a computed value/expression or a literal value to a variable.   Variables are defined in the Entry block. Capable of multiple assignments.
Call Subroutine Subroutine Creates reusable sub-modules.
Entry Entry Sets global error (exception) handlers. Defines global variables (see Variables section below).. All routing strategy diagrams must start with an Entry block.
Exit Exit Terminates the strategy and returns control back to calling workflow in case of a subroutine.
Error Segmentation Multiple error output ports can be created in Composer blocks based on each block's Exception property.


ECMAScript Builds an ECMAScript expression using the Expression Builder.  Many URS functions are available as Genesys Functional Modules described the Orchestration Server Documentation Wiki Can invoke multiple functions.
If Assign, Branching, ECMAScriptBlock blocks all open Expression Builder Expression Builder can be used to create IF expressions.
Multi-Attach  ECMAScript Can be used for attaching data to an interaction.

IRD Routing

IRD Object Name Composer Block Name Description
Selection Target Routes an interaction to a target, which can be Agent, AgentGroup, ACDQueue, Place, PlaceGroup, RoutePoint, Skill, or Variable. Skill target uses Skill Expression Builder.
Percentage Target Statistics Order property in Target block, lets you perform percentage allocation. Also see sample: Routing Based on Percent Allocation.
Default Default Route Routes the interaction to the default destination.  
Routing Rule   Orchestration Server 8.1 does not support service level routing rules.
Switch to Strategy   Orchestration Server 8.1 does not support switch to strategy routing rules.
Force Route Force Route Not exposed as a routing rule in Composer.
Statistics Target Although statistical routing rules are not yet supported as in IRD's Statistics routing object, users can use the Target object Statistic property to route based on the value of a statistic.  A Statistics Manager and Builder let you create your own statistics from URS predefined statistics.

IRD Segmentation

IRD Object Name Composer Block Name Description
ANI Branching See YourFirstApplication: DNIS Routing for an example.
DNIS Branching See Your First Application: DNIS Routing for an example.
Date Branching See the sample: Routing Based on Date and Time.
Day of Week Branching See the sample: Routing Based on Date and Time.
Time Branching See the sample: Routing Based on Date and Time.
Classification Segmentation Branching For classification segmentation, an ECMAScript function determines if a particular category name or ID exists in the array of category objects represented by an application variable.
Generic Branching Use as a decision point in a workflow. It enables you to specify multiple application routes based on a branching condition.

Also see Context Services Blocks.

IRD Voice Treatment

See Composer Equivalent to IRD Treatment.

IRD Multimedia

See Composer Equivalent to IRD Treatment.

IRD Outbound

See Outbound Common Blocks

Context Services

See Context Services Blocks

Business Process

See Interaction Processing Diagrams Overview and Interaction Process Diagram Blocks.

Reusable Objects

In contrast to IRD, which defines variables in a special dialog box outside of the strategy, Composer defines both workflow and Project variables.  

This page was last edited on November 30, 2018, at 18:46.
Comments or questions about this documentation? Contact us for support!