question Business rule on sys_email table in Developer forum

Business rule on sys_email table

JohnnySnow — Tue, 18 Jul 2023 10:25:45 GMT

Hi Team,

I want to use the event name in the business rule condition (created on sys_email table ). I'm not sure how to determine or rather dot walk the event name. Can some one please guide

Re: Business rule on sys_email table

Community Alums — Tue, 18 Jul 2023 10:23:43 GMT

Hi @JohnnySnow ,

Events are special records that the system uses to log when certain conditions occur and to take some kind of action in response to the conditions.

The system uses business rules to monitor for system conditions and to generate event records in the Event [sysevent] table, which is also known as the event log or event queue.

Event-generating business rules typically use this script logic:

If [some condition is true for the current record], then [add a specific event to the queue].

For example, here are some of the conditions in the incident event business rule:

If a user adds a comment to an incident record, add an incident.commented event.
If a user adds an incident record, add an incident.inserted event.
If a user updates an incident record, add an incident.updated event.

Event-generating business rules use the GlideSystem eventQueue method to insert event records, which typically contain this information:

Event fields
Field	Description
Name	Unique name of event. Baseline event names include the record affected and the triggering action, such as incident.commented.
Parm1	Event-specific parameter the system uses to pass record information to other parts of the system, such as a record Sys ID or a field value.
Parm2	Event-specific parameter the system uses to pass record information to other parts of the system, such as a record Sys ID or a field value.
Table	Table to which the event applies. This is the same table on which the business rule ran.
Instance	Sys ID of the record to which this event applies.

Scheduled jobs periodically read the event queue and forward them to the appropriate handler for processing. The handler uses information from event records to take some kind of action such as:

Run a script action
Schedule a job
Send a notification
Trigger a workflow activity
Trigger an inactivity monitor

By default, the system provides events covering a broad view of application activity. If existing events do not meet your needs, you can create your own events to watch for specific changes to records.

Re: Business rule on sys_email table

Ankur Bawiskar — Tue, 18 Jul 2023 10:56:15 GMT

@JohnnySnow

why to create BR on OOB table?

It's not recommended.

What's your use case?

Re: Business rule on sys_email table

JohnnySnow — Tue, 18 Jul 2023 19:47:06 GMT

Hi @Ankur Bawiskar I wanted to attach the pdf to the email notification, I can’t use the include attachments option as there would be other attachments on the hr case which might not be relevant. I’m sending this notification from a common subflow and that doesn’t return the sys id, hence thought of achieving through business rule. Is there other ways to achieve it?

Re: Business rule on sys_email table

sushantmalsure — Tue, 18 Jul 2023 20:54:30 GMT

The even name which you see there is nothing but email log from table (sys_email_log).

from BR on sys_email table, you can write following script to get event name:

var getEvent = new GlideRecord('sys_email_log'); getEvent.addQuery('email',current.sys_id); getEvent.query(); if(getEvent.next()){ gs.addInfoMessage('Event name is '+getEvent.event.getDisplayValue()); }

Re: Business rule on sys_email table

Ankur Bawiskar — Wed, 19 Jul 2023 05:12:02 GMT

@JohnnySnow

then you can have after insert BR on sys_email table and copy the required file you want to the email record

what script did you start with and where are you stuck?

Re: Business rule on sys_email table

Mahalakshmi Rav — Tue, 13 Jan 2026 12:17:53 GMT

Hello @Ankur Bawiskar ,

Is it not recommended to have before BR on sys_email table? we have a requirement to check the user from sys_email table and query the user table and fetch the user name then map it to user id in the sys_email. we are thinking to acheive it in before insert BR, what's your thought on this one?

Re: Business rule on sys_email table

Ankur Bawiskar — Tue, 13 Jan 2026 12:34:30 GMT

@Mahalakshmi Rav

please post a new question and share all the details there and tag me as this is an old thread

Re: Business rule on sys_email table

Prathmeshda — Tue, 13 Jan 2026 12:53:24 GMT

Hello @JohnnySnow
current.event is the reference to the Event table (sysevent).
current.event.name fetches the actual event name.

Instead of creating a BR on sys_email, use one of these:

Event Script – Triggered when a specific event fires.
Script Action – Fires when an event occurs; you can check the event name and perform actions.
if (event.name == 'incident.assigned') {}

If this response proves useful, please mark it as Accept as Solution and Helpful. Doing so benefits both the community and me. 👍🙂