async-idle-notices
Section: settings
Default Value: major
Valid Values: none, major, major2, typing, all
Changes Take Effect: Immediately
Introduced: 8.5.202.09 (Restricted); 8.5.301.06 (Generally Available)
Modified: 8.5.310.09
Specifies which notifications count as async chat session activity for the purpose of inactivity control.
- all: All user notifications are included (custom, push URL, typing on/off, update nickname).
- major: Only major notifications are included (push URL, file uploaded, file deleted).
- major2: Extends the major value with custom notifications.
- none: All notifications are excluded.
- typing: Only major and "typing on" notifications are included.
include-notices
Section: inactivity-control
Default Value: major
Valid Values: none, major, major2, typing, all
Changes Take Effect: Immediately
Modified: 8.5.310.09
Specifies which notifications count as chat session activity for the purpose of inactivity control.
- all: All user notifications are included (custom, push URL, typing on/off, update nickname).
- major: Only major notifications are included (push URL, file uploaded, file deleted).
- major2: Extends the major value with custom notifications.
- none: All notifications are excluded.
- typing: Only major and "typing on" notifications are included.
8.5.310.09
Chat Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 03/12/20 | Update | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- The values for configuration options include-notices (section [inactivity-control]) and async-idle-notices (section [settings]) have been extended to add the value "major2", which now includes custom notifications, along with major option values. (CHAT-3550)
Resolved Issues
This release contains the following resolved issues:
Chat Server now ignores a chat bot presence in a chat session when processing the logic for the configuration option stop-abandoned-interaction. Previously, Chat Server would not stop the chat session, as directed by stop-abandoned-interaction, when a chat bot was present. (CHAT-3633)
Chat Server now correctly sets the event ID numbering after a chat session restoration by increasing the event ID value for the next, new, event after the session restoration. Previously, if some of the session events were not saved before the restoration (due to configuration specifics or failed communications), these events could be rewritten with the content from another, identical, event ID after the restoration. (CHAT-3591)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.310.09.