30 day + Inactive Lifecycle Workflow trigger

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Does anyone have a tip or has done a workflow trigger that will kick off if an account from a certain source has an end date of 30 + days and is inactive to fire off? I have never done this with a date and have not seen anyone yet try this as well for a workflow trigger

I rather not add another attribute on a profile if I do not have too

2

Hi,

I tried date comparison with startDate from identity attribute, it works. For eg:

{
	"id": "0001",
	"type": "donut",
	"name": "Cake",
	"ppu": 0.55,
	"topping":
		[
			{ "id": "5001", "type": "None","startDate":"2024-07-01" },
			{ "id": "5002", "type": "Glazed" },
			{ "id": "5005", "type": "Sugar" },
			{ "id": "5007", "type": "Powdered Sugar" },
			{ "id": "5006", "type": "Chocolate with Sprinkles" },
			{ "id": "5003", "type": "Chocolate" },
			{ "id": "5004", "type": "Maple" }
		]
}

$.topping[?(@.startDate >= “2024-07-01”)].id → This query will only return 5001. However, there is no difference computation as such to check more than 30 days or so. Json path can be helpful for date comparison against two date variables or with a static date.

Regards,
Uday Kilambi

3

In my opinion, best approach here would be to create an Identity Attribute that will change when end date is in 30 days (you can do it with dateCompare), and trigger the workflow on Identity Attribute change.

1 Like
4

Yes, That is my backup but i would like to have more attributes,

5

You could try using the schedule trigger to run a workflow every day. The workflow will start by using a search query to query all identities with an end date attribute that is 30 days out, and that is inactive. This would give you a list of identities that you can process further.

6

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