Workforce Ready Integration
The Task Manager further supports the integration using task types for imports and two task types for time entry exports.
The following imports task types supports accrual and people import from Ready:
The following export task types support time entry exports from this application to Ready:
Ready integration settings and applicable tasks automatically enable
with the purchase of the Gateway Manager module.
Workforce Ready Configuration Assumptions
The following items are assumed to be completed in Ready prior to any successful export.
- Every WFC02 field that is mapped to a Cost Center level in this application must have a corresponding Ready Cost Center with a matching unique External ID preconfigured. For example, if the WFC02 Staffing AccountCh in this application is mapped to Cost Center level 2 in Ready then there must be Cost Centers in Ready for each and every possible StaffingAccountCh value that could exist on an exported Roster. Each cost center's External ID in Ready must match each StaffingAccountCh value exactly in this application. Mapped fields in Ready can be blank in this application; as such if the WFC02 mapped field for a record is blank, then that time entry record will export without the Cost Center.
- Every Employee in this application that will at any point have
time cards exported to Ready must exist in Ready, and must meet the
matching criteria set in the Ready Employee Mapping area located in
the Integration tab of the Import Manger in this application. Note: An employee with blank mapped fields in this application is valid. If an employee does not have a mapped field, for instance no External ID, then the employee's records will be excluded from the export; and no error will be reported. A lack of a mapped field value in this application means, do not integrate that employee’s time entries into Ready. If an employee mapping field value is added after a previous export where that employee was skipped due to a lack of a mapping field value, then this application refactors that employee’s staffing records and exports previously un-exported records for that employee.
- Every work code this application reads as a Time-Off category
has been preconfigured in Ready so that the name of the Time-Off category
matches exactly in the Time-Off to Work Code Mapping section
of this application. For instance, Sick 101 in Ready, means Sick
Leave in this application. Note:
If a work code is not mapped to a Time-Off entry, then that exported time entry will not be marked as Time-Off in Ready regardless of the “type” of work code record in this application.1
Export Failure Behavior
As noted above, the mappings fields for cost centers and employees can be blank in this application, and interpreted as a desire to not include a cost center on an employee’s record. However, if this application contains a value, and that value fails to map to a cost center and/or an employee then an export error will display in the Activity Log and the entire export will fail. Failure of any record will trigger an "All or None" behavior. Failure of one record within an export will prevent the export of all other records for that export; a subsequent export after resolving all mapping issues will re-attempt all records for that failed export.