App Connect

App Connect

Join this online user group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

Using IBM® App Connect to interact with Factorial HR

By Irene A Peter posted Mon August 05, 2024 07:21 AM

  

Using IBM® App Connect to interact with Factorial HR

Factorial HR is a Human Resources (HR) software that helps small and medium-sized businesses streamline HR administration. With Factorial HR, you can track each employee's work day and productivity, log working hours, keep track of remaining time off, and schedule employee shifts.

Building a flow in IBM App Connect with Factorial HR

Use App Connect to build flows that integrate with Factorial HR and other applications. The connector is displayed as Factorial HR on the App Connect User Interface (UI). 

To allow App Connect to connect to your Factorial HR account, you need to fill in the connection fields that you see in the App Connect Designer Catalog page or flow editor.

Supported authorization types: 

BASIC OAUTH

OAUTH 2.0 AUTH CODE

For detailed information about different authorization types, how to generate connection field values, and how to use the Templates gallery, see How to use IBM App Connect with Factorial HR on the IBM Documentation page.

Supported objects in Factorial HR

The following are the Factorial HR objects that can be run in App Connect.

Object  Description
Absences  Absences are recorded as time off requests that are submitted by employees.
Absence types  Absence types are categories of time off that employees can select when taking an absence.
Attendances  A record of an employee's presence or absence from work, including the date and the type of attendance.
Employees  A list of employees in a company. Each employee record includes their personal information, job title, department, and  other relevant details.
Tasks  Tasks are the activities that employees are assigned to complete. 

 

Scenario 1: Create time entries in Toggl Track for each time registry added in Factorial HR

Consider the following scenario:
In this flow, when a time registry is added in Factorial HR, the flow creates a time entry in Toggl Track for each added registry, ensuring accurate time tracking and reducing manual effort. The flow retrieves the necessary information from the time registry and creates a new time entry with the relevant details, including the employee's name, the project name, and the duration of the time entry.

The following are the steps involved in the flow:


1. In the event Scheduler node, specify a time schedule based on your requirement (choose how often you want to run the flow). 

2. Using the Factorial HR Retrieve shifts operation, the details of new time registries in Factorial HR are retrieved.

2. When creating time entries in Toggl Track for each time registry added in Factorial HR, the following formatting conventions are applied to ensure accurate time tracking:

Month: If the month is less than 10, a leading zero is added to the month field to ensure that Toggl Track reads the month correctly.
For example, if the month is 5, it will be displayed as 05 in Toggl Track.

Day: If the day is less than 10, a leading zero is added to the day field to ensure that Toggl Track reads the day correctly.
For example, if the day is 5, it will be displayed as 05 in Toggl Track.
3. Using the Toggl Track Retrieve workspace projects node, the flow retrieves the workspace projects associated with the employee's time registry.
4. Using the Toggl Track Create time entry operation, the flow creates a new time entry in Toggl Track for the employee, including the relevant details such as the date, time, and project name.

 Scenario 2: Create an event in Google Calendar for each applied absence in Factorial HR

Consider the following scenario:
In this flow, an employee applies for an absence in Factorial HR and the flow creates an event in Google Calendar for each applied absence, ensuring accurate time tracking and reducing administrative burden.
The following are the steps involved in the flow:

1. In the event Scheduler node, specify a time schedule based on your requirement (choose how often you want to run the flow). 
2. Using the Factorial HR Retrieve absence details operation, when an employee requests an absence in Factorial HR, the flow retrieves the absence information from Factorial HR based on the previous event time set in the Scheduler node .  
3. Using the Factorial HR Retrieve employee by ID operation, the flow creates a new employee in Factorial HR using the retrieved information, such as the employee's name, email, and other relevant details.
4. Using the Google Calendar Create event node, the flow creates a new event in Google Calendar for each applied absence. The event title, description, and other details are populated using information from Factorial HR, such as the employee's name, the type of absence, and the dates of the absence. 
The event is created and an email is sent to the employee who requested the absence, which they can then accept or decline.

Resources

You can view this template and other useful templates in the Templates gallery of your App Connect Designer instance.

Get started with a free IBM App Connect Enterprise as a Service trial for 30 days to try out all our templates, visit https://ibm.biz/app-trial.

If you are running a containerized instance of IBM App Connect, use the following URL to directly access the template:

  • Create time entries in Toggl Track for each time registry added in Factorial HR: https://<your-instance-id>/templates/Create%20time%20entries%20in%20Toggl%20Track%20for%20each%20time%20registry%20added%20in%20Factorial%20HR
  • Create an event in Google Calendar for each applied absence in Factorial HR: https://<your-instance-id>/templates/Create%20an%20event%20in%20Google%20Calendar%20for%20each%20applied%20absence%20in%20Factorial%20HR

            Note: Replace <your-instance-id> in the URL with your custom instance ID.

You must enable the Designer AI features in your containerized environment to access the App Connect templates. For more information, see The preloaded IBM App Connect templates.

You also have the option to import the .yaml file for this template directly into your App Connect Designer instance. These templates are available in a public GitHub repository.

0 comments
16 views

Permalink