Skip to main content
All CollectionsPulseway PSAPSA Release Notes
Pulseway PSA (v5.33.0) - May 2024
Pulseway PSA (v5.33.0) - May 2024

This release includes new feature, enhancements, and fixes.

O
Written by Oliver Anthony
Updated over 5 months ago

New Feature

Copy Tasks as a Template in Project Module

You can now copy tasks from one project to another with options available under Actions.

Enhancements


Azure AD is now Microsoft Entra ID

Microsoft has rebranded Azure AD to Microsoft Entra ID. The UI in PSA has, hence, undergone some changes which are related to the rebranding. For more information, see Microsoft Entra ID integration.

Integrations in Left Navigation Panel

All integrations (including Teams) are now listed under Integrations in the left navigation panel in the legacy view.

Teams Enhancements

Ticket Options under PSA-MS Teams Integration

When a ticket is created when a PSA-MS Teams integration is in place, if the Resource field is left blank, it will default to "Unassigned." Similarly, if the Due Date field is left blank, it will default to "Not available."

Resizing MS Teams Table

Resizing is now possible with the MS Teams table.

Bulk Edit Channels

In Admin > Integrations, Teams listing page, an option to bulk enable, disable, and delete endpoints has been added.

Fixes

Quotation

Fixed: When user opened a quotation and went to Line Items tab > Add Item > Etilize Catalog, an error which said "Something went wrong. Please contact the system admin," was displayed.

Pulseway PSA-Pulseway RMM Integration

Fixed: When an account was created via API v2, it was not being pushed to Pulseway RMM.

Pulseway PSA-IT Glue Integration

Fixed: When user logged into a PSA tenant that was already connected to IT Glue, opened a ticket in legacy, and tried to update a related item, an error was displayed.

Pulseway PSA-IT Glue Integration

Fixed: When a contact was opened in PSA and the IT Glue tray icon was clicked, an error was displayed which said "Unable to load related data." In case the related data loaded and if the user updated or deleted the related data, an error 500 was displayed.

Did this answer your question?