REST connector - statusAndThresholdConfig vs statusConfig

[GauravJain]

Which attribute should be used to in "accountParams" configuration to reflect account status in Saviynt - statusAndThresholdConfig OR statusConfig?

If we are using "statusConfig" then is there any point using "statusAndThresholdConfig" for account status updates?

I have another questions on this topic - Consider, i am using following configuration in "accountParams" to mark accounts "Inactive" but i am not taking any action w.r.t user-account correlation or deleting account-entitlement mapping

"statusAndThresholdConfig": {
"deleteLinks": false,
"accountThresholdValue": 0,
"correlateInactiveAccounts": true,
"inactivateAccountsNotInFile": true,
"deleteAccEntForActiveAccounts": true
},

So, my accounts are now marked Inactive but later i decide to remove user-account correlation and also delete linking between account and entitlements for inactive accounts. Can i now update above configuration to manage both the tasks for existing "Inactive" accounts?

Regards

Gaurav

[This message has been edited by moderator to merge reply comment]

[rushikeshvartak]

• You can update configurations
• It will be impacted from next recon

[GauravJain]

thanks @rushikeshvartak for an update. One more questions is - which configuration in "statusAndThresholdConfig"  is triggered as part of accounts import job and which one for entitlements import? OR only the accounts import job will use the "statusAndThresholdConfig" configuration and it has no relation with entitlements import job?

"statusAndThresholdConfig": {
"deleteLinks": false,
"accountThresholdValue": 0,
"correlateInactiveAccounts": true,
"inactivateAccountsNotInFile": true,
"deleteAccEntForActiveAccounts": true
},

Regards

Gaurav

[rushikeshvartak]

both uses statusAndThresholdConfig config.

Some sections used for account [Green] and some for entitlement  [blue]

"statusAndThresholdConfig": {
"deleteLinks": false,
"accountThresholdValue": 0,
"correlateInactiveAccounts": true,
"inactivateAccountsNotInFile": true,
"deleteAccEntForActiveAccounts": true,

"inactivateEntsNotInFeed": true,
"entThresholdValue": {
"entType": {
"Group": {
"ent": 240
}}

},

[GauravJain]

Thanks @rushikeshvartak . can you please confirm my first question in this post - If we are using "statusConfig" then is there any point using "statusAndThresholdConfig" for account status updates?

whats the difference and which one is preferable?

Regards

Gaurav

[rushikeshvartak · Accepted solution]

• statusConfig is used to decide what are active/inactive value 
• statusAndThresholdConfig can also used to define active/inactive status.
• You can use only statusAndThresholdConfig

[GauravJain]

Ok but this is only to define status of Accounts, right? Whats should we use to define entitlements status?

[rushikeshvartak]

• Its always active and if not coming from import then inactive

[GauravJain]

Ok, so i don't need to define "statusConfig" in each "entTypes" configuration. Examples given in documents are confusing - Developers Handbook (saviyntcloud.com)

I will remove this config and see if any changes in data.

[GauravJain]

Removed "statusConfig" from each entitlement type config and its working fine. Thanks @rushikeshvartak 

[GauravJain]

What value we should define to avoid this warning message - "Warning - entitlementThresholdValue limit exceeded. No changes has been imported from Recon."

currently, i have defined "ent":0 for each "entType" under "entThresholdValue".

I am using similar configuration for accounts "accountThresholdValue": 0 to avoid similar warning message.

[GauravJain]

Hi @rushikeshvartak it looks like entitlement threshold functionality doesn't work. 

i am using following configuration but still getting the warning message "Warning - entitlementThresholdValue limit exceeded. No changes has been imported from Recon."

I don't even have 10000 entitlements for any of the entitlement types (as mentioned below) but still getting warning message. its weird. Also, if i just remove this config "entThresholdValue" then Saviynt takes default configuration value of 1000 and gives same warning message. is it really working?

{
"statusAndThresholdConfig":
{
"statusColumn": "customproperty1",
"activeStatus": ["true"],
"deleteLinks": false,
"accountThresholdValue": 5000,
"correlateInactiveAccounts": true,
"inactivateAccountsNotInFile": true,
"deleteAccEntForActiveAccounts": false,
"inactivateEntsNotInFeed": true,
"entThresholdValue": {
"entType": {
"E1": {
"ent": 10000
},
"E2": {
"ent": 10000
},
"E3": {
"ent": 10000
},
"E4": {
"ent": 10000
}
}
}
}
}

[GauravJain]

Hi @rushikeshvartak - its working now. i missed adding one entitlement in configuration which was causing this issue.