Domain Restricted Visibility

In Capital applications, to ensure that you only see the content that you have domain access to, inaccessible designs are filtered out from view. If domain-restricted designs are included in objects, like build lists or ECOs, you will not be able to edit or view the content within these objects, or perform any additional actions on them. This ensures that each individual user can only access and view designs or objects that are relevant to their role.

Note

Some features and custom functionality, such as design searches, show / report usage on shared objects, or find and replace, requires access to all designs in a given scope to return correct results. Due to domain restrictions, if a function does not have access to all such designs, incorrect or limited results could be returned.

In exceptional cases where it is necessary to provide limited access to domain-restricted build lists and ECOs, access can be enabled. See the "Limited Editing of Inaccessible Build Lists and ECOs" subsection below for details.

Design Tree and

Dialog Box Filtering

Inaccessible designs are filtered from the design browser tree. In the case of harness designs, if either the composite or derivative has an inaccessible design, both the composite and derivative are filtered from the tree.

Figure 3: Filtering of Designs in a Design Browser Based on Domain Access

In the example shown in Figure 3:

• User A will see only Design 1 which has the domain ‘ITAR’ set, Design 2 will be hidden for this user.

• User B will see only Design 2 which has the domain ‘Civil’ set, Design 1 will be hidden for this user.

Any action that invokes the design revision selection dialog box also has inaccessible designs filtered from the available designs list.

Figure 4: Filtering of Designs for Design Revision Selection Based on Domain Access

In the example shown in Figure 4, User A will see only Design 1 which has the domain ‘ITAR’ set available for selection in the design revision tree. Design 2, which is in domain ‘Civil’, is hidden for this user.

Note

When a project is open, if a design within it is made domain accessible to you from a separate session, the project must be closed and reopened for the domain access change to take effect.

Object Restrictions

If domain-restricted designs are included in objects like build lists or ECOs, you will not be able to edit or view the content within these objects, or perform any additional actions on them. Some actions like ‘Copy latest’ will be available on the Build List if you have access to all the latest design revisions within the Build List.

Figure 5: Handling of Objects that Contain Domain-Restricted Inaccessible Designs

In the example shown in Figure 5, access to build list objects is restricted as it contains inaccessible designs. You cannot perform any actions on restricted objects that may reveal design details (for example, edit, open, copy).

Limited Editing of Inaccessible Build Lists and

				ECOs

By default, if domain-restricted designs are included in build lists or ECOs, you will not be able to edit or view the content within these objects, or perform any additional actions on them. This ensures that each individual user can only access and view designs or objects that are relevant to their role.

However, there are certain exceptional cases in which you may deem it necessary to provide limited access to domain-restricted build lists and ECOs, to align with specific process flow requirements for example. In such cases, system preferences allow limited editing access to inaccessible build lists and/or ECOs. See the "Allow limited access to data that contain inaccessible designs" preference in System Preferences for Project in the Capital Project Manager User Guide.

With the preferences enabled you can:

• Add or remove accessible designs from build lists and ECOs.

• Assign ECOs to a build list, if the ECOs contains only accessible designs. If the ECO contains non accessible designs, then assignment is not allowed.

• Set a build list to active (thereby enabling plugins to run based on the active build list status).

• Export ECOs, however, only accessible design content will be included in the exported data.

• Set the ECO design status on accessible designs.

Note

After enabling the "Allow limited access to data that contain inaccessible designs" preference, if you have an Edit Build List dialog box open, you should refresh the design revisions displayed to ensure the latest revisions are now shown.

Note

If you export inaccessible ECOs and build lists, the export will only contain data related to accessible designs, and you can only change the ECO design status for accessible designs only.

When you invoke the edit action, build lists and ECOs have inaccessible designs anonymized, and a message is displayed on the dialog box to warn you of the limited access.

Figure 6: Example Build List and ECO Dialog Boxes With Access Restrictions

You can add or remove accessible designs in these dialog boxes, but only accessible ECOs can be associated to the build list, all other actions remain disabled.

Plugins and Web Services Handling

Plugins and web services can only return or access domain-enabled sets of designs.

For example, a plugin that uses API objects IXBuildlist and IXEngineeringChangeOrder to retrieve designs, will return an exception if the accessed build list or ECO contains inaccessible designs due to domain restrictions. This is the default behavior. This behavior can be overridden, see “System Preferences for API” in the Capital Project Manager User Guide.

With web services and FEM tasks, if a design belongs to a domain which is not assigned to you, a fault is returned.

For example, with an ECO exporter service or build list exporter service, only an ECO and build list which contains accessible designs will be exported. If any of the ECO or Build List contains inaccessible designs they will not be exported.

Parent Topic:

Domains

Capital Access Manager User Guide, 2512.2606

Unpublished work. © 2026 Siemens