New in This Release

This section summarizes the new features in the Genesys Orchestration Server (ORS) 8.1.4 release.

New Features in ORS 8.1.4

The following new features were introduced in the initial 8.1.4 release of Orchestration Server:

• An ORS/Interaction Server protocol extension enhances the mechanism of getting the appropriate interactions for processing from Interaction Server. With enhanced pulling, the pull mechanism uses the strategy name and allows different priorities to be set for different types of interactions. This enhanced pull mechanism can result in improvements in performance and reliability.

• ORS supports Submitter objects configured in Composer. Submitters supply parameters that control how Interaction Server submits multimedia interactions to ORS.

• An ORS protocol extension supports the attachment of Virtual Queue data to multimedia interactions. The attached user data can then be used by a Reporting Solution, such as Genesys Info Mart. This feature requires Universal Routing Server 8.1.4.

• Support for activation/deactivation of any specific routing strategy.

• ORS can directly connect to Configuration Server and pull data. For example, when executing the GetListItemValue function, Orchestration Server can pull data without going through Universal Routing Server.

• Orchestration Servers configured as an High Availabilty pair can automatically synchronize voice treatment request data, thereby ensuring a smooth switchover.

• ORS can now terminate a session when the ixn.redirect action is successfully completed, and there is no other associated interaction attached to that session during the configured timeout. This functionality is enabled by the new Application-level option, ixnfm-idle-session-ttl, in the orchestration section.

• When upgrading/migrating the Orchestration Server Application to a newer release, you can perform a migration procedure without significant loss of data or impact to business operations. For more information, see HA ORS 8.1.4 Migration Procedure when Persistence Enabled.

The following new features were introduced after the initial Orchestration Server 8.1.4 release:

• Support for pulling from multiple Interaction Servers.

• Monitoring of ORS performance using a set of performance-related counters and configure conditions that will both trigger and clear Management Layer alarms.

• A new detach attribute for the <ixn:redirect> action, which controls whether ORS should detach an interaction from the current session before routing to the specified target.

• A new option, http-verbose, which can be used to control the volume of HTTP Request logging.

• ORS can request data directly from Stat Server instead of going through Universal Routing Server.

• A new resultof property is added to the interaction.notcontrolled event to provide a reason for a session not being able to control an interaction that it owns.

• A new option, getlistitem-binary-conversion, defines how binary-formatted Transaction List item attributes will be treated by the function _genesys.session.getListItemValue(list, item) when item is returned as an OBJECT of key/value pairs.

• Support for Red Hat Enterprise Linux 6 and Windows Server 2012 native 64-bit.

• Option, mcr-pull-cycle-quota allows you to define how many multimedia interactions ORS will request to be pulled from queues in a given pulling cycle during enhanced pulling.

• ORS adds the capability to specify a reasons property in the hints attribute for the ixn:redirect action.

• Debug Logging Segmentation, which provides more precise control of the logging when the log-trace-segments option is configured.

• Performance improvements in the SCXML documents processing minimize session-creation time.

• Configuration options, max-assembled-cache-age and assembled-cache-reload-threshold, allow users to fine-tune the behavior of the Assembled Document Cache.

• Support for voice call and Open Media interaction User Data properties represented by a key-value pair of Unicode or Binary type.

• Support for URIs of lengths up to 4,094 bytes.

• A new function allows you to retrieve the Orchestration Server version.

• When ORS requests a statistic directly from Stat Server, object names for Routing Point and Queue objects may be specified as DN aliases as well by using the existing Stat Server format.

• ORS can now automatically perform re-registration of unregistered DNs or in scenarios where ORS receives EventError for RequestRegisterAddress.

• Option, http-verbose, can be used to control the volume of HTTP Request logging.

• An architectural change streamlines the way that Orchestration Server obtains statistical data when executing routing strategies.

• Previously ORS allowed the function _genesys.session.setOptions to override only eight options. This restriction is now removed.

• To provide a reason for a session not being able to control a session that it owns, a resultof property is added to the interaction.notcontrolled event.