Active Directory get User Data Endpoint
Created by @dwhite Enter a base DN and an AD username to use LDAP search to find a specific user. Run as a trigger task endpoint or as a child pipeline. Configuration Enter the base dn to look for users in via the “baseDn” parameter. Enter the AD username in the “filterUser” parameter. Assign to trigger task and call via rest. Or assign to pipeline execute and run as a child as part of an orchestrator pipeline. Sources: Active Directory User Object Class Targets: REST call return Snaps used: LDAP Search, Filter, Mapper, Join, Union, Group by n Downloads AD Get User Data Endpoint.slp (14.9 KB)Pardot Prospect Import
Created by Chris Ward, SnapLogic This pattern provides the ability to integrate with Pardot’s async batch APIs allowing customers to import Prospects into their Pardot instance. Sources: SQL Server. Can be changed to another source by swapping out the SQL Server Select for another Snap Targets: Salesforce Pardot Prospect Note: Pipelines in this pattern use the expression library file pardot-config.json. Pardot_Prospect_Batch_Process Configuration Snaps used: SQL Server Select, Mapper, Group By N, Pipeline Execute (calling the pipeline Pardot_Prospect_Orchestration) Pardot_Prospect_Orchestration Configuration Snaps used: Pipeline Execute, Head This pipeline calls a series of other pipelines: Pardot_Prospect_Generate_CSV Pardot_Prospect_Open_Batch Pardot_Prospect_Add_Batch_Child Pardot_Prospect_Update_Batch_Child Pardot_Prospect_Generate_CSV Configuration Snaps used: Mapper, JSON Splitter, CSV Formatter, File Writer Pardot_Prospect_Open_Batch Configuration Snaps used: JSON Generator, REST POST, Mapper Pardot_Prospect_Add_Batch_Child Configuration Snaps used: REST POST, File Delete, Mapper, Union Pardot_Prospect_Update_Batch_Child Configuration Snaps used: REST Patch, Mapper, JSON Formatter, File Writer, Union Pardot_Prospect_Check_Batch_Status Configuration Snaps used: Directory Browser, Copy File Reader, JSON Parser, REST Get, Router, Tail, Join, File Delete, Mapper, Document to Binary, File Writer Downloads Pardot_Prospect_Batch_Process.slp (7.8 KB) pardot-config.json (233 Bytes) Pardot_Prospect_Orchestration.slp (8.8 KB) Pardot_Prospect_Generate.slp (6.6 KB) Pardot_Prospect_Open_Batch.slp (7.1 KB) Pardot_Prospect_Add_Batch_Child.slp (7.9 KB) Pardot_Prospect_Update_Batch_Child_.slp (9.1 KB) Pardot_Prospect_Check_Batch_Status.slp (23.8 KB)Sopra HR to Cornerstone - Worker Sync
Created by Jocelyn Arcega, SnapLogic. Master Data synchronization of workers between Sopra HR and Cornerstone. Configuration Sopra HR authorization is non standard, in the body of the message Cornerstone authorization is OAuth2 client_credentials Sources: Sopra HR Worker Targets: Cornerstone Worker Snaps used: Mapper, REST Post, REST Get, JSON Splitter, Join Downloads Cornerstone Integration - Worker Sync.slp (21.3 KB)Sopra HR to Cornerstone - Job Sync
Created by Jocelyn Arcega, SnapLogic. Master Data synchronization of jobs from Sopra HR to Cornerstone. Configuration Sopra HR authorization is non standard, in the body of the message Cornerstone authorization is OAuth2 client_credentials Sources: Sopra HR Jobs Targets: Cornerstone Jobs Snaps used: Mapper, REST Post, REST Get, JSON Splitter, Slack Send Message Downloads Cornerstone Integration - Job Sync.slp (13.7 KB)Sopra HR to Cornerstone - Org-Unit Sync
Created by Jocelyn Arcega, SnapLogic. This pattern is a a Master Data synchronization pipeline between 2 HR applications: Sopra HR and Cornerstone. It uses REST Snaps for integrating with both. Configuration Authorization with Sopra HR is non standard and in the message body. Authorization for Cornerstand is OAuth client credentials What’s tricky about this use case is that there are relationships between OUs so they need to be imported in the right order and sequentially, hence why the group by org hierarchy. Sources: Sopra HR Org-Units Targets: Cornerstone OUs Cornerstone Integration - Org-unit Sync pipeline Snaps used: Mapper, REST Post, REST Get, JSON Splitter, Filter, Conditional, Sort, Group by Fields, Router, Union, Group by N, Pipeline Execute, JSON Formatter, File Writer Cornerstone Integration – Insert child org Snaps used: Record Replay, JSON Splitter, Join, REST Get, Mapper, REST Post, Union Downloads Cornerstone Integration - Org-unit Sync.slp (46.3 KB) Cornerstone Integration - Org-unit Sync - Insert child org.slp (14.8 KB)
CI/CD Solution with Bitbucket
Submitted by @Linus and @uchohan The pipelines in this solution are for a proposed CI/CD process. The implementation and documentation will enable the following capabilities Ability to source control any SnapLogic Pipeline, Task and Account Commit entire project Commit individual asset Specify commit message Specify branch name Automatic Bitbucket project, repository and branch creation Automatic Bitbucket CI/CD file upload and Pipeline enablement Automatic SnapLogic project space, project and asset creation Ability to pull assets from Bitbucket to a SnapLogic project Revert changes based on specific branch Revert entire project or specific asset SnapLogic Compare Pipeline review Bitbucket Pull Request creation, approval and merge Automatic promotion of assets from development to production Terminology A SnapLogic project space (belongs to a SnapLogic organization) will be mapped to a Bitbucket repository A SnapLogic project (belongs to a SnapLogic project space) will be mapped to a Bitbucket repository (belongs to a Bitbucket project) Each repository will have 1 or more Bitbucket branches. By default, the master branch will reflect the state of assets in the SnapLogic production organization. Additional branches (feature branches) inherits the master branch and will reflect various new development efforts in the SnapLogic development organization Developer assets Each SnapLogic user that should be involved in committing or pulling assets to the Bitbucket space could have its unique and individual assets. It is recommended that each user duplicates the User_Bitbucket project and replaces User with its unique name. Although covered in greater detail in the attached PDF, the User_Bitbucket project holds these four Pipelines, each containing a single Snap: Commit Project - Commits any Pipelines, Accounts and Tasks within the specified SnapLogic project, to the specified branch in Bitbucket Commit Asset - Commits the specified asset within the specified SnapLogic project, to the specified branch in Bitbucket Pull Project - Reads any Pipelines, Accounts and Tasks from the specified branch in the specified Bitbucket, to the specified project and organization of SnapLogic Pull Asset - Reads the specified asset from the specified branch in the specified Bitbucket, to the specified project and organization of SnapLogic For each Pipeline, each user needs to update the bitbucket_account Pipeline Parameter in the respective Snaps, matching the path to their own Bitbucket Account. Downloads Documentation CI_CD Documentation.pdf (1.3 MB) For User_Bitbucket project: Commit Asset.slp (3.5 KB) Commit Project.slp (3.4 KB) Pull Asset.slp (3.6 KB) Pull Project.slp (3.6 KB) Note: These pipelines all rely on shared pipelines located in a CICD-BitBucket project. Make sure to update the mappings to the pipelines within the CICd-BitBucket project to your location. For CICD-BitBucket project: 1.0 Main - SL Project to Bitbucket.slp (17.5 KB) 1.1 Create Project and Repo.slp (19.2 KB) 1.2 SL Asset to Bitbucket.slp (14.8 KB) 2.0 Main - Migrate Assets To SL.slp (23.1 KB) 2.1 Upsert Space And Project.slp (16.4 KB) 2.2 Read Assets.slp (29.3 KB) 2.2.1 Upsert Pipeline To SL.slp (12.8 KB) 2.2.2 Upsert Account To SL.slp (17.9 KB) 2.2.3 Upsert Task To SL.slp (21.2 KB) PromotionRequest.slp (26.0 KB)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)
