V3.3.3 Release Notes

Full List of Enhancements:

• Internalization:

  • Allows users to select their preferred language and interact with the ModelOp UI in the selected language. See the detailed documentation: Language Preferences.

  • Supported Languages include: Japanese, Spanish, Portuguese, English.

• User Experience:

  • Custom Forms: added support for:

    • Additional custom form field types, including a date selector and url field. Each field is validated by the UI before saving.

      • Date:

        Open

        

      • URL:

        • Open

          

    • Tooltips: ability to specify tooltip text that can provide the user more information about the given custom field.

      • Open

        

    • Required vs. optional fields: allows administrators to define mandatory fields that must be provided before a user can save a given form (e.g. a new use case record).

      • Definitions:

        • Mandatory: field must be completed before the form can be saved.

        • Priority: field must eventually be provided. The Governance Score will report if this field is not completed.

        • Optional: field can optionally be provided.

      • Open

        

    • Default values: allows administrators to define default values for a given field, such that the default value is auto-populated upon creation of the field in the custom form.

  • LDAP: added support for integrating with a Customer’s LDAP to lookup users and assign them to Use Case or Model-specific custom fields

  • Compliance Dashboard: added the ability to drill-down into the specific failing test directly from the compliance dashboard chart

  • Test Result Filters: allows users to filter all of the charts within a Model Test Result page by a given segment/group.

  • Notification Docs: allows users to add documents to any notification type:

    • Open

      

       

• Configuration:

  • For Custom Forms, added a DEFAULT option for available actions/states in the notification drop-down. To configure the “default” option, simply include a “DEFAULT” section in the SCCS settings. Here is an example:

    • center: internal-notifications-enabled: true tasks: configuration: '{ "types": [ { "id": "DEFAULT", "label": "Default", "states": [ { "status": "Open", "open": true, "actions": [ "APPROVE", "REJECT" ] } ] } ], "actions": [ { "id": "APPROVE", "label": "Approve", "changes": { "close": true, "status": "Approved" } }, { "id": "REJECT", "label": "Reject", "changes": { "close": true, "status": "Rejected" } } ] }'

• Reporting:

  • PowerBI Server: added support for PowerBI Server, allowing customers to refresh/republish PowerBI reports on a scheduled basis. See the detailed documentation: PowerBI Server Integration.

  • PowerBI Custom Data: for notifications objects, added support to include the notification custom metadata in PowerBI tables

Bug Fixes:

• Security:

  • Addressed an issue where the first call to any /group-access-privileges/admin endpoint with a new client-credentials token returns 403, subsequent calls succeed

• Model Test Results:

  • Addressed an issue where the key of a model test result was a null character such as {"n\u0000a\u0000m\u0000e\u0000": [["2025-07-03", 1]]}