Documentation
Docs
Learn
Release Notes
  • English
  • Українська
Docs
Learn
Release Notes
  • English
  • Українська
  • Release Notes
  • 5.6.6
  • 5.6.5
  • 5.6.4
  • 5.6.3
  • 5.6.2
  • 5.6.1
  • 5.6.0
  • 5.5.6
  • 5.5.5
  • 5.5.4
  • 5.5.3
  • 5.5.2
  • 5.5.1
  • 5.5.0
  • 5.4.4
  • 5.4.3
  • 5.4.2
  • 5.4.1
  • 5.4.0
  • 5.3.42
  • 5.3.41
  • 5.3.40
  • 5.3.39
  • 5.3.38
  • 5.3.37
  • 5.3.36
  • 5.3.35
  • 5.3.34
  • 5.3.33
  • 5.3.32
  • 5.3.31
  • 5.3.30
  • 5.3.29
  • 5.3.28
  • 5.3.27
  • 5.3.26
  • 5.3.25
  • 5.3.24
  • 5.3.23
  • 5.3.22
  • 5.3.21
  • 5.3.20
  • 5.3.19
  • 5.3.18
  • 5.3.17
  • 5.3.16
  • 5.3.15
  • 5.3.14
  • 5.3.13
  • 5.3.12
  • 5.3.9
  • 5.3.6
  • 5.3.5
  • 5.3.3
  • 5.3.2
  • 5.3.1
  • 5.3.0
  • 5.2.14
  • 5.2.13
  • 5.2.12
  • 5.2.11
  • 5.2.10
  • 5.2.9
  • 5.2.5
  • 5.2.3
  • 5.2.2
  • 5.2.1
  • 5.1.1
  1. Docs
  2. /Release Notes
  3. /Release 5.6.8

Release 5.6.8

What Changed

  • Action Library: each custom action appears once; filter by several groups at the same time.
  • Viber: images keep their caption; messages with several photos deliver every image.
  • Website widget: inline button links with scenario variables resolve to working URLs before the chat shows them.
  • Operator Line: long folder and group names truncate cleanly in the sidebar.
  • Scenario Builder: reorder keyboard buttons without breaking connections; clearer run-details output in light and dark themes; more reliable section and alias state when opening a scenario.
  • Scenarios: the “last operator dialog” action returns complete, chronologically ordered history when your flow reads conversation context after a chat closes.

How It Changed

Before: Custom actions could appear twice in the library; Viber sometimes dropped captions or extra photos; widget buttons could show unresolved placeholders; narrow sidebars scrolled horizontally; keyboard button order was fixed in the editor; run output blocks were harder to scan in dark theme; last-dialog history could be empty, out of order, or from the wrong bot.

Now: The action list is easier to scan and filter; Viber outbound media matches what the operator sent; visitors get clickable links from dynamic buttons; folder labels stay within the panel; editors can reorder buttons safely; debug panels distinguish result types; scenario flows that store last-dialog text or JSON get consistent data for the current bot.

Why It Matters

Scenario authors spend less time hunting duplicate actions and fixing keyboard order; operators trust Viber media delivery; site visitors follow working links from bot buttons; the Operator Line sidebar stays readable on smaller widths; post-run inspection in Scenario Builder is faster during troubleshooting.

Product areas in detail

Settings — Action Library

Improved

  • Each custom Action Jail action is listed once (the editable entry), without a second non-editable copy under the same name.

  • Group filter supports multi-select with chips; with no groups selected, all groups remain visible.

  • Instance setting Deduplicate actions in GET /kw/actions (on by default) controls the new list behaviour; turn it off only for rollback or diagnostics.

Operator Line — Viber

Fixed

  • An image sent with a text caption reaches the client with the caption attached.

  • A message with several images delivers all photos, not only the first one.

Website widget

Fixed

  • Inline buttons that open a URL or web app resolve placeholders such as {{const.*}} before the message is shown, so the visitor receives a working link.

Operator Line — folders

Improved

  • Long folder and group names in the narrow sidebar truncate with an ellipsis instead of forcing horizontal scroll.

Scenario Builder

Improved

  • In keyboard settings, move buttons up or down with arrows; connections on the canvas stay aligned after reorder.

  • When opening a scenario, the active section and duplicate connector-alias warnings restore more reliably.

  • In node run details, output and action result blocks are easier to read in light and dark themes, with results highlighted separately.

Scenarios — last dialog history

Improved

  • Flows that read the last operator dialog after a chat closes receive history even when the room had no messages, in chronological order, scoped to the current bot, with readable text or JSON depending on format settings.

Please note

  • Action deduplication applies to the action list API and Action Library UI; disable the instance flag only if an external integration relied on duplicate runtime rows.

  • Widget link substitution applies to inline buttons rendered through the standard Engine path.

  • Last-dialog improvements affect scenario actions that fetch operator chat history; verify multi-bot setups if the same customer identifier exists on more than one bot.

Related documentation

  • How to configure a bot
  • Clients — operator hub
  • How to configure skill groups

On this page