Structure Manager


Every organization has different data needs. Structure Manager enables an organization to easily configure its Cartegraph database structure in ways that improve data integrity and boost workforce efficiency.  To make changes, the system status must be Locked for Maintenance.


  • A field is the smallest bit of information in your database. It contains one piece of information in a record. For example, Entry Date, ID, Cost, or Street.
  • Add fields to your database to track information unique to your organization. Update properties of existing fields to match your data needs.
  • Fields are added using Structure Manager.
  • There are rules which prevent a field from being removed from the database.
    • Fields marked with the System property cannot be deleted from the database.
    • A field cannot be removed if it is the target of a lookup. The lookup field need to be removed before the field can be removed. For example, the City field in the Cities library is referenced from many asset recordsets. You cannot delete the City field in the Cities library unless all lookup references are removed first.
    • A field cannot be removed if it is a lookup field associated to a relationship between recordsets. The relationship needs to be removed before the lookup field can be removed. For example, Facility Lighting has a Facility field which references the Facilities recordset. This lookup field is used to share Facility Lighting under Facilities.  A relationship exists between Facilities and Facilities lighting. Before the Facility field on the Facility Lighting could be deleted, the shared recordset of Facility Lighting under Facilities would need to be removed first.

Field Size

You can select the size of the field for some field types. Possible values are Small, Medium, and Large.  Below is a list of the field types and their available sizes. Fields are added using Structure Manager.

The following fields can be sized as Small, Medium, or Large. The default value is Medium.

Field size is determined when the field is added to the database but it can be adjusted for these field types.

  • Currency
  • Integer
  • Number
  • Quantity (applies to the amount part of the field)
  • Text (unless field is marked as Unlimited Text)

Field size is automatically determined for the following field types:

  • Attachment
  • Date
  • Date and Time
  • Lookup
  • Time
  • Check box
  • Text (when field is marked as Unlimited Text)

Field Validation Rules

Fields, whether stored in a recordset or a library, may be validated when information is entered. Validation means that the contents of the field are checked to ensure that they follow the rules defined by the Administrator. Validation rules help ensure that data is entered consistently.

Fields are added using Structure Manager. Field validation rules can be added to any existing field. If the rule is directed at the field you are adding, the field needs to be added before that rule can be established.

For example, you are adding a number field called Count and the numeric value cannot be greater than 10. The rule would be: ([Count] >10). Because the Count field name is part of the rule, the field needs to exist before the rule is added.

If a validation rule is entered then validation text is required.

Filter Syntax View

  • Create filters by writing instead of selecting from an interface.
  • Basic SQL (Structured Query Language) syntax knowledge is required to create an advanced filter.
  • Prompts are not allowed in Syntax view. If you have a prompt in your Advanced filter, the Syntax view button is disabled.
  • Once you place an advanced filter in Syntax view, you might only be able to view it in Syntax view.
  • Click on the Advanced Filter dialog box to open the Syntax view.


Libraries are database tables used to store information that is used repeatedly. This information is typically used by more than one recordset. Libraries are useful tools for ensuring data integrity.

Libraries are used in fields with a list for selecting data.

  • Create a library in Structure Manager.
  • Manage library values using the Library Manager in Cartegraph. Library field properties are the same as other field properties and are changed in the same way.
  • Libraries are available on lookup fields.
  • Some libraries may include start up data.
  • Populate any library with data that matches your organization.
  • Some libraries contain child data. Data for the parent library displays with the child data.

Library Manager


The Library Manager is used to add, edit, or delete records in existing libraries. All libraries in your database display in the left panel. Narrow down the libraries using the Filter lists to a specific area of Cartegraph. You can also find libraries using the Find a Library search field.

When a library is selected, the current records for the library are displayed. In the list view, you may select a record to edit or delete, or click Create to add new records to the selected library. If a library is set as read-only, you are not able to add to the library or edit or delete any library entries. The library list view can be filtered by using the search above the list view to find specific records in the library.

The Library Manager has the ability to upload and delete images for libraries with attachment fields. These images are stored in the Project Home, <project home>\attachments\Libraries\.

Read-only Libraries

