What's New 🌟​

Major New Features/Release Items:

• New AI & Triage Experience
• AI AutoStart
• AI AutoReply
• Doubling of Pia AI Ticket Classification Capability

Other Items In This Release:

• Pia Portal Refreshed Look and Feel
• Package & Activity Editor Refresh
• Bug Fixes 🐛

New Features and Enhancements​

🌟 New AI & Triage Experience​

(Early Adopters Program Only)

Configuring Pia Triage & Dispatch has never been more seamless. The New AI & Triage Experience brings a refreshing visual interface to what was once a task for coding aficionados. We know that setting up automations shouldn't require technical expertise, and with this new experience, it doesn't have to.

The updated interface includes:

• Dashboard - View the entire flow, activate or disable Pia Triage with just a click.
• Stamping Screen - Easily configure automated ticket categorization for different service requests.
• New Dispatch Screen - Set up rules to automatically route tickets to specific engineers or boards based on predefined conditions.
• AI Analysis Screen - Influence and enhance Pia's accuracy by tweaking Pia's AI engine.

With this comprehensive overhaul, managing ticket flows becomes as easy as navigating a very intuitive UI, freeing up your technical resources to focus on more complex tasks.

Read more on how to navigate this new feature here: New AI & Triage Experience

🌟 AI AutoStart​

(Part of New AI & Triage Experience)

AI AutoStart activates as soon as a ticket enters your system, launching pre-defined automations to collect information or solve problems instantly.

For example, if a client submits a ticket about a performance issue, AI AutoStart triggers a performance report right away, capturing the system's condition at the time of submission. This saves time and provides accurate data for troubleshooting.

Read more on how to navigate this new feature here: AI & Triage: AI AutoStart

🌟 AI AutoReply​

When clients email a ticket that could have been submitted through SmartForms, AI AutoReply automatically informs them about using SmartForms to ensure faster, more efficient service. This helps improve adoption and reduces friction for your team.

For a deep dive into AI AutoReply you can read more here: AI AutoReply

🌟 Doubling of Pia AI Ticket Classification Capability​

We’ve expanded our ticket classification system to around 60 categories, allowing us to detect and handle even more types of tickets with improved precision. By leveraging the new AI&Triage Experience, you can easily create custom stamping and dispatching rules further optimize your triage operations, ensuring smoother workflows and faster resolutions.

And we're not stopping here—stay tuned for more updates!

For a comprehensive list all available classifications including the newly introduced ones you can read the following article: AI Analysis

🌟 Pia Portal Refreshed Look and Feel​

We're certainly guilty of releasing heaps of new functionality, but we've also managed to squeeze a refreshed the look and feel into Pia Portal!

🌟 Package & Activity Editor Refresh​

For all the Automation Engineers out there, the package & Activity Editors also gained a refresh, designed to give you the maximum screen space possible while working on your next big automation. As an extra bonus, we've added a new button in the activity editor which will validate your PowerShell for you, saving you extra time!

Bug Fixes 🐛​

