An alias is an alternate name for a feature class that gives the feature class a unique identity with a map service. The Lucity mapping applications check the alias names of the layers loaded into them to determine which feature class is present. This in turn tells the Lucity system which feature class configuration to use in the geodatabase configuration.
Note: The geodatabase configuration must be complete before an administrator can configure Lucity to recognize aliases.
Note: An administrator must establish and import aliases to the geodatabase configuration in order for the Lucity mapping applications to work.
Setting an Alias
An administrator can either set an alias for a feature class within ArcCatalog or set aliases on a per-map basis in ArcMap. Feature class aliases are tied to the feature class in ArcCatalog. Per-map aliases are set in ArcMap and are only saved for that .mxd, or for any map services or map packages generated from that .mxd.
Note: Aliases must be completely unique throughout the geodatabase configuration. For example, a Sewer Pipe feature class and a Water Pipe feature class cannot both have a "Pipes" alias.
In ArcMap, click on a feature class in the table of contents and rename it.
OR
Right-click on the feature class and select Properties.
On the General Tab, change the name in the Layer Name field.
Click OK. The new alias is now set for that feature class.
Repeat for other desired feature classes.
Import Aliases
Aliases can be imported into the Lucity geodatabase configuration in two ways: 1) by importing the feature class alias or 2) by importing the per-map aliases.
In the Geodatabase Configuration tool, select the geodatabase connection or the feature class for which you wish to import an alias.
Right-click on the selected geodatabase or feature class and select the Import tool.
If it is a geodatabase, the tool is Import Feature Class Alias Names.
If it is a feature class, the tool is Import Feature Class Alias Name.
The system immediately begins importing aliases from the feature class aliases set in ArcCatalog. A log screen appears to provide information about the import.
Review and close the log screen when the process is complete.
On the Lucity Edit toolbar, click the Alias Import button. The following message appears:
Click Yes to continue. The process log displays the results:
Importing aliases using this method directly links them to the feature classes' Alias Names tab in the geodatabase configuration.
Note: This import enables users to load their feature classes into a map. Change the names of the layers, and then quickly import them before publishing the .mxd as a map service or map package.
Manage Aliases
Aliases can be added manually for each feature class and managed in the Geodatabase Configuration tool.
In the Geodatabase Configuration tool, select a feature class. A window with several tabs appears in the center of the screen.
Select the Alias Names tab. This tab has two grids:
The Associated Aliases grid lists all aliases assigned to the feature class.
Right-click on an existing record for options to Add, Edit, Delete, or Disassociate.
Disassociating a record in this grid detaches it from the selected feature class and moves it to the Available Aliases grid.
Whenever a feature class with a name from this list appears in the Lucity Viewer, the Web Map, or the Mobile Map Mode, Lucity connects the feature class to the associated module.
The Available Aliases grid lists aliases set up by the user that aren't associated with any feature classes. The grid is shared among all feature classes. Aliases in the grid can later be associated with or re-associated with any feature class.
Right-click on an existing record for options to Add, Edit, Delete, or Associate.
Associating a record in this grid attaches it to the selected feature class, removes it from the Available Aliases grid, and adds it to the Associated Aliases grid for the selected feature class.
How To Add an Alias in a Grid
Right-click in the desired grid and select Add. The following pop-up appears:
Enter the Alias Name and click OK.
Note: Aliases apply to the feature class and any replica feature classes.