<img src="https://secure.leadforensics.com/85165.png" alt="" style="display:none;">
Skip to content
English
  • There are no suggestions because the search field is empty.

Tractivity v24.2.3 - Release Notes

Our last release of the third quarter brings bug fixes and updates as requested by you

Improvements

  • Mapolitical - Duplicate Checking
    The internal tools used to identify duplicates when carrying out Mapolitical imports have been strengthened, further eliminating the chance of duplicate Contacts being added to your system.

    Bug Fixes

    The below bugs reports have now been resolved.

    • Issues - Copy and Paste formatting
      The "Copy and Paste" tool was found to produce irregular formatting for the pasted text in some instances.
    • Issues - Highlighting text
      The text highlighter in the Issue tagging window was found to be erratic, highlighting multiple sentences unintentionally.
    • Events - Invalid email notice
      Email addresses entered into the Event registration form would be flagged as invalid, even if the main Tractivity system found them to be valid.
    • Mailshot - "HasError" Status
      A Mailshot was set with this Status, resulting in the Mailshot Statistics being unable to view.
    • Organisation and Contacts - Incorrect search results
      A search using a Category filter was returning stakeholders who were not tagged with the chosen Category.
    • Reports - "All Users" Report
      When the toggle for showing data across all Projects was set to '1', the Report would produce an incorrect number of Users.
    • Reports - Enquiry Report duplicates
      The Report Scheduler had been found to create multiple rows of the same Enquiry in Enquiry Reports. 
    • Surveys - Accessibility issue
      An issue was raised where screen reader software had difficulty reading out certain types of questions in Surveys.
    • Surveys - Error messages
      The development team identified crashes that would happen on occasion when registering or completing a Survey.
      • A similar issue to the above when registering for an Event was also resolved.