- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2025 02:04 PM
When looking at an Event Rule, specifically in the "Transform and Compose Alert Output" tab, how do you control the options that show up in the main section of this table? Not the Event Input/Raw Event Input sections, but the main area you define how to compose the Alert?
We've added a few custom fields to the em_alert table and it seems like they automatically show up in this view, and we'd like to be able to control if they're visible.
Thanks,
Travis
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2025 07:19 AM - last edited a month ago
Fields are controlled in table 'em_event_rule_black_list'
If you want a specific field to show in event rule, go to table 'em_event_rule_black_list.LIST' from application navigator and open the field and select 'show in rule'. To hide a field from transform and compose section, uncheck 'show in rule' and save the record
If this helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2025 11:46 PM
Did you get a chance to review this ?
If my response helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Fantastic! Thank you for this information. One minor note for anyone looking to use this is that the table can be viewed with `em_event_rule_black_list.LIST` (the solution contains a slight typo) -- not sure if that can be edited.
Thank you again though. I tested this and it worked.
Regards,
Travis Linville
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Thanks for accepting the solution and highlighting the typo. I updated the original post 🙂
Thanks,
Bhuvan