---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/de-DE/employee-service-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Create a custom Emergency Outreach notification channel

# Create a custom Emergency Outreach notification channel {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

Create a custom Emergency Outreach notification channel to send
privacy consent requests using your company's preferred communication method, such as the
Slack or Microsoft Teams collaboration platforms. Create
the notification channel using a script or a subflow.

## Vorbereitungen

Role required: sn_imt_checkin.checkin_admin or admin

## Warum und wann dieser Vorgang ausgeführt wird

After you create a notification channel, you can select it when sending a notification. The channel uses the specified subject and body, and sends notifications to the users that you select when you send the privacy consent request.

For example, if your company's IT network group has a Slack channel that they monitor more closely than email, you could create a Slack notification channel. To communicate with IT network group
members, you would select the group as the target audience and select the Slack notification channel.

## Prozedur

1. Navigate to AllEmergency OutreachChannels.
2. Click New.  
3. Enter the name of your notification channel.  
   Use a short name to indicate the communication method so requesters can easily pick the correct channel.
4. In the Subject field, enter the subject of your notification channel message.
5. In the Body field, enter the body of the message.
6. Create a script for the notification channel.
   1. In the Notification type field, leave the default notification type of Script.
   2. In the Script field, replace the code in the comment with the script to connect to your channel.  

          {
                      // sendNotification(responses.privacyGr.user.email, 
          channelGr.subject, channelGr.body);
                  }

      For information about JavaScript APIs for GlideRecord, see [GlideRecord -
      Scoped](https://www.servicenow.com/docs/access?context=c_GlideRecordScopedAPI&version=australia&pubname=australia-api-reference&ft:locale=en-US).
   3. Click Submit.

   {#create-additional-channel-notif__substeps_tlr_wqp_plb}  
   The following example includes code to count the number of privacy consent
   requests generated when the notification is sent. It displays the number of
   privacy consent requests that were delivered successfully. Use this
   information to review and handle errors that appear in the Delivery Log
   related list in the Outreach record.  

       (function notify(responses, channelGr) {
       	var totalCount = responses.privacyGr.getRowCount();
           var numSent = 0;
           if (responses.mode === 'privacy_consent') {
               while (responses.privacyGr.next()) {
                   try {
                       // sendNotification(record.user.email, channelGr.subject, channelGr.body)
                       numSent += 1;
                   } catch (err) {
                       gs.error('Error occurred: ' + err.message);
                   }
               }
           }
           return {
               total_count: totalCount,
               sent_count: numSent
           };
       })(responses, channelGr);

7. Create a subflow notification channel.
   1. Create a subflow to use in the notification.  
      For information about creating, publishing, and testing subflows, see [Subflows](https://www.servicenow.com/docs/access?context=subflows&version=australia&pubname=australia-build-workflows&ft:locale=en-US).  
      Use the following inputs in the subflow that you create:
      * <var class="keyword varname">mode</var> (string)
      * <var class="keyword varname">Privacy Consent</var> (Records of sn_imt_tracing_user_privacy_consent)

        If the mode is
        <var class="keyword varname">Privacy Consent</var>, then
        acknowledgements are set to a valid GlideRecord and
        <var class="keyword varname">survey_instances</var> is
        `null`.
      * <var class="keyword varname">channel</var> (Reference of sn_imt_checkin_channels)
      {#create-additional-channel-notif__ul_zg2_2rm_rlb}  
      The following outputs are optional:
      * <var class="keyword varname">total_count</var> (integer)
      * <var class="keyword varname">sent_count</var> (integer)
      {#create-additional-channel-notif__ul_zmy_csm_rlb}

      To review these outputs, include the number of total
      privacy consent requests versus the successful privacy consent
      requests.
   2. Select the Subflow notification type.  
      The Script section changes to Flow, and the Subflow reference field appears.
   3. Select the subflow that you created.
   {#create-additional-channel-notif__substeps_qn5_ytp_plb}
8. Click Submit.
When a notification is sent using a custom notification channel, a Delivery Logs
related list appears in the Outreach message.  
Abbildung : 1. Delivery logs related list  
1. Test the notification channel for an outreach message.
2. Open any failed channel record to review the error messages and fix errors that caused the notification to fail.
3. Continue testing the notification channel until the channel no longer fails.
{#create-additional-channel-notif__ol_o5x_33d_vlb}