{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":39096,"path":"platform-administration/noti-new-update-notification.md","title":"Create and update a provider notification for all users","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create and update a provider notification for all users\n\nCreate a notification in the notification provider framework to send to both sys and non-sys users.\n\n## Before you begin\n\nRole required: notifications provider admin and admin\n\n## Procedure\n\n1. Navigate to **All** > **System Notification** > **Provider** > **Notifications**.\n\n2. Select **New** to create a notification.\n\n3. On the form, fill in the fields.\n\n\n
\n\nFields\n\n\n\nDescription\n\n
\n\nName\n\n\n\nName of the notification.\n\n
\n\nApplication\n\n\n\nScope of the notification record.\n\n
\n\nCategory\n\n\n\nSelect the category to which this notification belongs. A category identifies and groups related notifications. This notification, if active and listed in the selected **Category** in the notification preferences for each user \\(Notifications tab in the System Settings window\\).\n\n
\n\nActive\n\n\n\nOption to activate the notification.\n\n
\n\nTriggered By\n\n\n\nTrigger used in the notification record.**Note:** The options in this field depend on the selected table. For example, if you select an incident table, the options are Events or Record Change.\n\n
\n\nTable\n\n\n\nThe table name on which the notification is triggered.\n\n
\n\nInserted\n\n\n\nCondition to trigger the notification.\n\n
\n\nUpdated\n\n\n\nCondition to trigger the notification.\n\n
\n\nEvent\n\n\n\nEvent that triggers the notification. For example, to send a notification after an incident is closed or resolved, you would select the **incident.inactive** event. By default, this event is logged in the system each time an incident is resolved or closed.\n\n **Note:** You can select only an event that shares the same table as the notification.\n\n This field appears when you select **Event** in the **Triggered By** field.\n\n
\n\nConditions\n\n\n\nAdditional conditions to trigger the notification.\n\n
\n\nUsers\n\n\n\nNames of the available sys users.\n\n
\n\nRecipients in fields\n\n\n\nField in the currently selected table that contains the users or groups who receive a notification.**Note:** The **Recipients in fields** field under Recipients enables you to choose both sys and non-sys users to whom you can send notifications.\n\n
\n\nIs the originating user included?\n\n\n\nOption to include the originating user to be included in the notification.\n\n
\n\nEvent Parm1 contains recipient\\(s\\)?\n\n\n\nOption to select if Parm 1 contains a list of comma-separated sys\\_ids.\n\n
\n\nEvent Parm2 contains recipient\\(s\\)?\n\n\n\nOption to select if Parm 2 contains a list of comma-separated sys\\_ids.\n\n
\n\nResolve Parm1 recipients from table\n\n\n\nTable that is used to resolve the sys\\_id of a Parm 1 recipient.**Note:** This field appears only when you select Event Parm 1.\n\n
\n\nResolve Parm2 recipients from table\n\n\n\nTable that is used to resolve the sys\\_id of a Parm 2 recipient.**Note:** This field appears only when you select Event Parm 2.\n\n
\n\nAdvanced event condition\n\n\n\nOption to select when the recipients are from more than 2 tables. These options are dynamic conditions.\n\n
\n\nAdvanced condition\n\n\n\nCreate a script to perform certain actions, like sending a notification based on the current email record, changing field values, or changing system properties. [The advanced condition](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/c_OptSpecifyingAdvancedCond.md) script must return **true** or set a global answer variable to **true** to send the notification.\n\nThe advanced condition script uses the following global variables:\n\n- **current**: Contains the current record from the table to which the notification is linked.\n- **event**: Contains the event that triggered the notification.\n**Note:** The **Advanced condition** field is evaluated in addition to other conditions that you set on the notification. Both the condition and advanced condition must evaluate to true to send the notification.\n\n
4. Select **Submit**.\n\n5. Open the recently created notification.\n\n6. Update the form using any of the available related lists.\n\n See [Create and add additional recipients](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/noti-add-additional-recipients.md) and [Create and add assignment groups](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/create-add-assignment-group.md) for more information.\n\n **Note:** All the validation messages given by different providers are retained. Warning messages of one provider isn’t overridden by warning messages of another provider.\n\n\n- **[Create and add additional recipients](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/noti-add-additional-recipients.md)** \nUpdate the notifications form by adding additional recipients from the Additional Recipients related list to send notifications to.\n- **[Create and add assignment groups](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/create-add-assignment-group.md)** \nCreate and add assignment groups where you want users that are part of a group to be the recipients of the provider notification.\n\n**Parent Topic:**[Create provider notification](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/create-provider-notification-using.md)\n\n"}}