08/01/2023 08:35 AM
Hi,
We are generating the delete account tasks for Active Directory using Actionable Analytics. We want to define a threshold value such that if the number of rows in the Analytics query is greater than the threshold, no delete account task should be generated.
We couldn't find anything that would help achieve this.
So, we tried the provisioning threshold configuration at the Security System level:
Task Type: DeleteAccount, Threshold: 1.
We ran the Analytics job for delete account and 2 delete account tasks were generated. We tried provisioning these tasks and both got processed.
Ideally, it should not provision any of the 2 tasks because we have a threshold defined at the Security System.
Please advice as to why this might be happening.
Thanks.
08/04/2023 11:39 AM
Hi @SinghAtul ,
Greetings.
If you're keeping the threshold as 1, it wouldn't even pick any tasks. So instead for testing purposes try creating 10 tasks and keep the threshold as 6 or any number less than 10. Please let us know on your findings.
Thanks
08/07/2023 05:53 AM - edited 08/07/2023 06:00 AM
We have a similar scenario. We tried creating 11 tasks and setting the threshold to 5. Still all the delete account tasks were processed.
I think what @rushikeshvartak mentioned is correct. This seems to work only for tasks created through ARS requests.
Could there be any alternate way to achieve this?
08/06/2023 04:47 PM - edited 08/06/2023 04:49 PM
The provisioning threshold configuration at the Security System level seems used for ARS Request only.
To confirm behavior set config to 5 and keep 6+ task open state and run WSRETRY