Dictionary attributes impact Domain SupportDescription<!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> This article will discuss key dictionary attributes that impact domain support. ResolutionHere are three key attributes: 1. global_visibility: If this attribute is present or true in the dictionary collection record of any table, makes this table visible globally even if there are domain restrictions (that is, the sys_domain field has a value). This attribute can be added to the table collection record that has sys_domain field. OOB this attribute is not present for any table, adding it to any table will be customization. All you need to do is add attribute global_visibility=true to the collection record of the table you want to restrict from domain separation. 2. no_separation: If this attribute is present or true, marks the table as not participating in domain separation. This attribute needs to be added to the collection record on any table and when domain separation will enable this will never be separated/domain aware. 3. domain_main: This attribute is to derive the domain from the parent table. domain_main needs to be added to the child table to derive the domain from its parent table. The domain_main attribute ensures that the domain between a child and parent record remains the same as the domain for the child is derived from the specified reference field. Here is an example of a table that uses domain_main: Workflow tables use domain_main attribute, see screenshot: a. As you can see collection record of wf_activity has attribute domain_main=workflow_version. This means it is pointing to a reference field 'workflow_version' which is referencing to 'Workflow Version' table. b. If you look in the workflow version table this table doesn't have the sys_domain field as well. Now let's see from where the workflow version is getting its domain separation. In the screenshot above wf_workflow_version (Workflow Version) table also has domain_main attribute domain_main=workflow. This is again pointing to the workflow reference field which is referencing to Workflow table that has sys_domain field So sys_domain is derived from wf_workflow table to wf_activity and wf_workflow_activity.