Is there a way to combine event trigger filters with identity attribute filters to tie down the event triggers further? e.g. for an identity attribute change event trigger, can one access other attributes on the identity that may not necessarily be a part of the event trigger and use them to further fine tune event triggers?
Something along the lines of:
$.changes[?(@.attribute == "department")] && attributes.firstName == ‘John Doe’
Hi @RTASB
Event trigger filters can only filter what is in the payload. However, I can see the utility of triggers being able to filter on other identity attributes not in the payload. I’ve added this as an idea in our ideas portal. Please up vote so it gets visibility.
Hi everyone,
We have a similar desire where we’d like to be able to filter out which items are sent through the trigger and then select the attributes to be delivered.
$…[trackingNumber,requester,recipient]
$[?($.requester.id == “2c9180877b9ce230017bd0ece41c56f8”)]
The idea was to combine these filters to only have those that contain the requestor.id of 2c9180877b9ce230017bd0ece41c56f8 and then send filter the data sent with $…[trackingNumber,requester,recipient]
This would cut down on the body being sent to another platform to digest