Initial HR sync takes the most ‘obvious field’ and maps it to Snappy
Advanced Mappings replace previously pulled field with the field the customer wants to use
Advance Mappings Example
Fields that work with Advanced Mapping
First Name
Last Name
Email
Hire Date
Department
Override Email
How does it work? (technically)
After an initial HR connection is made to Snappy we are able to view and monitor that connection through our vendor Dashboard (Merge).
We can then click into the client’s account and view all of the fields returned to us by their HR system.
Then we can set the new mapping
Limitations and Known Issues
Replaces all the data of the mapped field
E.g. we cannot support preferred name if exists otherwise use first name
We need the exact name of the requested fields
Company name vs. organization name
Optional workaround (temp until custom fields)
using the department field to pass other information to recipients. E.g. passing the company code
Non supported fields:
ADP: Credited service date, Preferred email
Fall Back
Advanced Mapping with fallback will replace previously pulled field with the field the customer wants to use if it has values
Advance Mappings Example NO FALLBACK
Advance Mappings Example with Fallback
What fields work with Fall Back
First Name
Last Name
Email
Hire Date
Working Since Date
Department
Custom Fields
Custom Fields add a new field the customer wants to use
Phase 1 - Overview
Creates a new field on the Snappy recipient
Companies will be able to use the information in Snappy flows
Example: filter employees for a campaign with a specific company code
Supports any String field
Release Date (TBD - early Q4)
How it’s used
Limitations and Known Issues
Supports only Strings (e.g. no dates)
Cannot be used as triggers for campaigns
Not shown on invoice