Some libraries purposely cannot be changed in Library Manager. If a library is set as Read-only, the user cannot add, edit, or delete values to any library entries.

  • A few libraries, such as Priorities or Overall Ratings, need to contain a specific set of values for the Cartegraph system to function, and therefore cannot be changed in Library Manager.
  • If a library is associated to a Domain or Subtype with the GIS integration, the library is read-only in Library Manager. A library such as this displays a message in Library Manager pointing the user to make changes in ArcCatalog in the Geodatabase Properties dialog box. For example, the Pipe Materials library may be read-only because it is associated to the Pipe Materials domain.
  • Any library can be set as Read-only by altering the library properties in Structure Manager.
  • If a library is marked as System, the Read-only property cannot be turned off once it has been set.
  • If you have the Advanced Assets Extension, some libraries are designed to be edited in other areas of Cartegraph because of specific display or edit needs of the library.
    • All of the Condition Category, Condition Group and Prediction Group libraries are edited outside of Library Manager, in Asset Condition Manager.
    • Condition Category, Condition Group, and Prediction Group libraries display in Library Manager, but there is a convenient link to Asset Condition Manager to allow the user to make the necessary changes in that function.
  • If you do not have the Advanced Assets Extension, Condition Category libraries are edited in Library Manager.
    • The Index Mapping and Impact child recordsets are read-only, except Impacts for Signs.

Layout Manager


The Layout Manager is located in Cartegraph‘s Administration section and is the feature that allows you to set your screen layout.

If a new field is created, it may not be visible in the Layout Manager file list. The user will need to sign out, then sign back in to see the new field as available.

Use the Layout Manager to design screens, grids, and lookups for parent-level recordsets, child-level recordsets, and libraries.

If you change grids in the system, the change persists for in session and overrides the default Layout Manager setup.

There are three view types:

  • Detail view: To design the Detail view with information about an individual record. Detail Views display after you click on the View button on a summary tip or list. This displays all the fields and field entries available for a specific record.
  • List view: To design the List view layout with record and library information. List Views are located under the Map view for records from Requests, Work Orders, Tasks, Assets, Labor, Equipment, Material, Material Locations, and Vendors.
  • Lookup view: To design the multi-column lookup grids in any recordset or library.

Drag and Drop functionality of fields, grids, sections, and group headers. Use these three actions:

  • Add Section: allows the addition of a section which can be placed wherever is desired and can be named
  • Reset: Resets the screen to the original default that is provided out of the box
  • Save: Saves changes made

Rename section headers by hovering over the right side of a Section header and clicking on the pencil.

Add Group Headers by hovering over the Section header and click the +. Drag and drop to the desired place.

Delete fields, grids, group headers, and section headers from the layout by hovering over them and clicking on the X on the right.

Clear the check box to the left of the section name to hide the section.

Esri and Active Directory

Cartegraph supports a single sign-on experience through the use of ArcGIS Enterprise Login capabilities. Enterprise logins support a variety of SSO methods, with Active Directory Federate Services being one; the ability for a user to use their Windows active directory credentials to sign into both Cartegraph and ArcGIS solutions.

Security Role Administration

Role Administration allows you to create security roles, or a group of users with the same access to Cartegraph functionality.

Those roles are assigned Security Settings:

  • Screen Assignments
  • Create, Update, and Delete Security Assignments
  • Command Permissions
  • Global Command Permissions

Security settings are per role, not per user. By default, all users have access to all areas of the system except for the functions requiring opt-in security. The System Administrator removes and adds rights where appropriate.

All users should be signed out of Cartegraph when setting up Security or have all users sign out and sign in to get the latest security settings. Otherwise, users receive error messages trying to access functionality they previously had permission to use.

Role names have a minimum of two characters and a maximum of 25 characters.

User accounts can only be assigned to a single role.

Any users assigned to a role that does not have security for the List view:

  • Do not have that Asset displayed in the Select Asset Type list on the Assets tab
  • Do not have that asset available on the Asset Type list when converting a Non-Asset Task to an Asset Task

Any users assigned to a role that does not have security for the Detail view do not have that Asset displayed in the Create list on the Assets tab.

Cartegraph comes with these roles, Default Administrator, Default User, Default Power User, and Internal Request User, as well as a process to create your own:

  • Default Administrator—all users have access to all areas of the system.
  • Default Power User—all users have access to the system and the following in Administration:
    • User Administration
    • Import/Export
    • Error Log
    • Geocode Settings
    • GIS Integration
    • Library Manager
    • *Preventative Maintenance
    • *Scenario Builder
    • *Asset Condition Manager
    • Manage Layers
  • Default User—all users have full access to the system, except for the functions requiring opt-in security.
  • Internal Request User—all users have access to the Internal Request feature.
  • New role—create a role, and all users of that role have full access to the system except for the functions requiring opt-in security.

Changes made to security settings are immediate upon save. A user in the system, while changes are made to security settings on their Security Role, will be impacted when they next attempt a Create, Update, or Delete action on the recordset.

User Interface

Request Management

Work Management

Asset Management & Analytics

Resource & Inventory Management

Report Management

Mobile Management

Workflow Management

System Management

Integration Management