Need help on DB connector with store procedure OUT parameter

[ShantanuKumar]

We have a DB connector. The Target Application  has exposed Stored Procedure for provisioning/de-provisioning.

The stored procedure has multiple IN and 1 OUT parameter. Looks like the DB Team has done exception handling in the stored procedure. The OUT parameter will return "SUCCESS" if the operation is success else it will return the error description. 

I have 3 questions:

1. Based on the documentation, i don't see how to pass the OUTPUT parameter and it only has sample to send the IN parameter. Need some sample JSON to call stored procedure with OUT parameter.

2. We need to fetch values from one of the form attribute, extract a string and use in the stored procedure. Can we use fetch the value, manipulate to extract the string and use it in stored procedure? For example, User would see "Business User Controller:BU" on the form but we need to send "Business User Controller" in the procedure, removing the string after ":".

3. The OUT parameter would return "SUCCESS" if the operation is successful or else it will return the error message that means the provisioning failed. We need to have some logic in configuration to error out the task or consider as success based on the response. This applies for for user cases like Add Access, Remove Access and Disable. 

[rushikeshvartak · Accepted solution]

• 1. Based on the documentation, i don't see how to pass the OUTPUT parameter and it only has sample to send the IN parameter. Need some sample JSON to call stored procedure with OUT parameter. OUT parameters are not supported currently

  2. We need to fetch values from one of the form attribute, extract a string and use in the stored procedure. Can we use fetch the value, manipulate to extract the string and use it in stored procedure? For example, User would see "Business User Controller:BU" on the form but we need to send "Business User Controller" in the procedure, removing the string after ":". String manipulation can be performed 

  3. The OUT parameter would return "SUCCESS" if the operation is successful or else it will return the error message that means the provisioning failed. We need to have some logic in configuration to error out the task or consider as success based on the response. This applies for for user cases like Add Access, Remove Access and Disable.  OUT parameters are not supported currently

• Saviynt confirmation https://forums.saviynt.com/t5/application-access-governance/db-connector-can-saviynt-execute-procedu...

[ShantanuKumar]

So another question, how does Saviynt will know if  the store procedure is successful if the exception handling done in stored procedure? How does Client handle these kind of request? Is the only way to handle to have a new stored procedure created without having a OUT parameters?

Could you share a sample or syntax how to use a string manipulation for DB connector?

[rushikeshvartak]

• You can create Stored procedure without OUT parameters.
• If job is successful then DB connector consider as successful
• ${task.entitlement_valueKey?.entitlementID?.split(\"-\")[0]} https://forums.saviynt.com/t5/identity-governance/db-connector-splitting-entitlement-id-s-in-json/m-... 

[ShantanuKumar]

Appreciate all the help @rushikeshvartak .