| Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 8.1.400.19 [08/30/16] – Hot Fix | X | X | X | X | ||
| 8.1.400.18 [05/25/16] – Hot Fix | X | X | X | X | ||
| 8.1.400.17 [09/09/15] – Hot Fix | X | X | X | X | ||
| 8.1.400.16 [03/31/15] – Hot Fix | X | X | X | X | ||
| 8.1.400.15 [11/26/14] – Hot Fix | X | X | X | X | ||
| 8.1.400.14 [07/02/14] – Hot Fix | X | X | X | X | ||
| 8.1.400.13 [06/05/14] – Hot Fix | X | X | X | X | ||
| 8.1.400.11 [03/04/14] – Hot Fix | X | |||||
| 8.1.400.10 [01/23/14] – General | X | X | X | X | ||
| 8.1.400.07 [12/05/13] – General | X | X | X | X | ||
| 8.1.301.07 [10/15/13] – Hot Fix | X | X | X | X | ||
| 8.1.301.06 [10/07/13] – Hot Fix | X | X | X | X | ||
| 8.1.301.01 [09/06/13] – General | X | X | X | X | ||
| 8.1.200.20 [08/05/13] – Hot Fix | X | X | X | X | ||
| 8.1.200.18 [07/11/13] – Hot Fix | X | X | X | X | ||
| 8.1.300.15 [07/03/13] – General | X | X | X | X | ||
| 8.1.200.17 [01/22/13] – General | X | X | X | X | ||
| 8.1.100.27 [12/14/12] – General | X | X | X | X | ||
| 8.1.100.26 [12/07/12] – Hot Fix | X | X | X | X | ||
| 8.1.200.15 [11/19/12] – General | X | X | X | X | ||
| 8.1.100.14 [05/17/12] – General | X | X | X | X | ||
| 8.1.000.42 [09/27/11] – General | X | X | X | X |
This release note applies to all 8.1 releases of the Genesys Rules Authoring Tool.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release for this product. This release contains no new features or functionality.
This release contains the following correction/modification:
A problem with scrollbars being unavailable in the Chrome browser has been corrected in this release. (GRS-2923)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release for this product. This release contains no new features or functionality.
This release contains the following correction/modification:
A problem with use of the hashtag (#) character in rules syntax has been corrected. Previously this was causing the creation of snapshots to fail to complete, and the deployment of snapshots to remain in pending state. The problem was caused by a bug in DROOLS. (GRS-2885)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release for this product. This release contains no new features or functionality.
This release contains the following correction/modification:
In later versions of Tomcat, the user may see a “syntax error” on the screen when trying to log into GRAT. This issue has been corrected. (GRS-2534)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release for this product. This release contains no new features or functionality.
This release contains the following correction/modification:
A potential cross-site scripting (XSS) security issue with login.jsp has been fixed. The fix involved removing support for
auto-login from iWD to GRAT. iWD customers must disable this support in the iWD Manager, because it will no longer work
after this fix is applied. To turn auto-login off:
The Rules Authoring option that allows single sign-on (SSO) to GRAT will no longer display. (GRS-2627)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release for this product. This release contains no new features or functionality.
This release contains the following correction/modification:
Previously, when users were working with database parameters, if the database connection recovered from a temporary outage, users could not see any parameters in the drop-down list until the GRAT server was restarted and the user logged into GRAT again. With this modification, GRAT attempts to reconnect to the database if the connection has dropped, and a hard restart of GRAT is no longer required. However, users must log into their GRAT client again to re-initialize the database parameter values.(GRS-2490)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release for this product. This release contains no new features or functionality.
This release contains the following correction/modification:
A problem with scheduled deployment times becoming corrupted has been corrected in this release. Previously, if users first selected a decision table before deploying, the default time was shifted to the GMT timezone. (GRS-2309)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release for this product. This release contains no new features or functionality.
This release contains the following corrections and modifications:
GRAT has been modified to validate LATEST packages before deployment (in the same way as snapshots are validated), and prevent deployment if errors are found. Any such validation errors are now displayed to the user for correction. Previously, such validation errors were pushed to Configuration Server, causing it to fail in cases where the error data was very large. In addition, if for any reason GRE fails to validate a package, there is now a 4K limit on the size of any error text sent to Configuration Server. (GRS-2279)
Deployments were failing in environments where GRAT was front-ended by a firewall or load balancer whose external port was different from the GRAT application server's. This issue has been corrected. (GRS-2278)
GRAT has been changed to warn the user and to prevent deployment if the Configuration Server connection is down at the time of deployment. During deployment, GRAT checks to ensure that all rules in the rule package are associated with a valid node of the business hierarchy. For example, the “Sales Department” node might have been deleted when there are several rules associated with that node. In this case, GRAT warns the user during deployment and moves these “orphaned rules” to the package level. Previously, if the Configuration Server connection was down during deployment, the cross-check against the business hierarchy did not occur and all rules were considered orphaned. (GRS-2260)
A problem with importing templates and rule packages on certain UNIX platforms has been corrected. (GRS-2205)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release for this product. This release contains no new features or functionality.
This release contains the following corrections and modifications:
An unnecessary and corrupt .jar file (webhelp.jar) has been removed from the online help archive provided with software distribution. This
file could not be expanded for virus scanning and this was preventing proper installation. (GRS-2191)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains no new features or functionality.
This release contains the following corrections and modifications:
GRAT now writes only the root cause to the log file. Previously, both the root cause and the repository connection details were logged. (GRS-2156)
clear-repository-cache has value true. Previously,
empty directory files were not correctly cleaned up, resulting in GRAT failing to start in this scenario. (GRS-2153)
Users can now refresh the Deployment History tab display by clicking the Deploy Rules node in the navigation tree in the
left-hand navigation pane of GRAT. (GRS-2149)
A new Force Deployment checkbox has been added to the Deploy Now and Schedule Deployment dialogs to enable users to force a
deployment that bypasses duplicate deployment checks. (GRS-2148)
The Check My Permissions feature now displays only the templates a user has access to. Previously, some templates continued to display after access rights had been removed. (GRS-2140, GRS-2088)
Some minor formatting issues in localized versions of GRAT have been corrected. (GRS-2150, GRS-2152)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new features and functionality:
Check My Permissions window—Users can now check the state of their permissions (templates, tenants and role permissions)
by clicking a screen button. See the GRAT online Help for more details.This release contains the following corrections and modifications:
The correct application version is now displayed in GRAT during installation. Previously, the version was shown as 8.1.000.00 in some installation scenarios. (GRS-2109)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains no new features or functionality.
This release contains the following corrections and modifications:
Composer's Rule Block is now able to display correctly the rule package's Fact model. (GRS-2090)
In grouped linear rules, the colors were not properly displaying the nesting levels. This has now been corrected. (GRS-2100)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains no new features or functionality.
This release contains the following corrections and modifications:
Problems with unexpected database growth when running multiple test scenarios have now been been resolved. (GRS-2106)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains no new features or functionality.
This release contains the following corrections and modifications:
Previously, when rule templates were imported as an XML file, an additional template "version" was also created in error. This no longer happens. (GRS-2023)
A problem with excessive log messaging between GRAT and Message Server has been corrected.
The log4j.properties has been modified to log only warning and error messages from the
DefaultExpander and from JackRabbit. Also, the logging in BRTemplateInterface
of asset locking and loading have been changed from standard to debug. (GRS-2022)
A problem with the export of rule packages causing exceptions when the user did not have TESTSCENARIO_VIEW
permissions enabled has been corrected. Users can now successfully export a rule package even without this permission. Genesys recommends that users who need to export and import entire rule packages should have full permissions
granted. For example, if users do not have the ability to view business calendars or test scenarios, these will not
be exported in the rule package XML. Likewise, if a user does not have permission to create calendars or test
scenarios on import, they will not be able to create these resources from the imported rule package. (GRS-2027)
GRAT now correctly removes all related snapshots when deleting a rules package. Previously, if a rules package containing a snapshot was deleted, then a new one re-created with the same name, the snapshot would appear in its menu. (GRS-2038)
When a snapshot is created, package DRL is now stored within the snapshot, which speeds up deployments to single or clustered GREs. (GRS-2041, GRS-2075)
A problem with the performance of rule package imports in release 8.1.300.15 has been corrected. This was caused by the generation of superfluous audit comments for individual package components. (GRA-2060)
An occasional problem with scheduled deployments failing has been corrected. This was caused by repository access errors when the package was being used by more than one thread. (GRS-2042)
GRAT performance when using very large rule packages has been improved. Save, import and deploy operations are now substantially faster and unexpected database growth issues are now resolved. (GRS-2067, GRS-2068, GRS-2074)
A problem with saving rules when using operational parameters has been corrected. The change was required as a result of upgrading from DROOLS 5.1 to 5.5. (GRS-2073)
The export of rules that contain empty values to Excel spreadsheets now correctly leaves blank values where the empty values occur. Previously, a space was entered in error instead. (GRS-1437)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This release contains no new features or functionality.
This release contains the following corrections and modifications:
A problem that caused Unable to find business structure errors to occur during rule package
deployments has been corrected. This was caused by excessive configuration event processing in GRAT, and by an
unnecessary double-fetch of the DRL file by GRE during deployment requests. (GRS-2034)
ADDP support can now be activated for the application's connection to Configuration Server. To activate it, edit
the bootstrapconfig.xml file found in the WEB-INF\classes directory and un-comment
the line that references ADDP. This line is as follows:
‹!-- ‹addp clienttimeout="30" servertimeout="30" /› --›
(GRS-2007, GRS-2026)
The option protocoltimeout can now be added to the cfgserver section of
bootstrapconfig.xml. This file is found in the WEB-INF\classes directory. This value
is the timeout used for Configuration Server requests (in seconds). It is used for requests on both the
application connection and the user connection to Configuration Server. The default timeout is 30 seconds.
Example:
‹protocoltimeout›30‹/protocoltimeout›
(GRS-2043)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This release contains no new features or functionality.
This release contains the following corrections and modifications:
A problem with deploying rule packages to a cluster has been corrected. Previously, in deploying to certain clusters when the GRAT verify-deploy-address option
was set to true, a rule compilation error was generated. This is now fixed. (ER# 319670079)
Test Scenarios now correctly process spaces contained in Given parameter values configured as List objects. (ER# 325251653)
A problem after upgrading to FireFox Version 21.0 in which users experienced an error pop-up box after logging into the Genesys Rules Authoring Tool has been resolved. (ER# 325354047, GRS-2003)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new features and functionality:
Enhanced template selection features on the General Package screen. Users can now:
Improvements to the display of Test Scenario results in order to show how expected results match actual results. A green or red indicator will appear next to each results column to show whether or not it matched the expected results.
A new Package Snapshot Deployment feature, which allows rules authors to save snapshots at key phases of the authoring process. A snapshot freezes the contents of a rule package at a point in time, including templates, rules and calendars. It also allows authors to revert to earlier snapshot versions if needed in the authoring or deployment process.
Up to release 8.1.2, only the latest package could be deployed, and although no rules might have changed between any two deployments of the package, other non-rule-related changes could have been made to the package that could affect the behavior of the rule package. For example, between deployments, someone could have changed a business calendar definition or upgraded the version of a template that was being used, both of which could affect package behavior. Users with the appropriate permissions can now do the following:
pending deployment status on a rule to pending snapshot
A new Package History feature, which allows users to do the following:
Support for DROOLS 5.5
Support for Java 7 Runtime
Support for IBM Websphere Application Server 8.5
Support for JBOSS Application Server 7.1.1
This release contains the following corrections and modifications:
A problem with invalid date formats during deployment in non-English locales has been corrected. (ER# 321808963)
Security improvements have been made to GRAT to prevent the possibility of cross-site scripting attacks. All servlet application parameters are now cleaned of any possible malicious HTML tags and scripts. (ER# 318547501)
To improve security, GRAT now uses a POST request between the login.jsp and the login servlet application. Previously,
a GET request was used. (ER# 317067686)
Problems with assigning role privileges in GRAT have been corrected. Previously, since 8.1.1, a workaround required the
renaming of the Annex tab section from CfgBusinessRulesApplication to
CfgBusinessRulesApplication. This workaround is no longer required. (ER# 318462695)
GRAT now deploys correctly into Websphere 7.0 without the need for a workaround. See Known Issues and Recommendations. (ER# 317449931)
GRAT now reconnects correctly to LCA after LCA is restarted. Previously, this reconnection failed, resulting in the application status not being updated in SCI. (ER# 323985242)
GRAT now correctly connects to the backup Message Server, and then correctly reconnects to the primary Message Server, in scenarios where the primary connection fails and is restored. (ER# 323051261)
A problem with Tomcat's shutdown processing when a user is still logged in has been corrected. All users are now logged out during shutdown processing. (ER# 318450275)
A problem with a failed rule deployment resulting in a Websphere thread hang has been corrected. A timeout has been
added for the deployment POST request. If no response is received in the specified time, the POST
will fail with a timeout. The default timeout value is set to 5 minutes. Configuration option
deploy-response-timeout can be set if a different timeout limit is required. (ER# 318532571)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new features and functionality:
There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new features and functionality:
There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
Decision tables can now contain a maximum of 30 columns, and attempts to create more than this will now generate a new pop-up box. Previously, the maximum limit was 18 columns, and attempts to create more than this generated an error. (ER# 313569454)
Decision tables containing multiple condition and action columns can now be successfully re-imported from a spreadsheet format (.xls) after being exported. Previously, the generated package source was incorrect for the re-imported rule. (ER# 313675913)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of the Genesys Rules Authoring Tool.
Support for the creation and execution of automated test scenarios before deploying new or edited rules. Test scenario results can be viewed in summary and in detail. Test scenarios can also be imported and exported from spreadsheets in a similar way to rules packages.
Support for either iWD, or user-defined complex event processing (CEP), or Stateless (default) template types and package types.
The CEP template type enables rule authors to create rules and packages that use event fact types. Note that the CEP
template type requires the presence of Genesys Web Engagement. Note also that the reserved template type iCFD has been
removed in this release.
Support for deploying rules packages to application clusters. A Configuration Server or Genesys Administrator
application of type Application Cluster can be used to define a group of Genesys Rules Engine (GRE)
or Genesys Web Engagement engines to which packages can be deployed. When deployed to a cluster, the package
is deployed to every engine in the cluster.
Support for forced password change during user login, and password reset upon user request, where the application supports it.
Support for mapping multiple instances of a rule parameter to a single parameter definition. The underscore (_) character in parameter names can now be used to specify an index of the parameter where the rule expression requires additional instances of the parameter.
Support for duplicate template names across tenants.
Support for single-click grid editing.
Support for resizing of columns in linear rule grids. Any changes made by users are stored as preferences for that user and retained across logins.
New Genesys branding is applied throughout the user interface and installers.
Support for IPv6.
This release includes the following corrections and modifications:
Login to GRAT when the connection to the primary Configuration Server has been lost and switchover to the backup has occurred now functions correctly. Previously, GRAT tried in error to establish a connection with the primary Configuration Server when a user logged in, and the login failed. (ER# 308327976)
A problem that caused GRAT to incorrectly build the XML that is returned to the browser when an operational parameter was used in an action has been resolved. (ER# 303413221 )
The mapping.xml file has been enhanced to allow a tenant mapping to be specified.
iWD tenant names can now be mapped to CME tenant names via this file.
Note: The mapping.xml file is used
only for migration from iWD 7.6. For migration from iWD 8.0 the CME tenant ID as
specified in the iWD database determines the CME tenant. (ER# 300118922)
Shutdown processing has been improved to ensure the correct shutdown of a standalone Tomcat application
via the shutdown.bat script. (ER# 300695905)
Additional logic has been added to map a solution name to a valid Java name for the package. Previously, it was necessary to change the name of an iWD solution before running a GRS Migration Tool, if the name included a number after a space. This workaround is no longer required. (ER# 300201547)
The default display time for all locales is now 12:00. Previously, some locales displayed a PM default time. (ER# 310134527)
An additional error message has been added for login failures caused by the maximum number of connections being reached. Previously an authentication failure message was displayed. (ER# 299683122)
Rules copied to another package now no longer keep the original calendar name. Another calendar must be chosen in the destination package. (ER# 302150961)
The Cancel button on the General tab of a rules package is now enabled only in the correct
contexts. (ER# 301433592)
Worktime calculations based on the Business Calendar where a business rule with a workday that spans midnight is running are now correct. (ER# 298532001)
A problem with edits to rules being saved in error after a request to cancel them has been resolved. (ER# 300194972)
Names of rule templates are now displayed in the correct color. (ER# 300930932)
The sorting arrow now behaves correctly in the rule's body tab. (ER# 301433596)
Display of a rule's body tab headers has been corrected to prevent the display of lines. (ER# 301620652)
When iWD 7.6.1 or 8.0 rules are migrated to Genesys Rules System rules 8.1.x, the order of the rules at each node in the business structure is now correct. The previous workaround is no longer required. (ER# 300314633)
Discrepancies between browsers in the sort order of tenants in the tenant drop-down menu have been corrected. (ER# 301433573)
Re-ordering rules at a node of the business structure now correctly updates the Deploy Rules node tree in the
navigation tree. (ER# 300390041)
Semi-colons in rule package descriptions are now displayed correctly and no longer cause a line break. (ER# 303883521)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of the Genesys Rules Authoring Tool.
Users can now import and export all rules within a package, to facilitate troubleshooting and lab deployment efficiency.
The rule search functionality is enhanced, enabling users to search a rule condition or action by using the parameter name.
A tooltip is provided for business users that describes the constraint to which users must adhere when using string parameters. A rule developer is now able to specify tooltip text that is displayed to the business user for a given parameter.
A business user can now view the name of the rule template from which each condition and action is derived.
The Explorer Tree now displays a visual indication when there are rules in the package that have changed, but have not yet been deployed.
Genesys Workforce Management (WFM) integration is now provided to enable the business user to select a value for use in a rule action that is dynamically retrieved from the Multi-site Activities and Activities lists on the Genesys Workforce Management (WFM) Server.
Genesys Rules System (GRS) is now integrated with intelligent Workload Distribution (iWD) 8.1.
This release includes the following correction and modification:
The issue with database parameters requiring the existence of a defined script object is resolved and a workaround is no longer necessary. Previously, if there was no defined script object, an error would cause any rule that referenced the database parameter to become hidden. (ER# 282957097)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This is the initial release of the Genesys Rules Authoring Tool. This section describes new features that were introduced in this release of the Genesys Rules Authoring Tool.
Support for both decision tables and linear rules.
Version history of rules, allowing the user to revert a rule package with a previous version of a rule, or restore a previously deleted rule.
Audit trail of rule deployment history.
Creation and editing of business calendars that define the working hours and holidays for the business.
Role-based access control, using permissions that are defined in the Genesys Configuration Layer, to control which parts of the application the user can access. Role-based access control requires Configuration Server 8.0.2 or higher, and Genesys Administrator 8.0.2 or higher.
Search capabilities to find instances of rules that match a specific Rule ID, that include specific words in the rule name, that were last modified by a specific user, that contain a certain business calendar, or that were created within a specific date range.
Ability to import and export of linear rules (in XML format).
Ability to import and export of decision tables (in XML and XLS formats).
There are no corrections or modifications for this release.
This section provides the latest information on known issues and recommendations associated with this product.
Start dates in the Simulated Time of test scenarios might be processed incorrectly where differences between user-selected timezones and server timezones exist. (GRS-2113)
| Found In: 8.1.301.06 | Fixed In: |
The deployment of large rule packages to multiple Genesys Rule Engine nodes can take several minutes to complete. In this case, Genesys recommends using the Scheduled Deployment feature so that you do not have to wait for the operation to complete. You can schedule the deployment for 1 minute in the future. If you prefer to do a "Deploy Now", you should make sure that the session-timeout configuration setting is long enough to prevent your session timing out during the deployment operation. (GRS-2072)
| Found In: 8.1.301.01 | Fixed In: 8.1.400.07 |
When a current calendar time falls outside working hours, the day is considered in error as a non-working day. (GRS-1410)
| Found In: 8.1.300.15 | Fixed In: |
The file type of a rule history that is exported correctly as .XLS is recognized incorrectly by the browser as .XML. (GRS-1406)
| Found In: 8.1.300.15 | Fixed In: 8.1.301.01 |
If a user has Test Scenario - View permission, but does not have Test Scenario - Execute permission,
the Run Test Scenario button is still visible, though the user will not be able to successfully execute
the test. (GRS-2001)
| Found In: 8.1.300.15 | Fixed In: 8.1.301.01 |
It is possible to resize the browser window in such a way that certain buttons may become hidden, even after restoring the browser to its original size. Users can restore the buttons by refreshing the browser. (GRS-1340)
| Found In: 8.1.300.15 | Fixed In: |
Documentation:"Last-modified-by" data and all rule audit history are not part of the rule package (or rule) export. So, when re-importing an exported rule package, the user doing the importing becomes the new owner of each rule created. Package and rule history are not maintained. The imported rules is considered a new rule package with new history starting from the point of import. (GRS-2010)
| Found In: 8.1.2 documentation | Fixed In: 8.1.4 documentation |
For security reasons, GRAT does not allow any HTML commands to be entered as parameters of a rule. For example, if a condition is:
Customer requests a callback on {day}
and {day} is defined as a string, we would not allow a rule author to enter the string:
Customer requests a callback on ‹b›Tuesday‹/b›.
All HTML constructs will be removed from the string. This applies to string parameters as well as dynamic list parameters such as business attributes, database or web service. (ER# 311219763)
| Found In: 8.1.200.17 | Fixed In: |
For the Genesys Rule Authoring Tool 8.1.2 to be deployed properly on Websphere Application Server 7.0, you must modify the
web.xml file before deployment as follows. The web.xml file can be found inside the Genesys Rules
Authoring Tool .war file in the installation directory. You can modify it with a zip/rar program such as WinZip.
At the bottom of the web.xml file, locate the following code:
‹listener›
‹listener-class›com.genesyslab.brs.brgui.servlet.SessionManager‹/listener-class›
‹listener-class›com.genesyslab.brs.brgui.servlet.ServletManager‹/listener-class›
‹/listener›
Change this to read as follows:
‹listener›
‹listener-class›com.genesyslab.brs.brgui.servlet.SessionManager‹/listener-class›
‹/listener›
‹listener›
‹listener-class›com.genesyslab.brs.brgui.servlet.ServletManager‹/listener-class›
‹/listener›
(ER# 317449931)
| Found In: 8.1.200.15 | Fixed In: 8.1.300.15 |
To configure the PSDK to use netty, the netty .jar file (version 3.2.3 or later) needs
to be copied to the webapps lib directory for
genesys-rules-authoring. For example:
C:\GCTI\Tomcat6\webapps\genesys-rules-authoring\WEB-INF\lib
| Found In: 8.1.1 | Fixed In: 8.1.2 |
In order to use GRAT with a UTF-8 Configuration Server, uncomment the following line
in the GRAT bootstrapconfig.XML file:
‹stringsencoding›utf-8‹/stringsencoding›
| Found In: 8.1.2 | Fixed In: |
After the iWD 7.6.1 or 8.0 rules have been migrated to Genesys Rules System rules 8.1.1, the order of the rules at each node in the business structure will be inverted from the order that was configured in 7.6.1 or 8.0. (Within a decision table, the order of rows are migrated correctly.)
Workaround: Reorder the rules to match the original order, by using the up and down arrow icons. (ER# 300314633)
| Found In: 8.1.100.14 | Fixed In: 8.1.2 |
Change the name of an iWD solution before running a GRS Migration Tool if the name includes a
number after a space. For example, change names like Solution 1 to Solution1. (ER# 300201547)
| Found In: 8.1.100.14 | Fixed In: 8.1.2 |
When iWD 7.6 Rules, Templates and Business Structure are migrated to 8.1 Genesys Rules System, the default method of mapping iWD tenants to the Configuration Manager tenant is by matching names. If the one-to-one mapping of iWD tenant name to Configuration Manager tenant name does not exist, migration will fail.
Workaround: To ensure rules migration completes successfully, temporarily change the tenant
names in the iWD Manager cmc_tenant table to match the tenant names that exist in Configuration Manager.
Note: If you are using a single-tenant Configuration Manager, each iWD tenant
must be mapped to
the single Resources tenant (ID = 101) in Configuration Manager. (ER# 300118922, 300045918)
| Found In: 8.1.100.14 | Fixed In: 8.1.2 |
When a business rule with a workday that spans midnight is running, work-time that is calculated, based on the Business calendar, might be incorrect. (ER# 298532001)
| Found In: 8.1.100.14 | Fixed In: 8.1.2 |
When the Genesys Rules Authoring Tool is deployed on WebSphere, you can export a decision table as an XML file, but not as an XLS spreadsheet. (ER# 276512936)
| Found In: 8.1.000.42 | Fixed In: |
This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.
There are no discontinued items for this product.
Information in this section is included for international customers.
The 8.1.4 release ships with 8.1.3 language packs. This means that some new UI elements introduced in release 8.1.4 will display in English only.
Language Packs are supported from the 8.1.301.07 release of this product.
Language Packs are supported from the 8.1.100.27 release of this product. Language Packs allow installers to select the language in which the user interface and online help files are displayed. For details on what Language Packs are available, including languages, see the Genesys Rules Release Notes section of the Genesys Documentation website.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
Genesys Rules 8.1 Deployment Guide describes deployment procedures for all Genesys Rules System.
Genesys Rules Authoring Tool Help is a guide to the Genesys Rules Authoring Tool user interface.
Genesys Rules Development Tool Help is a guide to the Genesys Rules Development Tool user interface.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).
Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up to date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.