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)

We are thrilled to announce our new Automation Release, RFC364- Automation 8.0!

This release includes new integrations and new automations along with added functionalities to some of our existing automations.

🌟 4 New SmartForms Automations!​

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

• Smartforms: Terminate User is now available for Cloud Only & On Prem environments (#22082)
• Smartforms: New User is now available for Cloud Only & On Prem environments (#21945)
• Smartforms: Grant/Revoke Mailbox Permission is now available for Cloud Only & On Prem environments (#22083)
• SmartForms: Create/Remove a Mail Forwarding Rule is now available for On Prem environment expanding the total scope to Cloud Hybrid, Cloud Only and now On Prem.(#22453)

⚒️ More Pia Automations!​

5 Semi-Hybrid Automations​

The following Pia Automations now support Semi Hybrid Environment:

• Pia: Account Locked Out (#15142)
• Pia: Change User Details (#15150)
• Pia: Add/Remove Users to Groups (#15143)
• Pia: Bulk Add/Remove Users to Group (#15146)
• Pia: Bulk Add/Remove Contacts to Group (#15147)

Pia: One Drive Troubleshooting​

With the new Pia: One Drive Troubleshooting Automation, you can troubleshoot your One Drive issues using the various troubleshooting steps provided and automatically executed by the package. The package will perform the following tasks:

Note: The Automation will confirm any action perform it is performed.

• Obtain a list of OneDrive Profiles on the target machines
• Find all synced locations and performs validation of a few common scenarios, such as:
  • Too many synced files
  • Synced Files too large
• Present a list of synced locations to the user with the option to reset
• Perform a Stop/Start of the OneDrive Software Application
• Perform a Log Out of a specified OneDrive profile
• Perform a Password Reset on the specified profile and optionally send an SMS with the details to a mobile. (#5992)

Pia: Computer Space Cleanup​

In this release, we are launching a version 2 of the Pia: Computer Space Disk Cleanup Automation with additional package enhancements and performance improvements.

This package will perform the following tasks:

• Present a list of drives on the machine to perform cleanup on
• Allow selecting folders to expand the tree view deeper
• Confirm deletion of files before proceeding
• Provide a report after the selected actions have been performed
• Add ticket notes to the ticket once the cleanup task is completed (#13307)

🤝 CSP License Provisioning Integration with Microsoft Partner Portal​

Updates to New User and Terminate User Automations​

The Pia: New User Package and Pia: Terminate User Package have now been updated to support License Provisioning and De-provisioning through Microsoft (Microsoft Partner Portal/ Microsoft Partner Center). (#23036)

For the New User Automation, you can use the License Provisioning options available in the Package Configuration Form to enable/disable this feature.

For the Terminate User Automation, you can use the License De-Provisioning options available in the Package Configuration Form to enable/disable this feature.

Microsoft Partner Portal: Modify Subscription package​

We are also introducing Microsoft Partner Portal: Modify Subscription package that allows you to review and choose how you wish to adjust the subscriptions for your Microsoft Licenses.

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.

🤝 CSP License Provisioning Integration with DickerData​

Updates to New User and Terminate User Automations​

The Pia: New User and Pia: Terminate User Automations have now been updated to support License Provisioning and De-provisioning through DickerData (#23051)

For the New User Automation, you can use the License Provisioning options available in the Package Configuration Form to enable/disable this feature.

For the Terminate User Automation, you can use the License De-Provisioning options available in the Package Configuration Form to enable/disable this feature.

DickerData: Modify Subscription package​

The new DickerData: Modify Subscription package allows you to perform License provisioning/deprovisioning your DickerData Licenses using Pia. (#23054)

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.

Improved Support for Halo PSA Ticketing System​

The Pia: New User and Pia: Terminate User Automation Process have now been updated to align with other ticketing systems where they update contacts when they are executed in the Halo PSA ticketing system. (#22960)

🔒 New Password Textbox​

All Pia Automations have been updated to use the new Password text box. This change is a part of Pia's ongoing security effort that aims to improve handling of passwords in the Pia chatbot for all automations including the ones that are created by you. (#21731)

You can modify the behaviour of this field in the Tenant Settings screen.

Here are the Automations that have been updated with the New Password textbox

• New User (All Environments)
• Re-enable Terminated Account (Cloud Hybrid, Cloud Only & Prem Only)
• Reset Network Password (Cloud Hybrid, Cloud Only & Prem Only)
• Account Locked Out (Cloud Hybrid and On Prem)

🔥 Additional Package Enhancements​

1. The 'Important Notice' message in the Pia: Reset Network Password (Cloud Only) Automation has now been modified slightly to remove confusion for clients that are not AD Synced. (#11195)
2. The Pia: New User (All Environments) Package Configuration Form now provides an option to enable default "Password Never Expires". When this is ticked, the new user account password will be set to never expire by default. (#8749)
3. The Pia: New User (All Environments) Automation has additional field added to Access Levels that allows you to set locations for contacts when they are created in Connectwise as a part of New User process. (#22531)
4. The Pia: New User (On Prem) Automation has also been modified so that you are now able to customise the email address to be different to the UPN of the user you are creating if the suggested email does not match your company policy. This option is already available for Cloud Hybrid and Cloud Only Environments. (#22527)
5. The Pia: New User, Terminate User and Change User Details Automations have now been updated with an additional option in the Package Configuration Form that allows you to enable/disable contact sync to your ticketing system during the execution of these automations. (#17823)

🐛 Bug Fixes​

1. The Setup Mail Forwarding (Cloud Hybrid) Automation while the scheduled package was running at the appropriate time, the scheduled date in the chatbot was being displayed in UTC Time instead of local time which has been fixed to remove any confusion. (#21869)
2. The Pia: Manage User Licenses Automation now informs the engineer when the user is not found and provides an option to retry. (#20015)
3. The Pia: Win10 Install Network Printer Automation has now been made more robust by updating one of its activities to be more efficient, faster and support additional printer drivers. (#21634)

We are releasing a new version with a rollup of additional bug fixes - Automation 7.2!

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

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

🌟 Package Enhancements​

1. The Pia: Bulk Add/Remove Users to Group Automation will now display all Mailbox types if the selected group is an Exchange based Distribution list. (#23448)
2. The Pia: Create a Group Automation now allows you to create an exchange online Distribution list without specifying owners or members. (#23377)
3. The Pia: New User (On Prem Only) Automation now checks for the status of the Microsoft Exchange Information Store Service before creating user mailbox and display a chat message if the service is offline. (#23127)
4. The Pia: New User (Cloud Hybrid) Automation now has an additional Username format allowing you to set UPN and SamAccountName (Username) formatting by lastFull.firstInitial and lastFullfirstInitial naming convention. (#23464)
5. The Pia: Teams Troubleshooter Automation now supports Microsoft Teams 2.x (the new version of Teams). (#22613)

🐛 Bug Fixes​

1. The Pia: Add/Remove User from Groups Automation now has extra wording to the form to inform users of the selection process (right means selected and left means unselected) which was previously causing confusion. (#23563)
2. The Pia: Bulk Update User Details (Cloud Hybrid) Automation will now update ConnectWise Contact only if required/corresponding fields have been changed. Otherwise, the update task is skipped by the Automation. (#23011)
3. The Pia: Install/Uninstall/Reinstall Software Automation has now been made more robust by adding verbose debugging information including interpretation of error codes and exception messages and ability to handle multiple versions of Winget installed on target machine. (#23145)
4. The Pia: Install Network Printer Automation has been updated with changes to improve the stability of operation with extra error handling and retry behaviour. (#22655)
5. The Pia: Install Network Printer Automation has been modified to check for special characters in the Printer Name so that it does not error while installing printers. (#23378)
6. The Pia: Microsoft Teams Troubleshooter Automation has now been updated to retrieve and display ALL users in the user selection drop-down if it could not find users in the configured All Staff Group. (#22870)
7. The Pia: Manage User Licenses Automation now informs the engineer that the sending of the welcome email feature is currently unsupported if they assign a M365 Copilot license to the user. (#23369)
8. The Pia: New User (Cloud Hybrid) Automation has now been added with an ability to handle multiple domains in the client's environment during AD Connect Sync. (#23567)
9. The Pia: New User (Cloud Hybrid) Automation now skips additional mailbox related actions (such as setting Calendar Permissions) when it cannot find user mailbox within Exchange Online which was previously causing the Automation to fail. (#23370)
10. The Pia: New User (Cloud Only) has now been updated to display additional information in the chatbot before failing if it cannot create a user due to misconfigured environment type (i.e. a client should be configured as Cloud Hybrid but is configured as Cloud Only). (#23308)
11. The Pia: Terminate User (Cloud Hybrid) Automation now does not error if the user hits cancel during Directory sync retry. The Automation will only cancel the attempt to retry the sync and return to the parent Automation informing the engineer of what went wrong, and also continuing on with the rest of the tasks. (#23314)
12. The Pia: Triage Automation now also checks for the Engineer Status of the currently run company while performing triage function depending on your Triage Configuration. (#23012)
13. The Pia: Triage Automation now also creates an Audit Log for custom fields that were modified in the Ticket during the triage process for AutoTask Tickets. (#22951)
14. The SmartForms: New User (Cloud Hybrid) Automation now auto selects the correct group specified in New User Cloud Hybrid access list which can also be modified by the user. (#23439)

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)