Skip to content

4.35

Important announcement

With release v4.30.0 we have officially marked our kubernetes repository as deprecated. If you are an on-premise customer and you are running Cognigy.AI/Cognigy Insights yourself, please have a look at our Helm Chart which we have crafted for Cognigy.AI/Cognigy Insights! Our Kubernetes repository will still receive updates until 31st December 2022.

4.35.1

Cognigy.AI

Released September 26th, 2022

Bugfixes

  • Fixed a bug where ongoing handover requests would fail for the "Salesforce Handover Provider" due to an imcompatible data-format

4.35.0

Cognigy.AI

Released September 23rd, 2022

Features

Audit Events dashboard

This release of Cognigy.AI adds a new Audit Events dashboard. This new dashboard is only usable for users with the "admin" role assigned. The dashboard shows all operations which have manipulated objects in Cognigy.AI such as "create"/"update" & "delete" operations.

Attachment Handling for Whatsapp Cloud Endpoint

This release of Cognigy.AI add support for handling attachments such as video, audio and file-uploads through the Whatsapp Cloud Endpoint.

Improvements

  • Create a new Webchat release 2.42.1
  • Improved by adding a metric that shows if a service is connected to dependencies such as MongoDB
  • Improved by adjusting the Liveness Probe to align more with industry best practices
  • Improved by adding a startup check for whether NFS is working
  • Improved reconnect handling for RabbitMQ connections
  • Improved reconnect handling for Redis connections
  • Improved by the error message for failures in an Extension
  • Improved by storing response data from Salesforce into the Input object after starting a Handover

Bugfixes

  • Fixed a bug where RCE handover was not working when the "Forward Only Handover Conversations" toggle is OFF for first time in the chat session (works again on next message) in the handover settings section of the endpoint
  • Fix Line structured content converter issue
  • Fixed a bug where manually triggered intents (cIntents) got no porperty intentLevel in the input object
  • Fixed a bug where uploading intents intents in secondary locales that are localized, would not work
  • Fixed a bug where the Agent Assist Cards would not be sent to LA properly if no Handover Accepted Message was defined in the Handover to Agent Node
  • Fixed a bug where activating a deactivated Profile did not work
  • Fixed a bug where the ChatRequestFailed event from Salesforce would cause the Handover status to be set to "completed" instead of "error"
  • Fixed a bug where context updates during agentInject where lost when the Handover was finished
  • Fixed a bug where intent trainer records would not be stored if the triggered Intent had a Default Reply
  • Fixed security vulnerabilities in the Runtime services for Mongoose
  • Fixed a bug where there could be a possible attack vector on "indexUsers" RESTful API. The API is now restricted to users with admin/userManager/userDetailsViewer global roles or with roles projectAdmin/memberManager in any assigned project
  • Fixed a bug where tag was mandatory to work with Voice Preview SSML
  • Fixed a bug where traning out of date error badge will not hide immediately after training
  • Fixed a bug where html is not rendered in a standard message in the Interaction panel
  • Fixed a bug where index trainer records timed out

Cognigy Insights

Released September 23rd, 2022

Bugfixes

  • Fixed a bug where Step explorer was crashing
  • App crash if Step Explorer API call returns invalid data
  • App crash if the custom theme could not be loaded
  • Transcript Explorer - Channel Filtering

Cognigy Live Agent

Released September 23rd, 2022

Improvements

  • Removed OAuth popup window on login. The entire login experience should now take place in the same window

Bugfixes

  • Fixed a bug where the conversations tab counters (me, unassigned, total) are sometimes incorrect
  • Fixed a bug where mentions were not being removed when clearing chat history

Infrastructure (AI + IN)

New Services

This release contains a new microservice:

  • service-runtime-file-manager
  • clamd

This new service provides functionality which is currently only used by our new Whatsapp Cloud Endpoint and allows end-users to upload file attachments such as images, audio, video and e.g. files like PDF. Once a file has been received, it will be checked for infections with the "clamd" component.

DNS record

You will have to create a new DNS record for service-runtime-file-manager as this is a new microservice which will also be fully exposed to the external/public network. The DNS record needs to be pointed to your loadbalancer which has been provisioned when Cognigy.AI was installed initially. The following would be an example of what this can look like:

Let's assume that your Cognigy.AI API is available on the DNS name api-trial.cognigy.ai

  • a good DNS name for the new microservice would e.g. be files-api-trial.cognigy.ai -
  • so we have essentially just prefixed the Cognigy.AI API address with files-.

Using a command like dig on Linux needs to reveal that both DNS names (old one and the new once after you have created it) should point to the same loadbalancer address:

dig api-trial.cognigy.ai

; <<>> DiG 9.10.6 <<>> trial.cognigy.ai
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26015
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;trial.cognigy.ai.              IN      A

;; ANSWER SECTION:
trial.cognigy.ai.       300     IN      CNAME   ae79c0ec73eca4d64a0509f7a75fe42a-1344350581.eu-central-1.elb.amazonaws.com.
ae79c0ec73eca4d64a0509f7a75fe42a-1344350581.eu-central-1.elb.amazonaws.com. 60 IN A 52.29.55.202
ae79c0ec73eca4d64a0509f7a75fe42a-1344350581.eu-central-1.elb.amazonaws.com. 60 IN A 3.121.18.227
ae79c0ec73eca4d64a0509f7a75fe42a-1344350581.eu-central-1.elb.amazonaws.com. 60 IN A 3.64.138.183

;; Query time: 30 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Aug 10 18:37:42 CEST 2022
;; MSG SIZE  rcvd: 181

Make sure that the dig command shows similar information after you have provisioned the new DNS record.

Values modifications

Please make sure that you also update your Helm values and implement the following changes in them:

In the ingress section, make sure that you define a host for the runtime file manager:

serviceRuntimeFileManager:
  host: "files-api-trial.cognigy.ai"