Does anyone know from where label.notify is being triggered?

[krishna_t]

On http://wiki.servicenow.com/index.php?title=Baseline_Email_Notifications you'll come across a notification named "Change Notification".

Name: Change Notification

Type: EMAIL

Description: Notification of a change in the fields label in a form.

Event: label.notify

Interesting enough I can't find where label.notify is being triggered. It's not a business rule, client script or script include. And the description of this isn't very detailed in what it's for.

Is this saying any time a field's label changes on any table a notification should be sent out?

And where is it being triggered??

Can any help me with this please?

[corina]

Hello Krishna.

The event is here:

https://yourinstance.service-now.com/nav_to.do?uri=sysevent_register.do?sys_id=b800a6dfc61122aa01727...

replace yourinstance with your instance name.

IT fires when there is   a change in the fields label in a form. You can choose the table in the above link.

[Michael Ritchie]

These are notifications about Tags (label and label_entry tables):

Creating and Using Tags - ServiceNow Wiki

https://docs.servicenow.com/bundle/helsinki-servicenow-platform/page/use/common-ui-elements/concept/...

Tags used to be called "labels" but that was changed several releases ago.

[Minh Huy Lam Qu]

Hello @krishna_t ,

Please follow this workaround solution, and here is the relevant information regarding that notification cannot trigger.

Root Cause:
The "Change Notification" notification is not triggered because it relies on the event "label.notify", which is an Out-Of-Box (OOB) event that was deprecated after the Eureka release. Since then, no script has been generating this event, rendering the notification inactive.

Solution Proposal:
To restore the functionality of this notification, update its configuration by:

• Changing the "Send when" field to "Record inserted or updated"
• Checking the box for "Inserted"

Additional Fix in the Future:
ServiceNow has acknowledged this as a defect and created a Problem ticket (PRB1857726) to address the issue in future releases. They plan to either remove or reevaluate the conditions for this abandoned notification.