Release notes
3.6.9
Released: September 8th, 2021
Improvements
- Improved interface for Intent Trainer by sorting options alphabetically
3.6.8
Released: May 17th, 2021
Improvements
- Make error-logging more verbose when sending emails would not work
- Added the ability to specify regex-modifiers for regex-based validations in Process questions
Bugfixes
- Fixed a bug where Intent confirmation does not work after export/import to a different environment in our Intent Trainer
- Fixed a bug where inputs containing a $-sign could not be stored in conversation analytics
- Fixed a bug where the Cognigy.AI LiveChat UI would not update without manually reloading the page
- Fixed a bug where the Intent Trainer UI could crash
- Fixed a bug where agents can not reply after the Webchat reconnect
- Fixed a bug where the "NLU Connector Transformers" could not be activated
3.6.7
Released: January 29th, 2021
Improvements
- Update our integrated WebchatWidget to version 2.25.1 which brings in multiple improvements. Please consult the changelog in the WebchatWidget GitHub repository
Bugfixes
- Fixed a bug where the inject/notify APIs would no longer work when clients would re-connect after they lost the socket connection
- Fixed a memory leak in our
service-analytics-odata
microservice and fixed an issue where the ODATA service could crash while streaming data - Fixed a bug where multiple reply-to emails would break our sendEmail-node
- Fixed a bug where images in the say-node preview and within the interaction panel would have a different aspect ratio
- Fixed a bug where opening a link to a different project would cause errors
- Fixed a bug that our password-reset functionality would not work in newer versions of Chrome
3.6.6
Released: October 27th, 2020
Improvements
- Do not set the intent to "NotHandled" for Dashbot reporting when an Intent was not found
- Improve sanitization of error messages
Bugfixes
- Fixed a bug related to Playbook asserts
- Fixed a bug related to cloning a Flow with a Once Node
- Fixed a bug where slots were not stored in analytics
- Fixed a bug in saving Default Replies that contained Microsoft Bot Framework content
- Fixed a bug where the Dialogflow Testing Console could not be used
- Fixed a bug related to triggering Rule Intents on DataOnly messages
3.6.5
Released: September 15th, 2020
Improvements
- Updated our integrated WebchatWidget to version 2.19.4 which brings in multiple fixes and improvements. Please consult the changelog in the WebchatWidget GitHub repository.
- Update our dependencies in order to close several potential security vulnerabilities. Please consult our documentation (installation manual) and/or the Kubernetes repositories changelog in order to understand how you can update your system(s).
Bugfixes
- Fixed a bug related to SAML 2.0 and Azure on-prem SSO
3.6.4
Released: August 7th, 2020
Improvements
- Updated our integrated WebchatWidget to version 2.19.1 which brings in multiple fixes and improvements. Please consult the changelog in the WebchatWidget GitHub repository.
- Released a new version of our management-ui which renders timestamps in a more human-readable format
- Add /CreateConversation suffix to all AudioCodes endpoint URLs
- Activate a new conversation-counter which replaces the old-message counter in our software
Bugfixes
- Fix bug in our generic language where dashes ("-") in long numbers would lead to errors during execution
- Fix issue where contact profiles in the contact profiles viewer would sometimes not load if the data-set is large
- Fix issue where certain intent properties (score, mapper-results) would get reported incorrectly if executeFlow is being used
3.6.3
Released: June 15th, 2020
Improvements
- Updated our integrated WebchatWidget to version 2.18.3 which brings in multiple fixes and improvements. Please consult the changelog in the WebchatWidget GitHub repository.
- Added new monitoring-related metrics to our product
- Added the ability to use the task.assigned webhook for our RingCentralEngange handover integration
- Remove cookie-based socket.io handshake which removes the io cookie
- Add more configuration options (through environment variables) for our intent-training pipeline
- Add the ability to configure allowed CORS origins for our endpoint service. Please consult our dev-ops manual in order to understand how this can get configured.
Bugfixes
- Fix bug, where the accessToken field for RingCentralEngange endpoints could not get updated as our validation on the field, was too strict
- Fix community role so users within this role can also update/add/remove schema fields from contact profiles
- Fix bug where paginated contact profiles query would time-out in large product installations
3.6.2
Released: May 15th, 2020
Improvements
- Updated our integrated WebchatWidget to version 2.18.1 which brings in multiple fixes and improvements. Please consult the changelog in the WebchatWidget GitHub repository.
- Improved naming on the Webchat tab within the Say-Node (from 'use Facebook channel' to 'use Facebook Messenger channel')
- Added "Getting started" cards to the project-creation wizard and our project overview page
- Added multiline capabilities to text input fields in the Facebook Messenger Say-Node tab
- Added the ability to collapse learning sentences in the Intent Editor
Bugfixes
- Fixed a bug within the "handleExecutionFinished" transformer for REST endpoints
- Fixed a bug where keyphrase-data (data within Lexicons) would sometimes get masked in the Cognigy Input Object when the "mask analytics" setting would be used in the endpoint (or by using the blindMode-Node)
- Fixed a bug where the executeFlow-Node would use the wrong language when entering a Flow using a different Language - this would lead to issues in system-slot detection
- Fixed a bug where the text send to an external handover-tool like RingCentral Engage would be masked when the "mask analytics" functionality is used
- Fixed a bug in service-nlp-ner where this service could not start in a Kubernetes-/Docker-Swarm cluster where privileged containers could not work
- Fixed a bug where the Intent CSV export would crash our user interface in certain situations
- Fixed compatibility issues with older versions of Microsoft Edge for our user interface
- Fixed a bug in the login form where the email field was not case-insensitive
- Fixed various layout problems in the Facebook Messenger Say-Node tab
- Fixed a problem in Cognigy Script parsing where an expression like "$1" would not properly parse
- Fixed a user interface crash when using the BasicCard template
- Fixed a bug related to our inject/notify API
3.6.1
Released: April 22nd, 2020
Improvements
- Updated our integrated WebchatWidget to version 2.17.0
- Update Traefik to v1.7.24 in order to fix the "same-site" cookie issue. Traefik is the load balancer we ship with our product. Please make sure that you re-deploy Traefik and ensure that you are using the updated version (v1.7.24) for the "same-site" cookie-fix to work properly.
- Upgraded our Facebook Graph-API we are using for our Facebook endpoint to v3.3 as the old API which was used is now deprecated
Bugfixes
- Fixed a bug related to NLU cutting-edge not being able to score models which were trained previously of Cognigy.AI 3.6.0
- Fixed a bug related to the "Get-Started Message Field" and our "Auto-send" message feature for our Webchat endpoint
- Fixed an issue related to "Cognigy tokens" where the Flow-Editor would crash when opening an "if/switch"-Node
- Fixed a bug where Twilio (voice) would hang-up the call when no user-input was detected
3.6.0
Released: April 2nd, 2020
Important:
Because of a queue-related bugfix (see bugfixes) in 3.6.0, you will have to adjust the update-mechanism. Please first manually stop ``service-parser``, visit the RabbitMQ management panel and delete the ``service-parser`` queue. You can then start the update to 3.6.0. If you don't follow these steps, our ``service-parser`` microservice will not be able to start. Please contact ``[email protected]`` if you have any additional questions.
Features
Finnish & Swedish NLU
We have introduced Finnish
and Swedish
as new officially supported languages in our product. Please consult our installation- & dev-ops manual in order to get all details on how this language can be enabled on an infrastructure level.
Connection-Strings for MongoDB database connectors
We have added the ability to switch between specifying individual fields
or a full connection-string
for a MongoDB database-connection. This will allow customers to connect to a replica-set hosted on e.g. Mongo Atlas.
Extend support for additional HTTP verbs in transformers
We added support for additional HTTP verbs (other than POST) for endpoint input-transformers for the following endpoint-types:
- REST
- Webhook
The input-transformers of those two endpoint-types will now also be executed if e.g. a GET-request arrives and hits the endpoint-url. You can utilize this functionality to e.g. implement a verification process most of external platforms use.
NLU transformers
With our 3.5.0 release we have introduced endpoint-transformers which give you more possibilities to create your own integrations with third-party platforms. With NLU-transformers, we extend the ability to inter-connect with external NLU platforms as well.
Configurable TTL for contact-profiles & session-information
Until now, contact-profiles and session-information could only get dropped upon request. We have now added the ability to configure a TTL (=time to live) for those objects. Once configured, our software will drop those objects automatically.
Custom questions
We have added the ability to ask custom questions within Processes. These allow you to ask a question and e.g. trigger a webchat plugin in order to give the user a nice possibility to answer your question - e.g. by using a multi-select.
Improvements
- Moved Chinese NLU to our new and improved NLU system
- Improved our analytics-reporter service and add support for extremely huge analytics-data-sets
Bugfixes
- Fixed a bug where the
service-parser
queue could fill-up and get blocked over time. - Fixed a bug where answer tokens would no longer be available in Processes
- Fixed a bug where realtime-analytics in our product UI would not refresh correctly
3.5.2
Released: March 16th, 2020
Improvements
- Updated our integrated WebchatWidget to version 2.16.0
- ensure that sessionStorage is being used instead of localStorage for the Webchat-Demo page in our product
Bugfixes
- Fixed a bug where NLU exact-matching could break in certain circumstances
- Fixed several issues related to our CognigyScript Text-Field
- Fixed a problem in the Playbook-execution which lead to Playbooks failing when they ran multiple times in a row
- Fixed a problem related to the YN-Question Node
- Fixed an issue where changes in a Think Node could not be saved when the user interface language was not set to English
- Fixed a bug where certain settings on the Flow-Analytics page would not work
- Fixed a bug where analytics-data was not kept when entering a Process
- Fixed an inconsistency for ci.understood when the Execute-Flow Node is used
- Fixed a Google-related issue when NO_INPUT intent gets triggered
- Fixed an issue related to non-deterministic Intent-Training for huge Lexicons
- Fixed an issue related to the Reject-Intent
3.5.1
Released: February 26th, 2020
Improvements
- Updated our integrated WebchatWidget to version 2.14.0
- Allow users utilizing certain browsers to close our user interface without an additional confirmation
- Improved our export feature in a situation where Flows with attached Cognigy Flows (e.g. Smalltalk) or attached Cognigy Lexicons would take longer than usual
- Added support for AU, GB & CA English within the Date Picker in Cognigy Processes
- Added full support for data-redaction for our Alexa-Dashbot integration
- Added the ability (opt-in) to configure an account-lock which will disable accounts after n consecutive login fails
Bugfixes
- Fixed a bug where the meta-data shown for a Cognigy Secret would be incorrect after import
- Fixed a bug where an Endpoint could not be renamed when it was not loaded into our frontend beforehand
- Fixed a bug which occurred when an Intent-reconfirmation was negated - this lead to a
AI Flow Promise Failed
error in the logs - Fixed a bug where preview elements in the SayNode-Editor would have overflow-issues in certain browsers
- Fixed a caching related bug with Cognigy Processes which occurred after import
- Fixed a bug related to additional confirmation words for languages based on our new NLU pipeline
- Fixed a bug where an empty text-input would trigger NLU_UNAVAILABLE
- Fixed a bug where special characters in keyphrases would cause issues during Intent mapping
- Fixed a bug where uploaded lexicons without synonyms would have empty synonym entries which could not be deleted
- Fixed a bug where large packages could not get exported during a 2-minute timeout
- Fixed a bug where default replies could not contain a $-sign within their data-object
- Fixed a bug where Cognigy resources would only allow ASCII characters for their names
- Fixed a bug where the password-reset functionalities email field was case sensitive
- Fixed a bug where certain debug-information would be printed multiple times below each other in the Interaction Panel (and multiple times)
- Fixed a bug where the wrong Action-Flow was executed after import
- Closed a security vulnerability which was related to password hashes
- Fixed a bug where certain queues within RabbitMQ would not have the correct auto-delete flag set and would forever remain in the message broker even if they were no longer used
- Fixed a bug where date-slots were incorrectly cached in our new NLU pipeline and for new languages
- Fixed a bug where the Intent-download (CSV & JSON) would not contain "learned sentences"
- Fixed a bug where our Slack integration would not properly work as Slack has changed their data-format slightly - this would produce an endless-loop within new Slack-bots
3.5.0
Released: February 6th, 2020
Features
RingCentralEngange extended Handover
We have introduced the RingCentralEngange
endpoint already some releases ago. With this release, we have added full support to use their platform if a user wants to talk to a real agent. Customers can now pick whether they want to use our Cognigy Livechat
tool or RingCentralEngage
for handover scenarios.
French NLU
We have introduced French
as a new officially supported language in our product. Please consult our installation- & dev-ops manual in order to get all details on how this new language can be enable on an infrastructure level.
Endpoint transformers
We have added a new feature called endpoint transformers
to all endpoints (a ka channel connectors) within our platforms. Endpoint transformer allow you to extend our system and make it compatible with new foreign systems. You can now, e.g. create a Webhook
endpoint and add the necessary input/output transformers
which will extract the necessary information from the request payload - this way, you can add support for a platform like KakakoTalk
without relying on us to actually build an integration with them! Please consult our documentation for example implementations and further documentation.
Audiocodes enpdoint
We added support for the Audiocodes Voice Gateway
which allows you to call your virtual agents you can build within our product.
Increased security
We added support for configurable password policies and will now give admins the ability to avoid the reuse of old passwords when developers need to change their passwords. The whole functionality is hightly customizable through our management ui
interface.
Improvements
- Updated our integrated WebchatWidget to version 2.13.0
- Improvements to our
Japanese
NLU engine - Improvements to the platforms overall security by changing multiple security-relevant functionalities like the
change password
functionality - Added support to configure the
password policy
which is used for our product - Improve the
NLU training
performance by improving our multi-threading support - Improved our `
Dashbot support
for the two channels Alexa & Google - Added support for exporting
default reply data
within Intents - Improve the stability and throughput of our
new NLU pipeline
which is currently being used forKorean
,Arabic
&Japanese
- Added support for the
Amazon.StopIntent
in Processes - Rename
Smooch
toSunshine Conversations
- Improved performance of our
Import
tool by avoiding unnecessary memory allocations - Improved our
hot-key
support within the Flow Editor
Bugfixes
- Fixed a bug where the
Webchat tab
in our Say Node would disappear when you try to write text in certain browsers - Improve the security of our platform by further blocking excessive authentication attempts
- Fixed a bug where Intents within
Japanese
Flows could not be trained in certain conditions - Fixed a bug where the
License is invalid
message would not be displayed correctly in our user interface - Fixed a bug where
Japanese Intent reconfirmation
sentences would not be send - Fixed a bug related to
Keyphrase mapping
and special characters - Fixed an overflow bug in our user interface for the
Textfields
in ourFacebook tab
within the Say Node - Fixed a bug where
text redaction
would not work properly for ourDashbot integration
- Fixed a bug where
default replies
from theFacebook tab
would not be displayed in FB messenger - Fixed an
api-key
related bug - Fixed a bug where
livechat records
would not show-up in our ODATA feed - Fixed a bug in the
Playbook editor
where a click on the drag handles for Playbook steps would reset the current scroll position - Fixed a bug where the
URI
to a custom RingCentralEngange platform could not be specified - Fixed a bug where the
case sensitive Intent mapping
flag would not display correctly in some browser and some NLU language combinations - Fixed a bug where our
Export
could break in some situations - Fixed a bug where
Non ASCII resource names
would break ourExport
tool within our product - Fixed a bug where certain messages within the
Interaction Panel
could not be displayed in theFirefox browser
- Fixed a bug in the
default replies
editor - Fixed a bug where our
ODATA interface
returned data which would lead to multiple requests from tools likeMicrosoft PowerBI
3.4.4
Released: December 20th, 2019
Improvements
- Updated our integrated WebchatWidget to version 2.11.0
- Added a new API endpoint which can be used to drop raw analytics records using various search patterns
- Added the ability so you can jump into Processes from within a runProcess Node
- Added the ability to define a custom encryption key for import/export packages, please have refer to our installation- and configuration documentation
- Added support for Facebook endpoint message validation, please refer to our updated documentation for Facebook endpoints
- Added the ability to use input sanitization in our WebchatWidget, please refer to the WebchatWidget documentation
- Added a proper error-object to the Context if an operation exceeded the current Context size limit
- Added the ability to use CTLR+F to open the seachbox in the Flow Editor
- Added the ability to define the FROM field within SMTP connections, this is an opt-in, please refer to our installation- and configuration documentation
- Improved our Dashbot Webchat support by adding data-mapping for our own Webchat and its data format
Bugfixes
- Fixed a bug in our keyphrase-matching algorithm for Japanese
- Fixed a bug where keyphrase-matching with latin uppercase characters would fail for Japanese
- Fixed a bug where keyphrase-based questions in Processes would not work properly when keyphrase span across multiple words
- Fixed a bug where
ci.currentTime
was not set for Alexa - Fixed a problem where Chinese NLU would not properly start because if an improperly packaged NLU model
- Fixed a bug where a person with
developer
role could not update Tokens within a project - Fixed a bug where customers could not use Custom-Modules together with a private NPm registry
- Fixed a bug where the Contact Profile of certain Facebook users would not be filled correctly
- Fixed a bug where keyphrases with numeric literals were not found as expected
- Fixed a bug in the new analytics on the project-overview where the data could overflow
- Fixed a bug in our httpRequest Node were caching was not working properly in some circumstances
- Fixed a bug where ending a session for Google actions would not work on Dialogflow
- Fixed a bug where user inputs within a Process would not show up in the ODATA analytics records
- Fixed a bug where analytics records were not correctly stored when returning from a Process back into the Flow Editor
- Fixed a bug where our Flow Editor could crash when used in Korean language
Deprecation warning
Facebook quick replies
Facebook removed the ability to send your location
within quick replies. We adjusted our product and also removed the necessary user interface to create such quick replies. Please ensure that you are no longer using this feature in your Facebook Messenger based agents.
3.4.3
Released: December 3rd, 2019
Features
Korean
We added support for Korean as a new language within our system.
Arabic
We added support for Arabic as a new language within our system.
Advanced Dashbot integration
We enhanced our support for our Dashbot analytics integration. Our customers can now also use native Dashbot channels
(like Facebook, Alexa, etc.) next to the universal
connector.
Improvements
- Updated our integrated
Webchat
to the2.10.3
release - Improved
performance of our user interface
on the project-page - Added new analytics widgets on the
projects page
giving you feedback about flow-usage and their intents - Improved
ODATA data caching
so huge data-sets can be retrieved through the analytics interface - Improved the stability of our
Intent Trainer
- Improved the stability of the
Google WYSIWYG
editor
Bugfixes
- Fixed a bug where
Alexa
would crash inCognigy Processes
when aKeyphrase question
was used - Fixed a bug where
attached Flows
could not be trained in certain conditions (data corruption) - Fixed a bug where the
MongoDB
connection of individual services could not be re-established when connected to aMongoDB replica-set
in certain conditions - Fixed a bug where
Keyphrase detection
would fail in English on contractions - Fixed a bug where
Synonym usage
within example sentences ofIntents
would not work correctly forJapanese
- Fixed a bug where the
Intent Tester
would not output the same intent scores compared with the Interaction Panel for Asian languages - Fixed a bug where
text and quick replies
would not be displayed correctly in ourLivechat tool
- Fixed a bug where the
conversation history
within ourLivechat tool
would load very slowly - Fixed a connectivity related problem in the
Livechat tool
which would lead to poor user experience - Fixed several problems in our
Import/Export
functionality within the product so it can also handle huge projects - Fixed a bug where
saving Intents
would not work while bots were updatingexample sentences
- Fixed a problem where
location permissions
would not work inDialogflow
in certain conditions - Fixed a
memory related
problem within the message broker we are using - Fixed a bug where the
Interaction Panel
could crash when a project was still selected which no longer exists - Fixed a security related issue with projects
- Fixed a bug where the
Interaction Panel
could crash on specific inputs - Fixed a bug where
required questions
withinCognigy Processes
could be skipped - Fixed a bug where
Cognigy Script
would not work withinDefault replies
- Fixed a bug where the
Use Project Settings
button would not properly update within the settings page of a Flow - Fixed a bug where the
Cas Sensitivity Setting
would not update correctly on the settings page - Fixed a bug where the
Flow Editor
could crash in a certain condintion within aswitch Node
Documentation
- Improved documentation for
mask sensitive logging
andmask sensitive analytics
3.4.2
Released: November 11th, 2019
Features
RingCentral Engage
We now have an official RingCentral Engage endpoint which allows connecting Cognigy.AI with RingCentral's platform for agent-handover.
Improvements
- Added the ability to use our
User Interface
inKorean
language - Updated to
Node12
for our JavaScript-based microservices, this improves the overall performance of our platform - Update our integrated
Webchat
to the2.10.0
release - Added the ability to see the
project name
within a conversation
Bugfixes
- Fixed a bug in our
NLU services
where those could crash - Fixed a bug where our
service-parser
could crash in some situations - Fixed a bug where the
default replies
within anIntent
would always be random - Fixed a bug where our
NLU services
would experience higher load because sentences got scored multiple times for a single message - Fixed a bug in the
Intent Trainer
where a menu could grow outside of thebrowsers viewport
- Fixed a bug where the
case sensitivity
-flag would not get displayed correctly when not defined - Fixed a bug where our
tag replaced
andsynonym replaced
example sentences within Intents would not correctly use the case sensitivity flag - Fixed a bug where
SSO
users would get a strange error when they tried to use thepassword reset
functionality on our login screen
Notes
- Fixed a problem in our api-documentation for projects and the color property
3.4.1
Released: October 18th, 2019
Improvements
- Added the ability to use our
slot parsing
when thecIntent feature
is used to inject an intent - Added the ability to use
capital
letters foranswer-ids
within Processes - Update to newer
MongoDB
driver in order to fix an issue withreplica-sets
and re-connection when a newmaster node
gets elected within a replica-set - Added a way how an
admin
can retrieveall projects
via our REST API, not only the assigned projects - Removed
potential sensitive information
from a JWT payload - Improved performance for our
logging
service - Add support for
message_referrals
event-type for our Facebook Endpoint - Improved
Chinese NLU
- Improved overall system performance by reducing the
number of queues
withinRabbitMQ
- Removed the ability to allow clients to request the type of supported
http methods
- We added a new field to the
input object
-endpointType
. This field is more reliable thanchannel
to determine which type of endpoint is used to talk to a Flow - Slightly adjusted the
rule editor / condition editor
functionality to better visualize what will be evaluated during runtime - Improved our
any slot
feature - Improved
Webchat compatibility
when theWebchat demo page
is used e.g. behind a API-gateway - Updated bundled
Webchat version
to2.9.1
, see our GitHub release
Bugfixes
- Fixed a bug where the
query
field within ourSQL nodes
was not multiline - Fixed a bug where the
CTL+B
hotkey would sometimes not work properly in the Interaction Panel - Fixed a bug where the
Webchat demo page
would not render the background image correctly in different browsers - Fixed a bug where
SQL connections
would break when an error occurred on the connection (e.g. error in query) - Fixed a bug where
multiple custom nodes
could not have afunction with the same name
- Fixed a bug where
special
characters where not handled correctly forTwilio
- Fixed a bug where
slot assertions
would not properly work in Playbooks - Fixed a bug where the
Interaction Panel
would crash when Playbooks steps would get deleted while Interaction Panel is executing the Playbook - Fixed a bug where
Google Actions cards
would not always show up when multipleSay nodes
are used - Fixed a bug where
multiple recipients
would not properly work for thesendEmail node
- Fixed a bug with
multiline fields
within the Process Editor - Fixed a bug where
empty Synonyms
could be created within the Lexicon Editor - Fixed a bug where the Interaction Panel could break when
no projects
are assigned to a user - Fixed an
api-key management
related problem for certain users - Fixed a bug where a
switch node
could not get deleted in some circumstances - Fixed a bug where
reparse slots
forAlexa
would not work within Processes - Fixed a bug where the
Intent Trainer
ui would not work properly - Fixed a bug where an old
http request
node could not be re-saved - Fixed a bug related to
default replies
in executed Flows - Fixed a bug related to
no NLU
andexecute flow
- Fixed a bug where a
switch node
could not be deleted when it has no child-nodes anymore - Fixed a bug where our
inject/notify
APIs would not work for facebook & webhook endpoints in some situations
Notes
- We introduced a limit on project-names - names are now limited to 60 characters
- We adjusted the
resource constraints
forservice-logs
(Docker Swarm, Kubernetes) - We adjusted the
nlu ZH resource constraints
forservice-nlp-score-ZH
andservice-nlp-train-ZH
3.4.0
Released: September 18th, 2019
Features
Project templates
We added a new wizard
that supports you when creating a new project within our product. The product can now get bootstrapped from one of our English / German
project-templates which help you to get started even faster.
Twilio Autopilot
We now officially have a new endpoint for Twilio Autopilot
! This endpoint allows you to connect autopilot to Cognigy.AI and use autopilots NLU capabilities. In addition, this endpoint also has a new built-in
NLU connector that helps you to translate the NLU outputs of autopilot into the Cognigy.AI format.
Microsoft Bot Framework
We now have a Microsoft Bot Framework endpoint. This allows you to use adaptive cards
in e.g. channels like Microsoft teams
. Fields within those cards which have an id
and a prefix
of cognigy_
will trigger our NLU engine.
Userlike
We now have an official Userlike endpoint within our product.
Intent injection
We added the ability to directly trigger an intent by sending an arbitrary text-input pre-fixed with cIntent:
. Customers can use this within their e.g. rich-media payloads to directly trigger an intent if a user e.g. clicked a certain button.
Intent trainer records import & export
We added the ability to import/export intent trainer records. Customers can use this feature to export intent trainer records
from e.g. their production environment, import them into their dev environment and refine their bots, there.
Overwrite analytics-data
We added the ability to overwrite certain analytics properties within Code nodes
. This allows customers to implement their own logic to e.g. set the understood
or intent
field, right before we store them.
Inject & Notify API for more endpoints
We made our inject
and notify
APIs compatible with a wider variety of endpoints
. Customers can use these APIs in projects where long running
processes get started by a bot and where the process will come-back to the bot after a longer period of time.
Any-slot
We added a new concept to the example sentences
of ML-intents - the so-called any slot. Any-slots will be highlighted within example sentences and have a syntax of <<slot>>
.
Rich-media editor for default replies
We added the ability to use the very same editor you are already using in say nodes
for our default replies
. This allows customers to send back rich-media (e.g. a gallery) when a default reply
was triggered.
Intent tagging & searching
We added the ability so intents can be tagged
. Developers can then search through their intent-list by name
and by tag
.
Organization level quotas & limits
We introduced the ability to set organization specific quotas and limits. This is especially interesting for our customers who are using our product in multi-tenant mode.
Typescript & Code-Nodes
We have slightly re-styled our Code-Node editor and added full support for Typescript
! This allows customers to use the power of Typescript and e.g. define Interfaces
and use them within their Code-Nodes. The feature is meant for developers and power-users who have large Code-Nodes in place. Simply write Typescript into your Code-Nodes - we will transpile it to modern JavaScript and execute it.
Improvements
- Removed an internal error message that would get displayed
in the UI
even though everything is fine - Changed the way how the
webchat demo page
isolates theendpoint token
from the URL. This helps to support API gateways that might sit in front of a Cognigy.AI installation. - We slightly improved our
NLU for German
and added the wordsofort
to be handled correctly (similar tojetzt
) - Improve our
Japanese NLU
- Improve security on
users
page by not exposing theemail
within the browsers URL. We are now utilizing the underlyinguser id
- Improved security on our
livechat
where agents could see chat-requests with bots in projects they had no access to - Expose
http response headers
within the context when ahttpRequest
node is used to send requests - Adjusted location for
tooltips
displayed onselect fields
within thetoolbar
of our application. The old tooltip location would often interfere with the mouse-cursor and would make some select fields not editable - Introduce a new menu to delete
custom modules
more easily - Improve the
editing experience
forlexicon tags
andlexicon keyphrases
- We added the ability to
jump
into a flow if you open aexecuteFlow
orswitchFlow
node. This helps developers to navigate through their interconnected flows during editing - update our
geo ip
database so it contains the latestip ranges
for analytics purposes - Improve the information of
errors
when thrown e.g. inCode nodes
. This allows to developers to jump into the flow which produced the error - We added a
case sensitivity
flag to ourNLU settings
. Customers can now decided, whethercasing
should have an impact on e.g. their intent mapping - We added the ability to use a
hotkey
to save changes withinCode nodes
- We added a new return value for the
intent
field whenno NLU model was trained
. The input object will then contain an intent field with an appropriate information that intents need to be trained - We added the ability to use
system slots
for intent mapping within yourexample sentences
- We added the ability to
delete
,rename
andcopy
a project resource within theproject overview
- A Flow's language can now be
changed
after the flow was created - We added the ability to add a
label
to flow nodes - We added the ability to sort
intent trainer records
bycount
andtimestamp
- We added the ability to render
Microsoft adaptive cards
in theInteraction Panel
- We render information in the
Interaction Panel
when aswitchFlow
event occured. Users can also click on the name of the Flow to directly jump into it. - We now offer separate containers for
NLU services of different language
. This greatly improves the scalability of installations with multiple languages and higher load. - We improved our
ODATA interface
which can now be used to e.g. retrieveconversation data
- We added alphabetical sorting for
custom modules
in the overview page and within the Flow Editor
Bugfixes
- Fixed a bug where the whole
http response
was checked for its size, instead of theresponse body
- Fixed a bug where the request was
not anwered
directly after awebhook
endpoints payload was validated - Fixed a bug where the
project settings
would not get applied after aswitch flow
orexecute flow
node, this would result in anNLU timeout
in certain conditions - Fixed a bug where
typing on/off
indicators would also be emitted forsocket endpoints
even ifpure data
outputs are used - Fixed a bug where
Google actions
would not properly work whenkeep session open
was set to false - Fixed a bug where the
alexa verification
could not use aconfigured proxy
- Fixed a bug where
certain endpoint settings
would not be updateable - Fixed a bug where
reported analytics data
would not be visible after anexecute-switch flow
chain - Fixed a bug where the
reconfirmation question
would not appear, if anintent
has adefault reply
- Fixed a bug where
events from the server
would not correctly be delivered to our frontend application. This resulted in some long-running processes to not report correct data (e.g. notifications) - Reset the
NLP connector
toCognigy
when navigating into another project - Fix
negation
in ourNLU pipeline
- Fix a
caching issue
for ourODATA
analytics endpoint - Fixed a bug where
CognigyScript
withinconfirmation sentences
would not work properly - Fixed a bug where
implicit exportable resources
would show up multiple times within theexport wizard
(Import/Export feature) - Fixed a bug where the
intents need training
flag would never appear after a flow was imported - Fixed a bug where
analytics
would not get stored when adefault reply
was triggered - Fixed a bug where the
attachedFlow
view could sometimes crash and disappear - Remove the
EnableFileUpload
flag for the newwebchat
endpoint editor. The new webchat supports file-uploads through a custom file-upload plugin, which is not loaded by default - Fixed a bug with
incorrect line breaks
within aCognigyScript field
- Fixed a bug where a
system state license
error could get displayed after login - Fixed a bug where the
Facebook Messenger Endpoint settings
would sometimes not work and behave properly - Fixed a bug related to
Google CANCEL intent
in Cognigyprocesses
- Fixed a bug where the
intent trained
status would get reported the wrong way - Fixed a bug within
SMTP connections
were you could not reliable sendemails
from within our system - Fixed a bug where a
project
could not get created when a project with the same name was deleted beforehand - Fixed a bug where
ci.data
would get lost in theAlexa payload
when a user answered a slot question
Deprecation Warning
Old CognigyScript syntax
With this release we are moving forward and dropping support for the very old CognigyScript
syntax. We have introduced the new {{ }}
syntax already with Cognigy.AI 3.0.0 and this should not impact most of our customers. Please still double-check your flows whether you are using any of the following:
<cs>some script</cs>
, replace it with{{ some script }}
<cc>contextValue</cc>
, replace it with{{ cc.contextValue }}
<ci>text</ci>
, replace it with{{ci.text}}
You might also have some weird combos of the above statements, e.g.:
<cs>cc.value</cs>
, replace it with{{cc.value}}
.
The current syntax has a lot of benefits compared to the old one, is more readable and actually fixes security vulnerabilities.
3.3.3
Released: July 4th, 2019
Features
Smooch
We now officially have a new endpoint for Smooch
! This endpoint allows you to support a new variety of channels Cognigy.AI was not compatible with, yet! You can now e.g. use WhatsApp
and other phone-based messengers.
Values Input Object
We added two new fiels to the Input Object
:
- hashedIp: Contains the
sha1
of the clients IP address - flowName: The name of the flow the Input Object was generated for
Source property
We added a new source
property to the output of various endpoints. This allows customers to understand the origin of messages.
Configurable Get Help
We added the ability to configure the URL source
of our Get Help
button. Customers with on-premise deployments of Cognigy.AI can e.g. add a link to an internal support-channel / helpdesk.
Thai NLU support (Beta)
We added Thai as a new language to our product. This language needs to be specifically activated on the infrastructure-level. It is currently in beta - we are happy to get feedback from our customers!
Lazy connections
The Webchat will now only establish a connection to our infrastructure when the .open()
API was used.
Improvements
- Add support for
CognigyScript
within validation fields of Processes - Improve the data we send to
Dashbot
so customers have richer data points withi this analytics solution - Set the
Not Handled
intent forDashbot
- Add full
proxy support
forCustom Modules
so NPM installs will go through a configured proxy - Improve security for code execution within
CognigyScript
andCode Nodes
- Improve MongoDB
replica set
support for our services - Improved our
NLU pipeline
so messages would never get scored multiple times - performance improvement
Bugfixes
- Fixed a bug where the
Amazon.CancelIntent
could not be used to end a process - Fixed a bug where certain queues could not be deleted from RabbitMQ resulting in errors
- Fixed a bug where
Intents
in Processes where always used from thelatest locked
version - Fixed a bug where chaning the
NLU settings
in Flows with many intents could sometimes time-out - Fixed a bug where
Intents
of adeleted attached Flow
would still get parsed during Flow execution - Fixed a bug where
interactive messages
could not be used for our Slack channel - Fixed a bug where the Flow Editor would crash when saving an empty
start Node
- Fixed a bug where the
Datepicker
within the Webchat would not output the correct locale format - Fixed a bug where a field within the
Contact Profile
could be updated that was not designed to be updatable - Fixed a bug that would crash
one
of ourNLU services
- Fixed a bug where the new
Webchat
could not properly connect within IE11 and Safari - Fixed a bug where
December dates
would be not correctly identified within our NLU pipeline - Fixed an issue where
Google
would no longer send auserId
within their request payloads
Documentation
- Improve our API documentation
3.3.2
Released: June 3rd, 2019
Features
Environment tags
We added the ability for customers to add labels to their on-prem installations. This can be achieved through setting the ENVIRONMENT_TAGS
environment variable to a comma separated list of keywords. The keywords will be exposed in the Cognigy Input object
during Flow runtime. The tags can e.g. be used for conditional branching based on e.g. your dev
and prod
environments for httpRequest
nodes.
Contact Profiles creation API
We added the ability toc reate a new Contact Profile using our RESTful API. Contact Profiles get created automatically during Flow execution. The new API allows the creation of a profile in advance.
Clean RabbitMQ disconnect
All services will now properly shutdown when RabbitMQ gets unavailable during runtime. Cognigy services will no longer be in an undetermined state after a RabbitMQ restart.
Project wide search
We added the ability to search for project resources within the Project overview
. This is especially handy if you deal with huge Cognigy.AI projects that contain a high number of resources such as Flows, Lexicons etc.
Intent editor role
We added a new user-role to our product that only allows read- and update-permissions for intents. This role is perfect for editors who will use the Intent Trainer
to modify and update your Conversational AIs within Cognigy.AI.
Improvements
- Add full support to use a
system web proxy
for outgoing connections toAmazon services
- Allow the execution of
Flows
of a different language, please read our documentation https://docs.cognigy.com/docs/execute-flow - Auto-generate
Process Input fields
based on the given label - Improved the situation where the
Successfully trained Intents
notification would get displayed to often - Improved typings of
sytem slots
withinCode nodes
- Improved the preview of certain
graphical components
within theSay node
(Cognigy Script parsing) - Improved the way how connection-details for the RabbitMQ API could be specified (connection string using
secret
) - Improved scrolling behaviour of the
Interaction Panel
- it will now preserve its scrolling position if you e.g. open the settings tab - Various Webchat improvements, see our
Releases
page on Github: https://github.com/Cognigy/WebchatWidget/releases - Improved the visualization of
Custom nodes
within theFlow editor
by swapping the title and module name - this improves readability - Improved sorting within the
speed dial
when creating newProject resources
- Added the ability to create
Portugese (Brazil)
flows - Improved
Spanish
andJapanese
translations for ourCognigy UI
- Improved the false-positive rates of our
NLU 2.0
andNLU 2.1
systems
Bugfixes
- Fixed a bug where invalid characters could be stored in
Contact Profile fields
- Fixed a bug where an error message was displayed when visiting the
project page
after anew user
was created - Fixed a bug where the
new Webchat
could not be used with theCognigy Livechat
- Fixed a bug where
Yes
andNo
answers to questions would not get stored in theConversation history
withinContact Profiles
- Fixed a bug where the list view within the
Schema Editor
would not get displayed in a correct way - Fixed a bug where the
Intent Editor
would crash - Fixed a bug where
exact Intent matches (score = 1)
would not be always possible - Fixed a bug where a
Custom module
could not specify a vieldversion
as one of its arguments - Fixed a bug where our
parser
service (used for CSV imports within theLexicon Editor
) could not properly connect to MongoDB replica-sets - Fixed a bug where
Yes/no + switchFlow node
combination could break our intent-mapping - Fixed a bug wwhere certain
special characters
could break theRegex mode
within ourslotQuestion
node - Fixed a bug where the
Webchat
icon within theSay
node would never get highlighted, even if it contained content - Fixed a bug where certain special characters could
not be used
within yourCognigy password
- Fixed a bug where
data only messages
would not get discarded during intent mapping - Fixed a bug where
YN Questions in processes
would not be recognized for theAlexa
channel - Fixed a bug where our NLU systems would not give you a
1.0
score in certain situations
Documentation
- Improved documentation on
system slots
that get automatically detected whenCognigy NLU
is used. You can find the improved documentation following this hyperlink: https://docs.cognigy.com/docs/lexicon - Improved documentation on
Dialogflow V2 NLU connector
documentation. You can find it here: https://docs.cognigy.com/docs/dialogflow-nlu-connector - We renamed our NLU system-version to
Cutting Edge
andStable
. The naming with numeric versions was to confusing for some customers.
3.3.1
Released: May 09, 2019
Features
MongoDB connection string
Add the ability to configure the connection string for MongoDB using a docker-swarm/kubernetes secret. This is a more secure procedure than setting connection related information using environment variables.
RabbitMQ connection string
Add the ability to configure the connection string which is used for RabbitMQ using a docker-swarm/kubernetes secret. This is a more secure way than relying on env variables to store those type of information.
Import/Export for secrets
We added the ability to import/export secrets. Secrets within our import/export packages are still fully encrypted in addition to the encryption of the package itself. This now allows you to be more flexible and e.g. migrate your important credentials and sensitive information from one to another installation.
Dialogflow NLU Connector V2
We added support for API version 2 for our Dialogflow NLU connector. This now finally allows customers to use the modern version of the Dialogflow NLU. We are still supporting the old V1 API.
Flow overview
Added flow parent id and flow version id to the flow overview page. These values are necessary for certain API requests and were not displayed until now.
Improvements
- Removed
conversationId
field from dashbot payload. Dashbot had issues with this field being send - Added
sessionId
to output data for Webhook endpoint/channel - Sorted
Intent names
within a case-nodes alphabetically - Added CognigyScript support for
executeFlow
- &switchFlow
-nodes version fields
Bugfixes
- Fixed a bug where
CognigyScript
could not be used in keyphrase tag withinKeyphrase questions in Processes
- Fixed a bug where the original request was not available in
ci.data.request
for our Slack endpoint/channel - Fixed a bug where the setting
continueFlowAfterNegativeConfirmation
could never be changed - Fixed a bug where the user interface session would time out if multiple tabs are open
- Fixed a bug where the
Endpoint version dropdown
was sometimes not populated correctly - Fixed a bug where the
url
field withinhttpRequest
nodes was not trimmed - Fixed a bug where a
list item
from aFacebook List
(say-node) could not get deleted - Fixed a bug where
cp.profileId
was not always populated on the first message - Fixed a bug where a
think
-node within anexecuteFlow
could cause issues. - Fixed a bug where
Japanese lexicon entries
were sometimes not recognized correctly in sentences - Fixed a bug where the
Intent Trainer
would display empty records
3.3.0
Released: April 12, 2019
Features
Chinese NLU
We added full support for Chinese NLU, meaning you can now build Flows in Chinese.
Spanish NLU Improvements
We improved our Spanish NLU, especially when handling accents in sentences.
NLU 2.1
We added a new NLU version that greatly improves intent detection and has better support for short utterances.
Single Sign-on
We added the ability to login into COGNIGY.AI and to create users via Single Sign-on (SAML 2.0).
Secure Login
We improved the seuciryt of our platfomr by blocking repeatingly failed login attempts.
Tokens
We introduced Tokens, which can be used in Flows and Processes as shortcuts for CognigyScript. Tokens can be defined from developers using the new Token Editor. Your business users can then re-use those Tokens wherever they could use CognigyScript in the past. If the required Tokens exist, coding is no longer required within the platform to generate dynamic content within e.g. Say-Nodes.
Rule Editor
The Rule Editor is a new way which can be used together with Tokens in order to define conditions for logic branching. The Rule Editor works within the Cognigy Flow Editor as well as the Process Editor. It greatly reduces the amount of Cognigy Script that needs to be composed in order to support conditionals within your business logic.
Process Action Inputs / Outputs
In order to improve the workflow with Action-Flows within the Process Editor, we implemented the concept of Action Inputs/Outputs. Developers building an Action Flow can now define that those special Flows need certain Inputs to work properly. The Process Editor will re-use these information and render input-fields within the Process Editor. Furthermore, Cognigy will generate Tokens for your Action Flows and make them available within the Process Editor.
Custom Modules for Everyone
We changed the way how we execute Custom Modules, so that the execution of unsafe code is no longer a problem for the whole platforms stability. Thus allowing any developer to upload and test their Custom Modules without going through our review pipeline.
New Webchat (2.0)
Our Webchat was completely rewritten. The first iteration of the Webchat was already used by a vast majority of our customers. The new iteration of the Webchat is written in modern React and has a fully documented plugin architecture, which allows you to extend it.
We also introduced a new Date-Picker which uses the new Webchats plugin architecture and comes in a completely refresh design. There is even a new Flow-Node which let's you ask for dates in a new way.
Translated UI
We now have a fully translated UI in English, German, Japanese and Spanish - more languages to come in the future.
Blind Mode
More and more customers implement Conversational AIs dealing with sensitive information from users. In order to support the processing of sensitive data through Cognigy we introduced a new Flow Node and functionality within our software: The so-called blind-mode. This mode can either be activated through a Flow Node or through a setting within your Endpoints. Once activated. COGNIGY.AI will no longer store sensitive information such as the users text within system logfiles and analytics-data.
Intent Dropdown in Case Nodes
One of the most requested small features for 3.3.0 was a simple one and it landed within this release: If you now create a Switch-Node and select Intent from the dropdown, you will now be able to create Case-Nodes which contain a dropdown of all available Intents! You can still have a Text-Field available.
Settings Tab for some Flow Nodes
In order to remove some confusion from some of our Flow Nodes, we extracted certain settings and created separate Tabs within those Flow Nodes. Once candidate e.g. was the YN-Question-Node. It had certain settings in the "Default" tab which were actually used for all channel-outputs.
Bugfixes
- Fixed a bug where the
Send Email Node
couldn't send emails to multiple addresses - Fixed a bug where out-of-range dates were recognized (e.g. 31st of August)
- Fixed a bug where
yesterdays
were not recognized as a date. - Fixed a bug where
CognigyScript
didn't work indefault replies
- Fixed a bug where the
$push
operator couldn't be used in the MongoDB Nodes - Fixed a bug where the
Regex slot filler
did not work properly - Fixed a bug where
Lexicon synonyms
where not trimmed on ipmort - Fixed a bug where
Users
in theAccess Control
list were not sorted - Fixed a bug where
CognigyScript
didn't work inCase Nodes
- Fixed a bug where the
Flow search
crashed in rare scenarios - Fixed a bug where
Custom Modules
couldn't be executed in attached Flows - Fixed a bug where
additional confirmation words
couldn't be more than one word - Fixed a bug where the
Intent training status
would be incorrect
Deprecation warning
Flow Nodes
The following Flow Nodes
are now officially depcreated and will be removed in our next major release (4.0.0):
- setNextFlow (synonym for
switchFlow
) - copyKeyphrasesToContext (synonym for
copySlotsToContext
) - sayInterval (use a
say Node
behind ainterval
) - sayOnce (use a
sayNode
behind aonce
) - thinkOnce (use a
think
behind aonce
) - setContext
- askYNQuestion (we have a newer implementation!)
- askGenericQuestion (we have a
askSlotQuestion
) - retrieveMemoryWh
- retrieveMemoryHow
- getRequest (use
httpRequest
with methodGET
) - postRequest (use
httpRequest
with methodPOST
) - putRequest (use
httpRequest
with methodPUT
) - deleteRequest (use
httpRequest
with methodDELETE
)
API
The following API-paths will be removed within Cognigy 4.0.0:
- /contact/:contactId
See our API reference guide for guidance on how to upgrade to a newer API.
3.2.5
Released: March 14th, 2019
Features
Welcome message for the demo environment
We added a welcome message that will be sent in the beginning of all conversations on our demo environment.
The welcome message will not be sent when testing in the Interaction Panel
Bugfixes
- Fixed a bug where
Facebook list buttons
would render incorrectly in the interaction panel. - Fixed a bug where
Alexa skill simulation
in theInteraction Panel
didn't work. - Fixed a bug where
custom module uploads
would notify everyone in the organisation - Fixed a bug where
intent training
would take a long time in some scenarios - Fixed a bug where the
date format
in thenews section
were not locale specific - Fixed a bug where low access right users couldn't edit
Flow Nodes
they had access to - Fixed a bug where the
license page
was missing the background image - Fixed a bug where only the
latest Flow version
could be selected inEndpoints
3.2.4
Released: February 27th, 2019
Features
Timestamps for messages within Contact Profiles
We added timestamps on top of
each message within the Contact Profile view. This helps to understand when individual messages got composed.
Healthchecks for NLU
We added Docker healthchecks and implemented the necessary changes for healthchecks to work. Orchestrators such as Docker Swarm
or Kubernetes
can use these healthchecks to validate whether services are already fully initialized after starting - or still fully functional after running for a while. In case a healthcheck fails, the orchestrator will kill the container and create a new copy of it.
Train Intents
We changed the behaviour of the train intents
button so the button can always be clicked. In case COGNIGY.AI is already training a model for a Flow, an appropriate error will get displayed.
Intent Trainer adjustments
We introduced the Intent Trainer months ago to help our customers to refine their bots during they are online. We realised though, that the combination between saving and training intents was quite bad and lead to bad performance related to longer training times.
We therefore separated the functionality to store modifications within the Intent Trainer and to train intents later on. This goes hand-in-hand with the Train Intents modification described above.
Facebook page subscriptions
When COGNIGY.AI is used together with the Facebook messenger platform, a page needs to get created with subscriptions. Facebook supports a wide variety of different subscriptions, such as message
, message postback
, message read
and others.
The only relevant subscriptions for COGNIGY.AI are message
and message postback
subscriptions. We have documentation in place describing the process of how to create a messenger endpoint properly. In case users added more subscriptions than the ones mentioned above (e.g. message read subscription), you could easily create an endless-loop of events.
We therefore improved the checks in our endpoint, so we only allow the supported subscriptions and log appropriate errors in case other subscriptions are used.
Japanese NLU
We improved our Japanese NLU system. This also improves the way how we handle keyphrases.
Rights Management
We improved the rights management for our UI system on various locations within our product. The API did already use the correct roles to deny certain modifications - but the UI did still render some input methods / buttons etc. We improved the rights management to make it more streamlined compared to our API.
UI language
We improved support for the Japanese language within our UI and added Spanish as a new language for our UI! We are happy to retrieve feedback from native speakers.
Google certificate
Google changed their certificate which is used to sign requests used for google account linking. We implemented the new certificate to guarantee, that our support for Google Actions is still working properly.
Bugfixes
- Fixed a bug where a new
tag
within the Lexicon Editor would not give users the chance to directly use this new tag withinexample sentences
using the[[-bracket
notation. They had to reload the Flow Editor first. - Fixed a bug where our
bleeding edge
NLU (2.0) was not used forAttached Flows
- Fixed a bug in the Webchat where
quick replies with images
had bad formatting - Fixed a bug where the
AGE property
in the input object was null (German) - Fixed a bug where
single-character / single-word
inputs would behave odd during execution - Fixed a bug where the
Handover for Facebook
would only work for the second message - Fixed a bug where an
on-blur
event on aConnection Password
would re-set it - Fixed a bug where the Flow Editor would render an incorrect Flow after an Intent was updated
- Fixed a bug where the name of a Custom Module would not be displayed in the
Custom Node
within the Flow Editor - Fixed a bug where the
Intent Trainer
would crash - Fixed an NLU-related bug where
day after tomorrow / day before yesterday
were not resolved properly - Fixed a bug where the
Whitelisted Domains
field within our Facebook Tools (Endpoint) was to narrow - Fixed a bug where
Google Suggestions
would not have an icon within the Interaction Panel - Fixed a bug where US date-recognition was incorrect
Documentation
- Improved documentation for the
export contact
API - Improved documentation for our Facebook tools, so customers know that they need to whitelist the
https://fbextensions.cognigy.com
URL to use the calendar widget - Added documentation on how to configure
CORS
for the API service (on-prem) - Added documentation on how to configure
SMTP
so the product can send emails used for e.g. password-reset (on-prem)
3.2.3
Released: February 6th, 2019
Features
- Add ability to make
CORS
configurable for ourapi
service - Introduce
multiple languages
for our COGNIGY.UI - this feature is in beta currently - Add ability to toggle the
searchbox
andzoom
components within the Flow Editor
Bugfixes
- Fixed a bug where the
CSV import
within the Lexicon Editor would not generate ids for keyphrases - Fixed a bug where the
handover
functionality was not working for oursocket
Endpoint - Fixed a bug where the
executeFlow
Node would reload Flows from slower data-stores instead of taking the fast cache (performance) - Fixed a bug where the
inherited Intents
within Processes would not work properly - Fixed a bug where
ci.slots
was not fully typed and you got errors displayed within Code Nodes - Fixed a bug within the
COGNIGY.AI installer
related to Docker Volumes - Fixed a bug where the
Interaction Panel
would expand inf. in Mozilla Firefox
Documentation
- Improved documentation for the
import lexicon
API - Improved documentation for
how to use
COGNIGY.AIbehind a corporate proxy
3.2.2
Released: January 24th, 2019
Features
- Added
conditions
to theGoogle Action Builder
- Added built-in
percentage slot
- Added
userId
andsessionId
to the response ofREST Endpoints
- Improved
intent mapping
forshort sentences
- Changed the way
message delay
works in the Webchat
Bugfixes
- Fixed a bug where
http requests
sent overhttps
couldn't be sent through aproxy
running on http:// - Fixed a bug where the
Google Action Builder
didn't resolvecontext variables
in thepreviews
correctly - Fixed a bug where
deleting a Flow
wouldn'tdetach
it from other Flows - Fixed a bug in
Account Linking
withGoogle Actions
- Fixed a bug in
intent mapping
when using only Rule Intents - Fixed a bug in
intent mapping
for certain languages - Fixed a bug in
analytics
where theFlow execution time
was displayed as higher than in reality - Fixed an issue in loading
large Flows
3.2.1
Released: Januray 9th, 2019
Features
- Improved
Monitoring
by measuringRPC calls
- Added
Typing Indicators
and artificialdelay
to theWebchat
- Improved
Caching
in the system
Bugfixes
- Fixed a bug where our
nlp
service would allocate to much memory in a certain condition - Fixed a bug within the
CSV
import within the Lexicon Editor - Fixed a bug in the
Webchat
wherelist button
was missing styling - Fixed a bug where the
Livechat link
would be displayed even if an environment does not host theLivechat
- Fixed a bug in the
Livechat
where the data would overflow (css) - Fixed a bug where the
NLU model
could not be trained and saved for a huge amount ofintents
- Fixed a bug in the
Webchat
where the topList element
didn't display properly - Fixed a bug in executing
Actions
not written inen-US
- Fixed a bug where the
Context tab
in theInteraction Panel
inFirefox
would expand infinitely - Fixed a bug where the
Interaction Panel
couldn't connect viaWebsockets
in certain network topologies
3.2.0
Released: December 12th, 2018
Features
- Add the new
Cognigy Livechat
product (Beta) - Added the ability to
edit
properties withinContact Profiles
- Add a new
graphical UI
to managecustom modules
- Add configuration option to select whether
Flows should stop
onnegative Intent
confirmation - Add a new resource-type called
Secrets
which can be used in conjuction withCustom Modules
to store sensitive information (api-keys, tokens, etc.) - Added the ability to execute
cognigy NLU
within the Flow using a dedicatedFlow Node
- Added the ability to select
No NLU
within Endpoints to complete disable NLU - Added the ability to
import / export
intents within the intent editor - Added the ability to
Upload an Icon
for a Flow - Added the ability to
tag
flows and give them a description - Added the ability to exchange the
Avatar
within theWebchat
- Added a new feature that allows users to explicitly mention
Lexicon Tags
within theirexample sentences
- Make the
Hybrid DNN NLU
system the default one, new Flows will use this type of intent mapping - Added the ability to for our
NLU
to findforward dates
only - Added the ability to
prefill answers
within a Form by injection - Added the ability to call
Actions
within a Form - Add
graphical UI
to install / update theCognigy.AI license
- Refined session-concept so users can now define a
session expiration
within their Endpoints. Conversations from the Facebook- and Google-Channels can now also havemultiple sessions
instead of only havingone global
session - Add the ability to make the
infinite loop detection
configurable using an ENV variable - Added a new way to specify the
connection strings
for Cognigy-internal services. This allows users to e.g. connect to areplica-set
- Minimized data written by the
logging servic
. This helps to maintain a smaller memory footprit ofMongo
- Added the ability to use CognigyScript for dynamic values within
executeFlow
andswitchFlow
Bugfixes
- Fixed a bug within the
Intent Trainer
where theno match
toggle would not work propery - Fixed a bug within the
Train Intents
logic, where the button would not be clickable when e.g. a Flow was detached - Fixed a bug where the
Train Intents
logic would throw an error if a Flow only hasRule Intents
- Fixed a bug where
Statistical NLU
results would get returned from attached Flows even though they are usingHybrid DNN NLU
- Fixed a bug where
ISO Dates
would have aZ
appended - Fixed a bug within the
Webchat
where button styles would overwrite styles within the embedding web-page - Fixed a sticky-session related bug for
Internet Explorer
in the Webchat - Fixed a bug where
Keyphrases
could not be deleted that contain a comma - Fixed a bug where the
HTTP Request Node
could not handle certainheaders
that contain an underscore - Fixed a bug where the
Import / Export
feature could timeout cause of intent training - Fixed a bug where
Mongo
credentials for our in-productDatabase Connection
resources would not URI encoded username / password - no special characters could be used
Deprecation warning
The following Flow Nodes
are now officially depcreated and will be removed in our next minor release (3.3.0):
- setNextFlow (synonym for
switchFlow
) - copyKeyphrasesToContext (synonym for
copySlotsToContext
) - sayInterval (use a
say Node
behind ainterval
) - sayOnce (use a
sayNode
behind aonce
) - thinkOnce (use a
think
behind aonce
) - setContext
- askYNQuestion (we have a newer implementation!)
- askGenericQuestion (we have a
askSlotQuestion
) - retrieveMemoryWh
- retrieveMemoryHow
- getRequest (use
httpRequest
with methodGET
) - postRequest (use
httpRequest
with methodPOST
) - putRequest (use
httpRequest
with methodPUT
) - deleteRequest (use
httpRequest
with methodDELETE
)
Documentation
- Refined documentation for
Connections
. SMTP-Connections are now also mentioned. - Added full documentation for our
Users API
3.1.9
Released: November 23rd, 2018
Features
- Added the ability to render messages in the Webchat that get send using
client.sendMessage
- Added the
Flow Name
to all analytics-records
Bugfixes
- Fixed a bug where clicking a
Facebook Gallery
link would not open the link within a new tab/window - Fixed a bug where the
adminconsole
channel was not removed from analytics-records - Fixed a bug where the
e
hotkey would open theFlow Node Editor
and would add the letter to the first text-field. The new hotkey now isSHIFT + ALT + E
- Fixed a security issue where potential sensitive data within
Endpoint configurations
could be retrieved from the server - Fixed a bug where the
Import / Export
feature would throwTimeout-errors
during exporting larger packages - Fixed a bug so the
Webchat
is compatible withIE11
- Fixed a bug where the
flowLogic
settings where cached in a wrong way
3.1.8
Released: November 9th, 2018
Bugfixes
- Fixed a bug in
number parsing
where 50.000 would be recognized as 50 in German - Fixed a bug where the
Webchat
inSafari
couldn't reliably connect to COGNIGY.AI - Fixed a bug where
Alexa
couldn't displayAPL
- Fixed a bug where conversations on
Google Home
would give new userIds throughout the conversation. - Fixed a bug in the
Intent Tester
where Statistical NLU scores where shown when Deep Learning NLU was selected - Fixed a bug where a user with limited
Access Rights
could edit and view certain resources - Fixed a bug where
Hotkeys
couldn't be used on newly createdFlow Nodes
3.1.7
Released: November 2nd, 2018
Features
- Added a natural and configurable message delay for the
Intercom
Endpoint
Bugfixes
- Fixed a bug where the
train intent button
could not be clicked if the project settings were not opened first (if project settings were used) - Fixed a bug where
Google Actions
Endpoint was handling the message concatenation of multiple say-nodes differently than anAlexa
Endpoint - Fixed a bug where the
odata
service would crash during caching large data - Fixed a bug where the
digits
for aTwilio Voice
Endpoint would not get added to theinput text
- Fixed a bug where the
Alexa Skill Verification
would not work - Fixed a bug where the
Smalltalk DE
Flow would sometimes answer since thethresholds
were wrong - Fixed a bug where the
Interaction Panel
would not renderhtml preview
for theWebchat
- Fixed a bug where the
understood
sentences would still show up within theIntent Trainer
3.1.6
Released: October 26th, 2018
Bugfixes
- Fixed a bug where the
select type
didn't work forcustom nodes
- Fixed a bug where some
Intents
inFlows
couldn't be saved - Fixed a bug where the full
Webchat configuration
could be accessed - Fixed a bug where some
Intents
couldn't be trained - Fixed a bug where
HTML
didn't render properly for theWebchat Preview
in theInteraction Panel
- Fixed a bug where
Intents
couldn't train if theProject Settings
weren't loaded
3.1.5
Released: October 18th, 2018
Features
- Add new
Microsoft Teams
Endpoint.
Bugfixes
- Fixed a bug where
Forms
didn't work when executed from anexecuteFlow Node
via a Rest Endpoint - Fixed a bug where a
Form
would crash during intent mapping in certain edge-case scenarios - Fixed a bug where
Contact Profiles
wouldn't be exported properly if they had several IDs - Fixed a bug where
Search and Replace
in the Flow Editor would stop if one node would be invalid after replacing - Fixed a bug where deleting a
Lexicon
wouldn't remove the attached Lexicon from Flows
3.1.4
Released: October 12th, 2018
Features
- Add full hotkey support for
Mac
- Add new
Intercom
endpoint - Add
typing indicator
for theFacebook Endpoint
- Add the ability to display an
update notice
within the product
Bugfixes
- Fixed a bug where
Webchat
always goes fullscreen on mobile devices - Fixed a bug where
Forms
would only output a max. number of fivequick replies
- Fixed a bug in the NLU-pipeline regarding
number detection
- Fixed a bug where
Analytics
would produce an error message in a project without a flow - Fixed a bug where
Context
could not be stored in case a. (dot)
or a$
was contained (this also had an impact on database-requests and http-requests) - Added missing 'Twilio SMS' logo to the
Twilio SMS Endpoint
3.1.3
Released: October 5th, 2018
Features
- Add ability to
copy
anURL Token
andWebchat URL
in theEndpoint Editor
if you click on it - Add new
Twilio SMS
endpoint - Add suport for receiving
Digits
via theTwilio (Voice)
endpoint
Bugfixes
- Fixed a bug where
simple resources
could not be exported - Fixed a bug where
async
would not work for theHttp Request
node - Fixed a bug where the
Facebook profile
would not get filled after a userreactivated
hiscontact profile
in COGNIGY.AI
Documentation
- Improved various aspects of the documentation
3.1.2
Released: September 28th, 2018
Features
- Add the ability so the
new Intent Mapper
can be enabledproject wide
- Add the ability to
export
a specific version of aFlow
Bugfixes
- Fixed a bug where
a
oran
was replaced by a number, this prevented hitting aKeyphrase
during execution - Fixed a bug where the
create resource
functionality on theproject page
would not work inMozilla Firefox
- Fixed a bug where
realtime analytics
could not be fetched when users had a high number ofFlows
within the sameproject
- Fixed a bug where
HTTP APIs
could not be used if they only return abasic value (string, number)
instead of an object in theroot level
of the response
Documentation
- Improve documentation on the
format
we expect yourCSV files
to be formatted for uploading them in theLexicon Editor
3.1.1
Released: September 24th, 2018
Features
- Bring back
executeFlow
andswitchFlow
on on-prem installations using an environment variable
Bugfixes
- Fixed a bug where
executeForm
would not work when anIntent
was triggered in the flow that was calling theexecuteForm
node - Fixed a bug where an
executeForm
within a sub-flows called usingexecuteFlow
would not work - Fixed various other problems in the
Form System
- Fixed a bug where huge
Lexicons
could not be processed - Fixed a bug where all
AI
instances would not recognize new keyphrases after aCSV
file was imported within theLexicon Editor
- Fixed a bug where
Custom Flow Modules (custom nodes)
would not work inSub-Flows
(executeFlow) - Fixed a bug where the
Intent Training Badge
would not display within theSidebar
of theFlow Editor
- Fixed a bug where certain messages could
get stuck
in theNLU pipeline
Documentation
- Added documentation on how to setup COGNIGY.AI on
Windows Servers
3.1.0
Released: September 14th, 2018
Features
- Add
search & replace
to theFlow Editor
- Add
undo & redo
to theFlow Editor
- Add the ability to filter the
Interaction Panel
for a certain channel, e.g.Alexa
- Improve the
Facebook Endpoint
so users can utilize tools to updatewhitelisted domains
and thepersistent menu
- Add a new UI for the
bleeding edge NLU system
- Add new languages to the
bleeding edge NLU system
, these areSpanish
andJapanese
- Update the
Unity3D
integration so it is fully compatible with the3.X
product branch - Add new
Dialogflow
endpoint - Add new
Twilio
endpoint, with integration for the ``Say Node``` - Add new
Google Actions
support for theSay Node
- Add new
Line Messenger
endpoint, with integration for theSay Node
- Add new
Forms 2.0
system with a complete rewritten UI - Add the ability to
logout
from Amazon - Add the ability to use
Custom Flow Nodes
to extend the system - Add the
Intent Trainer
customers can use to improve their bots over time - Reduce the size of all
docker images
which reduces the footprint of aCOGNIGY.AI
installation
Bugfixes
- Fixed a bug in the
German
date parser - Fixed a bug where the flow would not
inherit
the correct intents - Fixed a bug where a user could get
stuck in the form flow
when no form was loaded
Deprecation warning
The following actions
where removed from Code Nodes
for security reasons and can no longer be used.
Please use our appropriate nodes like Switch Flow
if you need this functionality. We removed the following
actions from Code Nodes
:
checkThink, deleteSystemContext, executeFlow, switchFlow, executeForm, getCache, getLastTopic, getSystemContext,
interval, once, resetFormBrain, setCache, setLastTopic and setSystemContext
Please ensure that your productive flows are not using these methods within Code Nodes
.
3.0.8
Released: August 31rd, 2018
Features
- Add
japanese
intent mapping to the product (beta) - Add
japanese
parser withyes/no
phrases - Restructure the
Endpoint Editor
so users get more prominent feedback toselect a traget flow
for their endpoints
Bugfixes
- Fixed a bug where
opening a webchat
endpoint whereno flow
was selected would display a white page with console errors - Fixed a bug where the
color
for a project would not be displayed correctly in thetop bar
- Fixed a bug where a
misleading error message
got displayed when a user with a certain role would enter theFlow Editor
- Fixed a bug where
emails
would not be detected correctly if they contained anuppercase letter
3.0.7
Released: August 23rd, 2018
Features
- Add an API-side filter for
parsed token trees
for flows. This gives a huge performance increase when working with huge flows that have a high number of intents
Bugfixes
- Fixed a bug where
forms
could not be used in flows that have thegeneric language
set - Fixed a bug where the
Interaction Panel
could not be used aftercontacts
,access control
and/ormy profile
page was refreshed - Fixed a bug where an
non existent version
within a flow could be selected if a former flow had this version - Fixed a bug where the
timezone offset
was not used properly - Fixed a bug where
confirmation sentences
would not work properly
3.0.6
Released: August 17th, 2018
Features
- Migrated the
webchat
source into theservice-webchat
service so that the source is no longer served viaamazon S3
but our own service. This also fixes the issue thaton-prem
customers with strict firewall rules could not use thewebchat
since the source was not reachable.
Bugfixes
- Fixed a bug where
negative numbers
could not be used inform fields
- Fixed a bug where
actions.addLexiconKeyphrase
could not adddata
to a keyphrase - Fixed a bug where
trailing execute form nodes
wouldn't get executed when attached to anotherexecuteForm node
- Fixed a bug where a
german date form
did not get inputs that were notformatted as date
- Fixed a bug where flows were changing
their order
on the project page when new flows get created - Fixed several problems within the
import / export
feature - resource reference get nowlinked once again
after an import - Fixed several smaller issues within the
lexicon editor
- Fixed an issue where the
Cognigy.UI
was creatingtoo many socket/socket.io connections
to the server infrastructure - Fixed a bug where the
webchat
would rendernull
messages - Fixed a bug where
Cognigy.AI
would notcontinue main flow
after executing anattached flow
within a flow getting executed using anexecuteFlow
node - Fixed a bug where the
Interaction Panel
would crash if you useactions.output(1)
in a code-node - Fixed a bug where the
Interaction Panel's
manual chat could still be used even when aplaybook
got executed - Fixed minor
Cognigy.UI
issues when displayingcountry flags
- Fixed rendering of
once
node inCognigy.UI
when the...-button
got clicked - Fixed a bug related to
STT
and theInteraction Panel
3.0.5
Released: August 9th, 2018
Features
- Added
tooltips
to the sidebar of theCognigy.UI's
flow editor - Improved
bleeding edge NLU System
by automatically creating synthetic example sentences - Added
https
redirect by default foron prem installations
that use TLS - Improved the way on how we
write logs
into the log database (batch write) - Add
ttl
for logs in the logging service
Bugfixes
- Fixed a bug where the
number 0
could not be used in aform field
of typenumber
(falsy value problem) - Fixed a bug where the
interjections
forAlexa
where missing - Fixed a bug where
instance keyphrases
would not be persisted and not be available when the conversation gets switched to anotherai instance
- Fixed a bug where the
currently loaded flow
would switch when the session gets switched to anotherai instance
- Fixed a bug in the
playbook player
- Fixed a bug where the
project color
would disappear in the top bar when reloading the page - Fixed a bug where the
confirmation sentence
could not be removed within intents - Fixed a bug where the
flow editor
would crash when the user adds an{}
(empty object) as an alexa custom directive - Fixed a bug where the
projects icon/avatar
and thetop bar
would have slightly different colors - Fixed a bug where there was no proper
error checking
in place for thejson input
in thegoogle say-node tab
- Fixed a bug where the
mongo find one
would throw an exception in theflow editor
if no result was found - Fixed a bug where the
contact profile (cp)
would not properly update afterexecuting a thing node
- Fixed a bug where the
slots.DATE
property was not usable forAlexa
- Fixed a bug where services would crash when the
logCollector exchange
was not defined - Fixed a bug where
rabbit mq
would crash when updating services to newer versions (updating COGNIGY.AI
)
Documentation
- Major restructuring of the whole documentation so it is more easy to search for individual topics
3.0.4
Released: August 2nd, 2018
Features
- Improved
NLU System
that was introduced in3.0.3
for german language - Improved
Cognigy.UIs
error handling so users do not reload the page if a component crashes - Improved
actions.output
so the second parameter isoptional
- Improved the way how the
endpoint
is handling connections -websockets
andfallback http polling
is possible now - Changed the default value of the
keep alexa session open
to true - Changed the default values for
stop after childFlow
inquestion nodes
- Changed
save buttons
to have more consistent placing inCognigy.UI
Bugfixes
- Fixed a bug where the
system would not answer
sometimes - Fixed a bug where we had no
confirmation screen
in theintent editor
- Fixed a bug in the
facebook preview
wherevertical images
would not get displayed the correct way - Fixed a bug in the
webchat
where thepersistent menu
was broken - Fixed a race-condition within the
endpoint
that sometimes would result in anincorect order of messages
- Fixed a bug in
realtime analytics
- Fixed a bug where the
flow service
would throw timeouts - Fixed a bug within the
connection editor
- the type of the previously selectedconnection
would be used for new connections - Fixed a bug where the
state
would not be shown in theInteraction Panel
when displayed on theprojects page
- Fixed a bug that resulted in a
blank page
on anempty gallery element
for facebook - Fixed a bug where the
UI element to create projects
was shown even if users with a certain role could not create projects - Fixed a bug where the
vertical image
within analexa card
had a broken preview within theCognigy.UI
- Fixed a race-condition in the
Flow Editor
that resulted in astack of errors
if the page was reloaded in some circumstances - Fixed a bug where the
bot
would always have the nameCognigyBot
for theSlack channel
Documentation
- Improved documentation on
how to reach the api service
in an on-prem installation - Improved documentation for
facebook profile
andupdate profile
settings for endpoint(s)
3.0.3
Released: July 20th, 2018
Features
- Introduce a new
NLU System
that you can use (still experimental!) - Improve the
/inject
and/notify
API - Improve the performance of the Cognigy UI
- Add the ability so
HTML markup
can be used within theWebChat
- Add the ability to send
data
within aYN-/Slot-Question
node - Add the
reverse proxy / load balancer Traefik
to the Cognigy stack to improve the scalability of the UI and API
Bugfixes
- Fixed a bug where
US phone numbers
were always invalid in aForm
- Fixed a bug where
firstName / lastName
could not be updated using theUpdateProfile
node - Fixed a bug where
attaching a flow
did not always load thelatest version
of the attached flow - Fixed a bug where the
SwitchFlow
node would not display the name of the target flow - Fixed a bug where
SwitchFlow
andExecuteFlow
would allow you to switch into the currently loaded flow - Fixed a bug where
keyphrases
within trailing?
caused an error on creatingtags
andsynonyms
- Fixed a bug where a
lexicon
could be deleted but it was not checked for its usage in flows - Fixed a bug in the
lexicon editor
regarding the search functionality - Fixed a bug where the
settings editor
could not be accessed through the proper URL in the browser - Fixed a bug where the
name
of anintent
could not be changed - Fixed a bug where renaming a
project resource
allowed dublicat names - Fixed a bug where the
service-logs
would crash since thelogCollector
exchange was not created - Fixed a bug where the
endpoint
logs would not show-up on thelogs page
- Fixed a bug where an
empty display template list
for Alexa would crash the browser - Fixed a bug in the
dublicate check
of alexicon name
within a project - Fixed a bug where
flow nodes
with no content would still open the node editor - Fixed a bug within the
Email
node which did not check for required fields - Fixed a bug where
Send test email
would send the email, but would report a failed state - Fixed a bug within the
playbook editor
where switching theabort on error
toggle would throw an error - Fixed a bug where the
repeat playbook
setting would not work - Fixed a bug where a
contact profile
could not be properly exported - Fixed a bug within the
facebook list template
where you could not see thesubtitle
since of bad contrast - Fixed a bug in the
NLU system
where the system got confused when anus style date
was mentioned (month / day reversed) - Fixed a bug in the
NLU system
regarding the english question-wordwhich
- Fixed a bug with the
analytics graphs
in the UI - Fixed a bug where
image attachments
could not be used within theWebChat
- Fixed a bug where the
WebChat
did not scroll to the bottom forGallery
elements - Fixed a bug where the
Gallery
elements would not scale automatically
Documentation
- Improve documentation for
/inject
and/notify
APIs API Reference
3.0.2
Released: July 2th, 2018
Features
- Add ability so
AI
service can scale - Improve output of all flow ouputs for
REST
endpoint - Expose
sendMessage
functionality inWebchat
- Update
Unity Client
so it works with COGNIGY.AI 3.X - Shorten
ApiKeys
so they are more usable - Improve error message for
code
nodes so line numbers are displayed
Bugfixes
- Fixed bug where absorbing profiles does not work for the
facebook messenger
endpoint - Fixed bug where STT/TSS in
Interaction Panel
did not use current flows language - Fixed bug with weird scrolling behaviour in
Interaction Panel
- Fixed bug where
delete project
button was not visible - Fixed bug where
log history
could not be retrieved properly - Fixed bug in
regex slot filler
node - Fixed bug where users could not scroll in
state view
- Fixed bug that resulted in
inconsistent analytics reports
- Fixed bug in
number parser
- Fixed bug in
execute form
mechanic
Documentation
- Add full documentation to
/contacts
API (API Reference) - Improve documentation for
Google Home
3.0.1
Released: June 15th, 2018
Features unlocked
- Ability to delete your own account
- Ability to manage your profile
- Ability to send emails and create SMTP connections
Bugfixes##
- Fixed bug in
addLexiconKeyphrase
node - Fixed several problems within the
Interaction Panel
- Fixed several smaller problems within the UI
- Fixed a problem with playbooks
- Fixed a problem with
states
- Fixed a bug where
attached flows
could not be detached - Fixed a bug with the
Cognigy Form Flow
3.0.0
Released: June 13th, 2018
This is our latest
major release. We changed a lot, fixed a lot of issues and added many new features which make COGNIGY.AI the optimal solution to create, deploy and maintain your conversational AIs.
Updated over 1 year ago