Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • IT Service Management
Table of Contents
Choose your release version
    Home Madrid IT Service Management IT Service Management Walk-up Experience Domain separation and the Walk-up Experience application

    Domain separation and the Walk-up Experience application

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Domain separation and the Walk-up Experience application

    This is an overview of domain separation as it pertains to the Walk-up Experience application and how it relates to Service Portal pages, interaction queues, and configurations. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

    Overview

    Support: Level 1

    Domain separation is supported in this application. Not all ServiceNow applications support domain separation; some include limitations on the data and administrative settings that can be domain separated. To learn more, see Application support for domain separation.

    Domain separation in the Walk-up Experience application is supported at Level 3. However, the application depends on the Service Portal, which is supported at the Data-only level. Domain separation pertains to the Walk-up Experience application in the following ways:

    • Walk-up location queues support domain separation in order to define which end users can access each location queue.
    • The Interaction table supports standard domain separation for data security. Interaction tickets are opened for a specific domain.
    • Walk-up location queues and interactions support domain separation. Therefore, fulfillers also work within a domain-separated environment when addressing interaction tickets associated with a location queue.
    • Management and administration configurations reside in the walk-up location queue records. Therefore, those configurations are available to the respective domain managers and admins.
    • While the Service Portal pages are not domain separated, the Walk-up Experience application's portal pages retrieve data within the user’s specific domain. Therefore, those pages can be reused across different service portals designed and configured for separate domains. The admins must build each portal themselves.
    • The Domain field is available on the wu_location_queue table. Setting domain here ensures users only see queues that are part of their domains during online check-in.
    • For Advanced Work Assignment routing to operate, each wu_location_queue must include a work item routing condition which explicitly adds a reference to the domain the queue is part of.
      Note: The appointment booking feature is not domain separated. Since Appointment [itil_appointment] table data is not domain separated, list views could reveal data across domains.

    How domain separation works in the Walk-up Experience application

    For this application to be the most effective, walk-up administrators should configure walk-up locations accordingly. This is done by configuring the wu_location_queue record to meet user needs, which affects the Requestor experience. Each domain configured to the location queue record has its own set of rules. The same applies to other tables within the Walk-up application as well.
    Note: Elements of the Service Portal platform such as settings, portals and widgets cannot be domain separated. However, the data within the widgets displays based on how the domain is configured. The recommended approach is to set up separate portals for each MSP customer.
    Below are the elements of the Service Portal that are used as part of the walk-up experience:
    • Portal (Walk-up)
    • Pages (walkup_online_checkin, walkup_queue_on_site, walkup_home, walkup_survey, walkup_check_in)
    • Theme (Walk-up theme)
    • Widgets (Online check-in experience, walk-up queue on site, walk-up check-in, walk-up exit survey, walk-up home, walk-up schedule)

    To learn more, see Domain separation in Service Portal.

    For data separation, the Walk-up Experience application uses the domain of the walk-up user (Requestor/Walkup login user) to determine in which domain the Requestor data should be placed.

    • Requestors can check in only in locations for which they have visibility.
    • Requestors are able to select the Reasons that belong only to their own domain.
    • Interaction records are created in the Requestor’s domain.

    For the Fulfiller side, the application uses the domain of the walk-up user (walk-up technician/ manager/ admin) to determine which records are visible.

    • By domain separation rules, Fulfillers can work only on interactions that are visible to them.
    • Fulfillers are able to configure only walk-up location records that belong to their domain, are in the global domain, or have the parent-child hierarchy.
    • The same visibility rules apply for the Many to Many [wu_m2m_location_queue_reason]table that controls the mapping between a location and Reason.
    • The walk-up contexts records also have domain separation support, thereby ensuring technicians are able to view detailed Requestor information only for the records that are visible by domain separation rules.

    Domain-separated tables

    As part of the Walk-up Experience, records in the following tables can be domain separated.

    • Walk-up location queues [wu_location_queue]
    • Walk-up reasons for visit [wu_reason]
    • Walk-up reasons [wu_m2m_location_queue_reason]
    • Walk-up contexts [wu_context]
    • Interactions [interaction]
    Related topics
    • Domain separation

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Domain separation and the Walk-up Experience application

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Domain separation and the Walk-up Experience application

      This is an overview of domain separation as it pertains to the Walk-up Experience application and how it relates to Service Portal pages, interaction queues, and configurations. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can then control several aspects of this separation, including which users can see and access data.

      Overview

      Support: Level 1

      Domain separation is supported in this application. Not all ServiceNow applications support domain separation; some include limitations on the data and administrative settings that can be domain separated. To learn more, see Application support for domain separation.

      Domain separation in the Walk-up Experience application is supported at Level 3. However, the application depends on the Service Portal, which is supported at the Data-only level. Domain separation pertains to the Walk-up Experience application in the following ways:

      • Walk-up location queues support domain separation in order to define which end users can access each location queue.
      • The Interaction table supports standard domain separation for data security. Interaction tickets are opened for a specific domain.
      • Walk-up location queues and interactions support domain separation. Therefore, fulfillers also work within a domain-separated environment when addressing interaction tickets associated with a location queue.
      • Management and administration configurations reside in the walk-up location queue records. Therefore, those configurations are available to the respective domain managers and admins.
      • While the Service Portal pages are not domain separated, the Walk-up Experience application's portal pages retrieve data within the user’s specific domain. Therefore, those pages can be reused across different service portals designed and configured for separate domains. The admins must build each portal themselves.
      • The Domain field is available on the wu_location_queue table. Setting domain here ensures users only see queues that are part of their domains during online check-in.
      • For Advanced Work Assignment routing to operate, each wu_location_queue must include a work item routing condition which explicitly adds a reference to the domain the queue is part of.
        Note: The appointment booking feature is not domain separated. Since Appointment [itil_appointment] table data is not domain separated, list views could reveal data across domains.

      How domain separation works in the Walk-up Experience application

      For this application to be the most effective, walk-up administrators should configure walk-up locations accordingly. This is done by configuring the wu_location_queue record to meet user needs, which affects the Requestor experience. Each domain configured to the location queue record has its own set of rules. The same applies to other tables within the Walk-up application as well.
      Note: Elements of the Service Portal platform such as settings, portals and widgets cannot be domain separated. However, the data within the widgets displays based on how the domain is configured. The recommended approach is to set up separate portals for each MSP customer.
      Below are the elements of the Service Portal that are used as part of the walk-up experience:
      • Portal (Walk-up)
      • Pages (walkup_online_checkin, walkup_queue_on_site, walkup_home, walkup_survey, walkup_check_in)
      • Theme (Walk-up theme)
      • Widgets (Online check-in experience, walk-up queue on site, walk-up check-in, walk-up exit survey, walk-up home, walk-up schedule)

      To learn more, see Domain separation in Service Portal.

      For data separation, the Walk-up Experience application uses the domain of the walk-up user (Requestor/Walkup login user) to determine in which domain the Requestor data should be placed.

      • Requestors can check in only in locations for which they have visibility.
      • Requestors are able to select the Reasons that belong only to their own domain.
      • Interaction records are created in the Requestor’s domain.

      For the Fulfiller side, the application uses the domain of the walk-up user (walk-up technician/ manager/ admin) to determine which records are visible.

      • By domain separation rules, Fulfillers can work only on interactions that are visible to them.
      • Fulfillers are able to configure only walk-up location records that belong to their domain, are in the global domain, or have the parent-child hierarchy.
      • The same visibility rules apply for the Many to Many [wu_m2m_location_queue_reason]table that controls the mapping between a location and Reason.
      • The walk-up contexts records also have domain separation support, thereby ensuring technicians are able to view detailed Requestor information only for the records that are visible by domain separation rules.

      Domain-separated tables

      As part of the Walk-up Experience, records in the following tables can be domain separated.

      • Walk-up location queues [wu_location_queue]
      • Walk-up reasons for visit [wu_reason]
      • Walk-up reasons [wu_m2m_location_queue_reason]
      • Walk-up contexts [wu_context]
      • Interactions [interaction]
      Related topics
      • Domain separation

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login