Domain separation support

For more detail on the support levels, see Application support for domain separation.

How domain separation works in Safe Workplace applications

Admins must install the Domain separation pluginbefore working with these application tables. Most of those tables contain a sys_domain field so they are able to be domain-separated if they have data that needs to be partitioned by domain.

• Core domain table: Included in the Safe Workplace plugin is an sn_imt_core_domain table. Domains in this table are iterated when scheduled jobs run.
• Property table: The sn_imt_core_property table extends the sys_properties table and adds a sys_domain field. Adding that field allows sys_properties values to be overridden for a domain.

The following tables do not have the sys_domain field:

• app-imt-checkin

  • sn_imt_checkin_outreach_sysauto_script (extends sysauto_script)
  • sn_imt_checkin_response_criteria
  • sn_imt_checkin_response_option_for_health
  • sn_imt_checkin_response_option_survey
  • sn_imt_checkin_response_script
• app-imt-diagnosis: task_compliance_result
• app-imt-tracing

  • sn_imt_tracing_wifi_access_register_job
  • sn_imt_tracing_wifi_access_register_stage
• app-imt-core: sn_imt_core_sysauto_script (extends sysauto_script)

Scheduled jobs in applications with this level of domain separation run separately for each domain in the table. Scheduled jobs use the core table as the domain source table, and the Domain Iterator check box is automatically enabled by default when domain separation is installed. When the Domain Iterator option is enabled, the job can run in multiple domains.

The Domain Source Table value is also set to Safe Workplace Domains by default. If you don't see the tables, verify that the Domain Iterator and Safe Workplace Domains settings are selected, and refresh the instance.

Parent-child domains

Combination parent-child domains are not supported in these applications. You could add a parent domain but not its child, or a child domain but not its parent. This restriction helps avoid processing any data more than once. When a job runs in the context of a domain, only the data in that domain is visible. Therefore, with a child domain, only the child domain’s data is visible. However, with a parent domain, all of its data as well as the data of its child domains is visible. If you were to schedule a script execution for a parent and a child of that parent, the script would process the child domain twice.

Domains that also contain a sub-domain or “child” domain are not supported in these applications. Running a job in a parent domain that has a child would mean running the job twice and thus processing the data more than once. You could add a parent domain or add just the child domain but not both.

Working with domain-separated properties in the Safe Workplace Suite

When the Domain separation plugin is installed and you navigate to the Properties page in any of the four Safe Workplace domain-separated applications, their properties do not display by default. You must override properties for a domain before they appear in the list.

To display the properties, click New on the Properties page. In the form that creates a new domain-separated property, search in the reference field for the property you would like to override. Enter a specific prefix to narrow your search:

• sn_imt_core for Employee Readiness Core
• sn_imt_diagnosis for Emergency Exposure Management
• sn_imt_health_testing for Health and Safety Testing
• sn_imt_tracing for Contact Tracing

The properties display with a full description of the overrides.

After you create your domain-separated property override, the form displays the domain-separated properties.

You can navigate back to the record form by selecting a property name in the list.

Property functions

Learn more about how these properties function in the following topics:

• Health and Safety Testing properties
• Contact Tracing properties
• System properties for tracing systems in Emergency Exposure Management
• Employee Health and Safety Status properties