Version 22.1+ Internal Release Notes

× This article and its embedded links are for internal use only. External release notes are posted here.

Version 22.1.3

General Enhancements

  • The privacy policy text for anonymous portals now supports internationalization
  • Deleting an org no longer fails in cases where the org's data warehouse was only just created
  • The externalRefId property has been added to the response from the /user/role/#{user_id}/roles API
  • Data warehouse creation can now run concurrently when multiple orgs are created in succession
  • The updated user management logic for "scorched" org imports now handles role and user group membership
  • Success banners now appear on the email settings page when the email address has been generated and when it has been copied to clipboard
  • Org deletions are now queued (instead of failing) if one is already in progress

Bug Fixes 

  • A change in a user's email address no longer causes org import to fail
  • Multi-select field can now be updated through the API when byRef is set to True
  • Objects with location data can once again be created in languages other than English
  • Assessment deletion is now reflected in the Data Audit Trail
  • Org import no longer inserts duplicate API keys
  • Field options can no longer be attached to non-select list fields through the API
  • Address search is no longer restricted to a single country when the user's device location is blocked
  • Form selectors for workflow states no longer appear blank when the default form is selected
  • Relationship table fields are once again populated on page load
  • The Pull Data Values action once again reliably pulls from the latest object on a relationship
  • Field sorting in relationship tables has been improved
  • A race condition where a formula result could be calculated before one of its variables has finished updating has been resolved

Version 22.1.2

General Enhancements

  • Resolver has moved to a new Idea Portal, now embedded in-app to provide a seamless user experience. No need for a separate login or bookmarks - customers can simply navigate to the Resolver application's Help (?) menu and click the Idea Portal to access, view, and vote on idea cards (i.e., topics we chose to expose) and submit new feedback.
    • The Productboard-hosted Idea Portal uses SSO (not to be confused with the customer SAML-based SSO) and no longer requires account management from Resolver teams. 
    • If a customer operates in a highly restrictive environment and needs to explicitly allow select domains, then they should allow access to productboard.com, *.productboard.com.
  • A new option is available to calculate averages, maximums, and minimums on assessment tables – providing customers with more options to interact with their assessment data. 
  • The API for initializing Redis (an open-source database cache) now returns a Job ID that can be queried.
  • Moved palette descriptions out of the header and into the white portion of the palette, solving an issue with header text overflow.
  • Removed the title and some unnecessary white space from the relationship graph.
  • Restricted palette subtitles to a single line, solving an issue with header text overflow.
  • Set up the following lists to display alphabetically in the form editor:
    • Available relationships
    • Available roles 
    • Available actions 
    • Available references.
  • Removed ability for regular admins to disable SSO for Resolver Support Team members (aka Super Admins).
  • Enabled the available state triggers list in the form editor to show the corresponding workflow state, providing extra context.
  • Corrected minor typo in the two-way email communication modal.
  • Made tool tips on the form editor's state triggers list easier to read.
  • Regular admins can no longer edit Super Admin users’ first and last names.
  • Select list ordinals (i.e., set orders and ranks) are once again retained on org import.
  • Removing or deactivating form email settings no longer removes the form’s existing email communication.
  • Increased the sidebar card stacking breakpoint on configurable forms and navigation forms, which helps to enhance the quality of sales demos for the new form layouts.

Bug Fixes

  • Resolved an issue where some numeric values were incorrectly interpreted as boolean and stored as null in a data import.
  • Date variables are once again populated with the correct information in email notifications.
  • Resolved an issue where some relationship table data would display as blank until an object was opened in the palette.
  • Transitions are once again properly recognized when required relationships or references are filled in.
  • The Swagger API for retrieving relationships no longer ignores the limit parameter.
  • An error that was not being properly caught during org deletion is now being accounted for when the org delete's Job ID is queried.
  • Large numbers of comments no longer prevent deletion of assessments with thousands of objects.
  • Creating an object via API no longer allows you to set a select list option that doesn't actually belong to the field to which it's being set.
  • Triggering the Clear Fields action through workflow orchestration now updates formula automatically.
  • Resolver no longer attempts to display relationship graphs in microforms, improving the layout.
  • Corrected issues where the new forms refresh affected the display of microforms in palettes.
  • Select list fields no longer extend beyond the form layout.
  • Updating an org's parameters via the API no longer resets the session timeout to 15 minutes when a new timeout parameter is not provided.
  • Orgs can now be successfully deleted, even if there are active connections to that org's data warehouse.
  • Email addresses used with the two-way email feature are no longer regenerated on org import.
  • Improved the color contrast on toggle buttons.
  • Trending formula data no longer impacts date picker usage.
  • Resolved an issue that occurred with user groups in an org import.

For a complete list of bug fixes or known issues for Version 22.1.2, download the Release 22.1.2 Fixes.xlsx file from Box.

Version 22.1.1

