- Removal of SPF link under communication settings
- Fixed dunning process bug
- Addressed app domain redirect issue
Standardisation of Emergency Contact fields
Standard Emergency contact fields in HRA
Emergency contact information has become necessary data for all record types and for every type of client in AUS and NZ, at the moment this can be setup/enabled through system maintained custom fields at HUB level. So, it has been decided to make it available for all accounts to maintain this data and for employees to access this through ESS.
Primary and Secondary emergency contact fields are available for account admins for Australia and NZ accounts and for all record types (employee, Candidate, contractor, contractor candidate, Volunteer, Volunteer Candidate, person (WHS Legacy) , PersonRecord (WHS)).
Standard Emergency contact fields in eSS
All the employees with eSS access is now able to maintain their emergency contact information through eSS portal. Clients can setup workflow approvals through staging administration.
Primary and Secondary emergency contact fields are available to maintain data for all eSS users in both Australia and NZ accounts. These new standard emergency contact fields are now available in Staging Administration, clients can enable them for workflow approvals if necessary.
Candidate and Employee conversion function to include Emergency contact details
Merge and Transfer functions to include the emergency contact fields when they are used.
Employee record - Merge & Transfer functions now includes standard emergency contact fields.
Candidate to Employee now includes standard emergency contact fields.
Candidate record - Transfer function now includes standard emergency contact fields.
Merge another candidate to a candidate record includes standard emergency contact fields.
API end points were addressed too to include standard EC fields.
Migrate EC data from custom fields to standard Emergency contact details
After having standard Emergency contact fields client's data maintained in custom fields should be moved to the standard fields.
Migrated the emergency contacts data from custom fields to the newly created EC fields for all the HRA accounts.
Report changes to include standard Emergency contact fields in place of custom fields
The below reports uses custom EC fields and they need to be modified to use standard EC fields
Replaced the existing custom fields for emergency contacts with the new EC fields. Placement of the new EC fields on the report is as per the new order and not to the end of the report like for custom fields.
Importer changes to include standard Emergency contact fields in place of custom fields
Changes need to be made to the following Importer Jobs to replace the existing custom fields for emergency contacts with the new fields created for this purpose.
Importers when run with the emergency contact fields, the data gets stored in the new EC fields instead of the custom fields.
Exporter changes to include standard Emergency contact fields in place of custom fields
Changes need to be made to the below exporters to replace the existing custom fields for emergency contacts (EC) with the new fields created for this purpose.
While exporting the data, instead of custom fields for EC new fields are considered for the data, they are appearing at the same location as before with custom EC fields.
OpenAPI changes for Emergency Contact fields
Retrieve, Create/Update Candidates & Employee end points currently do not include emergency contact fields for the API Users.
Both Retrieve, Create/Update Candidates & Employee end points now includes standard emergency contact fields so that API users can retrieve and maintain this data.
Clear custom field setup for Emergency contacts
After migration of EC fields from custom fields to standard field, clear the custom field setup/configuration for emergency contacts so that only Standard EC fields appear to users for maintenance.
Custom fields for emergency contacts under the HUB have been disabled now.