Product Updates - (SP081) - 10 September 2024

This document will provide an overview of the features/updates the product development team has delivered in Sprint SPO81 (10 September 2024 Release)

What’s New 🚀

Add Family Members during Registration

A new setting is now available within Registration Form settings.

‘Allow family member creation’.

When enabled, a new section will appear at the bottom of the registration form. This section cannot be configured / moved within the form. 

Upon successful registration, the user submitting the form will become a family manager and family members will be attached to that user. 

Any registration automations will trigger for all family members.

💡How this helps

Allows users to save time by registering their family members during their own registration process.

Ability to Copy a Journey

📺 Watch Video

A ‘copy’ function has been added to the Journey listing. 

When a Journey is copied, the steps, criteria and actions are also copied.

💡How this helps
Helps save time by copying all steps, criteria and actions if multiple journeys are required.

‘Confirm Shift’ added as Journey Criteria

📺 Watch Video

A new Journey step criteria has been added - Event Shift User - Confirmed

The criteria is considered complete when the shift user status is set to confirmed.

💡How this helps
This update offers further options within the onboarding Journey.
Common examples of this include, requiring users to confirm for an interview shift or a trial shift as part of their journey before they can progress. 

Update Locked Template Fields - New Admin Permission 

A new permission has been added to Role Offer / Events / Shift administrator permissions to override any templated fields.

When enabled, the administrator;

• Will be able to update any locked template fields when creating a Shift. Event or Role Offer, but not when updating.

💡How this helps
This permission will help certain "super" admins make changes to templates after they have been created.

 

New Training User Status - ‘Exempt

📺 Watch Video

A new ‘Exempt’ status has been added to the list of training user statuses.

This status is intended to be used when users are not required to complete certain training modules that are assigned to them as part of their role or shift etc. 

Only administrators will be able to mark a user as ‘exempt’ from training, and users will not be able to see that they are exempt. 

Administrators can filter by the Exempt status:

💡How this helps

This new status will help administrators keep track of who is exempt from completing certain training modules. This will help keep the candidate moving through any role application journey's more efficiently.

Shift Feedback Forms for Team Leaders

Shift feedback forms can now be assigned to only shift leaders

💡How this helps
This new form will be useful to collect feedback or information from people leading shifts, rather than regular shift users. 

Defer Payments 

Administrators may enable a new account setting in the Payment tab which allows users to defer their payment until later by receiving an invoice.

 

Settings for the email template used to send the invoice link is now divided into two settings - one for Receipts (user has paid in full) vs Invoices (has not paid).

When the end-user views one or more paid Shifts in the portal, and are shown the payment screen, they are shown an additional ‘Defer Payment’ button. Clicking it applies them to the shift, and creates an unpaid payment record in the system.

Portal Shift payment screen, user shown the Defer Payment option.


In the admin console under Users > Payments, or within the User profile for a user, the unpaid payment can be seen alongside complete payments. The status shows as ‘Deferred’ and the Vendor shows as ‘Rosterfy’, to show that the record is not tied to a payment provider in any way.


Admin User Payments listing.

The administrator may use the row-level actions (three dots menu) to Record Payment / Note.

 

The administrator is shown a popup where they can decide which of the unpaid items to mark as paid, as one transaction may have been for 2 or more Shifts. All are ticked by default.

Only if an administrator selects all items to be marked as settled will the status update to ‘Complete’ and a ‘settled at’ date recorded.


Popup with which items to mark as paid, external id and notes fields.

To make things easier for Admin to find Payments that need to be settled, advanced filters on the Payment User listing now allows you to filter by Settled At date, Status = Deferred and Amount Paid. These are also available as columns on the listing.


Img.6/7, Payment User listing - new columns and filters.

On the Shift User listing, it is easier to keep track of which attendances have been paid for, using new columns ‘is paid’ and ‘is owing’. Paid means requires payment and the User has paid, Owing means ‘requires payment and the User has deferred paying this item. It is also possible to filter by these properties.

Img.8: Is Paid / Is Owing columns in Shift User listing.

In order to better communicate the status of a Payment User record at times like Invoice send/Tax Receipt send, admins may now use additional Merge Tags in the email template editor to dynamically show details about the Payment User.
This includes a bullet list of the items included in the transaction.

Minor Enhancements / Fixes ☑️

Display Form Titles in Portal

Form Titles will now display in portal for these forms:

• Attendance / Check-In / Check-out form / Apply  / Role Accept / Role Reject Forms

Include Role Offer ID and ‘Can Self Apply’ as filters on RoleOffer listing 

When bulk updating Check-in/Check-out times, warn the administrator that this will not update the shift user status to ‘attended’