Zero to Hero
Solved a problem in which leading 0s being removed from a .CSV would cause duplicate profiles and mass terminations during the synchronization. Now the automation will match the employee IDs regardless of the presence of leading 0s. (Friendly Reminder: Please still check your work when handling any .CSVs or uploads. We want to rely on accurate data over safety measures every time.)
They're baaaack!
Solves a problem in which emails attached to previously termed users were prohibiting correct synchronization if the user was re-hired under a new employee ID. Now the synchronization will identify the previously termed user and update their profile with the new information, including the new employee ID.
Better, Faster, Stronger
Condensed a two step process in which a rehired user would be un-termed in one synchronization and have their profile updated on the next synchronization. This now happens in the same step.
Who's in Scope?
Added an alert that allows us to identify when departments are included in the user provided .CSV but not expected in SwipeSense admin. This alerting is intended to address questions of department scope from users. We will continue to determine the need for further reporting here.
A Little Less All-Or-Nothing
Adjusted a feature in which any non ‘UTF-8 Encoded Characters’ would cause a total failure in the synchronization. Behavior has been adjusted to skip the offending line and continue the remainder of the synchronization as normal.
Who's in Charge Here?
Work done to ensure that the .CSV provided by the facility remains the source of truth for all synchronization automation.
Better than Microsoft Clippy!
eAdded some helper text to SwipeSense admin for internal users. A gentle reminder to verify whether or not you are adding users to a network with an active HRIS integration and to check your work accordingly. (Screenshot Below)... Here’s what Clippy is in case you’re significantly younger than me.