⬆️ We expect most of the rollout to be completed by first week of July. There’s no need to refresh your Pia tenant, you’ll automatically receive an email with the Release Notes as soon as the latest version becomes available to you.
Enhancements 🌟
- Added the ability to modify a form static name when copying the form to a sandbox. This will allow engineers to clone the form when copying to another sandbox instead of recreating the form in its entirety. (#31806)
- Improved styling to the email templates generated through approvals to ensure consistent rendering in Outlook, addressing display issues for some Partners. (#31874)
- Added support for configuring the Post‑Processing Delay in the Triage V2 automation. This allows partners to pause triage for a defined period, preventing infinite loops or unintended additional executions. (#31407)
- Improved error handling to better support scenarios where Halo PSA tickets fail to load in the Tech Assist bot due to insufficient Halo API permissions. (#31524)
- Adjusted the processing order of SmartForms submission events and workflow status updates to prevent PSA API overwrites. (#31725)
- Extended the SmartForms automation expiration window from 72 hours to 7 days to better handle scenarios where tickets created late in the week aren’t reviewed until the following Monday. (#32016)
- Improved Triage Dispatch company/contact selection performance for ConnectWise by loading active companies only in triage flows, reducing long-running company queries and dropdown load failures. (#32080)
- Modified the AI AutoReply email templates to return the display Ticket Id rather than the internal ID for AutoTask partners. (#32091)
- Added a retry button to the Microsoft Graph API authorization tile to allow retry if consent is taking time. (#32176)
- Added support for entering additional field types in global variable values such as storing URLs and keys (#32232)
- Modified the policy around retrying if a ticket creation fails due to transient timeouts or other network related responses. (#32246)
- Updated the triage variable resolver to retrieve rulesets more efficiently, preventing excessive database usage. (#32274)
- Updated the package YAML validation check to respect case insensitive static names when copying to other sandboxes / promoting to live. (#32311)
- Modified the Azure user sync to set firstname and lastname updates on user accounts when syncing an existing user. (#32360)
- Integrations downloaded from the Automation Hub can now specify a custom API Base URL. This supports scenarios like the Onetime Secret PiaPack, which may require a region‑specific API endpoint. (#32456)
- Removed the 200‑character limit on Integration Definition Variable defaults for consistency with Integration Configurations. (#32487)
- Improved the performance of the live package view for some scenarios. (#30299)
- Updated our Agent dependencies as a part of regular management of agent security. (#32102)
- Added the ability for automation engineers when developing custom automations to pass in dynamic approval point configuration. (#32363)
Bug Fixes 🐛
- Resolved an issue where the Tech Assist bot occasionally displayed the wrong approver’s first or last name after an approval was completed, even though the approval history remained correct. (#31831)
- Fixed a styling issue in email templates for AI AutoReply and approval emails to ensure the uploaded branding logo is a normal size on the email template. (#31837)
- Fixed an issue where automation deployments could generate stale activity PowerShell code, causing scheduled automations to fail validation during execution. (#31873)
- Fixed an issue where unsubmitted SmartForms tickets didn’t update status after the set time limit. (#30564)
- Fixed an issue that could result in duplicate activity versions when promoting an activity from sandbox to live. (#31002)
- Resolved an issue where deleted users would be displayed under the Pia Champions list in the adoption report. (#31015)
- Fixed an edge case where a ticket may not auto close after the completion of the scheduled child automation. (#31312)
- Fixed an issue where agents were not correctly identified when executing under a client profile for a child client. (#31603)
- Resolved an issue where duplicate clients were being created during sync for Partners who migrated to Halo PSA. (#31657)
- Fixed an issue with the odata nextSkip and nextTop response from the API when using paging. (#31772)
- Fixed an issue where clicking "Nevermind" when attempting to start a secondary automation on a chat session was causing errors. (#31894)
- Resolved an issue with health check event processor where Pia may fall into a state where a health check is missed, leading to never queuing the check and resetting its status. (#32017)
- Fixed SMS sender-number routing for Burst API so recipient destination drives sender selection for E.164 numbers. US/CA destinations (
+1) now use the US virtual sender number, preventing AU-tenant to US-recipient routing failures. (#32159) - Fixed performance issues caused by looping scheduled automations by adding in constraints to the cron scheduled expression to prevent automations from being queued at intervals of every second. (#32234)
- Fixed an issue where a misconfigured Tenant logo could lead to failed email sends configured in approval points. (#32252)
- Fixed an issue where some Partners could not see AI Triage extension points when their configured triage package was set to ‘latest’ but not yet published. (#32312)
- Resolved an issue where a deleted user sync rule was still being applied preventing management of the user role in the SmartForms portal. (#32388)
- Fixed an issue where consecutive API events could trigger duplicate automations to execute. (#32403)
- Fixed an edge case where the Editable table in the Tach Assist pod was not displaying correct data for a Partner. (#32498)
- Resolved an issue in the SmartForms Extension point screen where it was clipping off the data schema. The Extension point screen now shows the full data correctly. (#32514)
Your feedback matters to us! 💜
🛠️ We're here to address any issues or suggestions you have, just drop us a line at partner-support@pia.ai for assistance.
💡 Got ideas to enhance Pia aiDesk? 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! 🚀