Retry count for update user task

[ashutosh]

Hi All,

Is there a way by which we can set retry count for Update user task?

I am aware about configuration which we can give in our Security system for retries but for update user task there is no security system, so for them how can we specify this value?

Let me know if any further clarity is needed from my end.

Thanks

[rushikeshvartak]

Considering its REST connector . You can specify same in configJSON

https://saviynt.freshdesk.com/support/solutions/articles/43000521736-rest-connector-guide%C2%A0

Example 1: To define the number of tasks to be considered for different provisioning tasks using provisioningLimit and waitTimeMillis, use a format similar to the following:

{
  "provisioningLimit": {
    "types": {
      "NEWACCOUNT": 100,
      "UPDATEACCOUNT": 100,
      "ENABLEACCOUNT": 100,
      "DISABLEACCOUNT": 100,
      "REMOVEACCOUNT": 100,
      "ADDACCESS": 100,
      "REMOVEACCESS": 100,
      "UPDATEUSER": 100,
      "CHANGEPASSWORD": 100
    },
    "waitTimeMillis": 1000
  }
}

where,

• provisioningLimit: Use this attribute to specify the maximum number of tasks to be considered for different provisioning tasks in a single REST API call.

• types: Use this attribute to specify different type of tasks to be provisioned in a single REST API call. You can specify the following types of tasks:

  • NEWACCOUNT: Use this type of task to configure provisioning limit while creating a new account.

  • UPDATEACCOUNT: Use this type of task to configure provisioning limit while updating a new account.

  • ENABLEACCOUNT: Use this type of task to configure provisioning limit while enabling an account.

  • DISABLEACCOUNT: Use this type of task to configure provisioning limit while disabling an account.

  • REMOVEACCOUNT: Use this type of task to configure provisioning limit while removing an account.

  • ADDACCESS: Use this type of task to configure provisioning limit while adding access.

  • REMOVEACCESS: Use this type of task to configure provisioning limit while removing access.

  • UPDATEUSER: Use this type of task to configure provisioning limit while updating user.

  • CHANGEPASSWORD: Use this type of task to configure provisioning limit while changing password.

[ashutosh]

configJSON is fine for REST connector but this same field is not present in generic SOAP connector.

Is there a way it can be defined in any global configuration?

[rushikeshvartak]

Seems its not there in documentation can you raise feature request