Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Ability to Create Tasks on User's Day 1

Sivagami
Valued Contributor
Valued Contributor

I have a scenario where the application owner will log access requests for future hires in advance, so that the request is fully approved & ready for provisioning. They want the approval process to go ahead, but the access assignment needs to happen only on user's start date. They don't wanna use the startdate and enddate feature while requesting.

So, what's the alternate way to get the task created only on user's day 1 post all the approvals are secured?

-Siva

10 REPLIES 10

rushikeshvartak
All-Star
All-Star

Use WSRETRY advance query section join and based on start date pull tasks for provisioning 

rushikeshvartak_0-1667494892600.png

 


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

Sivagami
Valued Contributor
Valued Contributor

What if instant provisioning is enabled for such applications? Is there a way to block the tasks from going through?

amit_krishnajit
Saviynt Employee
Saviynt Employee

@Sivagami - If there is a start date and end date OOTB feature available, what is the rationale behind not using it? 

 

Thanks,
Amit

Basically, requestors will not know the start date of the future hire & hence want to provide the access on their Day 1 but have it approved and set before the user starts

amit_krishnajit
Saviynt Employee
Saviynt Employee

@Sivagami - Why can't you create a dynamic attribute which shows the user/beneficiary's start date while submitting the request? This will provide the requestors information about the start date of the future hire and they can select the start date accordingly. 

 

Thanks,
Amit

Sivagami
Valued Contributor
Valued Contributor

That's a good idea, Amit!

Start dates can change for the hires too, post App team submits the requests. If we go via this dynamic attribute method, if the start date changes post the app team submits the request to a later date / earlier date, provisioning will happen either before Day 1 / after Day 1 right? How can avoid such scenario's?

-Siva

@Sivagami - this would require an additional solution to support - build a custom jar solution. With the custom jar invoke Saviynt REST API to determine the list of new users for which start date has changed and then fetch any pending requests for them or any pending tasks for them, use API again to discontinue the pending requests/tasks for the user. Use the same jar to call APIs to put new requests for the user with the same access with the new start date (you may want to auto-approve this time as the access was anyway approved previously).

This could be a potential solution; however, you may want to vet out all the possible scenarios. 

 

Thanks,
Amit

How saviynt will know date change ?


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

From the HR data source user import.

In this case tasks start date can be updated using rest api using custom jar solution or you can discontinue tasks and recreate request but here request approval may again take time.


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