Network diagram management tasks

Network diagram configuration and management tasks are dependent on many factors, including the type of workspace connection and its permission level, the diagram type, the capabilities enabled on the diagram templates, and the connected database or portal account.

The following sections provide an overview of the dependencies that exist when working with a utility network or trace network.

Network diagram workflow tasks

The following tables summarize types of actions with the following details:

  • Action—The tool or type of action being performed.
  • Workspace—Specifies the required data source.
    • Service—The action must be performed against a feature layer from a utility network service.
    • Database connection—The action must be performed using a database connection to a utility network with an enterprise geodatabase. In this case, always ensure the workspace is set to branch for the versioning type.
    • File geodatabase—The action must be performed using a utility network or trace network with a file geodatabase.
    • Mobile geodatabase—The action must be performed using a utility network or trace network with a mobile geodatabase.
  • Diagram type—The type of diagram supported by the operation.
    • Temporary—The diagram is temporary.
    • Stored—The diagram is stored.
    • System—The diagram is a subnetwork system diagram.
  • Portal connection—Specifies the portal account that must be connected when performing the operation:
    • Any user—Any user who has a suitable access rights level on the diagram can perform the operation.
    • Diagram owner—The operation must be performed by the diagram owner.
    • Network owner—The operation must be performed by the network owner.
    Note:

    When running operations using a file or mobile geodatabase, the network diagram workflow tasks below can be run without being connected to a portal. However, there are differences for the following tools:

    • Store Diagram—When this tool runs without being connected, a user can only store diagrams as public diagrams. When the tool is run while connected, a user can also store diagrams as protected, or private diagrams. and prevent other connected users that work on the same database from editing or accessing them.
    • Alter Diagram Properties—When this tool runs without being connected, any user can access all public and protected diagrams that exist in the dataset—even those the user doesn't own—but can't alter the access rights level currently set for any of these diagrams. When connected, users can access all public and protected diagrams in the dataset, plus their private diagrams. In this case, users can alter the access rights level set for their own diagrams.

  • Diagram template restriction—Specifies whether the action can be locked at the diagram template level.

Usual editing operations on network diagrams

ActionWorkspaceDiagram typePortal connectionDiagram template restriction

Create Diagram

Service | Database connection | File | Mobile geodatabase

Temporary

Any user

No

Set root, end, pivot, barrier flags on diagrams

Service | File | Mobile geodatabase

Temporary | Stored | System

Any user

No

Apply any layout to diagrams

Service | File | Mobile geodatabase

Temporary | Stored | System

Any user

No

White space editing on diagrams

Service | File | Mobile geodatabase

Temporary | Stored | System

Any user

No

Store Diagram

Service | File | Mobile geodatabase

Temporary

Any user

Yes

Extend diagrams using the ribbon command

Service | File | Mobile geodatabase

Temporary

Any user

Yes

Extend Diagram

Service | File | Mobile geodatabase

Temporary | Stored

Any user

Yes

Overwrite diagrams using the ribbon command

Service | File | Mobile geodatabase

Temporary

Any user

No

Overwrite Diagram

Service | File | Mobile geodatabase

Temporary | Stored

Any user

No

Append To Diagram

Service | File | Mobile geodatabase

Temporary | Stored

Any user

Yes

Update Diagram

Service | File | Mobile geodatabase

Temporary | Stored

Any user

No

Alter Diagram Properties

Service | File | Mobile geodatabase

Stored

Diagram owner | Network owner

No

Delete Diagram

Service | File | Mobile geodatabase

Stored

Any user

No

Common nonediting operations on network diagrams

ActionWorkspaceDiagram typePortal connectionDiagram template restriction

Propagate selection between diagram and GIS maps

Service | Database connection | File | Mobile geodatabase

Temporary | Stored | System

Any user

No

Search for diagrams

Service | Database connection | File | Mobile geodatabase

Stored | System

Any user

No

Open stored diagrams

Service | Database connection | File | Mobile geodatabase

Stored | System

Any user

No

Check open diagram consistencies

Service | Database connection

Temporary | Stored | System

Any user

No

Export Diagram Content

Service | Database connection

Temporary | Stored | System

Any user

No

Work using dynamic diagram mode

Service | File | Mobile geodatabase

Temporary

Any user

No

Maintenance tasks on network diagrams

ActionWorkspaceDiagram typePortal connectionTemplate restriction

Delete subnetwork system diagram

Service

System

Network owner

NA

Change Diagrams Owner

Database connection | File | Mobile geodatabase

Stored | System

Network owner

NA

Purge Temporary Diagrams

Database connection | File | Mobile geodatabase

Temporary

Network owner

NA

Network diagram configuration tasks

The following tables summarize types of actions with the following details:

  • Action—The tool or type of action being performed.
  • Workspace—Specifies the required data source.
    • Service—The action must be performed using a feature layer from a utility network service.
    • Database connection—The action must be performed using a database connection to a utility network with an enterprise geodatabase. In this case, always ensure the workspace is set to branch for the versioning type.
    • File geodatabase—The action must be performed using a utility network or a trace network with a file geodatabase.
    • Mobile geodatabase—The action must be performed using a utility network or a trace network with a mobile geodatabase.
  • Portal connection—Specifies the portal account that must be connected when performing the operation:
    • Any user—Any user with the appropriate rights on the diagram or network dataset can perform the operation.
    • Diagram owner—The operation must be performed by the diagram owner.
    • Network owner—The operation must be performed by the network owner.
    Note:

    When running operations using a file or mobile geodatabase, all network diagram configuration tasks can be run without being connected to a portal.

Diagram template management tasks

ActionWorkspacePortal connection

Add Diagram Template

Database connection | File | Mobile geodatabase

Network owner

Alter Diagram Template

Database connection | File | Mobile geodatabase

Network owner

Add any diagram rule to a diagram template

Database connection | File | Mobile geodatabase

Network owner

Add any diagram layout to a diagram template

Database connection | File | Mobile geodatabase

Network owner

Delete Diagram Template

Database connection | File | Mobile geodatabase

Network owner

Create Diagram Layer Definition

Database connection | File | Mobile geodatabase

Network owner

Export Diagram Layer Definition

Database connection | File | Mobile geodatabase

Any user

Export Diagram Template Definitions

Database connection | File | Mobile geodatabase

Any user

Import Diagram Template Definitions

Database connection | File | Mobile geodatabase

Network owner