Re-enabled the Done Button on Object Forms

  • In the 22.1 release’s form layout improvements, we removed the Done button from object forms. The Done button was deemed redundant because:
    • It worked the same as the web browser back button and resulted in a lot of deep page scrolling on longer forms.
    • It did not serve as a save or complete button as many users mistook it for being (not realizing that Resolver already auto-saves your object form changes).
  • However, some customers rely on the Done button and would like to add it back. Therefore, we have introduced the option to add it back to object forms. Resolver controls this global setting, so if a customer would like to keep the Done button, they can contact Resolver Support to re-enable it. A few considerations:
    • The Done button Feature Flag can be enabled on the org level by Support team members through Swagger (objectDoneButton). 
    • When the Done button is enabled, it will show in same place as before. However, since the code behind the forms has changed, the Done button might not align exactly as before, as no additional adjustments were made for it to match the form changes.
    • Customers who re-enable the Done button on object forms can still eventually transition to the new forms layout and remove it once again, if desired. 
  • Read more here:

General Enhancements

  • User management logic has been updated for group-role membership, meaning app deploy org imports no longer delete users, roles, or user groups that already exist in the org (but are not in the imported JSON file).
  • For anonymous submissions, the Stay Informed modal window now only displays if the Submitter property is visible on the form.
  • Assessment palettes for updates and results now include an Expand button.
  • The deleteFromAllOrgs API now disables the user’s Support team member and SSO bypass, also removing their password.
  • Regular Admins can no longer update a Support team member’s user email.
  • Workflow state is now an option for setting form sections’ visibility.
  • Assessment table column names have been made more consistent.
  • The Privacy landing page now displays the org name.
  • The following are now presented alphabetically:
    • Report Editor’s Configure Your Chart tab items
    • Report Editor’s Configure Filters palette items
    • Report Editor’s Configure Parameters palette items
    • The Form Editor’s Form Elements menu options 
    • Roles added to object types.
  • If a form card has no content, it is now hidden entirely.

Bug Fixes

  • The Create a New Field modal window once again auto-closes when clicking the Create and Link button on Assessments.
  • Assessment results columns are now displayed in the Form Editor’s set order.
  • An object’s events can now be filtered or deleted by object name in the data audit trail.
  • The Email Template logo is now used for confirmation emails.
  • Location results are once again sorted by the current user’s distance.
  • SSO configurations with mixed case domains can once again be read or modified through the API.
  • Clicking a relationship for an assessment object in palette to a library object now correctly loads the desired object, instead of re-directing users to the homepage.
  • When self-referential transitions occur, previously queued nightly trigger events are no longer cleared.

For a complete list of bug fixes or known issues for Version 22.1.1, download the Release 22.1.1 Fixes.xlsx file from Box.

Version 22.1

New Features

Added Self-Serve User Profile Management

  • Resolver administrators (“admins”) can now independently edit a user’s first name, last name, and email address within the system. For example, when an error is identified, or someone changes their name, an admin no longer must contact support to make those user profile updates. 
  • Besides this increased self-sufficiency, our customers’ information security is strengthened, as application (“app”) users can confirm or deny said updates via a direct link in their inboxes. Self-serve user profile management also boosts customers’ library data integrity, as they can ensure accurate user data at the point of need.
  • If the admin is part of all the same orgs as the user they're trying to update, no user email confirmation is required, and the update is immediately applied. User workflows are also streamlined thanks to custom triggers configured for each state. 
  • Read more about using these new features here:
    Edit or Delete a User

The Admin: Edit User screen.

Enabled Anonymous Portal Submissions

  • A new Submitter Property type supports Anonymous Portal form submissions, so incident reporters’ identities will stay hidden if they want it that way. For example, an incident submitter can report inappropriate workplace behavior without potential backlash, because Resolver generates an alias via a unique object ID through the portal.
  • Anonymous Portal users can freely disclose such sensitive information because this new feature ensures their privacy. When flagged as Anonymous, no Personally Identifiable Information (PII) will be visible in or accessible through Resolver. 
  • These Anonymous Portal submissions also support the new two-way email feature, allowing our customers to engage directly with submitters, ask clarifying questions, and act quickly. Submitters can reply right from their email, but still stay confidential. 
  • Read more about using these new features here:
     Anonymous Portal Overview
    Enable the Anonymous Submitter Property 
    Anonymous Submissions Visibility Rules
    Configure the Submitter Column in a Relationship or Report Table.

The Anonymous Incident Submission web portal.

Introduced Two-Way Email

  • Two-way email takes our recent email ingestion feature to the next level, because customers can now converse with external users via email directly from a centralized object in Resolver. For example, an admin replies to an object’s submitter with a question or update. Or when a submitter wants to follow up on their incident report, they can use two-way email too (with no need for new licensing or system access). 
  • Resolver users must collaborate closely with external stakeholders. This new feature drives tighter communication between submitters and response teams, because admins can customize who’s notified when submitters reply via email. So, teams can resolve cases faster – without having to switch between their email inboxes and system tasks.  
  • Important Notes:
    • Maximum 100 email settings per org
    • Maximum 30MB total email size, including all content, headers, attachments, etc.
    • Emails can only be exchanged on an object originated by email between Resolver Users <> Submitter
    • Attachment fields are the only field that will continue to map values in subsequent Submitter replies. 
  • Read more about using these new features here:
    Create an Email Setting 
    Set Up Two-Way Email

