7.8¶
Features¶
Ticket no. |
Ticket Name |
Desc |
Link |
---|---|---|---|
7263 |
Webchat Javascript Implementation |
Webchat can normally pass information to Frontstage about which page it was launched from. However, the standard method was not usable in some scenarios, so an additional method of passing the information was added. |
|
7296 |
MobileChange Gateway Update |
||
7236 |
Post-chat Evaluation |
The system allows an ICR script to be run after the webchat ends. The script guides the customer through a set of questions they can answer. The responses are stored in a form associated with the specific chat instance. |
|
7264 |
New Configuration Parameter |
||
7240 |
ChatLink |
Performance and stability adjustments. |
|
7112 |
TeamsClient |
Closing an Issue associated with a communication was streamlined for quicker workflow. |
Bug fixes¶
Ticket no. |
Ticket Name |
Desc |
---|---|---|
7266 |
System Service Adjustment |
The system service “Servicesync ” sometimes lost the database connection due to the timeout. Situation fixed. |
7237 |
TeamsClient - Change Metadata |
The “Message metadata change” function changed the metadata correctly, but the following actions, like returning the message to the distribution queue, did not work correctly. |
7253 |
Agent Applications |
Forcing reload for cases where the message issue is changed in the database directly. |
6647 |
System Service “ServiceBulk” Adjustment |
Moving an email’s contents from the database to the repository caused the operation to time out and fail in certain cases. The operation then blocked email processing in ServiceBulk. |
7238 |
TeamsClient - Connection Error Indication |
The application was not handling the situation correctly when a connection outage occurred. Now, when the connection is interrupted for some reason, a stripe indicating this situation will appear visibly. |
6690 |
ReactClient - Email Attachments |
An e-mail attachment will be directly downloaded to your device when clicked. |
6714 |
ReactClient - Bulletin Board Notice |
The notice’s time values were shifted for two hours on the frontend, resulting in inaccurate periods. |
7212, 7224 |
ReactClient - Bulk Actions |
Custom-defined spam bulk actions did not mark any records. |
7211 |
TeamsClient - Queues Tab |
Changing the agent’s status using this tab resulted in blank status information in some cases. |
7128 |
TeamsClient - Assigning Contact to Communication |
The “Assign” contact button in the calls editor did not fetch any existing contacts. |
Smaller updates and internal fixes¶
Ticket numbers of less significant issues. Descriptions can be seen after entering the ticket number into the internal evidence system.
3893, 7227, 7228, 1623, 7226, 7241, 7235, 6304, 7221, 7207, 1759, 7239.