We often have errors on FPS's that are due to employees having special characters in their names/addresses. It would be great if we could run a special character report that flags any of these to us as at the moment, we have to scour through reports whch is frustrating as some of our payrolls have over 3000 employees
Hi Alex, if these characters come across via an API, what is the behaviour of staffology to flag these characters?
Hey, thanks for the idea - we've taken a slightly different approach to this which still solves the problem.
We've added validation that will prevent invalid names/addresses being entered in the first place that will later fail on RTI.
The enhanced validation was released in the product in September so since then you should have had no FPS failures for these reasons (unless the invalid data was already in the database).