Skip to main content

Platform 13.2 Release 🏭

What's New 🌟​

We are releasing a new Platform version containing additional bug fixes - Rc13.2!

Planned Release Date: Rollout period between 12/02/2024 and 16/02/2024

This release includes further bug fixes and additional enhancements see below:

  • 12 Bug Fixes 🐛

See below for further details.

As always, Partner Support is available to assist you.

🐛 Bug Fixes​

  1. Fixed an edge case scenario where the connected service for Dicker Data was failing for a partner due to insufficient information provided during API calls. (#22893)
  2. Fixed an issue where Pia was making multiple unnecessary API calls for the ticketing system connected service due to large amount of tickets being updated at once triggering those callbacks. (#22901)
  3. Amended a Partner issue for Office 365 Connected Service which was caused due to missing redirect URL during tenant provisioning. (#23088)
  4. Updated display of Scheduled ticket Ids in Pia so that they are correctly displayed in the Live Packages Screen for AutoTask. (#23179)
  5. Updated the Agent Version Health Rule in the Config Watcher to only filter for agents which have hit max retry count and are not on latest version. (#23270)
  6. Updated the Config Watcher to filter out deleted client tags before client packages are checked so that the alerts are correctly displayed in the Config Watcher. (#23273)
  7. Fixed an edge case scenario where a partner was not able to submit feedback in the Pia chatbot. (#23284)
  8. Updated the Software screen to resolve an issue with adding software via a link. (#23302)
  9. Updated the connected service for HaloPSA to give more details about permission issues. (#23347)
  10. Updated the Activity Editor screen to remove a restriction that allowed Global Variable to only be edited by the user who created it. (#23355)
  11. Amended a minor issue with the Software Screen so that the software versions are now sorted correctly. (#23367)
  12. Fixed an edge case scenario where the Scheduled package would succeed but send both a failure and success email to the engineer (instead of just a success email). (#23435)