...
| Info | ||||
|---|---|---|---|---|
| ||||
ClientSpace monitors the PrismHR Event queue and creates Dataform dataform records for every Event event containing changes that are mapped in an Import Map Header. The generated records can then be used to trigger system logic. |
...
Details
...
Scheduled Process: PrismHR Import Events
...
Import Map Configuration:
- Header SourcefileSource File: HRPAPI_event*.csv
- Dataform: PrismHREvent
- Import Type: API
- Special Import: true
- Import Map Details
- Source Field: <name_no_spaces>
- Data Type: always Text
- API Path: Schema/Class/field
- Project Type and Field not used
API Configuration
...
- Same as a typical PrismHR API Configuration (can use existing)
- Respects only the 'KeepLeadingZeros=0/1' parameter for Client Numbers
PrismHR Subscription forms
...
- New Type field, Standard or Event
- Existing Subscriptions must be set to Standard (run attached Script to update)
- This process uses Type 'Event'
Process Overview
...
- Retrieve the Event type Subscription
- Retrieve all Import Map Details with header source file = 'HRPAPI_event*.csv'
- Retrieve all Events from PrismHR for the Subscription
- Resolve each Event into a list of
- Schema (the type of change, such as Employee)
- Class (the category of change, such as Person or Direct Deposit
- Client Number
- Object ID (typically the Employee ID)
- Modified Attributes (which fields changed for this Event)
- If an Event contains a Modified Attribute that is not in the Import Map it will be added to the Excludes list on the Subscription
- For each resolved Event
- Populate a new PrismHR Event dataform with the resolved Event data
- Locate the workspace for the Client Number (from CM.ClientNumber)
- if found, save the PrismHR Event dataform in that workspace
- if not found, save the PrismHR Event dataform in the Admin workspace
- Save using the PrismHREvent Pipeline - Any business rules triggered by this will also need to be set to execute on the PrismHREvent Pipeline.
...