/
Saviynt

Saviynt

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 each value in the multiselect field.

image-20240629-174631.png

Here are the list of methods calling Saviynt’s “createrequest" API

To use the generic “Other Saviynt API” option to invoke any other Saviynt API, you need to use the “apiName” property in key-value config to specify the api. For example, to call “addrole” api, use below:

image-20250814-183929.png

 

Output Fields

Set status and an optional output 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.

image-20240629-175711.png

 

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.

image-20241019-144159.png

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.

image-20241019-145823.png

 

Other Config

api By default OnLink uses the api version specified in the URL in the connection. However you can overwrite that by setting this attribute in the “KeyValue” text area of the post function. E.g. api=v5