Skip to main content
All CollectionsPulseway PSAPSA Release Notes
Pulseway PSA (v5.24.0) - Aug 2023
Pulseway PSA (v5.24.0) - Aug 2023

This release includes enhancements and fixes.

O
Written by Oliver Anthony
Updated over a year ago

Important: All integrations with PSA should use API employee user in the future, not a credential employee user. This will impact all third-party integrations currently leveraging API V1 integrations with PSA. The option to use credential employee user will be deprecated by Sep 2023. Please take note. This is the last notice before the deprecation takes effect. For more information, see Pulseway PSA API | Dedicated API integration account in PSA.

Enhancements


  • V2 API

    • PATCH /v2/crm/contacts/{id}

      • Gives the ability to partially update one or multiple properties of the contact

    • PATCH /v2/crm/accounts/{id}

      • Gives the ability to partially update one or multiple properties of the account

    • GET /v2/admin/security/roles/lookup

      • Retrieves all the security roles available per tenant

    • GET /v2/admin/hr/jobtitles/lookup

      • Retrieves all the job titles available per tenant

    • GET /v2/admin/hr/departments/lookup

      • Returns all departments that the tenant has in PSA

    • GET /v2/system/locations/lookup

      • Returns all locations that the tenant has in PSA

  • Ability for Workflows, from Parent Tenant, to be Cloned by Child Tenants

    • This pertains to only specific PSA tenants.

Fixes


Quotation

Fixed: When you add a charge to a quote or sales order, you have the ability to add descriptions or notes respectively. In some PSA instances, this carries through to the invoice and in some instances, it does not.

Projects

Fixed: Projects | All Projects > Tasks tab : Actions icons were displaying under the relevant subtask instead of at the same level.

Ticket

Fixed: When you opened a ticket (Project/Task) and added a service call, the resources were displaying outside the dropdown list.

Ticket

Fixed: When a new ticket was created from default account and when the user logged out and logged in, an error appeared.

Did this answer your question?