Agile Research 25ARCR2.2 release notes

Release starting 16 June 2025

Highlights

  • The Text Analytics Best Practice Package (BPP) is a background process that runs every hour to send respondent data (for text-based question types) from Agile Research to Experience Cloud. It includes all active and closed Agile Research surveys from their accounts created within the last 12 months of installing the BPP. This process only sends the first five text-based questions from a survey, and then a "combined" field which aggregates all text-based questions.
  • The following enhancements have been made to the Survey Settings (Options) Page:
    • A new option added as Change Domain to change the default domain for the survey. This will not show for accounts that don't have survey domains.
    • Two separate checkboxes for contacts and respondents are available for Data Retention.

Resolved issues

  • Fixed an issue where the Questions page was not accessible in some cases.
  • Fixed an issue where uneven weighting splits were not able to be set.
  • Resolved an issue where SPSS reports were populating data in incorrect columns because of bad data.
  • Added implementation for data labels for the matrix question type in SPSS exports.
  • Resolved an issue where the SPSS report failed to export when a radio button question contained more than 100 choices.
  • Conjoint's attribute choice texts show in full on survey previews/live link, which is the same behavior as is in the editor.
  • If a question that is missing a required question type is attempted to be saved, an error message appears.
  • The following accessibility issues have been resolved:
    • Labels of the radio buttons in the Matrix (single select) question type have a display:none; in the CSS.
    • Screen reader users hear "indeterminate progress indicator" or a similar description instead of "Upload complete" followed by the file name.
    • In a JAWS screen reader, focus goes to the top of the page after a file is uploaded.
  • For MaxDiff question types, results for the utility score are accurate when switching the question layout from "Best - Attribute - Worst" to "Worst - Attribute - Best".