Sav4Sav RemoveAccountJSON - Default values wrong

[Murmur]

Hi everyone, 

I just noticed, that the RemoveAccountJSON of the default Sav4Sav Connector does not work, as it tries to set the userstatus to "1" where ist should be "0" or at least \"${user.statuskey}\" as mentioned in https://docs.saviyntcloud.com/bundle/Saviynt-REST-based-Guide/page/Content/Understanding-Integration....

I don't know where else to raise this, to get it a) fixed and b) noticed by others that may face the same issue.

Cheers 🙂

RemoveAccountJSON: 

{
"call": [
{
"name": "call1",
"connection": "userAuth",
"url": "@@BASEURL@@/ECM/api/v5/updateUser",
"httpMethod": "POST",
"httpParams": "{\"username\":\"${user.username}\",\"statuskey\":\"1\"}",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"successResponses": [
{
"message": "User Updated Successfully"
}
]
}
]
}

[sudeshjaiswal · Accepted solution]

Hello @Murmur ,

Thanks for bringing it up, i have updated to our DOC team to get it updated.
Will keep you posted.

Thanks.
Eve

[rushikeshvartak]

Its already documented "${user.statuskey}

https://docs.saviyntcloud.com/bundle/Saviynt-REST-based-Guide/page/Content/Understanding-Integration...

[Murmur]

While it is true, that it is in the documentation (as I mentioned in the initial post ;)), one would still believe, that the default behaviour of a connector is the same or at least similar to the documentation. 

Besides that, I believe that using ${user.statuskey} is a bad practice, as it could potentially lead to enabling an account, when we actually want to disable them (imagine somebody would like to "remove" only this account, while keeping the User active).