Home
Qatalyst
Home
Qatalyst
Getting Started
Study creation & Analytics
Question Blocks
UX Blocks
Qatalyst Features
User Management
Roles & Permissions in QatalystAccess User ProfileView User ListChange Roles of Users
Release Notes
Release Notes - 12th, September 2024Release Notes - 30th August, 2024Release Notes - August 22 , 2024Release Notes - August 14 , 2024August 8th, 2024July 24th, 2024July 17th, 2024July 10th, 2024June 28th, 2024June 20th, 2024June 18th, 2024May 31st, 2024May 27th, 2024May 23rd, 2024May 14th, 2024April 23rd, 2024March 28th, 2024March 19th, 2024March 6th, 2024March 6th, 2024February 29th, 2024February 16th, 2024February 14th, 2024February 8th, 2024 February 01st, 2024January 31st, 2024January 24th, 2024January 11th, 2024December 29th, 2023December 20th, 2023December 14th , 2023December 6th, 2023November 22nd, 2023November 20th, 2023November 6th, 2023October 27th, 2023October 18th, 2023October 9th, 2023September 22nd, 2023September 15th, 2023September 8th, 2023September 6th, 2023August 31st, 2023Release Notes - August 24th, 2023Release Notes - August 21st, 2023Release Notes - August 19th, 2023Release Notes - August 2nd, 2023Release Notes - July 27, 2023Release Notes - 17th July, 2023Release Notes - July 11th, 2023Release Notes - July 4th, 2023Release Notes - June 21st, 2023Release Notes - April 20th, 2023Release Notes - June 9th, 2023Release Notes - June 7th, 2023Release Notes - June 5th, 2023Relase Notes - May 26th, 2023Release Notes - 22nd May, 2023Release Notes - May 19th, 2023Release Notes - May 12th, 2023Release Notes - May 5th, 2023Release Notes - April 28th, 2023Release Notes - July 19th, 2023Release Notes - April 7th, 2023Release Notes - March 30, 2023Release Notes - March 28, 2023Release Notes - March 23, 2023Release Notes - March 21, 2023Release Notes - 17 March, 2023Release Notes - 04 March, 2023Release Notes - 18 February, 2023

Relase Notes - May 26th, 2023

What's New✨

  • We are thrilled to introduce the non-tech insights for the Prototype test in the result section. This will empower users to access important insights on the resulting dashboard once a test begins collecting information. Key metrics such as Success Rate, Average Time, Drop-off Rate, Alternate Path Analysis, and Tester Level Data (including time spent and movement back to previous screens etc.) are now accessible. These insights provide users with valuable information to understand user behaviour, make data-driven decisions, and enhance the user experience of their prototypes.

Note: Insights for Tech(facial coding, mouse tracking and eye tracking) is under development and will be coming soon.

  • Added a new feature that allows users to sign up and sign in using their Microsoft accounts from any external account outside entropik.io. With this integration, users now have the convenience and flexibility to utilize their Microsoft credentials to create an account and access our services seamlessly.
  • Added a new feature that enables the creation of a context screen within a study, allowing users to provide instructions and context to testers. This feature allows users to insert a simple extra screen between any two blocks, offering valuable guidance and engagement to participants during the test. With the Context Screen, users can effectively communicate important information, set expectations, and provide necessary context, enhancing the overall testing experience and ensuring clarity for testers. 
  • Enhanced the mouse click view in the heatmap by displaying the actual mouse clicks as points instead of a heatmap visualization. With this update, users will now see the exact points where the mouse was clicked, providing more precise information about user interactions. Additionally, if multiple clicks occur at the same spot, the intensity of the point will increase, allowing users to identify areas of high user engagement. 
  • Added a new feature that enhances the respondent experience by highlighting the hotspot areas in a prototype. When a respondent clicks on areas that are not designated as hotspots, the hotspot areas will be visually highlighted to inform the user of their selection. This feature ensures that respondents are aware when they interact with non-responsive or inactive areas of the prototype, preventing any confusion or frustration. 
  • Now the names of the studies will be automatically generated when created using Artificial intelligence. With this enhancement, users no longer need to manually enter study names during the creation process. The system will generate unique study names, saving users time and effort. 
  • Added functionality to send the skipped screen data in the prototype testing to the testers response data. When a user skips a block while on the prototype screen, the specific screen at which the skip occurred will now be included in the tester response data. This addition provides valuable insights into user behaviour and interaction patterns, allowing users to analyze the reasons behind block skips and optimize their prototypes accordingly.

Bug Fixes🔧

  • We have resolved a bug where a validation error was not triggered when the first journey path only partially covered certain journeys. The issue has been resolved, ensuring that a validation error will now be properly triggered when the initial journey path fails to include all the required steps for these journeys. 
  • Fixed a bug that allowed users to access the A/B, 5 sec, Preference block's dropdown menu in Add Block Mode/Post Publishing. With this fix, the dropdown menu for A/B, 5 sec, Preference blocks will be disabled and inaccessible during Add Block Mode and after post publishing.
  • Resolved an issue where the mouse heat map was not being displayed for prototype screens. Previously, users were unable to view the mouse heat map in the result section of their studies, which provides valuable insights into user interactions and behaviour. With this fix, the mouse heat map will now be properly displayed for prototype screens, allowing users to analyze and optimize their designs based on user interactions. 
  • Fixed a bug that caused incorrect capturing of mouse clicks in the Tester view of the study. Previously, the recorded mouse clicks did not accurately reflect the actual clicks made by the tester. However, our development team has implemented a fix to ensure that mouse clicks are now correctly captured in the Tester view.
  • Resolved a bug where the user's self-profile was inadvertently changed when updating any profile from the user list. Previously, when a user made changes to another user's profile, it resulted in unintended modifications to their own self-profile. With this fix, the system now ensures that only the selected user's profile is updated without impacting the self-profile of the user performing the update. This improvement ensures the integrity of user profiles.
Powered by Product Fruits