Date: 03-12-25
What’s New
Triggers & Actions
-
OR Triggers Now Available: When creating Triggers in the Governance Center, users can now select more than one selection to execute a “Trigger”. For instance, if Admins would like either answer“Yes” or “Maybe” to the question of “Is PII involved?” to add the Privacy team to a Use Case as a Reviewer, they can now configure their Trigger options to include more than one selection.
AI Registry
-
Each Use Case has a unique, user-friendly ID: we added a unique, user-friendly ID to each AI Use Case (UC-#). This ID is visible underneath the name from each page of the Use Case. To view this in the AI Registry, select “Use Case #” in the “Columns” menu.
-
Search for Use Cases by Description and ID: you can now search for Use Cases in the AI Registry by not only name but also description and Use Case ID.
Task Assignment
-
Assign a task to multiple users: you can now assign a single task, like an intake questionnaire section or a control, to multiple individual users and teams at the same time. Anyone who is assigned a task can mark that task as complete.
Use Case Review
-
Use Case Review Completion: Reviewers will now be presented with a confirmation dialogue when completing a Use Case Review, showing the number of Reviewers yet to approve the Use Case. Reviewer can accept the message, go ahead and close the Use Case Review. This dialogue will help Reviewers make an informed choice about contacting or waiting for other Reviewers to close their review, or to proceed ahead with the Use Case.
Bug Fixes
-
Typo fixed in Review History page: we fixed a typo in the empty state of the Review History page.
-
Added spacing to Use Case metadata chips: we added vertical spacing to the Use Case Overview between metadata field chips in the Use Case Info section.
-
Long Organization names are now properly displayed in the UI: we updated the UI so that long organization names now properly display instead of getting cut off.
-
Deleting a model now redirects to the Model Registry: we fixed a bug where users were incorrectly routed back to the Vendor Registry after deleting a model from the Model Registry.
-
Fixed email exception for external users: we fixed an issue where external users were not receiving emails from Credo AI.
-
Fixed issue with JSON Use Case export: we fixed an issue that were causing Use Case ID to be left out of the JSON export of all Use Cases.
-
Long comments no longer cut off in UI: we fixed an issue where long comments in the Review panel were getting cut off. Long comments are now scrollable in the Review Panel. We also have added a 3000 character limit on single comments moving forward.
-
Risk Report now appears on Reports page: previously, when a user generated a Risk Report, it failed to get stored in the Reports page of the Use Case; now, all previously generated Risk Reports will be available from the Reports page.
-
Unchecked alerts for Triggers & Actions will no longer display: we fixed a bug where alerts for all Triggers & Actions, including ones for which the “show alert” box had been unchecked, were displaying. Now users will only see alerts for Triggers & Actions where “show alert” has been checked.
-
Hidden Risk Scenarios no longer available when adding to a Use Case: we fixed a bug where hidden risk scenarios were still showing up as options for the user when adding Risk Scenarios to a Use Case Risk Plan.
-
Deleting a single trigger within a multi-trigger is now possible: we fixed an issue where deleting a single trigger within a multi-trigger caused the entire multi-trigger to be deleted.
-
Admin users can archive controls: we fixed a bug where admin users were not able to archive controls from the Control Library.
-
Triggered reviewers added to Use Case: we fixed an issue where sometimes, triggered reviewers were not getting added to Use Cases when submitted for review.
-
User can now download Questionnaire, Risk Report, and Compliance Report: we fixed an issue where users were getting stuck in an infinite login loop when trying to download a PDF of a Use Case Questionnaire, Risk Report, or Compliance Report.
API Deprecation Notice
-
In 17.0 we will be shipping 2 breaking changes in the Triggers and Action configuration endpoint:
/triggers
. Full migration guide will be emailed to all customers in March. Note: We have shifted the ship date of this breaking change from 16.0 to 17.0 in order to better accommodate 17.0 functionality.-
We will be deprecating
option
and replace it withoptions
-
Multi-triggers will be replaced with “conditions”. For now, “Conditions” will be a term used in the API only.
-