Genesys Rules System Rules Authoring Tool Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release includes only resolved issues.
This release contains the following resolved issues:
A problem with database parameter types in GRAT, because of which parameter values were not successfully fetched from the database, has been corrected. Previously, this might have required the user to log in several times to see the parameter values. To make the correction effective, database users must have read access to these system tables:
- V$VERSION for Oracle
- SYSIBM.SYSDUMMY1 for DB2.
The following problem related to export and import of a rule has been corrected: when you exported a rule into .xls-format and then imported it back, the rule condition or action value was not selected. This happened only in the cases in which the rule had a selected condition or action value that included consecutive spaces. The problem still remains in the case of Context Service rules, which will be fixed in a future release. (GRS-2799)
A new version of the Split Testing template is provided in this release. Previously, importing of .xml- and .xls-format rules failed in Split Test Configuration. To enable the fix, you need to load the new version of the Split Test template (grs_splittest_template.xml) and re-add the template to any rule that used the former version. (GRS-2801)
A security vulnerability known as session fixation, which results from the session ID not being reset to a new value after a successful login, has been fixed. (GRS-2803)
Conversation Manager template-related classes now integrate correctly with Composer. Previously, there were some instances of mismatches in Fact fields in Composer. To enable the correction, you must re-import the Conversation Manager template and update the rule package to point to the newly imported template. (GRS-2810)
When a Test Scenario is run for Conversation Manager rule packages, any updates to Customer Profile fields that were already specified in expected results are now correctly verified. Previously, this was not the case and, as a result, Test Scenario results did not reflect the updates. (GRS-2813)
After the upgrade to 8.5.300 and Java 8, certain rule packages—such as the ones using the Conversation Manager rule template—could not be deployed. This was caused by the lack of Java 8 support in version 3.5.1 of the Eclipse Compiler for Java (ECJ). ECJ has been upgraded in this release to 4.5.1 (the latest stable version as of the release of 8.5.300.08) which appropriately supports Java 8. (GRS-2814)
No special procedure is required to upgrade to release 8.5.300.08.