8.5.117.10
Genesys Info Mart Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Mac | Solaris | Windows |
|---|---|---|---|---|---|---|---|
| 07/16/25 | Update | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
All customers MUST migrate to GIM version 8.5.117.07+ before end of 2025.
Only customers that have migrated to 8.5.117.01 or 8.5.117.05 before: Please follow instructions provided in sql_scripts/delete-2025-records/readme.txt file of GIM installation directory.
- Starting from GIM 8.5.117.01 “date and time far in the future” that is used for end time of active fact records in GIM tables has been changed from 2025-12-31 23:45:00 to 2037-12-31 23:45:00.
Resolved Issues
This release contains the following resolved issues:
Now, extract doesn’t produce inconsistent GIDB GCX_* records with STATE=2 and DELETED_TS=NULL in scenario when one HA ICON doesn’t have corresponding record. (GIM-14975)
Multi media transformation now correctly populates technical result reason of technical descriptor as AnsweredByAgent when desktop uses InternalConferenceInvite auxiliary interaction and agent replied to main interaction. Previously, the reason was RoutedToOther. (GIM-14885)
Various Get GIM Data issues were fixed in this release. (GIM-14969, GIM-14928, GIM-14978, GIM-14979)
Upgrade Notes
- If you have migrated to 8.5.117.07+ and still observe presence of 2025-12-31 23:45:00 in column END_TS of various tables please follow instructions provided in sql_scripts/delete-2025-records/readme.txt file of GIM installation directory.
- Rollback instructions: If you want to rollback to the version of the GIM application prior to 8.5.117, run rollback-2037-to-2025.sql script from the sql_scripts/<dbms-type> folder before rolling back.
- Customers consuming GIM export to their DB with GIM-like DB schema maintained by update_target_gim_db.sql script must run update-2025-to-2037.sql script from sql_scripts/<dbms-type> folder on customer's DB after GIM migration.
- To rollback to pre 8.5.117 GIM run rollback-2037-to-2025.sql script from sql_scripts/<dbms-type> folder on customer's DB after GIM rollback.