New in This Release
This section summarizes the new features in the Genesys Orchestration Server (ORS) 8.1.4 release. The following new features were introduced after the initial Orchestration Server 8.1.4 release. Also see the Document Change History in the Orchestration Server Developer's Guide.
- 8.1.400.62—ORS provides the capability of masking sensitive data in T-Library messages of ORS log output in the following attributes: AttributeCollectedDigits, AttributeLastDigits, AttributeDTMFDigits, and AttributeTreatmentParms.
- 8.1.400.58—ORS enhances its Elasticsearch real-time reporting capabilities with the addition of explicit mapping of session and performance indexes; 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.51—ORS now supports Cassandra 3.9.
- 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.
- 8.1.400.48—The default values for some ORS Application level caching options in the scxml section have changed as noted in the release notes. ORS now supports Cassandra internal authentication. New persistence section options, username and password, support this feature. By default, ORS now attaches interaction properties to ESP requests. This release introduces a new attach_ixn_data attribute for the <session:fetch> Action of the esp method.
- 8.1.400.47—Support for Red Hat Enterprise Linux 7.
- 8.1.400.46—If a DN with an alias is created in the Configuration Layer after ORS is started, and no subsequent configuration updates are made to that DN, then an attempt to use that alias in the _genesys.statistic.sData() function for a statistic that is requested directly from Stat Server no longer causes an error in Stat Server.
- 8.1.400.44—A new cookie option defines the value of the Set-Cookie header in web responses. If empty, the ORS will use its own value in the format ORSSESSIONID=sessionId.nodeId.
- 8.1.400.42—ORS can now delegate session creation to the Reserved Node when the Assigned ORS Node that is responsible for call processing can no longer create a session under certain conditions as described in the release note.
- 8.1.400.40—ORS can now use Elasticsearch to store data, such as ORS session, performance, and node data. In support of the Elasticsearch feature, Debug Logging Segmentation adds a new Debug Log Segment header, ElasticConnector. The existing log-trace-segments option adds ElasticConnector as a new value. A new attribute, _es_store, for the <state> level SCXML Element, can allow ORS to save information about session states into Elasticsearch, which can be used for operational/performance monitoring and analytics. ORS now supports Cassandra 2.2.5.
- 8.1.400.39—New keepalive options, http-keepalive-idle and http-keepalive-intvl, are added. If TCP keepalive is enabled, these options can be used to configure it on TCP sockets used for document fetches. A new interaction.property.changed asynchronous event for multimedia interactions allows ORS to react on an OnCallInfoChangedEx notification. You can now define which ORS cluster will process multimedia interactions in a deployment with Legacy Pulling of multimedia interactions.
- 8.1.400.36—You can now define the ORS cluster that will process interactions. This functionality is introduced for deployments with Voice (DN level option application@<Orchestration cluster name> and Enhanced Pulling of multimedia interactions (cluster-id in Enhanced Routing and Interaction Script options). A new optional Boolean attribute, associated, for the <ixn:createmessage> action is introduced. When set to false, a new interaction is not associated with the session that created it. ORS now supports the extensions property of the hints attribute in the <ixn:redirect> action when applied to a multimedia interaction.
- 8.1.400.34—ORS now successfully attaches a parent interaction to a session started by a consultation call in a Network Consult scenario when the call parties are not monitored by ORS.
- 8.1.400.33—For compatibility with ORS 8.1.3, this release introduces the same-node-for-cons-prim-calls option. Its purpose is to control call distribution compatibility between ORS nodes when a deployment contains nodes from both 8.1.3 and 8.1.4 releases.
- 8.1.400.31—The Debug Logging Segmentation feature, introduced in Release 8.1.300.52, is enhanced. A new Debug Log Segment header ScxmlMetricEvalExpr is added for METRIC:eval_expr. The existing log-trace-segments option adds ScxmlMetricEvalExpr as a new value. A new option, filter-eval-expr, which works with METRIC:eval_expr, enhances the ORS capability of hiding of sensitive data in logs, which was introduced in Release 8.1.400.30.
- 8.1.400.30—ORS can now selectively hide sensitive data in logs when the printing of such sensitive data is not explicitly requested by an SCXML strategy. The Performance Monitoring feature, previously introduced in Release 8.1.400.21, is enhanced. You can now display ORS Performance Data in a RTME client such as Pulse.
- 8.1.400.27—ORS supports pulling interactions from multiple Interaction Servers. The Self-Monitoring feature now allows you to define separate log messages for each type of performance counter. You can now create the Interaction Server Application(s) using only the Interaction Server Application template.
- 8.1.400.26—ORS supports URIs of lengths up to 4,094 bytes.
- 8.1.400.24—A new function, _genesys.session.getServerVersion, allows you to retrieve the Orchestration Server version.
- 8.1.400.21—You can monitor ORS performance using a set of performance counters and the ability to configure conditions that will both trigger and clear Management Layer alarms. A new detach attribute, for the <ixn:redirect> Action Element, described in the Orchestration Developer's Guide, controls whether ORS should detach an interaction from the current session before routing to the specified target.
- 8.1.400.20—A new option http-verbose can be used to control the volume of HTTP Request logging.
- 8.1.400.17—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.
- 8.1.400.15—A new option getlistitem-binary-conversion defines how binary-formatted Transaction List item attributes are treated by the function _genesys.session.getListItemValue(list, item) when an item is returned as an OBJECT of key/value pairs.
- 8.1.400.17—ORS adds support for Red Hat Enterprise Linux 6 and Windows Server 2012 native 64-bit.
When ORS requests a statistic directly from Stat Server, object names for Routing Point and Queue objects may be specified as DN aliases.
ORS can now automatically perform re-registration of unregistered DNs or in scenarios where ORS receives EventError for RequestRegisterAddress.
An architectural change streamlines the way that ORS 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.
Option mcr-pull-cycle-quota defines how many multimedia interactions ORS will request to be pulled from queues in a given pulling cycle during enhanced pulling.
ORS adds support for Windows Server 2012 native 64-bit.
ORS adds the capability to specify a reasons property in the hints attribute for the <ixn:redirect> Action Element.
ORS supports 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.
ORS adds support for voice call and Open Media interaction User Data properties represented by a key-value pair of Unicode or Binary type.
8.1.4 Initial Release
The following new features were introduced in the initial 8.1.4 release of Orchestration Server in November 2014.
- 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.