­x360­­­Cloud 4.1.0 Release Notes 

New Features

Ability to back up and export Teams Posts

In this release we provide an ability for partners to enable backup for Microsoft Teams posts. 

To enable backup for the new connector (service), additional permissions need to be granted to x360Cloud Entra ID application. 

We are addressing compliance needs in the first turn, so restoration of Teams posts back to Teams is not supported at this stage. Backed up posts from a specific Team Channel (or from all channels of a Team) can be exported into one of the two supported formats: 

• JSON: the raw original format messages are returned by Microsoft APIs, containing all available metadata and message properties.
• HTML: user-friendly format that includes only the most important message fields (like timestamp, author, message content, reactions and attachments) and styled for better readability.

You can find more information on how to enable backup and export the data in Backup and export Teams posts - x360Cloud - Axcient.

Improvements in ConnectWise PSA integration

Ability to map x360Cloud Organizations with Companies on ConnectWise PSA side. 

Partners who set up ConnectWise PSA integration and enabled Ticketing are now also able to map x360Cloud organizations with ConnectWise PSA companies, so that the tickets alerting about SLA breach in x360Cloud are created in the correspondent company in ConnectWise PSA. 

To set up the mappings, navigate to the “Settings – PSA” page and scroll to the “Organization Mappings” section. 

Note: In case integration with ConnectWise PSA has not been set up yet, you can follow the guidelines on how to set it: Integrate x360Cloud with ConnectWise - Axcient

Then, for each organization you want to map, pick correspondent ConnectWise PSA company from the dropdown. Each time a PSA company is selected in the dropdown the mapping is saved, so will not be lost. 

The list is sorted by the “Status” column, so that “Not mapped” organizations are always kept on the top of the list allowing you accomplish mappings for all organizations without a need to navigate across list pages. 

Note: In case of a backup failure for x360Cloud organization that doesn’t have a mapping configured, a ticket will still be pushed to PSA, to the default “x360Cloud” organization that will be automatically created by x360Cloud. 

Also, this new organization-to-company mapping step is now available when you are creating a new organization. You can pick correspondent company from PSA for your new organization in x360Cloud:

Ability to pick a CW PSA company for a Test ticket to PSA.

In earlier release we added an ability to pick a PSA company when initiating a push for a Test ticket. We have added an option to pick a company the test ticket should be created in. 

When you click on the “Send test ticket” link, the following dialog is shown allowing you to pick a desired company. This way, the entire ticketing flow can be tested, and integration is up and running. 

Reporting Tickets to PSA in Audit Log.

In this version we also added events indicating PSA tickets generation to x360Cloud Audit Log.

Following events are now logged: 

 Ability to remove ConnectWise PSA integration.

To remove the integration with PSA system, navigate to the “Settings – PSA” page and click “Edit PSA Configuration” link. 

Once you confirm the action, you will see the page with connection details. 

Switch the radio button to “Do not use a PSA System” and click Save.

Once the action is confirmed. x360Cloud will remove the PSA configuration along with credentials (connection strings) information from the system.

Fixes 

• Fix for the issue when "ErrorQuotaExceeded" error is causing backup attempt to be stuck in "in progress" state for days.
• Fix/workaround for MS 365 calendar backups happening due to server 500 errors returned by MS 365
• Fix for backup failures caused by errors while indexing emails and email attachments with a complex structure.
• Fix for Gmail backups that were failing with NullPointerException, when a few emails are failing in batch and the scan task trying to build metadata for these failed emails with mailInfo.
• Fix for the issue when SharePoint restore fails in case folder with the name specified by user as target location already exists.
• Fixed issue when individual email restore was failing when its header is too long and cannot be restored by MS 365 (we've made the system to restore email without this header and mark it as successful)

Known Issues  

• When folders are partially selected and restored in x360Cloud Browser, each folder is processed as a separate restoration and is restored to a separate target folder in the target location. 
• Smart Search shows incorrect number of matching results for Mail when using “Filter by collection”.
• Descriptions for some issues and backup progress are not shown in the container-level downloadable backup report and on the Reports page.          
• Archive emails are restored in a separate (timestamped) target folder when restored with general emails.

 SUPPORT | 800-352-0248

• Contact Axcient Support at https://partner.axcient.com/login or call 800-352-0248 
• Have you tried our Support chat for quick questions?
• Free certification courses are available in the Axcient x360Portal under Training 
• Subscribe to Axcient Status page for updates and scheduled maintenance

2074