Accessing the Service Bus Messaging History app
If a record has been updated in PeopleXD and the employee either is not showing in Access Care Rostering or has not updated as expected, there will likely be an error stopping the message from processing.
To assist with this, a Service Bus Messaging History app is available within Access evo.
To add the app to your workspace:
Within Access Evo, navigate to a workspace tab and click Add App.
Search for Service Bus Messaging History.
Click Add to Evo.
The app has been added to your workspace dashboard.
Filtering and searching messages
Within the app, you can filter and search messages in the following ways:
Filter by status — click All Status to filter messages by their status (Success, Failure, or Pending).
Filter by date range — click Today to select either Today or a Custom Period. When selecting a Custom Period, the dates default to the current date and can be amended as required. The end date cannot be set past the current date.
Search by Person ID — type a Person Reference (Person ID) into the search box on the right-hand side of the app to find messages for a specific employee.
To refresh the messages, click the 3-dot menu on the right-hand side of the app and click Refresh.
Viewing messages
Messages are displayed on the dashboard. To view the full details of a message, click on the Message ID. This opens a pop-up with the full message details. You can scroll up and down within the message screen to see all content. To copy the message, click Copy.
If a message has failed, the failure reason is displayed at the bottom of the message when you click into it.
Message statuses
Status | Description |
Success | The message was pushed from PeopleXD and processed by Access Care Rostering successfully. All required fields match and have data. |
Failure | The message was pushed from PeopleXD and processed by Access Care Rostering, but there is an issue with the data. Examples include: Address Line 1 is blank; Branch does not exist in Access Care Rostering; the required fields are not populated in PeopleXD, or the data does not match between systems. |
Pending | The message was pushed from PeopleXD but has not yet been processed by Access Care Rostering. If the status does not update at the next refresh, it is likely a failed processing attempt and will eventually be followed by either a Success or Failure message. UpdateAppointment messages are tried up to 5 times before being failed, in case the person message is still being processed at the time it is sent. All previous attempts show as Pending; if the 5th attempt fails, a Failure message is recorded. |
Failed messages — JML interface
For the JML part of the interface, failed messages are typically caused by one of the following:
Mandatory data fields not populated in PeopleXD
Examples:
Address Line 1 is not populated.
All mapped phone number fields in PeopleXD are not populated (at least one must be populated).
Data fields do not match between PeopleXD and Access Care Rostering
Examples:
Pay Group on the employee does not exist as a Pay Run in Access Care Rostering.
Department on the employee does not exist as a Branch in Access Care Rostering.
Next of Kin Relationship field does not match the Emergency Contact Relationship Type in Access Care Rostering.
To resolve these issues, update the relevant data in PeopleXD or Access Care Rostering as appropriate, then resend the message. See the Managing New Starters & Employee Records article for full guidance on resending messages.
Failed messages — absence interface
For the absence part of the interface, you will see two message types:
PXD-updateabsence — assigned to all absence messages sent from PeopleXD to Access Care Rostering.
acr-absencetotalhours — assigned to all absence messages sent from Access Care Rostering to PeopleXD.
Failed absence messages are typically caused by one of the following:
Absence type description does not exist in Access Care Rostering
To resolve this, choose one of the following options:
Update the Absence Type Mapping in PeopleXD — enter the Alternate Description against the absence pay code to match the Unavailability Type set up in Access Care Rostering.
Set up a new Unavailability Type in Access Care Rostering — create a new Unavailability Type that matches the setup in PeopleXD.
Once resolved, resend the message from PeopleXD by editing and re-saving the absence record for the employee.
Unavailability cannot be created due to reconciled shifts
If the shift should not have been reconciled, unreconcile it in Access Care Rostering and resend the absence message from PeopleXD by editing and re-saving the absence record.
If the shift was worked by the employee, amend the dates on the absence record to exclude the reconciled shifts and resend, or delete the absence record.
Unavailability cannot be created as the employee already has unavailability for the period
This typically occurs if the employee has previously been saved down in Access Care Rostering and their PeopleXD record has since been updated to not match the Rostering Criteria. From the contract date change, the employee is moved to a non-rostered Branch and Area in Access Care Rostering and a non-rostered unavailability record is automatically created, causing a clash.
If the employee should be rostered, update their contract record in PeopleXD to meet the rostering criteria. Once updated, a message is sent to make the employee available for rostering again. The absence record can then be re-saved to resend the message to Access Care Rostering.
If the employee should be marked as non-rostered for the dates the absence was entered, the interface is working as expected and the failed message can be ignored.
If an unavailability record has been entered manually against the employee in Access Care Rostering, delete the manually created record and re-save the absence record in PeopleXD to resend the message.
Permissions
To restrict which users can access the Service Bus Messaging History app within Access Evo, a module and function has been added to People Planner for Access Evo – SB Messaging History App.
This module and function must be enabled (unticked) within the Access Care Rostering environment interfaced with PeopleXD. This is enabled by your Access Consultancy Team.
To set up access restrictions for specific users:
Click Settings, then click Other.
Click Profiles & Users, then click Modules & Functions.
Locate and open the relevant user profile.
From the QuickLinks, select Modules.
Within the Modules screen, from the QuickLinks, select General.
To grant access to the app, ensure the module and function is enabled (unticked). To restrict access, disable (tick) the module and function.
Click the save icon once changes have been made.
To assign a user profile to a user:
Click Settings, then click Other.
Click Profiles & Users, then click Modules & Functions.
Locate and open the relevant user profile.
Select the profile from the Modules & Functions drop-down and click Save.
⚠️Important: Users granted access to the Service Bus Messaging History app will have full visibility of all messages sent through the interface — both from PeopleXD to Access Care Rostering and from Access Care Rostering to PeopleXD — for all employees.