Hi All,
Can you please suggest how we can send email notifications to application owners when any new entitlements are created?
I tried exploring the native change detection for creating entitlements in the application details tab and configured the native change detection lifecycle event. However, after running the aggregation and refreshing the identity task, I am unable to see an email being sent to the owner.
Hello @puppamReddy !
Welcome back to the community 
[ISC]
Native Change Detection doesn’t work in this case . It is triggered when an existing entitlement attribute changes from application end. The scenario here is a NEW entitlement.
And we don’t have enough help with available triggers which can give new entitlement signal .
We can configure a scheduled trigger [5 minutes ] workflow which checks for latest created entitlements [using search query]
created:[now-5m TO now] AND sourceSchemaObjectType:*
But this is not a ideal way !
Thank you
Thank you for your reply.
I feel that calling workflow every 5 minutes is very expensive. For example, if 30 entitlements are created from one application, our workflow will send 30 emails to the application owner, which is not ideal.
I am considering writing a task that runs a rule to pick the entitlements created today-1 day, prepare a list, and send it to the owner, or alternatively, add all newly created entitlements to a CSV file.
How does this solution sound?
As far as I see it’s actualy IIQ not ISC 
@puppamReddy
You have 2 options - either customization rule and then once new entitlement is aggregated send the notification, second option - groupRefresh rule, you can do the same but you have to store somwhere information that you’ve sent notification already otherwise you will send it with every aggregation.
yea you are right I didn’t noticed that 
Thank you, Kamil.
This solution is applicable to all applications, including delimited connectors. If we write a customization rule, it will cause performance issues because every time we need to check whether we have sent an email or not, and store this information somewhere in an audit event or custom object.
The groupRefresh rule is only available for a few applications that have group aggregation rules.
The best would be write the rule runner task and query the entitlements based off the creation date , collect all details and put them in csv or in email body and send them to designated people. For create date filter you can check the when last task was started and add filter based on date time so that you send only unique ones which were created after the task executed on next day etc …
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.