38 posts tagged with "platform"

7 New PiaPacks 🌟​

Logout Azure Virtual Desktop User Sessions
Automate Azure Virtual Desktop (AVD) session logouts - securely retrieve active sessions and log out users via chatbot or SmartForms, ensuring fast and consistent management without the hassle.

Manage Office365 Email Lists
Simplify Microsoft 365 email security with SmartForms automations that let customers manage allowlists and blocklists instantly, reducing Service Desk workload while ensuring accuracy and compliance.

Export Users and Groups to CSV
Retrieve user and group information from Active Directory allowing engineers to quickly generate CSV reports through the chatbot.

Delete Contact via Active Directory
Clients often request contact removal from Active Directory when roles change. Using Smartforms with Zero-Touch enabled, our Delete Contact automation removes selected entries instantly, removing the burden from your service desk by allowing your clients to self-serve.

SmartForms: Add/Remove Access to Groups
Automates new user creation in Google Workspace via Pia’s onboarding workflow, reducing manual effort and errors by collecting details, assigning groups, and logging actions in tickets.

SmartForms: Create Mail Contacts
The Create Contact Pack automates mail contact creation via SmartForm, supports bulk entries, and assigns contacts to Active Directory or Azure AD groups, reducing manual engineering workload.

Datto RMM Operations Bundle
Bring Datto RMM workflows into Pia. Create and track QuickJobs, retrieve job results via GUID, and pull device details + alerts - reducing context switching, improving reporting consistency, and speeding up technician triage.

7 New Blueprints 🌟​

Activity Collection for Microsoft Exchange
A collection of Pia built and endorsed Exchange activities for you to use or reference when writing your own custom automations.

Activity Collection for Active Directory
Provides a sample of Active Directory automations which are used within our pre-built automations, allowing you to customise and build your own packages without starting from scratch.

Activity Collection for Microsoft Exchange
A collection of Pia built and endorsed Exchange activities for you to use or reference when writing your own custom automations.

Activity Collection for Workstations
Provides a sample of Workstation/Laptop activities which are used within our pre-built automations, allowing you to customise and build your own packages without starting from scratch.

Using Azure Key Vault for Secrets
Need to store sensitive secrets and not sure how to use them in your own automations. This sample provides a simple example of retrieving a secret from your Azure Key Vaults.

Client Package Configuration for your custom automations
Build your automation to work for all clients, the included package includes custom forms for configuration and even demonstrates how you can set the configuration from your automation.

Trigger automations from your custom package with inputs and outputs
Did you know you can chain your automations? Using the built in start_package activity with inputs and outputs you can orchestrate multiple automations together.

1 Updated PiaPack 🌟​

Gsuite New Staff Onboarding
Automates new user creation in Google Workspace via Pia’s onboarding workflow, reducing manual effort and errors by collecting details, assigning groups, and logging actions in tickets.

With the new update, this PiaPack now supports clients with single directory too!

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)

To learn more about Pia Engage and Pia Chat product, follow the links here:

• Pia Engage
• Pia Chat
• Pia Chat Branding
• Pia Chat Workflows

Enhancements 🌟​

