Bug fixes

  • Admin - ViewBag.Title = “Logs”;} code appears on the Logs screen in admin
  • Edit Role - Page formatting lost after scrolling beyond the page footer
  • ETL package - “Uncaught TypeError: Unable to process binding “css: function(){return {‘text-danger’:databaseName().length > 128} }”” error thrown when selecting Atmolytics version in the package manager
  • ETL package - Renamed forms are not flagged as renamed in the version history on the form selection screen
  • ETL package - No data state is not displayed when form search returns no results
  • ETL package - “Staging Database Settings” heading is shown when settings are hidden before an Atmolytics verison is selected in the package manager
  • ETL package - Character count doesn’t increment when entering database name until tabbing out of the field
  • ETL package - Form updates are not applied when selecting “Apply updates” from the form update modal
  • ETL package - Newly created and updated forms added to a package show the form name twice on the same line for each individual form in the form selection list
  • EULA - EULA is not fully readable because the white background covers less than half of the agreement when the page is viewed at 100%
  • Exports - “Most Recent Export” date is incorrect when an export is initially created and not yet exported
  • Exports - “No Data” state\message is not displayed when searching exports returns no results
  • Exports - Forms with long names overflow the “New forms available” modal container when performing an export
  • Exports - Long form list overflows and page styling is broken when adding forms to an export
  • Exports - Incorrect spacing on the “InProgress” status pill when exporting forms
  • Exports - Date in “Most recent export” column isn’t updated when the export finishes until the page is refreshed
  • Exports - Lazy loader for form selection when editing packages doesn’t load the list correctly when scrolling
  • Exports - When an input/selection is invalid the ‘Save’ button remains disabled even when the issue has been rectified
  • Exports - “Save failed: One of more forms were invalid” when any form version that is not the most recent is selected
  • Exports - Styling of the “my exports” screen scrolls past the formatting. 
  • Exports - HTML is rendered in the export definition when viewing the list of forms
  • Form designer - ‘Choose a question’ - Can’t start typing unless you click in the box first
  • Form designer - “Uncaught (in promise) TypeError: Unable to process binding “with: function(){return editLine().question }” thrown in the console when editing a header on a published form in V2.26
  • My forms - The dropdown lists ‘Large Data’ as an option. This is currently only used for one customer. Other organisations are unable to create a ‘Large Data’ form using the ‘Create new’ CTA. This is now feature flagged for Atmoforms only. your Imosphere data entry solution customers will no longer see this option
  • New Export - This has been redesigned so that rather than warning messages appearing, the ‘save’ button is greyed out until the mandatory criteria as been satisfied: Export is given a name, Export is given a description, At least one form has been selected, Export format selected.
  • Users - Filter search of ‘Full name’ does not match upper case input
  • Users - “No Data” state\message is not displayed when entering a term that returns no results in Admin - Access Management - Users
  • Users - When navigating to Admin - Access Management - Users the page briefly displays no roles\users have been created messages before loading the list