Aggregation Complete Workflow Trigger Help

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

Hello all, First time using the Account Aggregation Completed trigger and need a little help on any sample of what should go into the filter bob so that only fires off when xyz app runs and is Successful. I tried look at the even triggers but its not the right format nor is the query so i am just really stumped at this part.

I have seen all the others but for this one in documents or help. :frowning:

image
image758×489 19.2 KB

2

Based on the documentation this is the json response for this trigger

{
    "source":{
        "id":"4e4d982afddff4267ab12f0f1e72b5e6d",
        "name":"Corporate Active Directory",
        "type":"SOURCE"
    },
    "status":"Success",
    "started":"2020-06-29T22:01:50.474Z",
    "completed":"2020-06-29T22:02:04.090Z",
    "errors":[

    ],
    "warnings":[
        "Account skipped"
    ],
    "stats":{
        "scanned":200,
        "unchanged":190,
        "changed":6,
        "added":4,
        "removed":3
    }
}

Hence, you can apply filter $.source.id == 'SOURCE_ID' AND $.status == 'Success' for the workflow to execute based on your conditions.

Hope this is what you were looking for

3

Thanks, and i did try what you have in a different filter with the same result as i just did with your input. however, I am still getting not a valid expression. That is why I like to pull my hair out today.

I have also tried “$.Trigger.status.Success” which took but did not fire off when i ran the agg

image

1 Like
4

Looks like i got it to work using the $.Trigger.status.Success in the test run. Now i have to get it to just fire off on the one application when it runs.

2 Likes
5

The test workflow feature does not apply any trigger filters. No matter what you put into your trigger filter, the test workflow feature will always launch the test. The only way to test a trigger filter is to use a JSONpath editor, as described here and fire off test events in the ETS dashboard, as described here.

As for why you are not getting a valid JSONpath expression, try this.

$[?($.source.id == "4e4d982afddff4267ab12f0f1e72b5e6d" && $.status == "Success")]

6

Thanks Colin i will give it a try. Still trying to work on all the new things with how to use workflows from IIQ an very much appreciative.

1 Like
7

Hi Andy,
The documentation are not upto date with the sample trigger they have shown. The best way to see what JSON exactly that trigger with throw is to setup a dummy workflow in your environment with that trigger and End with success. So, there will be two block, one empty trigger and another success step. Enable that workflow and see in workflow execution , what JSON it throws in account aggregation completion.

After that you can use filter condition based upon the Json you have received which @colin_mckibben have mentioned in his answer.

Hope that helps.

1 Like
8

Hi Kapil,

Are you seeing a different payload from Account Aggregation Completed than what is documented here?

I just tested an aggregation and I got the same schema.

1 Like
9

Hi @colin_mckibben , I haven’t checked for this trigger. But for, Source Account Created trigger, I was seeing a different JSON than what it was in the documentation. Also, the source name has [source] attached at the end in the name of the source in that trigger.

So, I always create a dummy workflow to fetch JSON for the trigger that I use, and then proceed with creating filter rather than using sample JSON provided in the documentation.

1 Like
10

That’s fair enough. There is no substitute for real data when building filters. However, would you be willing to submit a bug to Bugs for the source account created trigger? We want to make sure our samples are as accurate as possible.

1 Like
11

Sure I will do that.

1 Like
12

Thanks everyone. Just so everyone is aware and if they have done this, please feel free to help as i think this will be a great help for others once completed and working.

Need to push Manager data from a source that is updated weekly in IDN to NERM so that the drop-down options are always up to date for Requesters.

I will give this logic a try and let everyone know as well. Cheers,

13

Yes, specifically that the “Terminated” status doesn’t seem to exist in the real world

Here are my reproduction steps that show aggregations ending in a “Warning” are showing a status of “Success” even though the documentation says it should end in “Terminated”: