Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Using bind variable in Remove access in Database connector

prachi
Regular Contributor II
Regular Contributor II

Hi,

I am trying to call the stored procedure for remove access in the database connector. However my stored procedure returns a result which is stored in the bind variable. I am using Oracle database , and access is revoked when i try executing the statement in db : 

CALL apps.Saviynt_remove_user_resp('3955','Journal Entry',:status)

where :status is the bind variable passed as input parameter.

I am trying to pass the same statement in my remove access JSON as :

{
"Responsibility": ["CALL apps.Saviynt_remove_user_resp('${accountName}','${task.entitlement_valueKey.entitlement_value}',:status)"]
}

After running the WSRETRY i do not see any error in logs or any chtange in task status or update date/time

prachi_0-1655123121350.png

Can you help me fix this issue, I am assuming this could be due to passing the bind variable, not sure of saviynt supports this format.

Thanks in advance

4 REPLIES 4

sahajranajee
Saviynt Employee
Saviynt Employee

Hello,

Since you will be using the JDBC driver for oracle to integrate with your target, the binding should be supported as long as your jdbc driver supports it. 

Which app version are you trying this on. Can you try executing just this task and share the logs.

 


Regards,
Sahaj Ranajee
Sr. Product Specialist

prachi
Regular Contributor II
Regular Contributor II

Hi,

Thankyou for the response.

The issue is resolved now.

 

sahajranajee
Saviynt Employee
Saviynt Employee

Hi @prachi 

That is great news! Could you please add the solution here on the post for the benefit of the community?

 


Regards,
Sahaj Ranajee
Sr. Product Specialist

prachi
Regular Contributor II
Regular Contributor II

Hi,

In security system i had turned automated provisioning off so the task time was not at all changing.. when i turned on the same JSON that i had when we were in call, it worked