Employee identifying information

ClientSpace provides additional data mapping through the HRPAPI to enhance the Employee related workflows. The additional mapping ensures that Employee data from PrismHR is imported into the fields on the Employee dataform, so that configured workflows trigger. Fields on the Employment dataform populate through the API import process (HRPAPI_initial_employment and HRPAPI_employment).

The HRPAPI_initial_employment and HRPAPI_employment import mappings have additional columns for the following fields.

These new fields are displayed in the Additional Information fieldset on the Employment dataform.

All of the fields can be used in field replacement to return the value stored in the related dataform field. The Yes/No fields can be used to configure trigger conditions by typing Yes or No in the trigger value field. Enrolled Benefits can be used for triggering by using a trigger operator of Contains and a decoded value such as Health, Dental, Vision, etc.

The fields have the following configured values for Enrolled Benefits options.

Code/ImportID - Decode

Field mappings for the fields are in the HRPAPI_initial_employment and HRPAPI_employment import configurations.

The following fields are triggerable, enabling workflow channel and email template triggering to occur on changes to the following fields:

• mluEnrolledBenefits
• luHasRetirement
• luHasDependents
• isFICAexempt
• isFLSAexempt