26.1 Features

AI-Generated Controls

AI-Generated Controls is an AI-powered feature powered by Claude Haiku 4.5 that allows Compliance and Risk teams to leverage AI to generate clear, structured operational controls when existing controls are missing or unclear, or when working with new or unfamiliar regulatory items or risk scenarios. Generated controls are informed by industry best practices and incorporate the context of linked requirements and risk details.

This allows teams to:

• Design controls aligned with industry best practices, regulatory requirements, and risk details

• Use AI-generated controls as strong first drafts that teams can review and tailor to their processes

• Promote standardized and structured control design across control libraries

By providing structured starting points (drafts), Generated Controls helps reduce the “blank page” problem, improves confidence in control creation, and supports more consistent understanding of how obligations and risks translate into day-to-day business activities.

Note: This feature is intended to be a starting point for the user. Please ensure to review the AI-generated content and make edits prior to linking to a requirement or risk.

Generated Controls can be self-enabled from the Feature Access screen.

Benefits

This feature allows Compliance and Risk teams to:

• Save time by accelerating control creation through the generation of high-quality drafts in seconds, reducing the time spent interpreting complex regulatory language

• Provide structured, audit-ready control suggestions that help users feel more certain about how obligations and risks translate into operational actions

• Help Requirement Owners and first-line teams understand what a good control looks like, even without deep compliance expertise

• Improve quality by encouraging more consistent, well-formed controls by applying best-practice structure across generated outputs

• Create a shared understanding between Compliance and the business by turning abstract obligations into concrete, practical activities

• Extend the impact of Compliance professionals by embedding their knowledge into the tool, rather than relying on 1:1 guidance

Supporting Documentation

Please refer to the following articles for more information on Generated Controls:

• Enabling AI-Generated Controls on an Org
• Using AI-Generated Controls on a Form
• Troubleshoot AI-Generated Controls

Portal Agent Updates

This release includes several updates to improve Portal Agent’s capabilities:

1. Nested relationship searches: Portal Agent now supports nested forms, allowing the Agent to collect additional information if an object is not already captured in Resolver.

   Note: Nested forms are only supported for relationships configured on the Portal Agent form.

2. Improved relationship searching context

   Note: To improve the accuracy of relationship and reference searches, we recommend adding clear descriptions to any relationships or references included on a Portal Agent form.

3. Improved attachment handling: Portal Agent now supports multiple attachment types, allowing for more flexible file uploads.

   Note: Attachments are only supported if an Attachment field is added to the Portal Agent form.

This release also includes performance optimizations, bug fixes, and Infosec enhancements to strengthen Portal Agent’s capabilities and security.

Note: If you are interested in learning more about this feature and enabling it on your Org, please contact your Customer Success Manager.

Disable Portal URL

The Enable Portal URL toggle switch was added to the Portal URL Settings: Edit Portal URL screen and allows Administrators to disable a Portal URL, removing user access. While a Portal URL is disabled, Portal URL settings are still editable, allowing Administrators to apply changes to the Portal URL. Users who attempt to access a disabled Portal URL will receive a 404-page error. A disabled label will appear next to the Portal URL name on the Admin: Portal URL Settings screen, indicating the Portal URL’s status. 

When a Portal URL is enabled again, the Portal’s URL in the Login URL field will not automatically regenerate a new URL.

Supporting Documentation

Please refer to the following articles for more information on disabling the Portal URL:

• Creating a Portal URL
• Creating a Secure Access Portal
• Editing or Deleting a Portal URL

Translation Supports

The following language translations are hard-coded on submitter components on the landing and confirmation screens in Secure Access Portal:

Additional Currency Support

To further support global organizations using their own currency symbols within Resolver Core, we have added the following currencies to the Currency field in the field and formula editors:

Note: The Resolver Core system does not perform currency conversions.

Include Formulas in Scoping Filters

Administrators can use formulas to filter an assessment when configuring assessment scoping filters by clicking the Filtering Options button on the Configuration tab on the Admin: Edit Assessment screen. Formulas will not be on by default. Users will need to enable formula filters when configuring assessment scoping filters.

Update Field and Formula Names in Dashboards

If the names on fields or formulas are changed within a dashboard, an Administrator must republish the dashboard's dataset for the changes to be visible within the dashboard.

Mandatory Fields Now Highlighted by Default

We’ve improved the form experience to highlight incomplete mandatory fields, and the tabs containing them, by default. The incomplete mandatory fields are highlighted in yellow, helping users quickly identify what requires attention. Once a required field is populated, the highlight is removed and the field returns to its normal state.

Mandatory Fields on a Form

UX Improvements

Secure Access Portal Enhancements

A banner will appear stating that “Submission not accessible: The submission you’re looking for isn’t available” when a user attempts to access a deleted object on the Secure Access Portal.

Secure Access Portal Banner

