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)

Following Automation 7.0, we are releasing a new version with a rollup of additional bug fixes - Automation 7.1!

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

See below for further details. As always, Partner Support is available to assist you.

🐛 Bug Fixes​

1. The Pia: Change Calendar Permissions (All Environments) Package has now been updated with additional logic to handle the case where the user selects themselves as the user they wish to add to their own calendar permissions. (#22388)
2. The Pia: Computer Space Cleanup Package has now been modified to display information on the file that could not be deleted instead of erroring. (#23163)
3. The Pia: Get User Account Details (Cloud Hybrid) Package has been updated to display the Password Expiration Date to 'Never' if the user password has been set to never expire or if the date is less than 2000's. (#22855)
4. The Pia: Get User Details (All Environments) Package now searches to find account using username as well if it has no other inputs. (#23154)
5. The Pia: Log Out User from Windows RDS Package now prompts more information if there are missing permissions so that the Engineer can change permissions then try log off users again. (#22676)
6. The Pia: Manage User Licenses Package has been modified with a logic to display a prompt warning of litigation hold in the Chatbot and offer confirm option before converting the mailbox. (#22372)
7. The Pia: Map Network Drive Package has now been updated to support backwards capability to PowerShell 2.0. (#22908)
8. The Pia: New User (Cloud Hybrid) Package has been updated with an additional check whether the suggested UPN is the same as the UPN added by the user. If not, the latter will be used to create the email address. (#23404 , #23394)
9. The Pia: New User (Cloud Hybrid) Package has now been updated to consider multiple partitions in the Org Unit while syncing user details. (#22813)
10. The Pia: New User (Cloud Hybrid) Package has now been updated to run check against the user licenses to confirm if they have the available plans for litigation hold. (#22723)
11. The Pia: Re-allocate User License (Cloud Hybrid) Package now waits for all the mailboxes to be retrieved before performing operations. (#22646)
12. The Pia: Re-Enable Terminated Account (Cloud Hybrid) Package now self verifies whether the account has been re-enabled on both AD and Azure. (#22887)
13. The Pia: Terminate User (Semi Hybrid) Package now moves the disabled user to the correct Org Unit based on the Default OU Configuration setup. (#22002)
14. The Pia: Triage Package was not setting custom fields in some cases for tickets triaged for Autotask which has now been fixed. (#23212 , #23354)

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)

What's New 🌟​

As usual following our Platform Releases (RC13), we are releasing a roll up of additional bug fixes - Rc13.1!

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

• 10 Bug Fixes 🐛

See below for further details.

As always, Partner Support is available to assist you.

🐛 Bug Fixes​

1. Fixed an edge case where packages that were scheduled (i.e. Terminate User, Change User Details etc.) now can make use of the data that would normally have been cleaned up or purged after 30 days increasing the time into the future where we can schedule the packages. (#22644)
2. Resolved an issue which Ingram Micro Connected Service which sometimes resulted in the test connection failing. (#22705)
3. Updated how the forms for Whitelist Email Packages is displayed in the Chatbot to remove an annoying doubleups of scrollbars. (#22766)
4. Fixed an issue where sometimes the New Password Field would display a hashed value rather than a password. (#22788)
5. Updated the Live Packages screen making the output for some of the activities more visible which was previously hidden due to a horizontal line. (#22799)
6. Made Pia Canvas more robust so that you no longer need to clock back in after refreshing the page. (#22835)
7. Fixed an edge case scenario where the test connection was failing when the connected service for Microsoft Partner Portal is used as a CSP. (#22845)
8. Updated the Live Packages Screen to handle larger volumes of Package data. (#22894)
9. Fixed an issue with the Package Configuration Screen which was causing duplication of data added to the package in certain scenarios. (#22930)
10. Fixed an issue with the Halo PSA Terminate User Package where the package was not executing when being scheduled in some scenarios. (#22934)

What's New 🌟​

We are excited to announce our latest platform release RC13!

Alongside various updates to SmartForms, this release includes significant improvements across different areas of the Pia Portal. These enhancements are:

• Introducing Pia Config Watcher! 🔍
  • Nightly Configuration Checked
  • Suppress Alerts
  • Email Notifications
• Added support for Clients with multiple environments 🤝
  • Ability to configure multiple profile for a client
  • Pia Chatbot Changes to support multi-environment clients
• Service Now Connected Service Updates 🌟
• Additional Enhancements 🌟
• 3 Bug Fixes 🐛

See below for further details.

As always, Partner Support is available to assist you.

🔍 Introducing Pia Config Watcher!​

Config Watcher Checks:​

With the Config Watcher, Pia will be alerting you when it detects any issue in the following areas:

• Ticketing System Configuration (Webhooks & API)
• Client Server Config (Global Config & DC, Azure AD and Exchange Server Checks)
• Pia Agent Checks (including version, activation, online/offline Checks)
• Microsoft Authorization (MS Graph plus Delegated consent checks)
• Client Environment Tags check
• Package Config check (required fields and valid config checks)
• SmartForms Setup Checks

Things you can do with Config Watcher:​

• Keep track of issues identified by Pia Config Watcher on the Config Dashboard
• Resolve issues with Pia Watcher with steps provided to you on how to fix each type of issue you may encounter (#22629)
• Ask Pia Watcher to re-check any issues once they have been resolved (#22629)
• Subscribe to notifications when Config Watcher detects issue so that you can be aware and action issues as they occur. Manage your notifications settings via the Email subscriptions option in Pia Config Watcher (#22059)
• Suppress Checks when you need to reduce the sensitivity level of the watcher
  • At this date, all the checks are relevant to Pia functioning correctly but you may wish to suppress some of the alerts temporarily while you fix them (#22626)

New User Permissions for Pia Config Watcher​

The Pia Config Watcher is tied to two new access levels that have been added in the partner Portal. These access levels are:

• View Config Watcher: This access level will give you the ability to view Pia Config Watcher dashboard.

• Manage Config Watcher : This access level will give you the ability to create and subscribe to notifications and suppress checks in Pia Config Watcher. (#22626)

Pia Chatbot Changes to support Config Watcher​

Pia Chatbot will display Config warnings for the issues which may affect package executions. You can manage this option in the Tenant Settings screen under the Config Watcher section.

🤝 Added support for Clients with multiple environments​

A new "Configuration profile" widget is now available in the Client Dashboard, enabling you to create and manage multiple profiles for your clients. The newly created profiles come with limited options compared to the default profile, streamlining the configuration process and eliminating the necessity to set up every detail for each profile.

You will be able to switch between profiles by clicking on the drop-down that will be available at the top right corner when multiple profiles are created. (#22330)

Pia Chatbot Changes to support multi-environment clients​

To support the multi-client environment furthermore, changes have been made to the Pia Chatbot as well. When using multiple profiles, you must first select a profile to run Pia automations with.

🛠️ ServiceNow Connected Service Updates​

We have also updated the connected service for ServiceNow to include the following changes:

• New Company Sync Button: This button will allow you to run a manual sync to import a list of clients from the ticketing system into Pia.
• Setup Webhooks Button: The Setup Webhooks button has now been added to ServiceNow so that you can automatically configure Webhooks into the ServiceNow Ticketing System using the Pia Portal.

🌟 Additional Enhancements​

• Performance Improvements to improve the speed of loading of the Pia chatbot and Package Editor for editing automations.
• Improvements to the setup and configuration of Pia integrations with your ticketing system during onboarding including additional troubleshooting tools to help troubleshoot connectivity issues with your ticketing system.
• Updated security certificate for the Pia Agent.

🐛 Bug Fixes​

1. The Live Packages Screen has now been updated to show single entry for each package run regardless of the number of tags assigned to the package. (#22345)
2. Fixed an edge case scenario for the packages to be unlocked when retrieved from sandbox. (#22346)
3. The Pia Canvas screen has now been updated to ignore accidental spaces in the ticket status field and display the tickets in the required column. (#22327)

We are excited to announce our new Automation Release, RFC352- Automation 7.0!

With this release, we are launching some exciting new features that the Pia Team has dedicated significant time and effort to creating.

🌟Introducing SmartForm Automations!​

Here are the SmartForm Automations that are now available for you to configure for your clients:

Additional SmartForm Automation: Basic IT Request

🤝 Full Integration with Pax8!​

Updates to the New User Package​

The Pia: New User package has been updated with additional configuration options that allows you to enable Pax8 license provisioning via Pia. These options are available in the Package Configuration Form and must be enabled for the package to use Pax8 as your licensing service.

Updates to the Terminate User Package​

Like the New User Package, you will find additional package configuration options available in this package which must be enabled to de-provision Pax8 licenses using Pia.

New Pax8: Modify Subscription Package​

To simplify the management of Pax8 subscriptions, we are introducing the Pax8: Modify Subscription package. This package presents the license and the cost within the Pia Chatbot, allowing you to review and choose how you wish to adjust the subscriptions. (#13094)

You can also set the maximum number of licenses that can be provisioned/deprovisioned in a single order using the settings option in the package configuration form.

⚒️ 4 New Automations!​

🔥 Additional Package Enhancements​

1. Packages with drop-down fields to select the mailbox addresses have now been updated so that you will now be able to see the email address of the user along with the user name to avoid confusion when there are multiple users with the same name. (#13290)

2. The Bulk Update User Details Package has now been updated with additional validation on the inputs in the user details form to minimise errors. (#14018)
3. The New User (All Environments) Package has now been updated to offer additional ways to fix upn conflicts in the package configuration form allowing you to pick alternative methods for making the upn unique. (#22179)

🐛 Bug Fixes​

1. The Add/Remove User From Groups (All Environments) Package was allowing users to select non-synced AD users with disabled account. This has now been modified by adding a filter in the package to only list synced accounts with valid samAccountNames or non-synced accounts with null SamAccountNames to minimise package erroring. (#22439)
2. The Bulk Add/Remove User to Groups (All Environments) Package was not displaying the users from the group correctly in some edge case scenarios. This has now been resolved. (#21805)
3. The Bulk Add/Remove Users to Group Package was not including shared mailboxes in the mailbox selection dropdown in some edge case scenarios. This has now been modified to display shared mailboxes as well. (#21969)
4. The Change User Details (Cloud Only) Package has been updated with additional validation of proxy addresses prior to updating the user details. (#18480)
5. The File Share Security Change (Cloud Hybrid) Package now handles situations that includes corrupted GPOs more gracefully. (#22141)
6. The Install/Uninstall/Reinstall Software Package has been updated with improvements to resolve the issue when installing certain software packages under the 'User' context. (#22228)
7. The Modify Distribution Group (Cloud Hybrid) Package was erroring if the Global Configuration Form did not have OnPrem Exchange configuration. This issue has now been resolved so that the package now skips On Prem Exchange activities if the exchange configuration is not available in the Global Configuration Form. (#19167)
8. The New User (All Environment) Package was having an issue where the name of the selected license was not consistent between the Chatbot and the ticket audit note. This has been fixed to display friendly name of the license in both areas. (#20371)
9. The New User (All Environments) Package was has been added with an additional license in the license dropdown for Windows Defender. (#22273)
10. The New user (Cloud Hybrid) Package was added with a friendly name for Minecraft Education Faculty, Microsoft 365 A3 Suite features for faculty and Minecraft Education Student licenses as it was showing SKU to make it easier to read. (#22600)
11. The New User (Semi Hybrid) package has been updated to improve handling for misconfiguration of UPN suffixes. (#22368)
12. The Terminate User (Cloud Hybrid) Package has been updated with additional waiting time to better support clients with large number of mailboxes. (#22199)

What's New 🌟​

We are pleased to share our latest platform release RC12.1!

In this release, more work has been done towards getting SmartForms Ready.

In addition to that, we have focused on some important bug fixes and made some enhancements to the Partner Portal to provide you with a better user experience.

• New "Access Pia Partner Portal" Role 🙋
• Additional Bug Fixes 🐛

See below for further details.

As always, We're here to help—reach out to Partner Support whenever you need assistance.

🙋 New "Access Pia Partner Portal" Role​

With this release, a new role "Access Pia Partner Portal" will be available in the Edit User screen of the Partner Portal. This role will provide you with initial access to the Pia Partner Portal from where you can be assigned additional Access levels as required.

This has been done to avoid the confusion around what the "Engineer" role in the Pia Partner Portal does.

From now on, the "Engineer" role will give you access to the Pia Chatbot in the ticketing system where you can execution automations and send feedback. However, if you need ANY access to the Pia Partner Portal, you will need to have the "Pia Partner Portal" role assigned to you.

🐛 Bug Fixes​

1. The Adoption Report was not updating the data as per the Start Date and End Date entered. This has now been fixed so that correct data are displayed based on the filters added. (#21843)
2. Fixed an issue in the Connected Service for Connectwise where the Company Sync was not working as expected. (#22680)
3. Fixed an edge case scenario for high memory usage causing stability issue for Pia. (#22717)
4. Fixed an edge case scenario where The "Export Chat History" popout in the Chatbot was not giving the option to enter an email address to send the PDF of the chat history. (#22696)

What's New 🌟​

We are pleased to share our latest platform release RC12!

Our primary focus in this release has been setting up more foundations for SmartForms, you will see few mentions of functionalities relating to SmartForms below.

We have also made some enhancements and important bug fixes which are mentioned below:

• 3 New CSP Integrations! ⚒️

  • Dickerdata Integration
  • Ingrammicro Integration
  • Rhipe Integration

• Live Packages Screen Enhancements

  • Added Ticket Filter option in the Live Package Screen
  • Added Source Filter option in the Live Package Screen
  • Extension automation now display as a nested log under the primary package

• Additional Enhancements 🌟

  • Updated Feedback options in the Pia Chatbot
  • New Activity and Condition have been added to support the SmartForms feature. More information will be available on the full release of SmartForms.

• 5 Bug Fixes 🐛

See below for further details.

As always, We're here to help — reach out to Partner Support whenever you need assistance.

What is SmartForms?​

🔥 A Sneak Peek into SmartForms​

Here's what your client will see in the SmartForms Portal depending on what you turn on:

🔆 Live Packages Screen Enhancements​

Added 'Ticket Id' Filter option in the Live Package Screen​

A new filter has been added in the Live Package screen allowing you to filter live Packages using the Ticket Id. This section is called "Filter Ticket ID" and can be used by typing your ticket Id.

If you are searching for a particular ticket in the Live Packages view, this will make it easier as it will save time. (#15511)

Added 'Source' filter option in the Live Package Screen​

One more filter has been added in the Live Package screen allowing you to filter the packages based on the source of the package execution.

By default, the 'Source' filter will have "Pia Chatbot" selected which will filter all the packages that were executed in the Pia Chatbot. However, you can choose from additional options to filter your package based on different sources such as Schedules or Triage (Ticketing System). (#22064)

Function Packages now display as a Nested log in Live Packages Screen​

Previously, the extension packages were displayed as a separate log when viewed in the live packages screen. This has now been changed so that they are displayed under the primary package as nested log making it clear that the extension package is running within the primary package. (#22062)

🌟 Additional Enhancements​

Updated Feedback Options in the Pia Chatbot​

The options available in the feedback drop-down of the Pia Chatbot have now been modified. The reason behind this is that we have taken a new approach to how we do machine learning making use of larger sets of data generated through AI.

If you would still like us to work with you on improving the ML on your tenant, please work with your PSM to give us good and bad examples of tickets that we are classifying for you.

These are the feedback options that are now available in the Pia chatbot:

• Pia was a good bot
• Pia had an issue during my ticket
• Other Feedback (#22151)

⚒️ 3 New CSP Integrations​

With this release, Pia will extend its support for more Licensing services. The configuration options for each of them will be available in the connected service screen of the Pia Partner Portal.

1. Rhipe CSP Integration (#7498)
2. Dickerdata Integration (#7499)
3. Ingrammicro Integration (#8177)

🐛 Bug Fixes​

1. The 'Client' Filter in the client screen did not allow ampersand symbol "&" previously. This has now been modified so that you can now use the filter to search for clients that have '&' in their name. (#22107)
2. Fixed an edge case scenario where the data was not populating in flexible assets as the IT Glue Connected Service was having an issue with the sync. (#21919)
3. Previously, the Triage package failed when it was executed against the ticket for clients that are not synchronised into Pia from your ticketing system. This is now handled gracefully. (#21834)
4. The Ticket Audit Note was not reflecting in the ConnectWise Manage Ticket for a custom built package which has now been fixed in this release. (#22203)

We are excited to announce our RFC271 release, introducing new and improved automations alongside some important fixes.

More Extension Points ! 🌟​

We have added more extension points in some of your favourite automation packages (i.e. New User package, Terminate User package and Reset Network Password package) allowing you to create and link more extensions into these packages. (#21889)

Below are the areas the packages will now have extension points available:

For more information on Extension Points, refer to this article.

Added Support for the Lastest version of Azure AD Connect Cloud Sync​

We have extended our support to the latest version of Azure AD Connect Cloud Sync enabling you to use Pia for clients that are on the latest version.

What do I need to do to use Cloud sync?​

• You need to re-authorise and re-delegate the client that you want to use Cloud Sync on because we have added a new scope which requires your client to do this.
• if you have not already filled this out, you need to add the Cloud Sync server to the Global Config Form. This may already be filled out if you were previously using AD Sync. (#18226)

Additional Functionalities in Get User Details Package​

The Get User Details (All Environments) Package has been updated to retrieve additional information about the user which are:

• Locked out status
• Password expiry status
• Enabled/Disabled status

Based on the status for each of the fields above, the package will then suggest additional actions that you can perform to change the status eliminating the need for you to manually search for a package which will perform the required action. (#9974)

New Bulk Add/Remove users to Group Package to support Semi Hybrid Environment​

A new version of the Bulk Add/Remove users to Group package has now been created to support semi hybrid environment so you can now run the package for the clients that are on semi hybrid environment. (#15146)

Improved Performance for New user Package​

Performance improvements should now be noticeable when executing the New User(All Environments) package in your Pia chatbot. (#22003, #22140)

Added Description Field to multiple packages​

A description field has been added to Terminate User, Re-enable terminated User and Change User Details packages allowing you to store and view custom information about the user for whom the action is being performed.

This feature is ON by default for Change User Details Package. For Terminate User and Re-enable Terminated User Packages, this is OFF by default. (#21826)

Additional Package Enhancements​

1. The Bulk Update User Details (Cloud Only & Cloud Hybrid) Package Form has been added with validation rules in the First Name, Last Name and Mobile Number fields to eliminate typos and validation errors. (#14018)
2. The New User (All Environments) Package has been added with one more configuration option called "Enable Default Password Never Expires" which when ticked will force the 'Set the password to never expire' to be ticked when creating a new user. You can Opt In this feature in the Package Configuration Form. (#8749)
3. The New User (All Environments) Package form has been modified so that you are now able to customise the email address to be different to the UPN of the use you are creating if the suggested email does not match your company policy. You can Opt In this feature in the Package Configuration Form. (#21708)
4. The Reset Network Password (Cloud Hybrid) Package has now been updated allowing you to set a default password. You can Opt In this feature in the Package Configuration Form. (#15004)
5. The Setup Mail Forwarding (Cloud Only & Cloud Hybrid) Package has now been renamed to Setup/Remove Mail Forwarding to correctly indicate the actions that can be performed through the package. (#9082)
6. The Terminate User (Cloud Only & Cloud Hybrid) Package has now been updated to force Sign out the user from their account in azure and force disable the user in azure upon termination. (#22180)
7. A handful of packages has been promoted to full release and the beta tag has been removed. (#21355)
8. We have increased the number of suggestions after each package executions based off common patterns of how they are used. Your automation will now finish before you are suggested with the automation options which means the suggestions will not affect the completion of your automation. (#12522)

🐛 Bug Fixes​

1. The Bulk Update User Details Package displayed UPN which was not required. This can been modified to only show relevant form fields. (#19771)
2. Changed the Chat Message Option from "Done" to "None" when Pia asks if you would like to perform any other action with the user after the original package execution is complete. (#18371)
3. The Create Shared Mailbox (Cloud Only) Package was sending incorrect values for display name which has now been amended. (#21867)
4. The Delete Mail Contacts (Cloud Only) Package had a clerical error denoting the wrong action which has now been fixed. (#21262)
5. The New User (All Environment) Package was waiting for the license even if the "Enable wait for group based license" option was not ticked. This has been fixed now so that the package behaves correctly as per the option selected/unselected. (#22261)
6. The New User (All Environments) Package was not updating the job title of the CW contacts. This has now been fixed so that the package now updates additional properties of a CW contact. (#22067)
7. The New User (All Environment) Package was not populating the Teams Phone with Phone Calling Plan licenss in the list of available license which has now been updated to consider the license. (#21720)
8. The New User (Cloud Hybrid) Package was having a validation issue in the form which has now been fixed to allow the users to be created with only one character in the Last Name field. (#18879)
9. The New User (Cloud Hybrid) Package was failing to create users due to an edge case scenario which has now been fixed. (#22130)
10. The New User (Cloud Hybrid) Package displayed negative license count. This behavior has now been modified to only display licenses with count above 0. (#22144)
11. The New User (Cloud Only) Package was not able to create a New User as the "Company Name" was longer than the defined limit. Updated the character limit in the form so that the package can accept longer names. (#19805)
12. The New User (Prem Only) package was failing due to the presence of extra grave (`) accent characters within the filter block. This has now been fixed. (#21974)
13. The OpenVPN Setup/Reinstall Package errored when configuring the end user's PC which has now been fixed. (#22289)
14. The Reset Network Password (Cloud Only) Package option "Change Password at next logon" was not working as the users were having to reset their password upon attempting to login in some cases. This has now been fixed so that if the option is not selected, the password is reset instantly. (#21319)
15. The Teams Troubleshooter Package was failing if the Teams cache could not cleared. This behaviour has now been modified so that the engineer will get a message in the chat if the Teams cache could not be cleared and also will get option to Force shut down Teams. (#18791)
16. The Terminate User (Semi-Hybrid) Package was not providing a list of OUs to move the terminated user to. This has now been fixed so that the package now displays a list of available OUs where the user can be moved upon termination. (#21604, #19268)
17. The Terminate User (Semi Hybrid) Package was only disabling Azure Account skipping the DC Account in some cases which has now been fixed to disable account is both areas. (#21915)
18. The Triage Package was not firing the tickets and assigning an engineer to the tickets due to an edge case scenario which has now been fixed. (#22166, #21513)
19. The Win10 Install Network Printer Package was erroring if the required information for the printer was not available. This has been modified to take into account additional information which can be used by the package alternatively. (#21281)
20. The Win10 Printer Troubleshooting Package was failing when no printers were found for the user. An error handling has been added so that a message is displayed in the chat advising the engineer that no printers are found. (#22276)

What's New 🌟​

We're pleased to share our latest platform release RC11!

In this release, we have laid the groundwork for Smartforms along with the following changes:

• 5 Enhancements 💡
  • Added Pax8 CSP Integration
  • Performance Enhancements
  • Added SharePoint Graph API Permissions
  • Added Azure Cloud Sync Graph API Permissions
  • Updated Partner Portal Menu layout
• 10 Bug Fixes 🛠️

See below for further details.

As always, We're here to help — reach out to Partner Support whenever you need assistance.

🔥 Enhancements​

Added Pax8 CSP Integration​

With this release, we have created support for our first CSP integration!

Pia now offers integration with Pax8, enabling you to meet your licensing needs through Pax8. You can now set up a Connected Service for Pax8 within the Connected Services screen of your Pia portal. This allows you to make use of it as part of Extension Automations and Custom Automations.

Pia will be updating over the next month or so it's existing automations (New User and Terminate User) to increment and decrement licensing as part of those processes. We will also be adding a new Automation for Managing Licensing via Pia.

To learn more on configuring the connected service for Pax8, refer to this article.

Performance Enhancements​

Performance improvements should be noticeable in the following areas across Pia:

• Client Screen
• Package Editor Screen
• Pia Chatbot Screen
• Pia ConnectWise Embed/Chatbot Screen
• Pia Package Execution (#21233, #20793, #20794, #20795 and #20796)

Added SharePoint Graph API Permissions​

SharePoint support has been added via the ability to reauthorise your client with an increased scope covering SharePoint which will allow you to write custom automations that connect to SharePoint to perform actions (#19878)

Added Azure Cloud Sync Graph API Permissions​

Azure Cloud Sync permissions have now been added in preparation for Pia to roll out support for Cloud Sync in place of Azure AD Connect for Pia's AI Desk automations (#19478)

Updated the Pia Partner Portal Menu Layout​

We have updated the Partner Portal Menu to be more condensed. This allows us to free up some space in the menu as well as make the menu options easier to find (#18016)

🐛 Bug Fixes​

Here are the bug fixes in this release:

Adoption Report Fix​

1. Tickets from 2021/2022 are coming up in the adoption report: Applied changes to make sure not to update the ReportingDate in the training record if the ticket lastmodified date is older than 90 days by default. The value can be controlled using the settings.(#21183).

Other Fixes​

1. An asterisk (*) is displayed on the activity while switching from one activity to another after discarding the changes made in the first activity. (#19516).
2. In the Agent Screen sorting via LastCheckInDate was not working previously. This has now been fixed. (#21272)
3. Live Packages: Width change should resize the package list. (#21780)
4. Live Packages Screen: fixed ordering of the logs in live packages view. (#21783)
5. Added some more robustness to the way that we handle Microsoft App Registrations/Authorisations to ensure that they auto renew more regularly and that the authorisation only expire when the password is changed on the account. (#19438)
6. When Authorising clients, there were a couple of scenarios that would cause the page to look like it was consistently loading meaning it looked like the Authorisation has failed or always in progress. We have updated to have some Refresh steps and retry loops which we would expect you to be able to authorise clients with one interaction now. (#21233, #21154)
7. Updated the scopes to allow cloud sync to be used as a part of the Pia automations. Like with most updates, we will update the Pia automations to take advantage of the updates on the scopes in the coming month. (#19478)
8. Fixed an edge case where an IT Glue link was not working for a client as there was an extra space in ConnectWise Connected Service. (#21462)