This release includes the ability to define triggers & actions based on multiple intake questions, support for date-type metadata fields, an expansion of the character limit for Use Case names, and more.
Date: 06-12-24
What’s New
Triggers & Actions
-
Define Multi-Question Triggers – You can now define triggers based on multiple intake questions, enabling you to have more control over complex intake workflow automation. For example, if your organization defines customer-facing LLM-based applications as “High Risk,” you can now define a “High Risk” trigger based on two questions: whether the use case is customer-facing, and whether it uses an LLM. Get there by heading to the Governance Center → Questionnaires.
-
Expanded Support for Setting Custom Metadata Fields via Triggers & Actions - We’re adding support for date and free text custom metadata fields to be updated by intake questionnaire answers via Triggers & Actions. Now, you can turn intake questions that expect date answers as triggers that define custom date metadata fields, and intake questions that expect free text answers as triggers that define custom free text metadata fields.
-
Reverting Policy Packs & Controls Added to a Use Case via Triggers and Actions - If a user changes an intake questionnaire answer to a non-triggering answer, the Policy Pack or control that was added to the Use Case by the triggering answer will be removed from that Use Case only if there hasn’t been any evidence uploaded to the controls of that Policy Pack; if there has been evidence uploaded already, the Policy Pack will remain applied to the Use Case.
Custom Metadata Field Date Support
-
Add Date Fields as Custom Metadata – Previously, custom metadata fields only supported string types. Now, users can explicitly define date fields with a calendar dropdown, ensuring data consistency and accuracy across the product.
-
Validation and Error Handling: If a non-ISO 8601 date format is submitted via API, users will receive an error message with guidance on how to correct it.
-
Expanded Use Case Name
-
Use Case Name Field is Expanded - We have enhanced the use case naming feature to support longer names, accommodating up to 250 characters.
Local Users vs SSO
-
SSO-enabled orgs cannot add Local users - For orgs with SSO enabled, local users cannot be added to a tenant. Local users can be added to a tenant if SSO is not enabled.
Platform Version Number
-
Version number is now displayed in the bottom left corner of the Platform - it’s easy to check which version of Credo AI your organization is running, so you can make sure that you’re fully up-to-date.