Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Integration Design Patterns for HR Service Management Usecases

In this article, we detail the common design patterns for integrations in HR Service Management.

Quick primer on the systems that serves HR Service Management use cases.

Applicant Tracking System: An applicant tracking system (ATS) helps companies organize candidates for hiring and recruitment purposes. e.g Greenhouse

Human Capital Management: Core systems and processes management of human resources, business processes and data. e.g Workday

Service Management: Unified application that categorizes service requests, incidents, tasks, and project management. e.g Jira Service Management

There are 3 levels of integrations that supports automation:

Integration is often the long pole in the project and can make or break the outcome of the project.


1. Deep Links: Direct Access to Resources

Deep links, often in the form of URIs, provide direct access to specific resources within different applications. With Single Sign-On (SSO) capabilities, users can navigate effortlessly across applications. Whether it’s accessing a worker’s profile, a candidate’s record, or a service ticket, deep links facilitate quick and targeted interactions, enhancing user experience and productivity. Tip: We can make the URI's dynamic by embedding the ID e.g we can have a URL that points to a given Worker ID.

2. Data Sync: Keeping Information in Sync

Data synchronization involves integrating systems to ensure consistent and up-to-date information. These integration jobs, often facilitated by dedicated tools, keep data aligned between applications. For example, synchronizing worker profile data between an ATS and an HCM system ensures accurate employee information without manual data entry. This patterns requires use of middleware and ETL tools to perform the integrations.

3. In-App Integration: Contextual Data Mapping

Advancements in APIs and webhooks have paved the way for contextual integration. Applications can perform in contextual integration that maps the data from one system to another. Atlassian Marketplace has several applications that connect to systems like Hubspot, Google Cloud, Azure, Github, Salesforce etc. OnLink is one such application that enables connecting to common HR systems such as Workday, BambooHR and Greenhouse.

We'd love to hear from you on the design patterns you have used for integrating HR Service Management use cases and lessons learnt.

Disclosure: I'm part of Onward. We are the developers of the OnLink application.



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events