New in 8.1.4

{{{{{TMPL8}}} |Release=8.1.4 |Draft=

8.1.400.58—This release contains Elasticsearch Connection enhancements: Explicit mapping of session and performance indexes; a new Orchestration SCXML extension, elasticconnector; and Kibana Visualization samples.

8.1.400.55—The assembled-cache-reload-threshold and max-assembled-cache-age options may be provisioned in the Application section of the Enhanced Routing Script objects, in which case they will override the corresponding options configured in the scxml section of the Orchestration Server Application. ORS introduces the /ors/help method to provide help for ORS REST APIs. ORS includes additional logging for the Enhanced and Legacy pulling methods of multimedia interactions. The ORS log now prints Warning messages regarding certain pulling conditions.

8.1.400.53—This release improves how ORS performs a re-association of an interaction with a remote target session started on different ORS node within a cluster. A new option, complete-assoc-on-target-node, supports this feature.

8.1.400.49— ORS installation includes an Orchestration Plug-in for a real-time view of sessions currently being executed by ORS. Option functions-by-urs is enhanced. A new option, http-curl-ip-family, explicitly defines the IPv4 for connections used by the ORS SCXML engine to retrieve SCXML documents from a web server. ORS option http-ssl-version supports additional values TLSv1_0, TLSv1_1, and TLSv1_2.

Bonnie, insert new content here for the next CD update.

|New=

The following new feature was introduced in the August 2016 CD update of Orchestration Server:

The following new features were introduced in the November 2015 CD update of Orchestration Server:

The ORS platform now includes a “Performance Monitoring” feature. You can configure performance-related counters, which can then be displayed through Genesys RTME clients, such as Pulse.

The Performance Monitoring feature of ORS allows users to define separate log messages for each type of performance counter. A new option, http-verbose, can be used to control the volume of HTTP request logging.

ORS now allow users to selectively hide "sensitive data" in logs when such data is not explicitly requested by an SCXML application.

The following new features were introduced in the June 2015 CD update of Orchestration Server:

You can now monitor 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 controls whether ORS should detach an interaction from the current session before routing to the specified target.

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 an item is returned as an OBJECT of key-value pairs.

A new 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.

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

Several performance improvements in the SCXML documents processing minimize session-creation time.

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

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

Orchestration Server now supports Red Hat Enterprise Linux 6 and Windows Server 2012 native 64-bit.

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.

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.

}}

Contents