Workflow to send email after an account Creation

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

Hello,

We are trying to create Workflows to send an email to the user when a new account is created by IdentityNow for him in a source, so that we can send him the details to access the system.

I have created for this a workflow with Provisioning Completed trigger and the following filter :
‘$[?($.accountRequests[0].source.name == “Source Name” && $.accountRequests[0].accountOperation == “Create” && $.accountRequests[0].provisioningResult == “SUCCESS” )]’

But we are never entering the workflow, I cannot understand why.
Any idea ?

Regards

2

Have you checked your JSON input from the Workflow? It’s possible that the trigger returns more than one account requests and maybe the [0]th one isn’t the Create operation on the source that you are comparing to.

If you remove this filter, are you able to execute the workflow?

3

Try this filter:

$.accountRequests[?(@.source.name == “Source Name” && @.accountOperation == “Create” && @.provisioningResult == “SUCCESS”)]

4

Yes i’ve check using documentation and also tried to run the workflow without filter. You were right there is multiple element in accountRequest.

$.accountRequests[?(@.source.name == “Source Name” && @.accountOperation == “Create” && @.provisioningResult == “SUCCESS”)]

This filter is not accepted in the trigger block.Maybe i should use the loop block to go through the accountRequests attribute ?

Regards

5

What is the error you are getting?

6

This filter works for me.

Make sure when you copy paste it, replace the quotes/white spaces.

7

Wow, it was tricky to view that the quotes were not the same.
But as of now, the workflow is not started when doing a create account.

8

I am creating a similar workflow, and it is not trigger for me either when the account is being created. I also changed fixed the formatting it still isn’t working.

Do you have a JSON file that we can use?

9

No, I don’t have one for this trigger.

Try using the documentation here to test your filter.

10

Is there a reason the filter wouldn’t work for us, but only for you?

11

I didn’t execute it, i just verified the JSON expression didn’t have any error.

12

Oh I see so you recommend finding one that works!

13

Hi Alexandre,

We did a similar workflow using the following trigger (code comes from the JSON directly) :

"trigger": {
		"type": "EVENT",
		"attributes": {
			"filter.$": "$.accountRequests[?(@.accountOperation == \"Create\" && @.provisioningResult ==\"committed\" && (@.provisioningTarget ==\"NAME OF YOUR SOURCE A\" || @.provisioningTarget ==\"NAME OF YOUR SOURCE B\" ))]",
			"id": "idn:post-provisioning"
		}
	}
14

Hello Thibault,

Thanks for your answer ! I have done a test and it works !
Huge thanks to all of you for your help.