• Fixed an issue where the service bus could stop processing messages, causing agent status updates to fail. Improved error handling and logging for resilience. (#25004)
• Addressed an issue where antivirus software blocked data processing, adding clear messages and retry options. (#25060)
• Resolved an issue in HaloPSA where mandatory custom fields weren't included during ticket creation, causing scheduled tasks to fail. (#25431)
• Improved form loading performance by optimizing data processing and decreasing SmartForm refresh frequency. (#25554)
• Fixed an issue where token refresh would occasionally fail, adding retry attempts to ensure successful completion. (#25766)
• Fixed incorrect reporting of missed opportunities by adding exclusion criteria for SmartForm package instances. (#25805)
• Reduced duplication in ticket status dropdowns within SmartForms Ticket Default to ensure only distinct statuses are available for selection. (#25806)
• Corrected a missing query call that caused automation errors in client support. (#25838)
• Fixed an issue where client contacts in Autotask were not showing in the approvers list in Pia, despite having the necessary details. Added paging to ensure proper display of all eligible contacts. (#25854)
• Fixed an issue where SmartForms for Halo PSA did not correctly associate the client contact by email address. Implemented a solution to properly match the submitted form to the correct client contact. (#25896)

Early Adopters Feature Update 🔍​

These features are currently available under our Early Adopters Program (EAP), allowing select partners to gain early access and provide valuable feedback. As we continue refining and enhancing these features, we expect to roll them out globally once development is complete. Stay tuned for updates as we bring these powerful tools to all users in the near future!

We hope you'll enjoy these new enhancements and features. Stay tuned for more updates and new features in future releases. As always, your feedback is invaluable to us. Please don't hesitate to reach out with any questions or suggestions.

Thank you for choosing Pia aiDesk as your automation platform of choice!

The Pia Product Team

What's New 🌟​

Release Items:

• Automated Time Logging
• Introducing the New Integration Experience (Early Adopters Only)
• Improved chatbot experience for MS Delegate Token Expiry
• Optional Session Timeout for Better Security
• Bug Fixes 🐛

New Features and Enhancements​

🌟 Automated Time Logging​

We’ve made tracking your automation time easier than ever! You can now specify a pre-defined amount of time to log against each ticket, which helps you keep an accurate record of the time spent on each task. This feature is configurable per automation and can be set up in bulk for all clients, reducing the need for manual effort. It’s a simple way to ensure you’re accurately tracking and billing your automation efforts. (#24684)

Read more on how to configure this new feature here: Automated Time Logging

🌟 Introducing the New Integration Experience​

(Early Adopters Program Only)

Imagine you’re using Pia’s staff onboarding automation, but it doesn’t quite cover the entire process—perhaps there's an extra step unique to your system. Or, say you need help troubleshooting and want a step-by-step guide generated automatically via ChatGPT which is specific to your ticket and issue. With the Integration Experience, you can bridge the gap by setting up custom automations with 3rd party Apps and API's to handle that final onboarding task automatically and give you that extra capability you are looking for on your service desk.

The New Integration Experience offers two key benefits:

1. Easily Set Up Pre-Built Pia Integrations: Get up and running quickly with Pia’s native integrations, designed to work seamlessly with popular platforms.
2. Custom Integrations at Your Fingertips: If Pia doesn’t have your favorite software pre-integrated, no problem! Use the Integration Experience. to build your own automations with any external API, allowing you to tailor Pia’s automation environment exactly to your needs.

Whether it's connecting to a CRM to create a new user every time the onboarding automation runs, or setting up a custom VoIP integration with your chosen vendor, the possibilities are endless—provided the software supports API access. With the Integration Experience, you’ll save time, boost efficiency, and gain the flexibility to automate exactly how you want, without being limited by pre-built options.

Dive deep into the New Integration Experience, check out the following articles and video tutorials!

• New Integration Experience, an introduction
• How to set up your first custom integration
• Tutorial: Build Automations with a custom ChatGPT Integration

🌟 Improved chatbot experience for MS Delegate Token Expiry​

We've enhanced how Pia handles expired MS Graph API and Delegate tokens. Previously, when a token expired, the automation would error. Now, instead of halting everything, Pia will notify that you need to reauthorize. You can then refresh Pia once you have reauthorised in the Pia Portal to continue the automation. This update ensures fewer disruptions and a much smoother workflow.(#22659)

🌟 Optional Session Timeout for Better Security​

We’re excited to introduce an optional session timeout feature for the Pia Partner Portal. This means you can choose to have users re-login after a period of inactivity, adding an extra layer of security. It's a great way to keep user sessions secure and reduce the risk of unauthorized access. Remember, this feature is entirely optional and can be configured to suit your needs! (#24181)

Bug Fixes 🐛​

• We resolved an issue where some styles were applied globally instead of to specific forms in the Partner Portal, ensuring the correct display of forms across the platform. (#25296)
• We fixed an issue where the search bar would scroll along with the table when viewing multiple automations. The search bar now remains fixed in place while scrolling. (#25351)

Early Adopters Feature Update 🔍​

Microsoft Partner Portal to perform the Microsoft Graph API "Authorisation" process​

Speed up your onboarding of new clients into Pia!

We are currently working with our alpha partners on the Microsoft Partner Portal feature, and the feedback so far has been positive. Everything seems to be going well, and we are making great progress. We anticipate that this feature will be ready for global availability soon. Stay tuned for more updates!

We hope You'll enjoy these new enhancements and features. Stay tuned for more updates and new features in future releases. As always, your feedback is invaluable to us. Please don't hesitate to reach out with any questions or suggestions.

Thank you for choosing Pia aiDesk as you automation platform of choice!

The Pia Product Team

Enhancements ✨​

• We've made significant improvements to our Machine Learning and AI model, increasing the accuracy to ~95%. This enhancement boosts ticket classification and improves the performance of Pia Triage and automation recommendations by the Pia Chatbot.
• The Pia Browser Extension now remembers its last position, so you don't need to adjust your Pia Chatbot each time you log in HaloPSA or Autotask! (#25081)
• Enhanced support for custom domains in the Halo PSA Chrome Extension, allowing partners to use custom domains such as psa.companyname.com instead of psa.halopsa.com (#22776).
• Added improvements in the Microsoft Partner Portal Connected Service (Pia Portal), including failure messages for better user feedback (#24946).

Bug Fixes 🐛​

• Fixed an issue where the chatbox session displayed wrong client data by removing session caching (#24495).
• Resolved a problem with SmartForms ticket stamping (Autotask) not applying due to inactive accounts not being filtered out (#24892).
• Addressed a Pia Browser Extension issue by ensuring the server address includes "https://" (#24899).
• Resolved an issue where restarting the Pia Agent could cause duplicate task execution by ensuring the task runs only once. (#24967).
• Improve handling of the "Agent Offline" error message by addressing an issue where the parent automation would incorrectly enter an error state when a child package is executed in "inline" mode. (#25031).
• Resolved the issue of client package configs not saving when there are blank sections by adding a null check (#25059).
• Improved error messaging when the antivirus blocks a PowerShell script execution by displaying a proper message and offering retry options (#25060).
• Added logic to prevent the Pia Browser Extension from overflowing off the screen in HaloPSA and Autotask (#25081).
• Added logic to prevent sandbox changes in the Activity Editor when there are unsaved changes (#25146).
• Fixed the creation of scheduled audit notes by ensuring both assignedResourceID and assignedResourceRoleID fields are properly handled (#25173).
• Addressed the issue where packages appeared to fail without errors by improving exception handling for duplicate executions (#25224).
• Corrected the rendering of input objects in the Activity Editor by removing unnecessary characters (#25264).
• Fixed the Reset Password form issue where default values were not properly compared, causing display problems (#25293).
• Resolved the issue in the Activity Editor where "Goto Line" was not working by adding the required import (#25299).

What's New 🌟​

Release Items:

• Customize Pia's SmartForms
• SmartForms Ticket auto-close
• SmartForms support for HaloPSA
• Additional Enhancements
• 15 Bug Fixes 🐛

📺 Watch our walkthrough video to explore the main features and enhancements included in the release!

New Features and Enhancements​

🌟 Customize Pia's SmartForms!​

Enhanced SmartForms with Extension Automations​

• You can now customize Pia's SmartForms to cover specific client scenarios by adding your own custom scripts! We're bringing the power of Pia's Extension Automations (EA) into SmartForms allowing you to create more bespoke and customer-centric workflows, ultimately enhancing the flexibility and capabilities of our platform.
  Initally we have activated EA extension points at the start of our SmartForms workflow, more to come in our next releases! (#23585, #23804).

🛠️ You can read the step-by-step guide on how to customise Pia's SmartForms here!

In the example below, we’ve added a custom form to Pia’s Staff Onboarding SmartForm. The possibilities are endless!

🔰 What is Extension Automations?

🌟 Smartforms: Ticket auto close… and more!​

• Close the loop with SmartForms automated ticket closure! By combining this with Zero-Touch automation, you can achieve a true engineer-free experience.
  With this new feature, you can now automate ticket status changes in your PSA based on SmartForms execution, simplifying the ticket management process. For instance, you can customize SmartForms to assign a specific status while being filled out or submitted, and automatically close the ticket after the automation has completed.
  This seamless integration adds even more value to your clients by reducing the need for engineer input (#22521).

Check out the picture below for customizable statuses

🔰 Curious about Zero Touch Automation?

🌟 Smartforms: HaloPSA support!​

• HaloPSA people out there, we've heard you! SmartForms is now compatible with your favourite ticketing system, enhancing your user experience and integration! (#22326).

⭐ SmartForms: Configuration Improvement​

• Enjoy a faster experience in the white labelling section of SmartForms which will now refresh immediately as you save them (#23777).
  

⭐ Halo PSA Chrome Extension Upgrade​

• Enhanced support for the HaloPSA Chrome Extension, including better handling of custom domains for the ticketing system (#22776).

⭐ Tree View Control Enhancement​

• With our new Tree View control, you can now select multiple items simultaneously in your custom packages, enhancing usability and streamlining processes. This feature will also be included in the Computer Space Cleanup Pia package in our next automation release. Stay tuned! (#24206). See example below:

Bug Fixes 🐛​

• Fixed an issue where the system audit log did not log changes for connected services (#24702).
• Corrected the Pia date/time display in the Chatbot to match local regional settings (#24673).
• Resolved issues with the Kaseya RMM connected service integration and token authentication (#24707).
• Fixed an issue where submitted form audit notes displayed reference names instead of display names (#24068).
• Resolved an issue where the ticket owner was not set in the adoption report by adding a new property to ensure proper assignment (#22027).
• Fixed an issue where the SmartForms configure form wasn't being properly logged in the audit trail by adding a feature that records changes made to the form values (#22474).
• Implemented feedback regarding Config Watcher and improved handling of Graph API and delegated consent alerts (#23317).
• Resolved the issue where the Chatbot session was displaying incorrect client in certain scenarios when using third party apps in ConnectWise (#24495).
• Resolved an issue where scheduled terminations in HaloPSA would return "Ticket Type not set" in case the ticket type default was not set (#24527).
• Prevented SmartForms to be configured for clients that have an unsupported environment tag (#24597).
• Fixed an issue where SmartForms configuration portal was returning inactive statuses in ConnectWise (#24629).
• Investigated and resolved issues with the Approvers list not populating in HaloPSA (#24701).
• Investigated and resolved issues with searching for Autotask tickets by Ticket ID (#24768).
• Fixed an issue where scheduled automations would return "null" as user if user wasn't set (#22579).
  
  

Early Adopters Features 🔍​

Microsoft Partner Portal to perform the Microsoft Graph API "Authorisation" process​

Speed up your onboarding of new clients into Pia!

We are currently working with our alpha partners on the Microsoft Partner Portal feature, and the feedback so far has been positive. Everything seems to be going well, and we are making great progress. We anticipate that this feature will be ready for global availability soon. Stay tuned for more updates!

New Activities Released​

We are also excited to announce the release of three new activities designed to enhance your custom workflows! Click on the activities below to access the individual article on how to use them. If you need help, you can join our DevConnect community for discussions around these activities and much more here.

New Activities:​

• Append SmartForms Interaction
• Get Form Data
• Get Approval

🐛 Bug Fixes​

HaloPSA:​

1. Fixed an issue where some HaloPSA users received an error "Ticket Type not set" while scheduling user offboarding automations. [#24527]

Automations:​

2. Added additional filtering to AI Condition autostart to prevent it from firing multiple times. [#24400]
3. Fixed issues where automations were timing out due to limits on how much log information they could generate. [#24778]
4. Fixed a issue where the Pia Chatbot would not detect the ticket as closed under certain conditions. [#24761]

ML​

5. Fixed package suggestions not returning results by changing to case sensitivity match. [#24788]

Adoption Report​

6. Updated Pia Adoption Report to ensure engineers count updates correctly when tickets are completed. [#24760]

Following our major release Platform 14, we are releasing an enchanced version with additional bugfixes Platform 14.1! 🚀​

🐛 Bug Fixes​

Performance Optimization:

• Refactored Agent Checkin procedure to reduce resource-intensive operations. (#24383)
• Improve general responsiveness of the Pia Chatbot and Pia Portal by optimising background data processes which were competing for resources. Ongoing assessments and further performance improvements are in the works. Please notify us of any slow package execution instances with screenshots, ticket ID, and timestamp (#24572)

SmartForms and Automation:

• Enhanced ticket merging logic to prevent duplicate merging when submitting SmartForms within the same minute. (#24465)
• Resolved an issue where Halo PSA Scheduled packages failed to bundle and close tickets upon completion due to ticket type default not being set in Halo PSA configuration. (#24519)
• Optimized ChatEvents processing to address delays in automation package execution via the Pia Chatbot. (#24448)

Integrations and Ticketing:

• Pax8 Integration: Improved API Authentication caching to reduce throttling and cache timeout issues for Pax8 API. (#24337)
• Resolved issues related to closed status matching in ticketing systems. (#24344)

Package Audit Logging:

• Fixed default ticket id settings to ensure accurate audit logging. (#24203)

What's New 🌟​

We are excited to announce our latest platform release RC14!

In this release, we have focused on improving the overall Performance of Pia aiDesk with database updates along with some exciting new features and bug fixes.

• Option to set Priority to SmartForms Tickets
• Additional Enhancements
• 5 Bug Fixes 🐛

Option to set Priority on SmartForms Tickets​

Currently, you can specify the board and status of a ticket when it gets created for SmartForms request in the SmartForms settings screen. With this release, we are adding a new option that will allow you to specify the Priority on these tickets as well.

You will see a new drop-down option called 'Priority' added to the Ticketing Defaults section of the Setup Tab (For Defaults) and in the Ticket Stamping Rules Column of the Forms Tab (for Individual Automation Requests).

The options available in this field are based on the Priority levels you have configured in your Ticketing System. (#23794)

Additional Enhancements​

1. A new built-in activity "Get Connected Services" is now available in the Package Editor screen. This activity allows you to retrieve a list of Connected Services that have been configured for your tenant in the Connected Service screen. (#23159)

   For more on this activity, refer to the article here.

2. The Pia Agent has been updated so that if an agent fails to connect to the server during the execution of an activity, it re-attempts connection to the server instead of marking the Automation as errored. (#22713)

3. The tickets created by Pia for SmartForms requests now show Date/Time when the request was submitted at the end of the Subject in Local Timezone. This will prevent Tickets from closing in AutoTask due to duplication and also remove confusion for Engineers while viewing tickets. (#23757)

4. Updated the Pia Chatbot in the Partner Portal so that it displays an error message if the user attempts to open a Ticket Number or Ticket ID (For AutoTask) that is no longer available in their Ticketing System. (#23809)

5. Made the Pax8 Connected Service feature more robust by improving how Pax8 API tokens are handled by Pia. (#23964)

Bug Fixes 🐛​

1. Fixed an issue where the Chatbot was displaying same values multiple times in a form that had the Repeating section option enabled. (#23086)
2. Fixed an edge case scenario for a Partner where the Live Package Screen was loading very slow while searching for packages. (#23754)
3. Fixed an issue with the Config Watcher screen where MS Graph API and Delegate Consent Alert was sometimes being displayed for the Clients with valid Authorisation and Delegate Consents. (#23967)

Early Adopters Features 🔍​

Microsoft Partner Portal to perform the Microsoft Graph API "Authorisation" process​

Speed up your onboarding of new clients into Pia!

Pia is now working on expanding integrations into Microsoft Partner Center/Partner Portal to perform the Microsoft Graph Authorisation and Delegate Access.

With this new feature, Pia will perform the App Registrations for each client with the relevant GDAP permissions by using a Service Account setup in Partner Portal. This will work for any delegated tokens for user impersonation into the client tenant via Partner Portal.

This will also eliminate the need for setting up Delegate Authorisations per client for commons tasks like Password Resets and will instead leverage the service account through Partner Portal.

What's New 🌟​

We are releasing a new Platform version containing additional bug fixes - RC13.4!

Planned Release Date: Rollout period between 14/03/2024 and 21/03/2024

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

• 9 Bug Fixes 🐛

See below for further details.

As always, Partner Support is available to assist you.

🐛 Bug Fixes​

1. Fixed an issue with Pia Canvas so that when a time entry is logged against a ticket, it only has "Internal" flag set against it in ConnectWise so that it is not visible to anyone outside the organisation. (#23619)
2. Fixed an edge case scenario when updating the tenants some of the MS Graph Delegate Tokens would expire. (#23648)
3. Modified the Date/Time conversion logic for Adoption Report so that the Package Execution Dates are now being correctly displayed and the time is displayed in Local Timezone. (#23687)
4. Fixed an issue where the Scheduled Packages Screen was showing internally assigned ticket number for the AutoTask tickets rather than the AutoTask Ticket Number which was confusing Pia Partner Portal users. (#23895)
5. Made the Adoption Report screen more robust so that it now takes lesser time to retrieve information in the Report screen such as Available Pia Boards. (#23851)
6. Fixed an issue for a Partner where the Description added by the SmartForms user while submitting an IT Request Form through the SmartForms Portal was not being added into the description field of the ticket that was created by Pia. (#23818)
7. Modified the message being displayed when a user tries to install a Pia Agent that is currently in uninstalling state so that it clearly informs the user that the Agent is in uninstalling state and the user will need to wait and retry in a few minutes. (#23814)
8. Fixed an issue that was causing Automations to fail in some cases for clients with multiple config profiles as the config profiles were failing to populate required information for package execution. (#23791)
9. Fixed an issue where sometimes SmartForms Automations where Pia was logging status messages in the chatbot for closed requests despite their closed/completed status. (#23935)

What's New 🌟​

We are releasing a new Platform version containing additional bug fixes - RC13.3!

Planned Release Date: Rollout period between 28/02/2024 and 06/03/2024

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

• 13 Bug Fixes 🐛

See below for further details.

As always, Partner Support is available to assist you.

🐛 Bug Fixes​

1. Fixed an edge case scenario for a Partner where the Agents were not uninstalling (or were re-registering) for a client that was no longer available or deleted. (#23245)
2. Updated the Adoption Report to display "User Not Found (USERID)" with additional details in the hover text in the 'Assigned to' field for when the assigned Engineer does not have an account in Pia's Partner Portal. (23453)
3. Fixed an issue with SmartForms Automations where Pia was not respecting the closed status of the ticket that were created from a SmartForm Request and the tickets were getting updated every hour. (#23461)
4. The Pia Config Watcher has now been updated to filter out Child Clients while reporting for Server Related issues such as Primary Domain Controller not being configured. (23507)
5. Fixed an edge case scenario for an authorisation error which occurred while running the Terminate User Automation even when the MS Graph API was authorised. (#23520)
6. The SmartForms Configuration Screen has now been updated to fix an issue when swapping between several tabs of configuration screen would cause certain details to not be saved. (#23531)
7. Fixed a minor issue in the Pia Clients screen where the 'Pia Status' column was not sorting correctly. (#23538)
8. Updated the test connection screen in the AutoTask Connected Service to call out when a permissions of the API user that Pia uses is incorrectly setup. (#23555)
9. The multiple listbox field in all Pia forms has now been modified to wrap the text of the listbox heading if the word is too long. (#23565)
10. Updated the scheduling email that is sent when a scheduled task for eg: Terminate User succeeds or fails to include the case for when the API user that Pia uses for ConnectWise doesn't have permissions to create a ticket. (#23574)
11. Fixed an issue which occurred when an AutoTask Ticket was created via SmartForms in the case that the SmartForms user matched a contact in AutoTask which was not linked correctly to the AutoTask company record causing the request to fail as we cannot specify a contact for a ticket which is not associated with the company set on the ticket. (#23580)
12. Improved the stability and robustness of the way Delegate tokens and consents are handled to reduce the chances of the delegate consents needing to be re-authorised. (#23648)
13. Updated the Pia Chatbot Chrome extension to automatically open the Pia window when the "Open Ticket with Link" feature for AutoTask is used. (#23668)
14. Updated the Pia Chatbot to display the message more clearly when a Client is not configured in Pia. (#23484)

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)