Release 6.3.1
Release 6.3.1 adds a personal ticket counter and list in statistics and a warning in the profile when sound notifications are on but no enabled notification type uses sound. It also fixes condition checks in scenarios for text with an apostrophe, saving variables before a chat is closed, and loading of Action Jail actions after an update.
Statistics
New
- Personal ticket counter and list. When the administrator has turned this feature on, the created-tickets counter and the list on the "Tickets" tab include only cases available to you in the operator panel. Personal filters narrow both the counter and the list, and going from the counter leads to the existing table. Other cards work as before. Export to CSV and XLSX requires your current session, and if your access to the cases changed after the export was created, the ready file may become unavailable: create a new export.
Settings
Changed
- The "Display outgoing chats of other operators" checkbox is removed. In the new operator panel design this checkbox changed nothing: operators already see colleagues' outbound chats within their own topics and bots. The checkbox is gone from "Settings" → "Operators" → "Panel display settings". The stored value is not changed, and the legacy constructor keeps the checkbox.
Fixed
- A warning when sound is on but will not play. In the profile, on the "Notifications" → "Channels" tab, the sound card shows a warning with a link to the "Notification types" tab if the "Sound notifications" switch is on but none of the enabled notification types has the "Sound" channel. The warning disappears as soon as an enabled type gets "Sound" (even before saving). For a mandatory sound channel the advice to turn the switch off is not shown. The test button still plays the sound, but now shows a yellow message instead of success. The hint at the top of the tab is now blue (informational) instead of yellow. The switch no longer turns on by itself when the page opens or on save because of "Sound" in a disabled type: operators who have "Sound" only in disabled types will see the switch as they left it.
Scenarios
Fixed
- Conditions with an apostrophe in the text work correctly. Previously, a scenario condition that checked a variable in quotes could wrongly count as false if the text contained an apostrophe (
it's,you'll) or a backslash. Because of this, an email or message with such text was treated as empty, did not continue along the scenario, and no dialog was created in the Operator Panel. Now such text is checked as an ordinary value and the dialog is created. The same applies to the "Condition" and "Switch" nodes and to setting a variable value. As a result, text with special characters is now kept literally: for example,\nin a value no longer turns into a line break, and an apostrophe in a value does not add extra quotes around it. - Variable changes are saved before an open dialog is closed. If in one step a scenario cleared or changed variables and then the "Close chat" node closed a still-open dialog, those changes were lost: on the client's next message the variables had their old values. Now they are saved. Nodes that come after "Close chat" in the same step still do not run: after closing, the scenario goes to the close entry.
Action Jail
Fixed
- Custom actions are available again after an update without a manual restart. After a platform update, custom scenario actions (Action Jail) could stay unavailable until the service was restarted by hand, and scenarios stopped at a step with such an action. Now, if the actions could not be read at startup, the system retries on its own until it loads them.