The following enhancements were applied to the Access Roles dropdown menu on the Portal URL Settings screen:

• Only roles assigned to the object type selected on the Object Type field on the Portal URL Settings screen will appear in the Access Roles dropdown menu.
• Global roles are excluded from the Access Roles dropdown menu.

Note: A role must meet all conditions above to appear on the Access Roles dropdown menu.

Updating Confidential to Anonymous

The Confidential terminology throughout Resolver Core is being replaced with Anonymous.

Confidential Submission Screen

Improved Object Creation via Object Type Group Relationships

Improved Object Creation Palette

Enhanced Latitude and Longitude Support in Reports and Data Analytics Exports

We’ve added full support for latitude and longitude properties in reports across all report types and export formats (Excel, Word, and PDF). Users can now configure latitude and longitude properties in reports, improving the accuracy and consistency of geolocation data. Data analytics exports have also been updated to use separate latitude and longitude columns to ensure consistency in how geolocation data is represented across reports and data analytics exports.

Latitude and Longitude Properties

Supporting Documentation

Please refer to the Properties in Report Tables article for further information on using the longitude and latitude properties in reports. 

New Email Address Field Type

A new Email Address field type has been created to store validated email addresses. The following format validation rules will be enforced:

• Local Part Syntax: The local part is the text before the @ symbol. It can be formatted in two ways:
  • Standard/Unquoted (the local part isn’t in quotation marks): Uses letters, numbers, and common symbols (!#$%&'*+/=?^_{|}~-).
    • Dots/periods (.) can’t be at the start or end of the local part
    • You can’t have two dots/periods (.) in a row in the local part

  • Extended/Quoted (the local part is in quotation marks): Uses letters, numbers, spaces, and special characters (including common symbols).

• Local/Domain Split: The domain is the text after the @ symbol. It must be a valid Fully Qualified Domain Name (FQDN) which is made up of labels for the hostname (e.g. mail), domain name (e.g. resolver) , and top-level domain (e.g. com). This also includes alternative/root domains (e.g. resolver.com). Its format is:

  • Each label must be separated by a dot/period (.) (e.g. resolver.com)

  • Labels can only contain letters, numbers, and hyphens

  • Labels can’t start of end with a hyphen

  • The last label (top-level domain) must be at least 2 characters long.

The email address must follow these length constraints:

• The total email address cannot be more than 254 characters

• The local part (before the @) cannot be more than 64 characters

• Each domain (after the @) label (between each dot/period) cannot be more than 63 characters

Single Line and Multi Line Text fields that are currently storing email addresses can be converted to Email Address fields, as long as the existing field is not being used in an unsupported location. The email address validation will be triggered the first time the field is edited by a user, post conversion. If the email address is in an invalid format, users will no longer be able to save the value.

Warning: Converting a Single Line and Multi Line Text field to an Email Address field cannot be reversed.

Supporting Documentation

Please refer to the following articles for more information on Email Address fields:

• Creating an Email Address Field
• Editing a Plain Text Field

Improvements

• Users will no longer be able to add field option to non-select list fields via the POST/PUT /object/field API.

Bug Fixes

• When refreshing the Privacy Policy screen from the Portal URL, it will now show the Privacy Policy screen again instead of a blank screen. 
• Links in emails will now successfully navigate to the correct record after a user has logged in with either SSO and email/password.
• Fixed an issue where the Linked Person field disappeared or became read-only after unlinking, ensuring it now stays visible and editable without needing a refresh.
• Field and formula number formatting will now be correctly represented in dashboards.
• The Add Existing Controls palette will successfully open when the control relationship is not currently visible on the form.
• The character % will not break search moving forward.
• After a session expires, the username is retained so that the user may now log in again right away.
• When an object is created via email, the Performed By field will accurately reflect the Message Service in the Data Audit Trail.
• When a user receives an email confirmation link, the link will redirect them to Resolver where they will be logged in and then brought to their Home screen.
• Read-only check box lists, radio button lists, and group toggles will now remain translated.
• Numeric formulas configured to display as None or Result will now be exported as numbers in Excel report exports. The percentage and currency symbol will continue to show and a decimal will be used for all currencies to represent the minor units.
• Expected fields and properties will now be displayed when configuring a relationship table on the default form.
• The User Management screen will now be displayed faster, and a “Loading …” message will be displayed to the user while processing.
• Columns can now be reordered when configuring imported reports.
• Fixed an issue where it was possible to enter extremely small/large values into numerical and date fields.

New Content Translations

Please review the file below for all new content translations added to the system.

Release 26.1 Translations Update List.xlsx

If your organization is utilizing the Language Translation feature, please download a new Language template (for your required language) and filter the Language column (last column) by empty cells, indicating new content. Any empty cells in the Language column must be translated, and the Language Template file must be uploaded to the system for changes. For further information, please refer to the Add a Language article.