A new release is deployed for AI App Frontend on March 17, 2025 (4:00 PM UTC).

Release name : ai-app-front-2025.3.1

Release scope : AI App Frontend

Release date : March 17, 2025 (4:00 PM UTC)

Release platform(s) : Production

Release content :

• FEATURE : Implemented a CDN for web components to enhance performance and scalability
• FIX : Improved handling of large audio files on the model page
• LEGACY : Removed the agents_performances_enabled boolean flag, replacing it with a feature toggle: agents-performances (for display use), now provided by ai-core-api
  

A new release is deployed for AI Core API on March 11, 2025 (6:00 PM UTC).

Release name : ai-core-api-2025.3.1

Release scope : AI Core API (Web Backend of AI App)

Release date : March 11, 2025 (6:00 PM UTC)

Release platform(s) : Production

Release content :

• FIX : Fixed bug on call filtering by metadata
• FIX : Fixed meilisearch queue, add debounce system to avoid concurrency problems
• MIGRATION : Performed calls reindexing

A new release is deployed for AI Core API on February 27, 2025 (7:00 PM UTC).

Release name : ai-core-api-2025.2.3

Release scope : AI Core API (Web Backend of AI App)

Release date : February 27, 2025 (7:00 PM UTC)

Release platform(s) : Production

Release content :

• FEATURE : Added the capability to use Engage calls with our Public API endpoint for API integration with Diabolocom CCaaS -> Dedicated documentation and release note will be published soon !
• FEATURE : Added documentation url used for display of multi-modal models (Markdown not yet updated)
• FIX : Single API call to Engage to retrieve agent and call info (instead of multiple calls)
• FIX : Fixed a bug on call retrieval that wasn't matched to a specific AI account (improve legacy behavior)
• MIGRATION : diabolocom_account_uuid added to our AI accounts + diabolocom_account_id corrected (not applied for AI accounts with only account_identifier)

New API Capability:

• It is now possible to specify the interaction date in the API payload when sending over recordings.
  
• This new optional parameter allows to specify the date and time when the interaction happened. If this parameter is not specified, it will default instead to the ingestion date, like it was the case before.
  
• The "add interaction" UI functionality also benefits from this feature.
  
• This will be deployed on SFTP later.
• This is very useful in the case a client wants to upload all calls at the end of the day while retaining the exact time of the interaction in the QM system. It also allows us to create more accurate data for statistics on demo platforms. 

Bugfix:

• We fixed an issue where some criteria could not be re-evaluated when the AI chose the "Non Applicable" option.
  

Security Fixes:

• We also applied security fixes to help us reduce the amount of information sent to the front end of the solution.
  

Added auditability for actions

• You can now check when actions were triggered and their entire trigger history. Trigger history also contain status code and response on click.
  

New filters

• It is now possible to filter by evaluation form on the interactions list.
• It is now possible to filter by criteria type in criteria list.

Fixes

• Fixed an issue where having two options having the same score would make manual modification impossible.
• Fixed an issue where deleting a report from a dashboard would necessitate to save in order to actually update the dashboard.

Technical/Backend

• Engage provided audio are not stored/encrypted by QM & instead we leverage native private API on demand

Code for SFTP functionality and additionnal AI Insights was deployed in the backoffice, but please do not activate it until the next release, it will not work as the infrastructure for production is still in deployment.

See full update demo here