The Notifications for New Replies screen.

Made Session Timeouts Configurable

  • Support team members can now configure the session timeout (between 15 and 1440 minutes) via an org API. For example, a Security Operations team member may want to monitor reports and see data changing throughout the day. Or a remote employee is multi-tasking between their work and personal life and keeps returning to a login screen. 
  • Thanks to these new timeout settings, platform users are not constantly logging back in every 15 minutes to keep their session active (even when their computers go to sleep!). This efficiency helps reduce potential customer frustration from doing repeat sign-ins.
  • Note: A signed addendum is required to modify session timeout for existing customers unless their existing contract/addendums do not specifically state the session timeout period. New Session timeout configurations can be done if the custom timeout is reflected in their contract/addendums.

Improved Transitions by Bypassing Required Fields

  • Admins can now configure transitions to bypass required fields via the Bypass Required Fields toggle on the Workflow Transitions Trigger pallet. Many customer scenarios can benefit from bypassing required fields. For example, an admin wants to run nightly triggers without a workflow change. This toggle can also be used when a response team wants to be notified of a new object submitter email, even if said email is missing required form info.
  • These annoying hurdles won’t prevent these customers getting their work done anymore, because of the new Bypass Required Fields Toggle. This minor change has a major impact, improving both our system automation and customer experience. 
  • Read more about using these new features here:
    Add a Trigger & Transition to a State.

The Bypass Required Fields Toggle

Kicked off Resolver’s Forms Transformation

  • Starting this spring, our customers will experience many enhancements to forms, including how they work and display! This release will improve screen utilization and user flows, while reducing the need to deep scroll, collapse, or expand sections in larger forms.
  • With these upgrades, Resolver Admins can build forms that give the Resolver user quicker data access, with a better overview and intuitive navigation. There are a lot of noticeable improvements already in-motion, such as:
    • Upper-level tabs - keep customer data better organized in one place. For now, these tabs include History, Communications (i.e., Comments and Emails), Relationship Graph, and Assessments.
    • Form Layout Options - experiment with single column layouts, or forms with two columns and a sidebar (on the left or right side), giving customers easy access to the essential details found in our software. 
      Form layout options in the form editor.
    • Separate Card Sections - divide up form content, while avoiding lots of scroll-time. These cards are collapsible, so customers can filter to just show info they require for their own work.
    • Removed the “Done” forms button - have peace of mind that Resolver automatically saves our customers' form data! To return to the previous screen, they can simply click the browser back button – no need to scroll to the bottom of the form anymore.
      Card sections within the main information panel (and the left sidebar).
    • New Headers - keep customer data organized in the same place all the time. Now most forms’ headers (excluding simplified “create” headers) will be a separate area, the full page-width (but they can also be shrunk down to take up less space). New form headers focus on the title, description, ellipsis menu actions, and workflow state or controls.
    • Workflow State Controls or Buttons - get the option to configure either workflow state controls (re-classifiable via dropdown) or buttons (indicating the workflow state). Customers will still see trigger buttons on the bottom of the form as well.
  • Read more about using these new features here:
    Form Layouts Overview
    Configure a Form Layout
    Form Headers Overview
    Configure a Standard Form Header
    Enable Workflow Control on a Form
    Form Cards Overview
    Add a New Card to a Form

Bug Fixes

  • Language imports can now be compressed, and the maximum allowable import size was increased to 5 MB. 
  • The trigger color circle was updated to behave like an object type monogram.
  • Queries for populating navigation trees were made more efficient.
  • Data imports now accept object names that only contain numbers.
  • Creating or updating anonymous logins through the API now correctly rejects calls with an invalid Object Type ID.
  • Attachment field Edit and Remove buttons have been restored.
  • Formula calculations are no longer stored if the formula depends on a value that is being recalculated itself.
  • Support team members can now insert users into orgs without current administrators.
  • Deleting users from global roles no longer creates a data audit trail entry.
  • Text search performance was improved to put a decreased load on the platform.

For a complete list of bug fixes or known issues for Version 22.1, download the Release 22.1 Fixes.xlsx file from Box.

NOTE: The .xlsx files are for internal use only and cannot be distributed to customers. For a summary of features and bug fixes that can be shared with customers, see the Version 22.1 release notes (external).

End of Internet Explorer Support

Effective with the 22.1 release, Resolver will be ending support for Internet Explorer 11 - meaning customers can no longer access the system by using IE. 

If your customers are currently using Internet Explorer 11, inform them that they must now switch to another supported browser, because they will lose access once their environment is upgraded to 22.1.0 regardless.

Read more here about Internet Explorer becoming an End of Life (EOL) software.