Employee Journey: Employee Data Management: Box Folder Management
This pattern is part of the Employee Data Management solution of the Employee Journey. Created by SnapLogic in conjunction with partner Eljun, LLC This pattern looks for active users within Workday that were updated within the last two hours and pulls employee files into their corresponding sub-folders, using the file structure created from the Box Folder Management pipeline. In this solution, the parent directory for employee files is divided into “Active” and “Terminated” folders. Under each of these subfolders is a series of sub-folders A-Z (representing the first letter of each employee last name). The actual Employee File Folder is then found within the appropriate alphabetical subfolder with a naming convention “EmployeeID_LastName_FirstName”. Additional sub folders are created within each employee folder, each representing a functional category of documents that the HR unit may want to capture such as performance, expenses, and training. Pipelines Get Employee Files With this pipeline, for active users updated in Workday within the last 2 hours, determine what information from the Workday Get_Workers object to include, then: kick off the Box_Folder_Management pipeline get the user’s active status, employee name, and ID from Workday get the user’s Jobvite candidate information get the user’s 7Geese information and write it to the user’s Performance sub folder. get the user’s Skilljar information and write it to the user’s Training sub folder. get the user’s Docusign information get the user’s Expensify information and write it to the user’s Expenses sub folder. Applications in use: Workday, Box, Jobvite, 7Geese, Skilljar, Docusign, Expensify Box_Folder_Management This pipeline creates a folder structure within Box to store relevant data for a new hire, moves it to a separate location when an employee leaves, or archives the termination folders if the employee is rehired. In the case where an employee leaves the company, their folders are moved to the Terminated folder. If a person is re-hired, their Terminated folders are archived. Applications in use: Box Snaps used: Mapper, Pipeline Execute, Router, Union, JSON Splitter, Box File Operations, Exit, Filter, Copy, Join, JSON Formatter, File Writer, Box Directory Browser, Tail Check_and_Create_Folder This pipeline checks to see if the requested folder already exists, and if not, creates it. Applications in use: Box Snaps used: Box Directory Browser, Group by N, Mapper, Join, Sequence, Router, Box Add Folder, Union Push_File_to_Box Use this pipeline to read a file from the SnapLogic Platform and write it to a users Box folder. Applications in use: Box Snaps used: Directory Browser, Filter, File Reader, Box Write Downloads Get Employee Files.slp (127.1 KB) Box_Folder_Management.slp (71.9 KB) Check_and_Create_Folder.slp (19.6 KB) Push_File_to_Box.slp (7.7 KB) See Also SnapLogic Human Resources Automate employee workflows from talent management to employee on and offboarding, all in one platform.Employee Journey: Create or Update Skilljar User
Contributed by SnapLogic Use this pipeline to create or update a user in Skilljar. This pipeline could be added into the Employee Journey: Employee Onboarding/Offboarding pattern. Configuration Update the parameters for action you wish to perform. As currently configured, set empStatus to Active indicate if the user is to be added and made part of the group “Internal”. Change which group to add them to by updating the value of groupName in the Snap labelled Filter Group. Applications in use: Skilljar (via REST) Snaps used: REST Get, Mapper, Router, REST Post, REST Put, Filter, Union, Copy, JSON Splitter, Join Downloads Create_or_Update_Skilljar_User.slp (37.3 KB)Employee Journey: Employee Onboarding/Offboarding
SnapLogic and SnapLogic partner, Eljun LLC, demonstrate an employee onboarding/offboarding automation use case across a multi-endpoint stack. This solution fully automates account and file management once an employee is hired or employee account deprovisioning once an employee is no longer with the company. Applications in use: Workday, Active Directory, ServiceNow, Salesforce Pipelines The following pipelines are used in this solution. Workday Event Based Integration This pipeline is meant to be triggered by hire and termination events in Workday, which will determine which child pipeline to execute. Snaps used: JSON Parser, Mapper, Workday Read, Router, Pipeline Execute, Union Child pipelines: Employee Journey-Onboarding-AD-SNOW-SF, Employee Journey-Offboarding-AD-SNOW-SF Employee Journey-Onboarding-AD-SNOW-SF This pipeline is called by the Workday Event Based Integration pipeline when a user is added. Snaps used: Workday Read, Tail, Copy, JSON Formatter, File Writer, Mapper, Active Directory List Users, Active Directory Create Entry, Active Directory Update Entry, Exit, ServiceNow Query, ServiceNow Insert, Router, ServiceNow Update, ServiceNow Create, Head Employee Journey-Offboarding-AD-SNOW-SF This pipeline is called by the Workday Event Based Integration pipeline when a user is being offboarded. Snaps used: Workday Read, Filter, Head, Copy, Mapper, Active Directory List Users, Active Directory Disable Entry, ServiceNow Query, ServiceNow Delete, Salesforce Read, Salesforce Update Downloads Workday Event Based Integration.slp (23.7 KB) Employee Journey-Onboarding-AD-SNOW-SF.slp (38.4 KB) Employee Journey-Offboarding-AD-SNOW-SF.slp (25.5 KB)Employee Journey: People Analytics
This pattern is part of People Analytics of the Employee Journey. SnapLogic and SnapLogic partner, Eljun LLC, demonstrate a people analytics use case, automatically moving Workday operational metadata updates to an analytics database for analysis and insights. Configuration Applications in use : Workday, Snowflake Snaps used : Workday Read, Mapper, Sort, Group by Fields, Copy, Group by N, JSON Splitter, Join, Filter, Snowflake SCD2, Snowflake Execute, Router, Conditional, Union, Snowflake Bulk Upsert Downloads People_Analytics_Warehouse_EmployeeTable.slp (73.2 KB)Employee Journey: Recruiting: Position Creation
This pattern is part of Recruitment Automation of the Employee Journey. SnapLogic and SnapLogic partner, Eljun LLC, demonstrate how the data from a new job position opened up in Workday can be automatically pushed to an applicant tracking system, such as Jobvite. Configuration Applications in use : Workday, Snowflake, Jobvite Snaps used: Mapper, Workday Read, REST Get, Router, REST Put, REST Post, Union, Snowflake - Insert Downloads PositionCreation_2021_03_18.slp (29.2 KB)Employee Journey: Insert new employee into Workday
Created by @rdill This pipeline pattern allows users to respond to a REST Post event triggered by a third party HR solution (e.g. Jobvite, Glassdoor, LinkedIn, etc.) and insert new employee(s) data into Workday. Configuration This pipeline requires the proper structure to insert a new employee in Workday. There are two kinds of data needed to create a new employee, “static” data, such as country reference, organization reference, etc. The second is the dynamic data, user name, hire date, etc. The pipeline is configured to provide the static data and all the user needs to do is provide the dynamic data. Sources: Any application that can invoke a REST Post to create an employee in Workday and contains the necessary attributes to create a new employee in Workday. (In this case, a JSON document is used.) Targets: Workday: Service, Staffing, Object, Hire Employee Snaps used: File Reader, JSON Parser, Mapper, Workday Write Downloads POST Hire Employee.slp (9.4 KB)Employee Journey: Scheduled employee data batch update from Oracle into Workday
Created by @rdill This pipeline pattern is ideal for organizations that require a complete view of their employees. This pattern is used to run a scheduled/periodic update of employee data and information from Oracle into Workday. The pipeline will compare the lists of employees in Oracle and Workday, if there are employees that are found in Oracle but not listed in Workday, then the employee information will be added to Workday. Configuration The table in Oracle needs to contain the necessary data required to execute the Hire Object in Workday Sources: Oracle database table, employees, Workday Hire Employee Targets: Workday Service, Staffing, Object, Hire_Employee Snaps used: Mapper, Oracle Execute, Workday Read, Workday Write, Diff Snap Downloads ORCL Workday Hire Employee.slp (15.9 KB)
