Integration with Kronos
Last updated
MangoApps Administrators Guide
Last updated
This guide offers a comprehensive overview of MangoApps software's integration capabilities with the UKG (Kronos) schedule management system, focusing on enhancing user experience and workflow efficiency. Tailored for MangoApps customers seeking to integrate the two platforms, this guide outlines the end-to-end process, from initial setup to routine schedule updates. The integration allows for the seamless display of real-time schedule information within MangoApps, specifically through its Shifts feature, providing users with the tools to optimize their workflow and make the most of this collaborative functionality.
From within the Admin Portal, navigate to Modules -> Schedules -> Source
Source of Shifts Data: Select "Kronos" as the data source from the dropdown menu.
Source URL: Enter the SFTP location of the csv file. MangoApps will use this SFTP endpoint to connect and fetch the shifts CSV file. If need be, you can download a sample CSV to verify all headings match.
Timezone in CSV File: If UTC is selected, MangoApps will convert the time values sent in UTC to users' store time zone prior to displaying it. If Store Timezone is selected. MangoApps will not convert the time and will display the time as is. It is recommended to use the Store Timezone option when the API is already sending the time values in the user's store time zone.
In the Login ID field, enter the login ID for the SFTP server for authentication when MangoApps tries to sync data from the .csv file.
In the Password field, enter the password for the SFTP server for authentication when MangoApps tries to sync data from the .csv file.
In the AES-256 Decryption Key field, enter the decryption key for the .csv file if you have encrypted the file with AES-256 Encryption for increased security.
After successfully testing the connection, you can proceed to configure the synchronization schedule for communication from Kronos to MangoApps.
Sync Schedule: Choose from intervals of 2, 4, 6, 8, 12, or 24 hours for the synchronization schedule to recur.
Sync Notification: Enable this setting to receive notifications once the synchronization process is completed.
Email notifications must be turned ON within the individual domain admins notification preferences to receive these emails.
Save/Save Settings & Force Sync Now: If you need to synchronize records before the scheduled time, use this option to save settings and initiate an immediate synchronization.
A crucial aspect of configuring Kronos involves populating a CSV file with specific information to ensure accurate representation of employee schedules. In this section, we will take a look into the key columns and data formats required for seamless data integration.
In this column, input the Employee ID for each user. The Employee ID must be a 6-digit number, ensuring a unique identifier for each employee.
This column requires a unique Shift Assigned ID for each shift entry. The same Shift Assigned ID should be consistent across all entries for a particular employee's shift.
Example: For a shift with Employee ID 300171, the ShiftAssignID remains the same across regular shifts and breaks. However, for another employee like 300172, the ShiftAssignID differs, maintaining consistency within their respective shifts.
The Shift Segment ID represents the regular and break time segments within a complete shift. This ID must be unique for each entry of the shift. This is crucial for accurately defining the segments of a shift, including regular work hours and breaks.
This column captures the date and time when the data is entered into the CSV file. The required data format is DD-MM-YYYY HH:MM:SS.
Use this column to indicate whether the record is new (0) or if it's intended for deletion (1).
These columns require the shift's start and end dates in the format DD-MMM-YY.
Enter the shift start and end times in the format HH:MM:SS.
Indicate whether the segment is "Regular" or "Break" in this column.
Enter the Location ID for the employee the shift is being assigned. This ID should match the extension ID attribute value of locations created in the Admin Portal's Locations section.
Double-check data integrity to prevent errors in the Kronos system.
Ensure uniqueness in Shift Assigned IDs and Shift Segment IDs for accurate mapping.
Adhere strictly to the specified date and time formats to maintain data consistency.
