Skip to main content

Platform 18.1 Release 🏭

Following our major Platform Release 18.0, we are excited to introduce Platform Release 18.1, packed with additional bug fixes and enhancements to further elevate your experience!

When will I receive Platform Release 18.1?

⬆️ Your Pia aiDesk tenant will be updated to PR 18.1 by end of July 2025.
No need to keep refreshing your Pia tenant! You will get an email with the Release Notes when you receive the latest version.

Enhancements 🌟​

  • Implemented browser language reading for Date/Time selectors within forms so that the Date Picker form now displays Date/Time format based on locale of the browser. (#27572)
  • The Get Ticket Data activity has now been updated to output Agreement and AgreementType associated with the ticket. (#27862)
  • Created a new built in classification - Incident|Workstation|Disk Space classification so that it can be mapped to the Pia: Computer Space Cleanup package to or to map low space alerts. (#27934)
  • The Set Agreement Action in the Triage: Dispatch screen is now converted to a text input field instead of a drop-down selector. (#27925)
  • Implemented html removal when submitting SmartForms so that initial audit notes are not bloated with unnecessary data. (#27635)
  • The text input form field in the form editor now allows you to modify the minimum input length in the form. (#28023)
  • Implemented caching to prevent rate limiting on the Dicker data connected service. (#28017)
  • The Smartforms: Staff Onboarding automation now gives you the ability to customize SMS text sent to the newly onboarded staff. This includes updating the SMS with variables such as #password, #upn, #displayname and #ticketid. (#27562)
  • A new "Business Name" field has been added to the Tenant Settings screen, allowing you to define your business name. If you fill out this field, it will be used in place of your tenant name where referenced in the SmartForms Portal. (#28179)
  • Updated Halo PSA webhook implementation to handle a new requirement from Halo to register specific fields when Pia performs webhook registration in Halo's System. (#27248)
  • The Scheduled Package condition has been updated to include a new optional input parameter, "unpublish_on_completion". You can use this as a way to force your scheduled automation to run once at the scheduled time and then self disable. (#28114)
  • The Adoption Report has now been updated to present SmartForms event and Chat Event automations only excluding custom scheduled events that may cause discrepancies in the report. (#28196)

Bug Fixes 🐛​

  • Fixed an issue where Pia was not suggesting Package selection option after the completion of AI Autostart automations. (#27634)
  • Resolved an issue where the Triage: AI Classification feature was failing if custom classifications included trailing and/or leading whitespaces. (#27885)
  • Fixed an issue in live packages screen where executing activities was not showing the correct timer. (#27807)
  • Fixed an issue where renaming ConnectWise boards was affecting triage mappings causing the tickets to not dispatch. (#27751)
  • Resolved an edge case scenario where duplicate tickets were being created for a Partner while running the IT Help Request SmartForm. (#27678)
  • Resolved an issue where the company_id variable was not populating with the ticketing system client id, but rather the pia clientUnderSupport id when executing a ticketing system event package execution. (#27997)
  • Fixed an issue where Halo Integration was not working due to modifications in the API response process by Halo. (#27816)
  • Fixed an issue where the chatbot was allowing engineers to submit the same form twice (e.g. if you have two browser windows open and hit submit at the same time). (#27753)
  • Updated the Edge/Chrome Extension for AutoTask/Halo PSA to prevent the Pia popup from appearing on the login screen of AutoTask and Halo PSA which was causing some confusion for users. (#27752)
  • Fixed an issue within the Canvas screen where the drop-down form fields in an executing automation was spawning away from the pod window. (#28003)
  • Fixed an edge case scenario in the Partner Portal where invalid ITGlue configurations for a client were preventing the client page from rendering. (#28157)
  • Resolved an issue where scheduled child packages were failing to generate audit notes in tickets. (#27421)
  • Resolved an issue that caused the Partner Portal to crash whenever the Agents screen table was sorted or filtered. (#28143)
  • Resolved an issue in the repeating section where default values were not automatically populated in a newly inserted section. (#28092)
  • Resolved an issue whereby Pia would become unresponsive and require a tenant restart for a handful of partners for a specific edge case due to a cache reset timing issue in combination with high demand / certain demand profile on the Pia tenant. (#28266)

Stay Connected with us at Pia! ⚡

Your feedback matters to us! 💜 🛠️ We're here to address any issues or suggestions you have, just drop us a line at our partner support email address for assistance.

💡Got ideas to enhance our platform? Share them at ideas.pia.ai and shape the future of Pia aiDesk! ⚙️ Ready to supercharge your automation journey?
Your Partner Success Manager is your go-to person. Reach out to them to explore custom automation possibilities and optimize your journey with Pia aiDesk.

Let's make AI and automation magic together! 🚀