Last modified at Friday 6 December 2024
This is our main release description. The change notes are ordered in 3 different categories:
- New functionality
- Improvement
- Support
New functionality
DELIVERABLE | FUNCTIONAL DESCRIPTION | CHANGE CATEGORY | EXTRA INFORMATION |
Pagination of the conversation thread for better user experience | Loading the conversations thread not all at ones, but by the first 5 message ID's will improve the experience of speed and reliability. In case there are more message IDs, these will be automatically by scrolling, added. | new | A thread can contain multiple email messages, and each of these messages will have its own unique message ID. However, all the messages in the same thread will share the same thread ID. |
Highlight search result |
After input of keywords on AMI Search box, the result is highlighted in the AMI list* and AMI show* * AMI List are the conversations in queues; open and closed. AMI Show refers to the email thread / message IDs |
new | see image |
Search result on relevance - on AMI list | With this method we support the search and relevance result on any keyword being part of subject and/or body. We expect a positive effect on these search results. | new | see image |
Improvement
DELIVERABLE | FUNCTIONAL DESCRIPTION | CHANGE CATEGORY | EXTRA INFORMATION |
Search input condition | before being able to toggle between open | closed | and both of the in AMI conversation, their needs to be keyword input on the search box or filter condition(s) selected. | improvement |
|
Sorting of conversation thread - on AMI Show | The default way to show AMI thread is by the oldest conversation at first. With this release it is allowed by AMI setting page, to switch always to newest, the last conversation of the thread. | improvement |
this is system width setting. Easy to change and immediate experience See AMI setting image |
UX update | better “glance” on AMI selected parts. Like queue, conversation and size of frames. | improvement |
|
AMI editor | Release update and functions like lowercase and uppercase converters, word counting and detection of CTRL + A use. | improvement | Additional the extra <br />-tags from html-emails are removed, and only apply to tekst-based emails |
AMI tag favorite | Ability to pin the Tag for own preference | improvement | Equal support as ability to favorite queues by pinning. See image |
AMI setting page | Many extra options to “customize” your AMI environment. Some highlights: a. Clearer view for AMI settings to be turned on and off – see here b. Allowance to change system tags by name and color. Wil be soon improved. c. Custom Font for selection from AMI editor. d. Improvement on Polly Knowledge Management and Queue signature template enablement. | improvement | ask for item c. to provide short instructions or try yourself by entering i.e. Source Sans Pro. See image where to enter. Disclaimer: not all web fonts are supported to native clients. In that case the font will be converted to the developer created alternative font. |
Support
DELIVERABLE | FUNCTIONAL DESCRIPTION | CHANGE CATEGORY | EXTRA INFORMATION |
AMI Clone created as closed conversation | Changed into “clone as reply conversation“ | support | This change results to create the entire email as historical conversation. And now historical thread, is shown below 3 dots. |
Interim reply validated on the email address setting “multiple action” activation | To have consistentie in the activation/deactivation of interim reply/multiple action support | support |
This change impacts in no longer being necessary to configure interim reply on usedd outbound emails of queue. Note. also no longer nessary to have interim reply (multiple action) configured for being able to forward a conversation in AMI interface (in that case conversation is closed after send) |
Disconnect permission simplification | alternative permission for disconnect depreciated | support | default is now only the allowance to disconnect the conversation if connected . Otherwise the extra permission: Conversation:Communication :Disconnect required. See details on AMI role and permissions |
AMI notes optimization | Allowance to enter in AMI Notes without being connected to conversation. | support | Equal the case for delete note content |
AMI Tag clear support | All AMI tags will be removed when define in WorkFlow | support |
When the following attribute value is added as Set Participant Data in the Workflow*, all AMI tags will be removed. See image *as first participant attribute |
AMI counters auto refresh delayed | AMI counter timer updated after 10 seconds. | support | For stability and avoidance by user to manual reload. Note.in R3.12 it was 7 seconds |
Auto generated optimization |
|
support | when conversation has only 1 message ID and is autoGenerated, show in AMI due to possible follow up actions. |
Auto sync conversation | to avoid experience on difference conversation status; open and close between Genesys and AMI | support | See image |