...
Feature | Description |
Common API Client | You can use the common Saviynt function to call a Saviynt API. OnLink provides the required JSON for the relevant API call. Users can modify this JSON and also replace hardcoded values with customfields. Since roles is a list, users can use a multiselect customfield. If more than one value is set for such a customfield, OnLink will automatically create multiple roles entries - one for eahc value in the multiselect field.  |
Output Fields | Set status and an optional output field API Response Field that can be mapped from the API JSON response. Set the JSON field path in Response JSON Path which allows OnLink to pull the field and map it to the issue.  |
Other API | You can also call any other Saviynt API using “Other Saviynt API”. Set the “apiName” key in the key-value config textarea as shown below.  |
API Body | You can use Jira for Automation to construct the API body message. This may be useful for cases where you have complex mapping requirements (transformation, asset field mapping, etc). Once you have constructed the API body in Jira for Automation, you can set the output API to a custom field of type Multi-Line Text Field/Paragraph.  Here’s an example of a Jira for Automation rule that sets the API Body. RequestJSON is a custom field that holds the API Request JSON message. This value can then be mapped to API Body of Saviynt API call.  |