We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

Pending Tasks scheduling

Skanga
New Contributor
New Contributor

Hi,

In one case I implemented  a Leaver process with an User Update Rule that contains and Update Account task (to update User's end-date on targets applications) and  an Account deactivation task but when the Leaver process is triggered, the Account deactivation task is completed before the Update Account task so on targets applications user's end-date is not updated: The account is deactivated with the old end-date value.

Someone can help me with a functional process for pending tasks sheduling to complete the update account task before the account deactivation task?

Thanks:)

Skanga
9 REPLIES 9

RakeshMG
Saviynt Employee
Saviynt Employee

Try using Task Execution Hierarchy

In Admin -> Global Configuration -> Tasks


​Regards

Rakesh M Goudar

adriencosson
Regular Contributor III
Regular Contributor III

Hello Rakesh,

The suggested idea did not help as Disable Account are still picked up before Update Account.

Also we tried to implement Instant Provisioning by enabling it on the Security System and in Global Configurations for Update Account. Still the task needs to be picked by WSRetryJob.

Any other idea or should we get in touch with support ?

Regards,
Adrien COSSON

Assign time based using advance query after leaver in next 2 hour update account task and then disable task


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

adriencosson
Regular Contributor III
Regular Contributor III

Hello @rushikeshvartak,

Thanks for your response. Where would we need to paste such advanced query to tell the system to execute the disable Account task in 2 hours ?

As of now in User Update Rule, we can only trigger tasks with a "day to day" dependency :

adriencosson_0-1688482438974.png

 

Regards,
Adrien COSSON

We can split rule into 2 and in condition block using SQL pull records for disable account after 2 hours


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

adriencosson
Regular Contributor III
Regular Contributor III

Thanks for clarifying, would you have any working example to guide us on this ?

Regards,
Adrien COSSON

Modify as per your need

and DATE_SUB( a.startdate,INTERVAL 7 DAY) and a.startdate between curdate() and DATE_ADD(curdate(),INTERVAL 7 DAY)


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

adriencosson
Regular Contributor III
Regular Contributor III

Hello @rushikeshvartak,

Let's say we have the following flow :

  • Identity is getting updated with an "Inactive" Status from Import (HR source)
  • Rules will be triggered respectively to :
  1. Update the account on SAP systems right after the identity is updated > OK
  2. Disable Accounts on SAP Systems > This task would need to be created after 2 hours
  3. Remove Access / Accounts tasks to be triggered and executed with delay. > OK
  • Hence, the update account can be completed before the Disable Account proceeds.

> How could we tell the system to trigger the task 2 hours later without any additional update on the identity ?

Regards,
Adrien COSSON

Using condition attribute and adding date time filter in rule


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.