• Implemented functionality to invoke the Get Form Data (get_form_data) activity from a scheduled package, enabling the collection of data from Extension automations within the scheduler package. (#29311)
• Updated the Pia: Reset Network Password automation to respect the toggle "Show Passwords when submitting Forms" in the Tenant Settings screen, allowing Partners to control whether passwords appear in audit notes during automation runs. (#29480)
• Updated the Scheduled Packages screen so that when a scheduled package date is edited, the date format now follows browser locale settings. (#30134)
• Modified the current method of setting priorities in Halo PSA, we should now provide partners with options of SLA > Priority, which allows granular selection of priorities. (#30656)
• Added the CompanyType to the Triage dispatch configurations for ConnectWise partners, this allows conditions to be executed dependent on the company type of the client. (#30684)
• Updated the Get Approval (get_approval) activity to provide Engineers with additional options when approval attempts exceed the limit (one original attempt and two escalations) without receiving a response from approvers. (#30688)
• Updated the SmartForms user contact sync feature so that any changes to the user is correctly reflected in the SmartForms portal. (#30837)
• Updated the ConnectWise integration to collect the contactEmailAddress for Partners, enabling identification of email addresses used in catch‑all tickets. (#30979)

Bug Fixes 🐛​

• Fixed an issue where the Agents without client mapping were not being sorted correctly. (#29349)
• Fixed an issue for a client where the SmartForms status was not updated on time due to delay in SmartForms submission. (#29837)
• Fixed an issue where the Pia: Triage V2 automation was timing out for multiple partners. (#30303)
• Resolved an issue for a Partner where changing multiple group names in the Active Directory was causing sync issues. (#30402)
• Fixed an issue where form submissions were failing after client disconnection and continued failing even after the connection was re-established. (#30448)
• Resolved an issue where the Partner was unable to obtain a license through Ingram Micro while running the SmartForms: Staff Onboarding automation. (#30454)
• Fixed an issue where child clients were not being excluded from config watcher health alert emails. (#30462)
• Fixed an issue where the chatbot was not updating for some Partners that used AutoTask or Halo PSA. (#30491)
• Resolved an issue where the per client component of the custom integration form was not working as expected. (#30560)
• Fixed an issue where the article notes added by a Partner for an automation were not appearing in Tech Assist chatbot info section. (#30618)
• Fixed an issue where automations with system ticketing events were not triggered due to rate limiting by Halo PSA. (#30623)
• Fixed an issue where modifying field values in an Editable Table caused the returned Form object to lose its original nested structure. (#30670)
• Fixed an issue for a Partner where the connection test for ConnectWise integration was not completing as Pia was collecting more data than required. (#30805)
• Fixed an issue where Extension automations were preventing SmartForms workflow statuses from being set. (#30807)
• Fixing an edge case where a Partner was receiving false positive Config Watcher Alerts for Triage Health Rules. (#30809)
• Fixed an issue where the SmartForms: User Offboarding automation failed to load due to insufficient permissions for Pia’s API to write audit notes. (#30826)
• Fixed an issue where the Partner was getting an error while testing a rule with null subject or description in Triage AI Analysis. (#30885)
• Resolved an issue where legacy users in the Pia Portal were provided Partner Administrator permissions in SmartForms if their account was attempting to be downgraded. (#30926)
• Fixed an issue where SmartForms workflow rules were not applied when engineer interactions occurred within a child package. (#30942)
• Fixed an issue where the AI Analysis test rule view in AutoTask displayed the ticket ID instead of the correct display value. (#31152)
• Fixed an issue for a Partner where they were not able to add licenses from Pax8 while running automations. (#30836)
• Fixed an issue where SmartForms submissions were not updating ticket in Halo PSA. (#31578)
• Fixed an issue where Pia was adding internal notes to older tickets. (#30849)
• Fixed an issue where clients were unable to reset Microsoft Graph API authorizations if app consent had been manually deleted from Azure. (#30875)

What's New 🌟​

Major New Features/Release Items​

• Renaming for the Future: Pia’s Chatbot Becomes Tech Assist
• Approvals 2.0: Smarter, Faster & Fully Flexible
• New API Launch: 30+ endpoints covering Build, Automate & Configure scenarios #💡
• New Pia Source VSCode Extension
• Thread Integration Unlocked: SmartForms at Your Clients’ Fingertips
• Enhanced Ticket Controls for Pia Scheduled Automations #💡

Renaming for the Future: Pia’s Chatbot Becomes Tech Assist ✨​

With this release, we are introducing Tech Assist within the Pia Portal. You'll find this on the main menu on the left. Tech Assist was created to centralize all configuration settings required to run your automations smoothly through the Pia Chatbot in your PSA.

Previously scattered options have now been consolidated into one place, making setup within your ticketing system far easier. This new section of the portal also includes new options and features to further elevate your Pia Chatbot experience.

To see the changes, click here. (#27912)

Approvals 2.0: Smarter, Faster & Fully Flexible ✨​

We’re excited to launch a major upgrade to Pia’s Approval Feature. Until now, the Approval feature available within the clients screen only allowed you to create and assign approvers within custom automations that you built with limited functionality.

The new approvals feature is a night‑and‑day upgrade compared to what we had before.

You can now create approval rules for both chatbot and SmartForms automations directly from the new Tech Assist screen in the Pia Portal. This enhancement also allows you to:

• Create approval rules for individual users, user groups, synced user or user roles within Pia
• Build multi‑layered approval flows across all pre-built and custom automations
• Easily configure approval for pre-defined points in pre-built automations or create extensions to add your own approval logic if you need more control using the new Approval Point Activity.

For more on this feature, click here. (#25651)

New API Launch: 30+ endpoints covering Build, Automate & Configure scenarios ✨​

This was an idea submitted by our Partners! #💡

In response to Partner feedback, we’re releasing an API that gives MSPs greater flexibility to build advanced solutions and adapt Pia to their unique workflows.

We're introducing three new API surfaces:

• Build: We're releasing API endpoints which will allow you to push and pull Pia automation scripts/code to and from Pia. You may use this to take backups your automations or help make it easier to import automations into Pia.

• Automate: Due to popular demand, we are allowing Pia automations to be triggered via API endpoints. Use these APIs to discover/retrieve automations, trigger them and then monitor their executions by downloading their execution logs.

• Configure: To make management of your Pia tenant even easier, we are initially launching API endpoints to help you manage Agents with the ability to activate, de-activate and uninstall agents as well as working with clients' information via API.

To learn more about how to setup API access and use the new APIs, read this article (#28801).

To see what API endpoints are available, access these swagger docs here: Build , Automate and Configure.

New Pia Source VSCode Extension ✨​

The VS Code extension for Pia Source is now here!

The extension is now available for download through the Visual Studio Code Marketplace offering a faster, more integrated way to manage and sync your Pia automations as part of your everyday development workflow.

Pia Source is a developer‑focused automation tool delivered through a Visual Studio (VS) Code extension. It connects your local Git workflow to your Pia tenant so you can pull, edit, version, and push automation packages using your normal development tools. Pia Source lets developers treat Pia automations like code - stored in files, versioned in Git, and edited in VS Code.

For more information on the installation process of this extension, click here.

Thread Integration Unlocked: SmartForms at Your Clients’ Fingertips ✨​

We’re continuing to expand SmartForms compatibility across platforms which has led us to our latest integration with Thread’s Magic Agent. Your clients using Thread can now access SmartForms directly when submitting a request through the Magic Agent without having to log in to the SmartForms Portal.

With this integration, your clients will automatically receive a SmartForms link within their Thread chat whenever a request relates to a SmartForm. These requests will then be processed through your PSA while also incorporating Pia SmartForms Zero Touch Automations.

For more on this integration, click here. (#29055)

Enhanced Ticket Controls for Pia Scheduled Automations ✨​

This was an idea submitted by our Partners! #💡

Pia’s Schedule for Later feature allows both built-in automations and custom automations to pause and resume at a future date. When an action is scheduled, Pia generates a second ticket that resumes the automation at the specified date and time. In platforms that support ticket bundling such as ConnectWise and Halo PSA, this new ticket is automatically bundled under the original as a child while in AutoTask, we add a ticket note to link it to the original.

Based on feedback we've had about creating a separate ticket and bundling, we are introducing a couple of new options that provide our Partners with the flexibility to decide how the scheduled automation will interact with either the original ticket request or new ticket created (if applicable). The available options are:

• Create and Bundle – Creates a new ticket and automatically bundles it under the original ticket
• Create without Bundle – Creates a new ticket that remains separate and unbundled
• Use Existing – Reopens the original closed ticket at the scheduled date and time to continue the automation execution (#25623)

For more information on Ticket Scheduling, go to this article.

🌟Further Enhancements​

• Published the Pia Browser Extension via the Google Chrome Web Store, see the Pia Browser Extension article for the installation url!
• To support easier troubleshooting, the Pia Portal now displays the current Pia version number. This includes both Platform version and the Automation version your tenant is in. (#25657) (This was an idea submitted by our Partners! #💡)
• Updated the automation scheduling feature so that the ticket audit notes created by scheduled automations now use the Partner’s time zone or time‑zone offset instead of UTC. (#30072)
• Added a new ‘ticket source’ dispatch condition to the AI Triage: Dispatch screen, enabling dispatch rules to be created based on a ticket’s origin. (#28821, #28810) (This was an idea submitted by our Partners! #💡)
• Added a new ‘Source’ option to the SmartForms Workflow: Ticketing Defaults section to allow defining the ticket source for SmartForms tickets. This is available in both global and client‑specific settings. (#27497)
• Added two new client health alerts in the Config Watcher: Health Rules to check for any misconfigured PiaPacks or PiaPacks requiring further setup and to check for bundles that have some requirement that is no longer being met ( i.e. integration, delegate, tag etc.). These health alerts are named as below:
  • Pia Automation Hub Integration Configuration Validator
  • Pia Automation Hub MS Graph Delegate Validator (#29691)
• Enhanced the SmartForms workflow so that when a SmartForm request is submitted, the initial description or body of the ticket is automatically updated with the information provided in the form. (#24868)
• Added four new user access levels in the Users screen to allow controlled access of the new Automation Hub feature. These access levels are:
  • View Automation Hub: Gives the user read only access to the Automation Hub
  • Manage Automation Hub: Allows the user to view and perform all actions such as Install, Update and Uninstall PiaPacks within the Automation Hub
  • Download to Sandbox: Allows the PiaPacks to be downloaded to a Sandbox
  • Publish to Live: Allows the user to publish the PiaPack directly in live mode (#29048)

🐛 Bug Fixes​

• Fixed an issue that caused special characters to be stripped out when applying a Ticket Agreement via the AI Triage feature. (#28663)
• Fixed an issue that prevented scheduled actions from being automatically cancelled when an automation was unpublished. (#27144)
• Fixed an issue in Halo PSA where the Triage stamping rules failed to assign the correct Ticket Type and Category when a partner configured all of their categories under Category 3. (#29187)

🔍 Early Adopters Feature Update​

You are up to date! All of our features have been made generally available.

Bug Fixes 🐛​

• Fixed an issue where the user sessions were incorrectly timed in Pia Canvas if the user forgot to clock out. (#27899)
• Resolved a UI issue where the SmartForms settings icon in the SmartForms portal was invisible if the theme color was set to white. (#28528)
• Fixed an issue where Pia was storing API Tokens for third party CSPs longer than its validity causing automations to fail during license provisioning. (#28823, #29734)
• Fixed an issue where inactive contacts were appearing within the "Route to Assignee" action of the AI Triage Dispatch rules screen. (#28918)
• Resolved an issue where Pia was disabled for clients of a Partner when migrating the clients from one ticketing system to another. (#29028)
• Resolved an edge case for a Partner where they were unable to access Pia in their ConnectWise ticketing system with Nilear Interface. (#29082)
• Resolved an edge case for a Partner where the AI Triage feature was including tickets that needed to be skipped. (#29293)
• Fixed an issue in the Agents screen where the paging was not working properly. (#29385)
• Fixed an issue for a Partner where clients were shown as un-configured in the adoption report. (#29453)
• Made the Pia tenant more resilient to handle a specific scenario where Triage was causing a performance issue. (#29547)
• Fixed an issue in AI Triage where the config watcher incorrectly reported a configuration error despite valid settings. (#29590)
• Resolved an edge case for a Partner where the tickets created via the SmartForms requests were classified incorrectly. (#29618)
• Fixed an issue where a scheduled AutoTask ticket for Pia: Staff Offboarding automation was failing due to Pia attempting to assign an inactive user to the ticket. (#29645)
• Resolved an issue where the chatbot was not automatically re-enabled if a ticket upon re-opening a closed ticket. (#29661)
• Fixed an issue where cancelling automations did not automatically cancel time logging for the Partner. (#29764)
• Fixed an issue in AI Triage where a permission error prevented company data from being collected, causing the existing company ID to be overwritten and resulting in an error. (#29797)
• Resolved an issue where the log entries for automations were displaying incorrect times due to missing time zone conversion in the Live Packages screen (#29801)
• Resolved an issue where the SmartForms: Staff Onboarding automation was failing during Active Directory Sync due to unexpected connection issue against a machine. (#29882)
• Resolved an issue where Partners were seeing Pia health alerts for invalid Triage mappings even when their configuration was correct. (#29911)
• Fixed an edge case for a Partner where a scheduled automation was sending duplicate notification emails. (#29960)
• Fixed an issue where the Pia: Triage V2 automation was failing when attempting to retrieve errored activity logs. (#30006)
• Fixed an issue where the Pia: Triage V2 automation was failing when attempting to retrieve ticket data due to restrictions in Halo ticketing system API. (#30008)
• Fixed an issue for a Partner where the Pia chatbot was not opening in AutoTask after the authentication update to the Pia Portal. (#30046)
• Resolved an issue for a Partner that was causing extended Triage processing times. (#30066)
• Fixed an issue where the Partner was unable to find a contact type when creating a new contact sync rule in the SmartForms screen. (#30137)
• Resolved an issue where re-selecting an approver did not automatically update the approval email field while creating a new approver in the Approvers Tab of the clients screen. (#30145)
• Resolved an edge case affecting a Partner where guest access authentication was failing for a user in Pia tenant. (#30212)
• Fixed an issue where Pia was not working within the AutoTask ticketing system due to webhook data failing to ingest correctly. (#30222)
• Resolved an issue where Pia encountered an admin‑consent error that required Partners to authorize MS Graph twice. (#30229)
• Fixed an issue where a Partner experienced performance slowness on the Users screen. (#30243)
• Fixed an issue where the Microsoft Graph API was not authorizing for a Partner due to exceptions in the assigned role. (#30277)
• Fixed an edge case for a Partner where a misconfigured Get Approval activity caused an unintended additional approver to be emailed during an automation. (#30312)

You can go to your tenant and explore the Automation Hub or follow these quick links to learn more about Automation Hub:

• Automation Hub Overview
• Installing a PiaPack
• Updating a PiaPack

Enhancements​

• Updated the Pia Config Watcher to exclude child clients from the Client Configuration health rule, preventing them from appearing as unconfigured. (#29375)

Bug Fixes 🐛​

• Fixed forced signout handling to prevent incorrect redirects and authentication errors in the Pia portal, ConnectWise embed, Halo embedded pod, and Autotask extension. (#28550)
• Fixed an issue where the Pia: Triage V2 automation was incorrectly categorizing a ticket for a partner. (#28733)
• Resolved an issue where emails sent via the SmartForms AutoReply feature were missing tenant details. (#28819)
• Fixed an issue with the Triage feature where inactive contacts were appearing in the 'Route to Assignee' action when creating a dispatch rule. (#28919)
• Fixed an edge case where AutoTask webhook failed due to an unexpected data type. (#29031)
• Resolved an issue where a partner using Halo PSA could not set ticket defaults for SmartForms tickets due to improper filtering of ticket categories. (#29061)
• Resolved an edge case where the 'Get Machine' activity automatically timed out for a partner. (#29083)
• Resolved an issue for a Partner where the AI Sentiment Analysis was not working as expected. (#29095)
• Fixed an issue where scheduled automations created by SmartForms did not display the ticket ID in the Scheduled Packages screen of the Partner Portal. (#29151)
• Fixed an issue where the Triage feature did not allow the use of shared ticket classifications in the ConnectWise ticketing system for Triage Stamping, which caused errors when creating ticket stamping rules. (#29173)
• Fixed an issue where the Pia: Triage V2 automation stopped executing for partners due to memory issues and overload in shared API service. (#29195)
• Resolved an issue where the Send SMS activity failed to send text messages. (#29391)
• Fixed an issue where the Pax8 integration was failed for a Partner when attempting to authorize delegate consent without a pre-existing integration configuration. (#29416)
• Fixed an issue where synced users could not access the SmartForms portal if their ticketing system record had an empty first name or last name. (#29502)
• Fixed an issue in the SmartForms portal that caused random error messages to display when submitting requests. The errors were non-blocking and did not stop users from successfully submitting. (#29515)

Enhancements🌟​

• Enhanced function package support for data return to parent packages with the following changes:
  • Added an option to define output variable in the Package Variables section in the Package Editor
  • A new activity 'set_variable' is now available. You can use this to return data from a child package back to its parent. (#22725)
• Updated the scheduled automation behavior so recurring / scheduled automations are automatically cancelled when the Parent automation is unpublished. (#27144)
• Improved the SmartForms workflow to ensure that when a user cancels a draft request, a message is displayed in the chatbot and an audit note is automatically added to the corresponding SmartForms ticket, informing the engineer of the cancellation. (#28995)
• Added the ability for you to define the ticket source for a SmartForms ticket with the new ticket source drop-down in the SmartForms Workflow Tab and the SmartForms Forms Tab > Ticket Stamping Rules popup.

Bug Fixes 🐛​

• Fixed an issue where the deactivated boards in AutoTask were still appearing in the Pia Partner Portal for a Partner. (#29300)
• Fixed an issue where validation errors from external events were causing the Pia: Triage V2 automation to fail. (#29460)
• Resolved an issue where SmartForms tickets failed to respect the Automated Workflow Statuses configured on the SmartForms screen within the Partner Portal. (#28740)
• Fixed an issue where the 'handle_errors_in_package' value in the 'Start_package' activity was not honored when a child package exceeded the maximum execution duration. (#28572)
• Resolved an issue where the repeating sections were getting default values repopulated in package configuration forms. (#28551)
• Fixed an issue where the Pia:Triage V2 automation could fail in high usage scenarios with an intermittent timeout. (#29184)

Enhancements🌟​

Changes to Get Approval Activity​

Note: The get_approval activity is for use with Custom Automations only. Broader approval functionality is planned for upcoming platform 20 release.

The Get Approval activity has been updated with the following changes:

• Delegate Consent Support: Added new input properties that allow users to specify a delegate consent, enabling approval emails to be sent from a designated address instead of the default info@pia.ai.

• Auto-Approval Protection: Added safeguards to prevent approval links from being automatically triggered by email security software that automatically clicks on embedded URLs.

• Timeout Handling Enhancements: Introduced two new input properties — StopOnTimeout and approval_timeout_minutes — to ensure Pia correctly identifies and blocks approval attempts made after the designated expiry period. (#28514)

Further Enhancements​

• The software installation screen has been updated to display only the options from Microsoft winget that are supported for software installation. (#28751)
• Updated the Send SMS automation to display a default chatbot message when no override message is provided. (#28896)
• Modified the retry logic for better error handling in the PowerShell Activities and Inline PowerShell Activities that execute on the backend VM associated with your Pia tenant. (#28704)
• Enhanced Pia chatbot for better user experience in scenarios where an automation with AI AutoStart feature is running or when a Triage is running and Pia is executing a chat interaction with user interaction at the same time. (#27687)
• Enhanced the SmartForms workflow for Partner Administrators by introducing a contact selection step when submitting a request on behalf of a client. (#28530)
• Updated Pia's support from Basic SKU public IP addresses to Standard SKU Public IP addresses following changes implemented by Microsoft. (#28649)
• Updated the Pia Config Watcher to exclude child clients from client configuration health alerts. (#29375)
• Updated the Get Approval (get_approval) activity to use the default subject value (i.e. "IT Approval Request #[ticketId]") if the email subject is null. (#29331)
• Enhanced the Pia Chatbot user experience when an automation is running via AI AutoStart or Ticketing System Event condition. (#27687)

Bug Fixes 🐛​

• Added additional handling to prevent unnecessary Ingram Micro API calls which was restricting Pia to retrieve required information from Ingram Micro causing automation failures. (#28529)
• Fixed an issue in the get_approval activity that prevented escalation of the approval request when no response was received from the first approver, specifically in cases where a custom email address was used. (#28610)
• Resolved an issue in the Triage feature that prevented support for custom classifications containing leading or trailing whitespace characters. (#27885)
• Resolved an issue that caused scheduled automation to fail when the parent ticket was moved to a different board. (#28735)
• Fixed an issue in the adoption report where closed tickets were excluded due to inconsistent status values. (#28762)
• Fixed an edge case where the Pax8 Integration was incorrectly displayed as not configured, despite being properly set up, resulting in halted automation execution. (#28808)
• Fixed an edge case where the feedback drop-down in the Pia chatbot was not displaying in Halo when accessed via the Edge extension. (#28830)
• Fixed a UI issue where the drop-down menu items sometimes displayed over the text input in the chatbot were blocking the user from viewing the associated text box. (#28984)
• Fixed an issue where the image attachment form control was not working in the SmartForms portal. (#28656)
• Resolved an edge case issue where the config watcher alert "next run" date was showing incorrectly in the UI if no run had been executed in the past day (due to no scan required). (#28712)
• Resolved an edge case scenario where the ITGlue procedure sync could cause duplicate articles to be created in IT Glue if the name of an automation changed. (#28763)
• Fixed an issue in the SmartForms contact sync feature that caused invalid contacts to be synced when the ConnectWise contact type was set to 'All Contacts'. (#29353)
• Fixed an issue where a custom automation for a Partner was failing when scheduled due to the Get Form Data (get_form_data) activity not being able to retrieve data from parent automation. (#29311)
• Resolved an issue where the Restart Agent Machine (restart_agent_machine) activity could not restart a windows machine that has pending windows update. (#29262)
• Fixed an issue in Triage Ticket Ingestion that caused existing form values to be removed upon adding an extension automation. (#29248)
• Resolved an issue where the users were getting authorization errors when attempting to add Sharepoint consent to the delegated email address. (#29240)