The Employee Sync via PrismHR Integrations needs to sync correlating effective date from PrismHR.
The sync should look at and pull the effective date listed in PrismHR that correlates with the item it is syncing. In our experience, rarely are changes made the same day they became effective, and this is why an effective date is used. For exampl...
I believe it will be very useful for all users utilizing the PrismHR integration if we could have the API pull in the Standard Hours field within PrismHR.
Customize or Limit fields in Employee Settings with PrismHR integration
There are more Employee fields syncing to Swipeclock than needed compared to TWP. Employee addresses are not necessary, but fields like PTO Approver and Email address that is marked as Primary are.
Use hire date as effective PrismHR employee sync date vs. the date of the sync.
This would eliminate having to manually update the effective date to the hire date so that scripting will function properly. The only field that should remain the date of the sync that we can think of would be for pay rate changes.
In addition to onboarding new hire information, an endpoint to get the signed PDF documents that employees sign during onboarding process, that we can pull via API to store in local documents store.
0
1
