| Table of Contents |
|---|
...
Log in to the Workday tenant.
In the Search field, type View custom report.
On the View Custom Report screen, click My Reports.
Select the report you want to view. Click OK.
On the View Custom Report page, click Actions > Web Service > View URLs. Make sure Report is Web Service enabled. Edit Report, Go to Advanced Tab, Check “Enable as Web Service” option.
Click OK.
For REST, on the View URLs Web Service page, in the JSON section, right-click JSON, then Copy URL. The URL format will be something like below:
https://wd2-impl-services1.workday.com/ccx/service/customreport2/mytenant/report_owner_username/report_name?format=json&Last_Updated=2023-10-01&Department=Sales
Use the output from the report to map fields in the trigger mapping section. The reportuser and reportname combination should be provided in the “report_name” property. Report filter values can also be setup as shown below.
...
Here you can see the same field on the Positions object.
...
Jira Issues - Create or Update
Normally every new record in the Workday custom report output ends up as a new ticket. However, there are instances when you may need an existing ticket to be updated e.g. the hire (or termination) date is pushed out. In this case it makes sense to to update a previously created ticket rather than creating a new one.
There are other more long running scenarios too e.g. an employee gets a promotion in February and OnRamp creates a new issue which is processed and completed. Nine months later, another Change Job is initiated as the employee’s location has changed. In this case, a new issue should be created.
Another scenario would be a hire (processed by OnRamp) leaves the company. After some time the employee returns to the company and is rehired with the same employee ID. In this case, again a new issue should be created for the second hire instead of updating the previous issue.
To handle all these scenarios, we recommend you use the Business Process Event WID as the key for OnRamp. The ‘wid’ will stay the same when a business process is ‘corrected’ or ‘rescinded’ so it will handle the above scenarios gracefully.
If, for some reason, your business processes do not support the use of wid, here are a couple of other suggestions:
Create a key that is unique not just employee level, but at the "event" level. For example, you may consider a key that concatenates employee id with position ID. Again assuming position id is new on rehires, this will ensure the rehire is created as a new ticket.
If you always want OnRamp to create a new ticket in Jira, then you can set this below config line: config:ignore_update_check=true