Search

enableHR Software Release 2023.09.20

Bugfixes

Self Service Approval (changeset) email not sending for collections/aggregate field changes

Background (FT-5058)

When a user submits a change to their personal, payroll, contact or emergency contact information, the change will send through a self service approval task waiting for the self service admin to review and action.

Update

We've made improvements to better detect changes in collection and aggregate field types (bank, super, etc). As a result, notifications will now be sent via email alongside the approval tasks.

Additionally, self-service approval emails will be triggered for any changes made within the self-service portal.
  • Standard security fixes
  • Document file extension fixes for files that are saved in invalid format (.file)
  • Cosmetic updates for ARA branded accounts

Enhancements/Features

New notification email to notify users when Billing Contact information incorrect

Background (FT-5040)

There are scenarios where users will update their billing contact details against their enableHR account settings > commercial > Billing tab section, but the data they input is incomplete or incorrect.

When the data is incorrect, Chargify/Maxio will reject this contact information. For accounts with incorrect or incomplete Billing email or phone contact details, they may miss their invoices sent out by Chargify/Maxio.

Updates

The update we made is to notify Billing/Primary contacts for the account when we first detect that Chargify/Maxio has rejected the billing contact details.

Email Scenarios

An email will send out for the below scenarios:

  • email is incorrect or incomplete
  • phone number is incorrect or incomplete
  • both of the above

Email sending logic

We will send out the incorrect or incomplete notification email to the account contact person based on the below priority order:

  1. Email contact entered in the Billing Details, else
  2. Email contact entered in the Primary Details, else
  3. All Users with AccountAdmin user role

Open API - /Users/self end point to include record details

Background (FT-4078)

To support our integration partners, an eSS user profile needed to also have the employee details using the linked record ID, our /users/self API endpoint did not have the information of the linked record.

Updates

The linked record for the eSS user is now accessible when using the /users/self API endpoint to retrieve user details.

This linked record is available in both REST and GraphQL API responses.

The documentation portal has been updated to reflect these changes in the example code, and the API change log has been revised to include the release details of these updates.