Introducing Platform 17.3 – our latest release, filled with key bug fixes and performance enhancements. This update not only improves the current experience but lays the groundwork for some exciting new features that will be announced in our upcoming release, Platform 18.
⬆️ Your Pia aiDesk tenant will be updated to PR 17.3 by end of March 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 🌟
- Enhanced several areas of the platform to better support client profiles. Scheduled automations can now execute against client profiles, and the 'get_clients' activity will also return the client profiles linked to each client. (#26703)
- The schedule for later activity can now be used inside an extension automation allowing you to schedule an extension. (#27097)
- The "Chat Suggest Packages" activity now allows suggesting the current package in the Pia Chatbot if the internal id of the current package is defined in the activity. (#26986)
- When accessed through a Sandbox, the Pia chatbot now displays an informative bar at the top informing you that the package options being displayed are for the current sandbox you are in and gives you the option to Switch to live. (#26921)
- Updated the package and activity editor so that automation engineers can scroll past the bottom - this was pre-existing behavior before the editors were upgraded in Platform 16 but it was missed so we've added this feature back in. (#26610)
- Updated the Triage Ingestion popup in the AI & Triage screen so that the id and value of the ticket status is stored correctly and in a manner that supports multiple ticketing system workflows. (#26744)
- The Form Editor screen has been updated to keep the text formatting consistent within different form fields. (#26793)
- Added memory limit warning threshold for logging to activity log output when memory limit of a PowerShell script is approaching. Also improved memory limit reached error logging to help with troubleshooting when a PowerShell script fails to execute due to exceeding memory limit. (#26879)
A hard memory limit of 600mb has been placed with platform 17.3 release for any PowerShell which is run on your Pia tenant backend (if you run a PowerShell script via an agent, the limit does not apply). This limit prevents your scripts from destabilizing your tenant - which you could do prior to 17.3 if you created a really memory hungry activity which would result in your tenant crashing and require a restart.
The primary purpose of the limits is to prevent accidental abuse or misuse of the tenant, not to be constraining limits. If you encounter an issue or foresee an issue with this on any work you have done on your tenants, please contact Partner Support.
- When promoting a package to live, a copy is now automatically saved in the Sandbox. You can turn this feature off by enabling the "Remove the package from my Sandbox" option in the Promote to Live popup of the Package Editor screen.
- The Time logging feature in the tenant settings previously only allowed to set time logging for Pia aiDesk Automations. This has now been modified to allow time logging to be configured for all automations, including custom automations built by partners. (#26931)
- Improved error handling in packages to ensure that when a package stops after meeting a stop condition, it no longer appears as failed on the live packages screen. (#26851)
- You can now add conditional display formatting to line breaks in the form editor. In addition, hyperlinks are now supported when using a paragraph via the form editor.(#27108)
Bug Fixes 🐛
- Fixed an edge case scenario where the MS Graph Token retrieved by the Pia: Reset/Modify Users MFA Authentication package was not processed correctly causing package failure. (#26845)
- Resolved an issue within the platform which prevented the function packages from looping in a case where a global variable was null. (#26612)
- Fixed an edge case scenario for a partner where the Pia Agent was failing to register due to a missing client record. (#26964)
- Added a filter to the User Groups screen so that deleted users are no longer displayed in the User groups summary. (#26467)
- Fixed an issue where the Pia Condensed Pod item was multiplying in the ConnectWise Pod Configuration everytime the connected service for ConnectWise was reconfigured in the partner portal. (#26720)
- Fixed an issue where the new variables added to an activity were not being processed through the package. This issue occurred only in the sandbox mode. (#26705)
- Fixed an issue with the Package Configuration form where the values in the form fields were autoselecting if they form fields had similar values to another selection. (#26632)
- Resolved an edge case for a partner using the AutoTask ticketing system, where multiple Pia chatbot windows were unexpectedly opening within the tickets. (#26558)
- The Live Packages screen has been optimized to prevent browser tab freezes when viewing large ticket outputs, especially on less powerful machines. (#26711)
- Updated the AI & Triage screen logic to prevent the failure of board / status collections for AI & Triage if some of the boards aren't able to be read. (#26817)
- Fixed an issue with Zero Touch Automations where Pia incorrectly marked the ticket status as 'Package Completed' in the ticketing system, even when the automation had failed. (#26890)
- Resolved an issue with SmartForms AI Auto-Reply not working correctly in some edge cases related to how specific automations were configured to use this feature. (#26842)
- Fixed an issue with the Pia Chatbot where the activity log was not displaying the correct step or the activity the package was executing. (#26628)
- Fixed an edge case where the config watcher incorrectly reported agents as offline for a partner, even when they were online. (#26745)
- Fixed an issue where the form data defaults were not being passed in properly to the form controller when producing the output for the Get Client Config form activity. (#26869)
- Resolved an issue for a partner where the chatbot was stuck while executing an automation and they were unable to cancel the request as well. (#26953)
- Resolved an issue in SmartForms where the 'Get Form Data' activity was returning incorrect data when multiple extensions were appended to the SmartForm. (#26774)
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!
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! 🚀