This page was last edited on April 30, 2019, at 11:26.
Comments or questions about this documentation? Contact us for support!
Genesys Administrator Extension Release Notes
Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
---|---|---|---|---|---|---|
12/07/17 | General | X | X |
This release contains the following new features and enhancements:
This release contains the following resolved issues:
The Application objects list view now loads correctly, even if there are lengthy application names. Previously in this scenario, the list disappeared. (GAX-9563)
The deployed IP page now loads successfully without any occasional errors. (GAX-9549)
GAX now correctly performs bulk imports of agents, even if the Person folder exists in the Configuration Unit. You can now import persons or agents to destinations under any Business Unit/Site/Folder. (GAX-9543, GAX-9467)
Cloning a Person object now works correctly in Mozilla Firefox version 40.0 (GAX-9540)
Names with the apostrophe (') punctuation mark can now be filtered properly in the Quick filter and Column filter. (GAX-9533)
Agents Bulk import now works correctly even if Application Rank is selected in the import. Previously, Agents Bulk import failed when Application Rank was selected. (GAX-9496)
GAX now connects and starts successfully if the multi-language configuration support is enabled in Configuration Server. (GAX-9492)
The system dashboard now displays accurate status. Earlier, the folder status was displayed incorrectly in the GAX system dashboard. (GAX-9477)
Now, when GAX is configured to run with the Oracle backend database, the centralized log loads much faster than before. (GAX-9398)
GAX support for Oracle Driver is now updated from ojdbc6 11.2.0.2.0 to the more recent ojdbc7 12.1.0.2. (GAX-9348)
Installation Packages list now refreshes correctly, when the PostgreSQL GAX backend database is restarted. Previously, there were errors while loading the list. (GAX-8702)
This release includes a core schema update for GAX to run successfully. For more information on how to upgrade from database schema version 8.1.301.01 to 8.5.260.11, see the database schema update provided in the Migration Procedures page.