/
Workday & Jira Service desk Integration - Requirements documentation
Workday & Jira Service desk Integration - Requirements documentation
- YUVARAJ KUNDASI (Unlicensed)
- Jay Karmarkar (Unlicensed)
- Dipesh Chouksey (Unlicensed)
- Nishanth K V (Unlicensed)
Owned by YUVARAJ KUNDASI (Unlicensed)
Objective:
Develop custom app for integrating Workday with Jira Service Desk to automate ticket creation in JSD.
Client Requirements:
When a customer raises an issue/request. Data from Workday auto populates fields when the request is submitted.
The Workday integration will update the JSD data tables at least once every 24 hours
We do not want the Workday dump updating any issue information once submitted.
Meeting Requirements:
- Frequency: Once a day, 1am central time US
- Not all graco users have emai ids in workday
- Therefore, create a custom reporter field with list of users who don't have email ids associated with them
- Send the excel sheet to chad with all the missing and incorrect fie
Functional Requirements:
- Workday user properties and users will be synced to Jira as Jira users with user properties. New users will be created if user is not in Jira. Sync will be done at a predetermined frequency (15 days or 30 days) which should be configurable.
- Workday and Jira Sync is independent of any Jira events & triggers.
- Jira user properties will be used to update custom fields based on user picker field. The mapping will be done in the mapping screen of the App.
- Custom field will be updated upon below Jira events
- Issue created.
- Issue updated.
Workday fields/data
| Workday Fields | Available in Get_Workers response | Comments | API operation required | Implementation status | Endpoint | Workday Fields | ||
|---|---|---|---|---|---|---|---|---|
| 1 | User ID | Available | Same as Employee_ID as per the response | Get_Workers | DONE | |||
| 2 | Manager | Available | Available in Get_Workers under Management_Chain_Data | Get_Workers | DONE | |||
| 3 | Location | - | Not able to fetch this data but Region is available. Yet to confirm if the value is correct. | Get_Workers | DONE | Workday Location Chain, | WD Location Hierarchy | Region |
| 4 | Cost Center | ? | Not sure should we use a separate endpoint as the Get_Workers will not fetch this data? The value is under another tag called "Organization_Type_ID" Yet to confirm if the value is correct. | Get_Workers | Organization_Type_ID | |||
| 5 | Employee ID | Available | Same as User_ID as per the response | Get_Workers | DONE | |||
| 6 | Business Title | - | Not available in this operation (Get_Workers). Should use a different operation called "Get_Employee" in order to fetch this data. | Get_Employee | https://community.workday.com/sites/default/files/file-hosting/productionapi/Human_Resources/v33.0/Get_Employee.html | |||
| 7 | Phone (Telephone) | Available | Available in Get_Workers under Phone_Data | Get_Workers | DONE | |||
| 8 | Phone (Mobile) | Available | Available in Get_Workers under Phone_Data | Get_Workers | DONE | |||
| 9 | Available | Available in Get_Workers under Email_Address_Data | Get_Workers | DONE | ||||
| 10 | Work Address | Available | Available in Get_Workers under Address_Data | Get_Workers | DONE | |||
| 11 | Region | Available | Available in Get_Workers under Country_Region_Descriptor | Get_Workers | DONE | |||
| 12 | Division | - | Not available. | Get_Establishments | ||||
| 13 | Location Hierarchy | ? | Not sure should we use a separate endpoint as the Get_Workers will not fetch this data? The value is under another tag called "Organization_Type_ID" | Get_Establishments | Organization_Type_ID | |||
| 14 | Employee Name | Available | Available in Get_Workers | Get_Workers | DONE | |||
| 15 | Superior | ? | Not available | |||||
| 16 | Supervisory Management Chain | Available | Available in Get_Workers but we get only "Manager" data and there are multiple "Managers" present under every user | Get_Workers | ||||
| 17 | Shipping Address | ? | Is this same as Home address? |
Workday response attachment:
YUVARAJ KUNDASI (Unlicensed): Please take a look.
Feature List of Workday:
- Time Tracking
- Goal Management
- Succession planning
- Global payroll tools
- Career and development planning
- Recruiting tools
- Strategic workforce planning
- Workforce analytics
- Operational headcount planning
- Workday Big Data Analytics integration
- Business assets
- Grants management
- Purchase orders
- Real time spend analytics
- Revenue management
- Expenses
- Project management
- Custom reports
- Manage your asset roster
- Centralized business management
- Talent Management
- Payroll Solutions
- Performance Management
- Career and Development Planning
- Cloud Connect for Third-Party Payroll
- Organization Management
- Absence Management
- Benefits administration
- Onboarding tools
- Performance management
- Revenue management
- Procurement
- Revenue recognition
- Invoicing
- Accounting and finance
- Management reporting
- Mobile friendly
- Online support
- Automatically reconcile bank statements
- Monitor processes and workflows
Detailed breakdown of tasks:
| # | Requirement | Responsibility | Related url links | Comments |
|---|---|---|---|---|
| 1 | Research on how to link and authenticate the Workday in JSD. | Nishanth K V (Unlicensed) | These links may not give us full details about linking workday with JSD but it might give us some insight for the scenario. | |
| 2 | Evaluate Workday API for sending fields data from Workday. | Nishanth K V (Unlicensed) |
| These are the available API's from workday documentation. |
| 3 | Sync from workday every 24 hours | |||
| 4 | Trigger the issue creation in JSD from workday (Issue update not required) | |||
| 5 | Mapping for Workday fields and JSD | YUVARAJ KUNDASI (Unlicensed) |
Useful Link for API: https://www.programmableweb.com/api/workday
Questions:
- Actual requirements
- Approach
- How to connect two apps
- What info to show on screen and where
:
, multiple selections available,
Related content
10.Functional Requirement
10.Functional Requirement
Read with this
20.Technical Documentation
20.Technical Documentation
Read with this