Release 5.3.33
What Changed
- Connection status banner. When the connection to the server is lost, a banner appears with connection status and a «Check connection» button — you see when updates are paused and can force reconnect.
- Inline keyboard callback fix. Telegram inline buttons now pass the button
value(or translated text) to the scenario variable instead of the translation ID — BDA scenarios work correctly. - Ticket custom_fields via API. The
POST /kw/operator_panel/chat_room/:id/editendpoint now supportscustom_fields— you can update custom ticket fields via API. - SLA and calendar for topics. SLA hours limit increased to 8760 (365 days); you can clear the calendar selection for a topic.
- QA quick search. Search in QA assessments works for checklist name, operator name, email, and chat title.
- Permission and QA settings. New permission «Allow CSAT to be sent»; QA Instance Settings section with Dify heartbeat timeout (1–30 min).
- Broadcast send_anyway. New option «Send anyway» for active dialog behavior — send to all recipients regardless of active dialog (e.g. critical announcements).
- Broadcast export to Excel. Button «Export to Excel» in Broadcast V1 logs — download results as .xlsx (up to 50 000 rows).
- Transfer chat fix. Fixed race condition when accepting or canceling chat transfer — no more double actions or incorrect state.
- Process Library: Set as default. Button «Set as default» in Process Library — set which bot opens by default in the constructor.
- Scenario Builder: Edge highlight. Edges highlight on hover and pin on click; delete button visible only for pinned edge; EntryPoint overflow fixed.
- search_list inline keyboard. Inline keyboard setting is now respected — no automatic override for search_list nodes.
How It Changed
Connection and transfer
Before: Connection loss was not clearly indicated; chat transfer could trigger double actions.
Now: Connection status banner shows when updates are paused; transfer dialog has correct guards.
Why it matters: Clear feedback when connection is lost; reliable chat transfer flow.
Tickets, SLA, and QA
Before: SLA hours were capped at 168; calendar could not be cleared; QA search had MySQL issues; custom_fields not supported in edit API.
Now: SLA up to 8760 hours; calendar can be cleared; QA quick search works; custom_fields supported in API.
Why it matters: Flexible SLA for long cycles; correct QA search; API integration for ticket custom fields.
Broadcast and Scenario Builder
Before: No «send anyway» option; no Excel export; search_list inline was auto-enabled.
Now: «Send anyway» for critical broadcasts; Excel export in logs; search_list respects inline setting.
Why it matters: More control over broadcasts; export for analysis; predictable scenario behavior.
Telegram and Process Library
Before: Inline button callback passed translation ID; default bot was unclear.
Now: Callback passes value; «Set as default» in Process Library.
Why it matters: Correct routing in BDA scenarios; clear default bot selection.