3.7.10 Update

Welcome to 2023 from Conductrics! Our first update for the year is 3.7.10.

While this is a relatively small update, there are a few minor improvements and fixes which may prove useful.

Those of you on dedicated Conductrics instances can request an update on your schedule, just reach out to us via the usual channels. As always, let us know if you have any questions!

  • Improved - Added a Auto-refresh CDN when deploying option for Express/JS Deploy Targets. When enabled, should eliminate wait time when making changes to agents during development. If this option isn't available for your deploy targets (under Settings > Deploy Targets > Edit > Distribution tab), contact Conductrics so we can enable it for you. #802

  • Improved - Added a Deploy Priority setting at the Deploy Target level (under Advanced Settings), for situations where it's important for a particular deploy target to be rebuilt before the others (you might also consider using Manual Deploys). #833

  • Improved - Added ability to remove/stop a QA Session given by its ID via the "trash can" icon in the QA Sessions window. This can be helpful if you want to "start over" for a given identifier, and you don't have an easy way to use a different identifier on your side. #831

  • Improved - The "Filter by Name" field on the Agent List page is now preserved if you go to another page and then return to the Agent List (within the same admin session). #845

  • Added - A simple Event Logging facility has been added to the Conductrics Admin for debugging a REST API implementation. Express / Local deploy targets may also be supported in the future. #855

  • Fixed - The Survey Responses report wasn't available for archived Surveys that had been archived (or for Surveys that had associated agents that had been archived or deleted). #836

  • Fixed - When using Provisional Selections, it was possible for selections to be under-counted if subsequent calls to "confirm" omitted the s parameter altogether. #841

  • Fixed - The Preview Launcher button wouldn't show for API agents that were only associated with certain Deploy Targets that were dual-enabled for the REST API and client-side use #843

  • Fixed - If using Single Sign-On (SSO) for logging into Conductrics, authorization could fail if the email address provided by the SAML IDP (such as Okta) was in Mixed-Case instead of lowercase. #847

  • Fixed - Certain Deploy Targets could get auto-associated with new Express Agents when they were first created, disregarding the corresponding settings at the Deploy Target level. #853

  • Fixed - Saving a Survey could fail with an error message if any of the Answers to a "Pick One" or "Pick Multiple" Question exceeded 50 characters and its "Track as Visitor Trait" option was on. #856