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.
Box Snap - Read file/folder properties
Hi, Current Box snaps does not allow to read file/folder properties like owner, created, udpated dates etc. Also when the folder is empty there is no way to get the folder path using folder id. Are there any enhancements coming for the Box snap pack which will address these gaps? Regards, Sripathi
Create multiple files in BOX
Hi Team , I am working on creating multiple files in my box folder. Created a child and parent. Child will create the File in the folder having a ultra task mapped to it Parent is having a CSV reader with all the file names and connects to the pipeline execute snap. This is doing the expected work. Instead it creates one file in the root folder with all the names. the name of the file is the parameter value. It worked in one point , i made some correction and then on it is not working , am on top of this for past few days , but not able to fix it. Any ideas will be deeply appreciated. attached both the snaps Snaplogic_POC_Filecreation_2019_11_01.slp (5.6 KB) Snaplogic POC file create_2019_11_01.slp (4.9 KB)Box account with our own Box connected app
Hi, Today while creating the Box account, SnapLogic internally uses a connected app in Box (client_id=4y9mpks2hql3xchpudijkct1vfhwwklx), it is not possible to override this with our own connected app. Due to this at the Box side all the API calls are registered against “Snaplogic app” connected app. There is no way to track which project in SnapLogic is actually using the APIs. In our case we have many projects uses Box, each have their own quota of Box usage, since SnapLogic is using same connected app at the Box side we are not able to govern the Box usage accurately. Is there a way or implementation plan in progress to allow feed in out own client_id for Box account? Regards, Sripathi
Salesforce Attachment to Box
Created by @skatpally This pattern downloads a (contract) attachment from Salesforce and writes it to Box. Maximum 25 MB attachment. Configuration Update the File path within the Box Write Snap to the correct directory within your Box instance. Sources: Salesforce attachment Targets: File on Box Snaps used: Salesforce Read, Mapper, Salesforce Attachment Download, Document to Binary, Box Write Downloads Salesforce_attachments_to_Box.slp (8.1 KB)Create Box folders for Salesforce cases
Created by @skatpally For an account created in Salesforce, SnapLogic checks if a Box folder named with the Salesforce case number exists. It it doesn’t exist, SnapLogic creates a new Box folder and names it with the Salesforce case number. SnapLogic also creates a shared link to the newly created Box folder. Configuration Set the SFDCAccount pipeline parameter to the Salesforce Account ID Sources: Salesforce account Targets: Box folder Snaps used: Mapper, Salesforce Read, Sort, Unique, Box Add Folder, REST Put Downloads Create_Box_folders_for_Salesforce_cases.slp (11.9 KB)New CSV in Box will create a new record in AWS Redshift
Created by @kjain This pipeline parses a CSV file in Box and creates a new record in Redshift. Configuration Provide value in update condition field in the Redshift - Update Snap. Example id = ‘5069829837’ Sources: Box Targets: Redshift Snaps used: Box Directory, Box Read, CSV Parser, Mapper, Redshift - Update Downloads Box_to_RedshiftUpdate.slp (6.9 KB)Record Box files to Google Sheets
Created by @skatpally A file is uploaded to Box, SnapLogic stores the metadata of the file into Google Sheets as a new row Configuration Create App to get the access_token. You can also do OAuth2.0 Authentication Sources: Box Targets: Google Sheets Snaps used: REST Get, CSV Parser, WorkSheet Writer Downloads Record_Box_files_to_Google_Sheets.slp (6.0 KB)Record new CSV file in Box to Google Sheets
Created by @skatpally SnapLogic moves a CSV file uploaded to Box into Google Sheets as a new row. Configuration Webhooks need to created by the Client Sources: CSV file in Box Targets: Google Sheet Snaps used: Box Read Snap, CSV Parser, WorkSheet Writer Downloads Record_new_CSV_file_in_Box_to_Google_Sheets.slp (5.0 KB)Upload Gmail attachments to Box
Created by @skatpally When new email is received in Gmail, if the email has attachments, SnapLogic uploads these attachments to the Box root folder. Configuration Sources: Email with attachments Targets: Box root folder Snaps used: Email Reader, Mapper, File Reader, Box Write Downloads Upload_Gmail_attachments_to_Box.slp (6.6 KB)
