• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 95 subscribers
  • Views 6408 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Threshold level for a process

Rahul Sharma
over 8 years ago

Hi Experts,

 

I am trying to set a threshold level for ADS_ADSAccount_Update and ADS_ADSaccount_Update_Updateperson process so that if more than 50 records are updated once then send a over limit Waring in Job queue and do not update the Values in ADS account table.

So I set the value Threshold(Abort) = 50. So I got the over limit warning when there are more than 50 accounts were about to update, but some how the values are updated in ADSAccount table   . How can I stop the values updating in ADSaccounttabe.

 

Thank you.

  • 0 over 8 years ago
    As you are using the term Threshold(Abort), I think you are referring to a template at a column an not to the mentioned processes.

    Could you please describe what triggered the changes, at which column you have set the abort value and what you are trying to prevent?
  • 0 over 8 years ago
    Hi Markas,

    We are currently using version 7.0.2 , I updated the threshold Value(Disable) in the custom process ADS_ADSAccount_Update_UpdatePerson and I also updated the value in the table : AdsAccount and column : Account Expires. In both the cases I kept the same value for threshold value (Disable) in process and Threshold (Abort) in Table.

    Still no luck , when I wipe the data of column Account Expires (number of accounts accounts that are about to update are more that the Threshold value) and run the AD SYNC the values in the column account expires are updated and I get a over-limit warning in the JOB Queue.

    Thank you,
  • 0 over 8 years ago

    So, just for my understanding. You are having processes in the job queue marked as OVERLIMIT, which would be the correct behavior as you have set the Threshold (disable) value for your process. So stopping your process by using the thresholds is working I assume.

    As you already figured out, the processes are generated because the objects in the table ADSAccount have been updated by the synchronization. 

    Without knowing your business use-case, maybe using the quotas in your sync project would help you out here.