What is Event Parm 1 and Event Parm 2 in Email Notification?

[nayaexam]

In Email notification, advance field event parm 1 and event parm 2 are there, what are uses of these two, can any one explain me.

[Marshall Day]

xiaix,

Typically, each Event is used to fire a Business Rule that will include the information you are trying to attach.

For example, here is an event: 

gs.eventQueue("knowledge.approval.inserted", current, grKB.owner_group, current.approver);

The first part is the event name that would be seen in the notification "When to Send" tab.

The second part relates to the current record that is associated to the event.

The third part, parm1, relates to the specific group or list or user that you want to send the email to.

The forth part, parm2, relates to the specific group or list or user that you want to send the email to. 

Parm1 & parm2 are there to provide you options on whom to send the email.

As such, your Business Rule would specifically call out the email list in your case as a variable in the script. Here you can see the way the grKB.owner_group is called out:

var grKB = new GlideRecord("kb_knowledge");
grKB.get("sys_id", current.document_id.toString());

So within your Business Rule script you would identify the email list that you want to send to in parm1 or parm2.

I hope this helps.

Regards,

Marshall

[sbh]

They need to be email.toString() - they can be pushed to the array/list that way.

[Nithin12]

Can you check the field by going to configure - - form layout - - check the field.

Just give a try

[Swarup Patra]

Event Parm 1 and Event Parm 2 are parameters that can be used in ServiceNow Email Notifications to pass additional information from an event to the notification. Here's how they work: - When an event is triggered in ServiceNow, you can pass additional information to the event using the parm1 and parm2 fields. This information can be anything that is relevant to the event, such as a user ID, a record number, or a specific message. - In the Email Notification, you can then use these parameters to include the additional information in the email. You can do this by using the syntax ${event.parm1} and ${event.parm2} in the message body or subject line of the email. Here's an example: 1. An event is triggered when a new incident is created. The incident number is passed to the event as parm1. 2. In the Email Notification, you include the text "A new incident has been created: ${event.parm1}" in the message body. 3. When the email is sent, ${event.parm1} is replaced with the incident number, so the recipient sees the message "A new incident has been created: INC0012345". Remember: - You can only use parm1 and parm2 in Email Notifications if they have been passed to the event when it was triggered. - The values of parm1 and parm2 are not stored in the event log, so they can only be used in the context of the triggered event. - You can use scripting to determine the values of parm1 and parm2 when the event is triggered. nowKB.com

[Swarup Patra]

Event Parm 1 and Event Parm 2 are parameters that can be used in ServiceNow Email Notifications to pass additional information from an event to the notification. Here's how they work: - Event Parm 1 and Event Parm 2 are fields in the Event [sysevent] table in ServiceNow. - When an event is fired, you can optionally pass values to these fields. - These values can then be used in the Email Notification that is triggered by the event. - You can use these parameters in the message body or subject line of the Email Notification by using the syntax ${event.parm1} and ${event.parm2}. For example, if you have an event that is triggered when a new incident is created, you could pass the incident number and the incident description as Event Parm 1 and Event Parm 2. Then in your Email Notification, you could include a message like "Incident ${event.parm1} was created with the following description: ${event.parm2}". Here are the steps to implement this: 1. Create an event in the System Policy > Events > Registry module. Let's call it "incident.created". 2. In your script or business rule that triggers the event, pass the incident number and description as parameters. For example: gs.eventQueue("incident.created", current, current.number, current.description); 3. Create an Email Notification in the System Policy > Email > Notifications module. 4. In the "When to send" section, select "When an event is fired" and choose the "incident.created" event. 5. In the "What to send" section, enter a message like "Incident ${event.parm1} was created with the following description: ${event.parm2}". 6. Save the Email Notification. Now, whenever a new incident is created, an email will be sent with the incident number and description. nowKB.com