We are seeing behaviour on the Saviynt for Saviynt endpoint where if a users SAVROLE is removed in the UI then when you perform an import using the default Saviynt for Saviynt Account and Access import jobs the account that is correlated to the user still shows as having the SAVROLE that was removed as an entitlement.
However, if you use analytics to create a task to remove the entitlement from the account a task is successfully created to remove the entitlement from the account and in addition the default actions on the connection/security system remove the SAVROLE from the user (which is the required outcome).
