Leaver workflow to set attribute in target application

Sailpoint 8.4

Hi, I need to set a target application attribute when a user’s termination date is set in HRMS. Need help on where can I modify the default leaver workflow to achieve it.

Hi @himabindu306,

do you want the leaver to start when the date is set?

Hi Emanuele,

Yes, but I also want to set the status attribute in the target application.

to start the leaver process you can configure the date of HRMS like an identity attribute and set the leaver trigger on this attribute.

To set the status attribute on application you can you the post leaver rule.

@himabindu306 get the value from hrms to sailpoint–> then populate that value in identity attribute -->write lifecycle event and there mentioned value change or rule compare old and new identity value and if value match return true. Call your workflow and inworkflow u can have your logic for application

1 Like

I have set identity “inactive” attribute to true when user’s termination date is equal to or less than today’s date. I configured the leaver event based on inactive attribute, but leaver is not triggering… Any idea what could be the issue?

@himabindu306 lifecycle event will trigger if process event is select in refresh task.
Also if you are checking old identity and new identity then make sure you are not setting attribute from debug

event got triggered when I tried for new identity. But still the update in the target system didnot happen. Attaching the leaver workflow.
Leaver-workflow.txt (10.8 KB)

Hi, Any help. I am still stuck here…

Hi @himabindu306,

if the leaver process is triggered on the identity, and if you want to make a change on the target application,
you try using the rapid setup,
configure the rapid setup in the environment.

where you enable the rapid setup just for leaver, or other lifecycle events

enable the rapid setup leaver in the global settings, then from
application → rapid setup
select the application. on which want to work (ex: AD)
in leaver configuration
enable the required options such as

  1. Disable the account
  2. Removing the entitlement
  3. moving the Disable OU

once the configuration is made then try to run a leaver on the test account.

Hi @himabindu306 I can see some issues in your code, however, forget about the code…
I’m just wondering why you are not using the normal provisioning policy OOTB for the “Disable” and change the value of the target attribute, it will be fast, easy, and clean as well

Thanks Muhammad for the response

1 Like

You are more than welcome @himabindu306!

Regards,
Muhammad

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.