TRAINING GUIDE Gedatabase Cnfiguratin Tl Overview
Gedatabase Cnfiguratin Tl Overview In this sessin, we ll intrduce yu t the Lucity Gedatabase Cnfiguratin tl. We ll give yu infrmatin abut gedatabase setup, feature class setup, and the many tls that can be used fr cnfiguratin. Table f Cntents Gedatabase Cnfiguratin... 4 Cnnectin Prperties... 6 Enterprise Gedatabase Cnnectin Prperties... 6 Edit Map Service... 7 Versin Setup... 7 Feature Class Cnfiguratin... 8 Feature Class Infrmatin Tab... 8 General Frm Infrmatin... 8 Feature Class Fields (Nt linked t Lucity)... 9 Feature Class Linking Fields... 9 Edit Map Service Tab... 10 Alias Names Tab... 10 Parent Recrd Linking Tab... 11 Lgical Netwrk Tab... 12 Assciated Wrkspaces Tab... 12 Feature Class Fields Grid... 13 Clr Cding... 14 Lucity Cde/Type fields... 14 Cmpsite Date fields... 15 X/Y fields... 15 Cmpsite Address fields... 15 Spatial Relatinships... 17 Number Generatr... 19 Gedatabase Cnfiguratin Tl (v2018r2) 2
Validate a Number Generatr... 21 Scheduled Tasks... 22 Cpying a Scheduled Task... 27 Validate a Scheduled Task... 28 Manually Run a Scheduled Task... 29 Tls... 30 Gedatabase Cntext Menu Tls... 30 Add a Feature Class Cnfiguratin... 30 Imprt Feature Classes frm Schema... 31 Delete Multiple Feature Classes... 33 Imprt Feature Class Alias Names... 33 Set Update Length/Area Flag t True... 34 Update Feature Class Services... 35 Feature Class Schema Tls... 36 Dmain Tls... 39 Dmain Cnfiguratin... 39 Update Parent Linking Dmains... 44 Update Street Name Dmains... 45 Update Street Light, MUTCD, and Tree Dmains... 48 Update Wrk Categry, Maintenance Zne, and Alternate Zne Dmain... 49 Validatin Tls... 51 Integratin Summary Reprt... 54 Gedatabase Cnfiguratin Tl (v2018r2) 3
Gedatabase Cnfiguratin Once yu have created the gedatabase cnnectins with the Lucity Administratin tl yu can use the Lucity Gedatabase Cnfiguratin tl in ArcCatalg t perfrm all ther cnfiguratins. Nte: Users must have the fllwing Lucity Security permissins t use this tl GIS > GIS System Cnfiguratin > Run GIS > Admin Cnnectin Strings > Edit In ArcCatalg, Click n Lucity GIS Tls>>Gedatabase Cnfiguratin. The fllwing dialg will appear: The left side f the frm lists all the gedatabase cnnectins that are currently cnfigured with Lucity. Nte: If there are n cnnectins cnfigured yu will need t use the Lucity Administratin Tl t create a new cnnectin prir t using this tl. Gedatabase Cnfiguratin Tl (v2018r2) 4
Expanding the ndes n the left side f the frm shws the varius cmpnents f the gedatabase. The frm will be updated t shw data applicable t the selected nde type. The ndes can represent 5 types f data: 1. Gedatabase: At a minimum yu will have at least ne gedatabase cnnectin and it will be called DEFAULT. Selecting this type f nde will let yu mdify the cnnectin infrmatin and versin setup fr the gedatabase. Yu will als get the fllwing cntext menu when the nde is right-clicked. 2. Feature Class: This will be listed in the frmat f feature class name <-> Lucity table name. Fr the image abve, cmaddress is the feature class name and that feature class is mapped t the Lucity CMADDR table. Selecting this type f nde will let yu mdify the prperties fr the feature class and its fields. 3. Number Generatr: This will start with the wrd Number Generatr and will then list the feature class field name that is cnfigured. Select this nde t mdify the number generatr prperties. 4. Scheduled Task: This will start with the wrd Scheduled Task and will then list the type f GIS Scheduled Task. Select this nde t mdify the scheduled task prperties. 5. Spatial Relate: This will start with the wrd Spatial Relate and will then list the feature class field name that is updated. Select this nde t mdify the spatial relatinship prperties. Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 5
Cnnectin Prperties The Cnnectin Prperties tab shws yu the gedatabase cnnectin infrmatin. T setup a Persnal r File gedatabase brwse t the database lcatin. 1. ArcSDE setup is as fllws: Enterprise Gedatabase Cnnectin Prperties Server: This must cntain the name f the machine where ArcSDE is installed Service: The name f the instance fr the SDE database. This supprts either spatial r direct cnnectins. Spatial Cnnect: This field shuld cntain the prt where ArcSDE is installed. By default, this is typically 5151. D nt include the /tcp identifier; enter nly the number fr the prt. Direct Cnnect: Enter the name f the direct cnnect driver and the name f the server instance. SQL Server Example:"sde:sqlserver:GIS_SERVER\DATA. " Oracle Example: "sde:oracle11g:gis_server\data." Database: This must cntain the name f yur SQL Server gedatabase. Instead, it is the gedatabase that cntains the infrastructure data that yu want t integrate with the desktp. Fr Oracle gedatabases this must be blank. Authenticatin type: Used by Lucity t cnnect t the gedatabase. If yu specify DB yu must als ppulate the UserName and Passwrd fields. UserName: If using DB authenticatin type, yu must specify a user. This user must have permissin t ALL feature classes linked t Lucity. Passwrd: If using DB authenticatin type, yu must als specify a passwrd fr the user. Versin: This infrmatin is always required; it designates the name f the ArcSDE versin that Lucity will use when cnnecting t the gedatabase. Fr Oracle, the Versin is case sensitive. Gedatabase Cnfiguratin Tl (v2018r2) 6
Edit Map Service URL: This is the URL fr a map/feature service that cntains this gedatabase s feature classes linked t Lucity. Update Frm Lucity: This indicates if the gedatabase shuld be updated with edits made in the Lucity desktp and web interfaces Replica Gedatabase: This indicates if the gedatabase is a replica gedatabase. If this is checked, functinality with the cnfiguratin tl will change preventing sme actins (such as deleting feature classes) and enable ther actins (such as assciating feature classes) Versin Setup Clients using an enterprise gedatabase (ArcSDE) can indicate which versins f their gedatabase are "Lucity versins". This gives users the ability t selectively chse which versins shuld update the Lucity database when they are edited in ArcMap. Nte: If "Update Lucity frm all Versins" is checked then the infrmatin listed in the grid is ignred as edits t ALL versins f the gedatabase will be psted t the Lucity database. If that ptin is nt checked, then edits made t nly thse versins listed in the grid with the 'IsSyncVersin' ptin checked will update Lucity. Add/Delete a Versin T add a versin: 1. Click n the Add Versin buttn. 2. A new line will be added t the versin grid. Fill in the versin name and check "IsSyncVersin' if yu want t update the versin. Nte: Fr Oracle gedatabases this infrmatin is casesensitive. T delete a versin: 1. Right-click n the versin yu want t delete and chse Delete. 2. The versin will be remved frm the grid. Gedatabase Cnfiguratin Tl (v2018r2) 7
Feature Class Cnfiguratin T view feature class cnfiguratins, expand the crrect database nde frm the grid n the left. A list f all feature class mappings will be displayed. Select the feature class nde t view its cnfiguratin. Feature Class Infrmatin Tab General Frm Infrmatin Feature Class Name: This is the name f the feature class. This is NOT the alias name. Nte: If the wner f the feature class is nt db, then yu must specify the wner in the frmat f wner.featureclassname. Mdule Name: This field is read-nly fr existing items in the feature class list. This is the name f the Lucity mdule t which the gedatabase feature class is related. Table Name: This field is read-nly and shws the Lucity table name that crrespnds t the selected Lucity mdule. Disable Feature Class: This flag allws yu t disable a feature class that yu are nt using, but d nt want t delete frm the setup. Always Update Length/Area: This flag indicates whether r nt the Lucity GIS Extensin shuld update the feature class field linked t the Lucity s length/area field when the shape f a feature has changed. If checked, the prgram will update the field in the feature class mapped t the Lucity length/area field. It updates the values in this field based n the shape.length and shape.area fields. If this ptin is left unchecked, the Length/Area fields will nly be ppulated when the feature is first created. Gedatabase Cnfiguratin Tl (v2018r2) 8
Feature Class Fields (Nt linked t Lucity) In Lucity Flag Field- This field is cntrlled by Lucity t indicate t users whether r nt each recrd in the feature class has been synchrnized with Lucity. This shuld be a shrt integer field and shuld be assigned a dmain that classifies 0=N r False and 1= Yes r true. This dmain will make it easier fr end users t understand the values that will be stred in the field. Last Mdified By - This field is cntrlled by Lucity t indicate which user last mdified the recrd frm an edit sessin in the map. Last Mdified Date - This field is cntrlled by Lucity t indicate what date the recrd was last mdified frm an edit sessin in the map. Last Synchrnized Date - This field is cntrlled by Lucity t indicate the date when the recrd was last synchrnized with Lucity. Field fr Display - This is the field name that will be displayed with the varius Lucity GIS tls. By default, this field will be set t the cmmn ID f the feature class. Feature Class Linking Fields Cmmn ID- (Required) The unique identifier assigned by the user fr this asset. The value fr this field cannt be directly mdified; it is autmatically ppulated based n the field mappings frm the grid at the right f the page. Every mdule has ne field that defines the asset as unique. These fields are highlighted in the grid t the right. T enter a value in this field, find the crrespnding highlighted field and type the field name int the Feature Class Field Name clumn. Lucity AutID- (Strngly Recmmended) This field is used by Lucity t stre an indexed lng integer link between the recrds in the feature class and the recrds in the Lucity inventry table. This field must be lng integer. The value fr this field name is nt editable; t update this value, use the grid t the right t find the crrespnding highlighted field. Nt having this field will impact the perfrmance f sme f the Lucity GIS tls as additinal resurces will be used t determine the AutID value based upn the cmmn ID. Gedatabase Cnfiguratin Tl (v2018r2) 9
Additinal Linking Fields Fr Inspectins- These are additinal fields that are used fr inspectin mdules. The clr indicates if the field is required. The value fr this field name is nt editable; t update this value, use the grid t the right t find the crrespnding highlighted field. Edit Map Service Tab Sme Lucity tls (Lucity Spatial Updater, Lucity GIS Updates via Feature Service, GIS Scheduled Tasks) interact with Lucity linked feature classes via feature services. The Edit Map Service tab can be used t define a feature service fr an individual feature class. Nte: By default, if a feature service hasn t been defined at the feature class level, Lucity will use the edit map service defined at the gedatabase level. Default Service fr gedatabase- This is read-nly. This indicates the service that is defined at the gedatabase level. This is defined n the gedatabase cnnectin inf tab r in UI Admin in the Cnnectin Strings mdule. Alternate Feature Service- Allws an admin t select a specific feature service t use fr this feature class. The drpdwn cntains a list f feature services as defined in the Lucity Admin GIS Services mdule. Only services that have been defined as having feature access capabilities are shwn. Alias Names Tab Aliases are alternate names fr feature classes that prvide a unique identity. They are used by the Lucity Webmap, Lucity Viewer, Lucity Mbile fr Andrid, and any ther Lucity applicatin that interacts with map/feature services t identify which feature classes are linked t Lucity. These Lucity mapping applicatins check the feature classes laded int them and check the display names f thse feature classes against the aliases names listed in the Gedatabase Cnfiguratin. The Alias Names tab has tw grids. The Assciated Aliases grid is a list f all the aliases assigned t the feature class. Right-click n an existing recrd t get a menu with ptins t Add, Edit, Delete, r Disassciate. Disassciating a recrd in this grid will detach it frm the selected feature class and mve it t the Available Aliases grid. Whenever a feature class appears in the Lucity Viewer, Webmap, r Mbile fr Andrid with a name frm this list, Lucity will cnnect it t the assciated mdule. Gedatabase Cnfiguratin Tl (v2018r2) 10
The Available Aliases grid is a list f aliases already added but aren t assciated t any feature class. Right-click n an existing recrd t get a menu with ptins t Add, Edit, Delete, r Assciate. Assciating a recrd in this grid will attach it t the selected feature class, remve it frm this grid, and add it t the Assciated Aliases grid fr the selected feature class. Parent Recrd Linking Tab Sme feature classes have parent relatinships. Sme relatinships are required where thers are nt. Fr example, A Park Furniture feature can be assciated t a Park feature but it isn t a requirement. On the ther hand, a Facility Site Asset feature must be assciated t a Facility Site asset. These assciatins are maintained via a linking field in the child table. This field is typically a lng integer field that stres the parent recrd s autid (the ID assigned by the database). In rder fr Lucity t acknwledge this relatinship this field must be included in the feature class mappings. The Parent Linking tab will assist yu in ppulating the GIS field linked t the parent s autid. If using this functinality, a user wuld just need t ppulate the parent s cmmn ID field and the Lucity GIS extensin will handle the rest. Lucity Parent Tables: This is a read nly field. This lists the table(s) that can have a relatinship t the current feature class. Lucity Parent Cmmn ID Field: This is a read nly field. These are the field(s) in the parent table(s). This is typically the same field that is used as the Cmmn ID fr the parent Table. Lucity Parent Aut ID Field: This is a read nly field. These are the aut ID field(s) in the parent table(s). Feature Class Parent Cmmn ID Field: This is a field in the feature class that cntains the string unique identifier that links the feature t the parent feature class r table. Fr example, if a Park Furniture feature class is being set up, this field will be the Park Number field. Separate multiple fields by cmmas. This field shuld crrespnd with the fields in the Lucity Parent Cmmn ID field. Include the cmma even if n field is t be used. Feature Class Parent Aut ID Field: This is a field in the feature class that cntains the aut ID f the parent feature class r table. Fr example, if a Park Furniture feature class is being set up, this field will be the Park AutID field. Separate multiple fields by cmmas. This field shuld crrespnd with the fields in the Lucity Parent AutID field. Include the cmma even if n field is t be used. Gedatabase Cnfiguratin Tl (v2018r2) 11
Lgical Netwrk Tab Feature Class Frm and T Nde Table: This is read nly. It shws which table the t and frm ndes will be stred. The feature class(es) that cntains the t and frm nde pint features shuld be cnfigured t synch t this Lucity table Feature Class Frm Nde Field: This field stres the name f the string field that will stre the upstream r frm nde identifier. Fr street segments, this is the frm intersectin and is ptinal, unless the Accident mdule is being used, in which case it is required. This field shuld be a text r character field. Feature Class T Nde Field: This field stres the name f the string field that will stre the dwnstream r t nde identifier. Fr street segments, this is the t intersectin and is ptinal, unless the Accident mdule is being used, in which case it is required. This field shuld be a text r character field. Assciated Wrkspaces Tab A feature class cnfiguratin can be assciated between multiple gedatabase cnnectins. Fr example, a client has a feature class named SewerPipe that exists in bth a parent and replica gedatabase. Instead f having t create a feature class mapping fr bth gedatabases, the feature class mapping nly has t be created against the parent gedatabase cnnectin, and then the feature class mapping can be assciated t the replica gedatabase cnnectin. The Assciated Wrkspaces grid shws all the gedatabases that this feature class is assciated t. This grid is read-nly. T assciate/disassciate a feature class there is a right-click cntext menu when yu select the replica gedatabase nde that gives yu these ptins. Default Wrkspace- Each feature class is required t have a default wrkspace cnnectin. The default wrkspace fr a feature class is the wrkspace it is assciated t that isn t marked as a replica wrkspace. Nte: A feature class is nt able t be assciated t mre than ne nn-replica gedatabase. Gedatabase Cnfiguratin Tl (v2018r2) 12
Feature Class Fields Grid The feature class fields grid allws yu t manage the feature class fields are mapped t Lucity fields. A mapping between the tw enables the Lucity applicatin t update the feature class when the data is updated in the Lucity desktp r web applicatin. A mapping als enables the Lucity extensin in ArcMap t update the Lucity database when the data is updated in the feature class during an ArcMap edit sessin. FieldName- The field name in the Lucity table. DisplayName- The field captin in Lucity. Field Type- The type f data stred in the field MaxMask- The data frmat. A numeric value fllwed by an x indicates the number f characters allwed. Feature Class Field Name- This is the name f the field in the feature class. This is NOT the alias field name. If yu are unsure f the field name use the Field Lkup buttn. In versin 2016+, yu may specify a default value here, instead f a field. Just add the prefix = in frnt f the value and all new recrds synced frm GIS will have that field in Lucity ppulated with that value. This value is validated when a validatin is run against the feature class, and during the sync prcess frm GIS t Lucity. *Nte: d NOT put qutes arund the default value, even if it is a string value. The prgram will detect what the value is based n the leading = and parse int the crrect data type. Gedatabase Cnfiguratin Tl (v2018r2) 13
Field Lkup- This buttn clumn displays a list f the feature class fields. Nte: If a cnnectin t the gedatabase was unsuccessful then n fields will be listed. Imprt Field- Indicates that data in the field will be imprted int Lucity. Exprt Field- Indicates that data in the field will be updated in GIS frm Lucity. Lkup Lucity ID- This clumn nly wrks fr feature classes linked t Lucity inspectin mdules and nly fr fields linked t a parent recrd #. The feature class must cntain an ID fr the Lucity asset the inspectin is fr. Lucity expects this field t cntain the parent recrd #. If the ID stred in the feature class is the asset s cmmn ID instead f the parent recrd #, check the Lkup Lucity ID field. This is necessary because Lucity needs the parent recrd # and this will cause the sync prcess t lk up the parent recrd # based upn the cmmn ID f the parent. Clr Cding Red- Required Field. This is the Cmmn ID (FacilityID) field fr the asset inventry mdule. Pink- Recmmended Field. Typically, this is the Lucity aut ID field. Althugh, technically this field isn t required it is strngly recmmended that the feature class cntain a field that stres the Lucity autid. Nt having this field will impact the perfrmance f sme f the Lucity GIS tls as additinal resurces will be used t determine the AutID value based upn the cmmn ID. Orange- Required Field. Stres the required ID number f related features (the parent recrd number) Yellw- These are cnsidered parent linking fields. They typically stre the ID f the related feature. Green- Building and Address cmpsite fields. Lucity Cde/Type fields Only the Lucity cde fields are displayed in the Feature Class Fields grid. The Dmain Cnfiguratin tl can be used t further define the mapping between a GIS field t a Lucity picklist field. Lucity supprts mapping a text GIS dmain t Lucity numeric picklist and vice versa. Gedatabase Cnfiguratin Tl (v2018r2) 14
Cmpsite Date fields Lucity Date and Time fields can link t a GIS cmpsite DateTime field. The difference between the tw is that Lucity stres the Date in ne field and the Time in anther. A typical Esri Date field can stre bth the Date and Time cmpnent all in ne field. T link a GIS cmpsite DateTime field t Lucity, link the GIS field t bth the Lucity Date field and the Lucity Time field. X/Y fields Lucity X-crdinate and Y-crdinate fields can be manually linked t a GIS field. Hwever, if they are nt mapped t a GIS field, then Lucity will autmatically ppulate these Lucity fields based upn the feature s x/y crdinate infrmatin during the ArcMap sync prcess. Cmpsite Address fields Lucity breaks ut street address infrmatin int the fllwing fields: Building number Building suffix Street directin Street prefix Street name Street type Street suffix Each f these fields that yu use in Lucity need t have a matching field in the feature class. Alternatively, yu can use the cmpsite address fields in the feature class fields grid t map a field in yur feature class that cntains the entire building number r the entire street name. Nte: If yu map t a cmpsite field yu shuld NOT map t the individual building r street cmpnent fields. Gedatabase Cnfiguratin Tl (v2018r2) 15
Multiple field cnfiguratin Single field cnfiguratin (Cmpsite) Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 16
Spatial Relatinships Spatial relatinships autmatically update features based n their lcatin relative t ther features t help aid general editing and maintaining these relatinships in ArcMap. There are fur ways in which spatial relatinships are triggered: 1. Within an ArcMap edit sessin, when a feature is created r when an existing feature s shape is changed. 2. Within an ArcMap edit sessin using the "Update Spatial Relatinships" tl n the Lucity GIS Edit tlbar. This tl is typically used if the data was imprted using a nn-lucity imprt tl r was added during a nn-lucity edit sessin. 3. When the Lucity Data Lader is used. 4. When features are synchrnized thrugh a scheduled task (GIS t Lucity), if the ptin is set. Nte: There are sme spatial relatinships that are hard-cded and updated autmatically by the Lucity GIS extensin during the ArcMap synchrnizatin prcess. The fllwing are the hard-cded relatinships which yu shuld nt create relatinships fr: T/Frm nde infrmatin fr: Sewer Pipe, Strm Cnduit, Water Pipe, Recycled Water Pipe, Raw Water Pipe, Street Mainline Cabling, Park Irrigatin Pipe, Facility Irrigatin Pipe, and Fiber Optic Cable. Field t Update- The field name in the selected feature class that will be updated. Related Feature Class- The name f the feature class that is being related t the selected feature class. Nte: The related feature class must be stred in the same gedatabase as the selected feature class. Related Feature Class Field- The field name in the related feature class that cntains the value that will be used t ppulate the Field t Update field. Relatinship Type- The type f relatinship. See the fllwing sectin fr a descriptin f the relatinship types. Distance Value- Distance used with the relatinship. This field nly applies if using the Is Within Distance Of relatinship type. Never verwrite a nn-null value- Check this bx t ensure that data ppulated in the Field T Update is never verwritten if a value already exists. Gedatabase Cnfiguratin Tl (v2018r2) 17
Update value t null if n relatinship is fund- Check this bx t allw the Field t Update t be set t null if n relatinship is fund. Service that cntains related feature class- Prvides the service t use fr GIS Scheduled tasks if the related feature class is in a different service. Relatinship Types Frm Intersect: Finds any features in the Related Feature Class that intersect the frm pint f the feature in the selected feature class. This relatinship nly wrks fr plyline, edge, r cmplex edge features. T Intersect: Finds any features in the Related Feature Class that intersect the T Pint f the feature in the selected feature class. This relatinship nly wrks fr plyline, edge, r cmplex edge features. Is Cntained by: Finds any features in the selected feature class that are cntained by features in the related feature class. The related feature class must be a plygn feature class. Intersects: Finds the first feature in the related feature class that intersects the feature in the selected feature class. US Intersect Distance: Finds the first feature in the related feature class that intersects the feature in the selected feature class and then calculates the distance alng the line that the intersectin ccurs (frm the t pint). The selected feature class must be a plyline, edge, r cmplex edge feature class. Midpint Intersect: Finds any feature in the related feature class that intersects the midpint f the feature in the selected feature class. This relatinship is designed fr plyline, edge, r cmplex edge features as the selected feature class, and a plygn feature fr the related feature class. Frce Related Feature t Self-Update: This relatinship finds any features that intersect the feature in the selected feature class and adds them t the edit cache s that they are synched t the desktp even if the recrds have nt changed. This is used primarily fr the street segment feature class (as selected feature class) and the street intersectin feature class (as related feature class). This frces the intersectins t autmatically recalculate the intersectin cnfiguratins fr the diagram in the desktp Intersectin mdule when street segments are changed. Is Within Distance f: Finds all features in the related feature class that are with a specified distance f the feature in the selected feature class. Gedatabase Cnfiguratin Tl (v2018r2) 18
Number Generatr Number Generatrs are designed t assist the user in ppulating a feature class field with a unique value. Fields in a feature class can be setup s that the Lucity GIS extensin will ppulate the field with a unique value. When features are created r mdified in an ArcMap edit sessin, if the field cnfigured with the number generatr desn t cntain a value the Lucity GIS extensin will ppulate this field with the next incremental value. There are fur ways in which number generatrs are triggered: 1. Within an ArcMap edit sessin, when a feature is created r edited. 2. Within an ArcMap edit sessin using the "Frce Sync" tl n the Lucity GIS Edit tlbar. This tl is typically used if the data was imprted using a nn-lucity imprt tl r was added during a nn-lucity edit sessin. 3. When the Lucity Data Lader is used. 4. When features are synchrnized thrugh a scheduled task (GIS t Lucity), if the ptin is set. Field t AutNumber- The field that will be aut-numbered. This shuld be a text field, large enugh t supprt the numbers that will be generated based n the settings n this frm. Buffered Number Length- Use this field t indicate a fixed min length. This causes the number t cntain buffered zeres. Fr example: If a buffered length f 5 is entered, and the next number generated is 985, the resulting aut number that will be ppulated is 00985. This is ptinal and allws fr easier number srting. Prefix Settings (Optinal): Nne- This is marked by default. If this remains checked, there will be n prefix used in the autnumber values. Use Set Prefix- This allws specifying a prefix in the next number grid and a separatr character. Use a plygn feature class t create a prefix- Uses a plygn feature class field t generate a prefix based n a feature s spatial relatin t the plygn feature class. Gedatabase Cnfiguratin Tl (v2018r2) 19
Plygn Feature Class- The name f the plygn feature class that the aut number prefix is based n. Nte: This feature class des nt have t be linked t Lucity, but it des have t reside in the same gedatabase as the Lucity Features. Field that cntains prefix value- The field that cntains the value that will be used fr the prefix. Separatr Character- Character used between the prefix and next number values. This field is nly enabled if a prefix ptin was enabled. Service that cntains related feature class- Prvides the service t use fr GIS Scheduled tasks if the related plygn feature class is in a different service. Generate Next Number- Click this buttn t generate a new rw in the grid. Yu can generate multiple rws nly if using the Use a plygn feature class t create a prefix ptin is checked. Otherwise, yu will nly be able t generate ne recrd in the grid. Next Number Grid- This grid is used t shw what the next number(s) will be. The Prefix clumn will be disabled if nt using a prefix The Value clumn will be the next number value used with a feature If Use a plygn feature class t create a prefix ptin is being used-multiple rws can be used in this grid. Each rw shuld have a unique prefix value. Fr example, if setting up a number generatr based upn a quarter-sectin plygn feature class, yu wuld want t create a recrd fr each pssible quarter-sectin since a feature in each quarter sectin may have a different next number (A-12, B-005, C-12, D-01, etc). Nte: When a new feature is created in the selected feature class if n Next Number is set the number generatr will set the new feature t 1 and set the next number t 2 and cntinue frm there. The same is true if the use plygn feature class ptin is being used. Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 20
Validate a Number Generatr Any time yu ppulate the next number grid with a value, the prgram will autmatically validate what yu entered against what is in the database. Here s hw it wrks: If the value yu entered is lwer than the highest number in the database, then a prmpt will appear suggesting a starting value equal t the highest number + 1. If Yes is selected, then the value will be ppulated with what the prgram suggests. Otherwise, it will keep the value yu entered (at yur wn risk!). The validatin des take prefix values int accunt (if any are used). Yu may als manually validate yur number generatr s next number at any time. T d this, simply right click the number and select Validate. This is handled the same way as ppulating the value in the grid, except yu will als be prmpted if the starting value is valid. Gedatabase Cnfiguratin Tl (v2018r2) 21
Scheduled Tasks Scheduled Tasks are designed t push data back and frth between Lucity and the gedatabase. There are tw types f synchrnizatins the tasks can be cnfigured t perfrm: 1. Lucity t GIS- Currently this is nly available fr inspectin feature classes 2. GIS t Lucity- This is supprted fr all GIS enabled mdules (inventry and inspectin). Scheduled Tasks can be cnfigured t run autmatically. The GIS Task Runner will prcess any Scheduled Task that is due based upn the user defined frequency and ther criteria. This functinality greatly expands the Lucity and GIS integratin capabilities with use f feature services. Edits t the feature service, regardless f wh did it and what envirnment they did it in, can be picked up by Lucity. Sme ptential examples: Cllectr fr ArcGIS (ios & Andrid)- including discnnected editing Lucity Web Map ArcGIS.cm map viewer Any ther 3 rd party apps that supprt feature service editinghttp://resurces.arcgis.cm/en/help/main/10.2/index.html#/using_feature_services_in_a_ client_applicatin/0154000005sq000000/ Ntes: Merges, Splits, Renumbers, and Deletes must still be dne in an ArcMap editing envirnment with the Lucity extensin enabled in rder fr the Lucity inspectin, cnstructin, and wrk histry t be prperly updated. Number generatrs and spatial relatinships can be perfrmed (if the ptins are set) when Scheduled Tasks synchrnize features with Lucity. Features must meet the Lucity mdule requirements in rder fr them t be synchrnized. Fr example, required fields such as the Lucity cmmn ID must be ppulated with a unique value. Scheduled Tasks interact with the feature class via map and/r feature services. Befre setting up a Scheduled Task yu shuld make sure there is a map service defined at either the feature class r gedatabase level. Gedatabase Cnfiguratin Tl (v2018r2) 22
General Inf Task Type- The type f synchrnizatin that will be perfrmed by this GIS Task. a. The ptins are: Sync- Lucity t GIS and Sync- GIS t Lucity. Disabled- Check this bx if this task shuld be disabled. This will prevent the Scheduled Task frm being prcessed by the GIS Task Runner service. Filter Optins Select whether the task will prcess all recrds (default) r prcess a filtered set. If using a Filtered Set- the Select Filter buttn will nly be enabled fr task types f Sync- Lucity t GIS. If manually entering the Where Clause, it must pass validatin f the underlying data surce. Optins Only prcess recrds mdified since last run- This ptin checks thrugh the recrds that were selected fr prcessing and nly prcesses thse recrds that were edited since the last time the scheduled task prcessed. a. Nte: If this ptin is checked and the Task Type is Sync- GIS t Lucity then yu must als prvide the Last Edited DateTime Field. If the Task Type is Sync-Lucity t GIS, then the Lucity Last Md Date and Time fields will be used. Gedatabase Cnfiguratin Tl (v2018r2) 23
b. Nt checking this ptin will result in the fllwing prmpt. Click OK t prceed. Last Edited Date Time Field- This ptin is nly enabled if the Only Prcess recrds mdified since last run is checked and the task type is Sync- GIS t Lucity. Insert recrd if it desn t already exist- Allws fr new recrds t be inserted int the GIS feature class r Lucity mdule depending n the task type. Enable number generatr fr imprts- Assigns the Cmmn ID fr each new recrd in the imprt task using the feature class number generatr. Enable spatial relates fr imprts- Applies the feature class spatial relatinships t each new recrd in the imprt and updates the recrd s fields accrdingly. Update existing recrd- Allws updates t existing recrds in the GIS feature class r Lucity mdule depending n the task type. Delete previus inspectin(s) fr asset- This ptin is nly enabled if the task type is Sync- Lucity t GIS. This ptin causes the task t delete any inspectin in the feature class that isn t the mst recent inspectin fr an asset. The purpse f enabling this ptin is if yu want the feature class t nly cntain the mst recent inspectin fr each feature. Scheduling Inf This sectin can be cnfigured s the task is prcessed by the GIS Task Runner service. Units- Enter a numeric value that indicates hw ften the prcess shuld run. This value is used in cnjunctin with the Frequency. Fr example, if Units = 3 and Frequency = Hurs then the Scheduled Task wuld run every 3 hurs. Frequency- Select the desired frequency frm the drp dwn. The ptins are Minute, Hurs, Days, r Mnths. Last Run- This is disabled by default, shwing the last time the scheduled task ran. Fr new scheduled tasks this will be blank. Gedatabase Cnfiguratin Tl (v2018r2) 24
Override-. Fr new scheduled tasks, r yu wish t reset the last run date t trigger the scheduled task t get prcessed again, then yu can check the Override checkbx which will enable the Last Run text bx. Next Run- This indicates the next time the scheduled task shuld be prcessed. The GIS Task Runner service uses this value t determine which scheduled tasks t prcess. Recalc- If the Units, Frequency, r Last Run infrmatin was updated then the Recalc buttn will update the next run date field based upn the new settings. Histry This sectin is read-nly and shws when the Scheduled Task was last picked up, when the sync prcess started and when it last finished. Last Prcess DateTime- The last time the GIS Task Runner prcessed this scheduled task. Last Sync Start- The last time this scheduled task started a synchrnizatin prcess. Last Sync End- The last time this scheduled task ended a synchrnizatin prcess. Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 25
Prcess lg This sectin is als read-nly and shws all lgging related t the previus prcessing f the scheduled tasks. When a scheduled task is prcessed either manually r via the GIS Task Runner service, lgging entries are recrded in GBACmm.CMGISTASKLOG. Entries are remved after 30 days. TimeStamp- The time the entry was inserted Status- Varius descriptins t indicate the prcessing status Edit- 1=Inserts, 2=Updates, 3=Deletes Errr-1=TransactinalDetails, 2=ValidatinFailed, 3=PrcessFailed, 4=ServiceIssue, 5=BusinessObjectIssue, 6=MissingData ErrrDescriptin- Further details regarding the edit r errr ErrrExceptin- Further details regarding errr GUID- The prcessing batch GUID MdID- The Lucity Mdule ID LucityID- The Lucity Recrd ID GISID- The GIS feature s ObjectID Syntax- The syntax used fr either retrieving, updating, inserting r deleting Gedatabase Cnfiguratin Tl (v2018r2) 26
Cpying a Scheduled Task T facilitate the prcess f setting up scheduled tasks fr multiple feature classes, yu can use the Cpy GIS Task tl t create a new scheduled task fr multiple feature classes: 1. In the Lucity Gedatabase Cnfiguratin tl, right-click n the existing Scheduled Task and click Cpy Task. 2. The fllwing frm will appear: a. Nte: GIS Task Prperties are all read-nly. Any item needs t be altered can be dne n an individual basis after the Cpy GIS Task is cmplete. 3. On the frm select the feature class(es) yu wish t create a new Scheduled Task fr using the existing scheduled task prperties. Once the feature classes have been selected click the Assign GIS Task t cmplete the prcess. Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 27
Validate a Scheduled Task A validatin tl is available fr scheduled tasks that will run the fllwing checks. Nte: these same checks are als perfrmed when running the scheduled tasks: Verifies at least ne ptin has been set: insert, update, delete. Verifies there are feature classes linked t parent mdule (fr inspectins nly) Validates Lucity t GIS field mappings Validates list f fields used t determine recrd uniqueness Tests cnnectin t map service fr feature class Validates feature class exists in the service Exprt Validatins Cnfirms feature class is an inspectin feature class Tests cnnectin t parent feature class service(s) If Use Last Sync Date ptin is true- verifies the Lucity mdule cntains a Last Md Dt field If Delete ptin is true- verifies that the Lucity mdule has a Mst Recent Inspectin flag Tests the SQL syntax used t btain the list f Lucity recrds Imprt Validatins If Use Last Sync Date ptin is true- cnfirms that a GIS Date Time Field is defined and exists in the layer in service Cnfirms that the Scheduled Task s Last Sync Date Time is ppulated If feature class cnfiguratin cntains the Lucity Last Sync Date field- cnfirm it exists in layer in service Cnfirms that the Lucity mdule cntains a Last Md Dt field Tests the SQL syntax used t btain the list f GIS recrds frm service Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 28
1. T run the validatins, in the Lucity Gedatabase Cnfiguratin tl, right-click n the existing Scheduled Task and click Validate Task. 2. The validatin will start, nce cmplete yu will receive a prmpt indicating if the validatin passed withut errrs. Any errrs r tests that failed validatin shuld be reprted in the prcess lg results. Manually Run a Scheduled Task The Lucity GIS Task Runner service kicks ff every min and determines if any Scheduled Task is due t run. There may be different situatins in which the Scheduled Task needs t be run manually. 1. In the Lucity Gedatabase Cnfiguratin tl, right-click n the existing Scheduled Task and click Run Task Nw. 2. The fllwing cnfirmatin prmpt will appear. Click Yes if yu want t prceed with the prcess. 3. Once cmplete yu will receive a prmpt indicating if the task cmpleted with r withut errrs. Any errrs r ther prcessing details will be reprted in the prcess lg results. Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 29
Tls The fllwing are varius tls available within the Lucity Gedatabase Cnfiguratin prgram. Gedatabase Cntext Menu Tls There are varius tls available that can be applied n individual feature classes r all feature classes in a gedatabase cnnectin that alter the feature class schema. T use any f these tls yu will be prmpted t enter gedatabase credentials that will have the necessary permissins t make schema changes and yu must be able t acquire an exclusive lck n the feature class. Add a Feature Class Cnfiguratin 1. T add a new feature class cnfiguratin, in the tree n the left f the Gedatabase Cnfiguratin Frm, right-click n the gedatabase nde t which the feature class resides and select Add Feature Class. Nte: This ptin is nt available fr replica gedatabases; instead refer t the Assciate Feature Class(es) tl. 2. The fllwing dialg will appear. Select the asset r inspectin type fr which this new feature class will be linked. 3. The Gedatabase Cnfiguratin Frm will be updated t indicate the new feature type. Yu must enter the name f the feature class befre this new feature class cnfiguratin will be saved. Either enter the feature class name directly, r select it frm the drp-dwn list: 4. Fill ut the remainder f the feature class and field mapping cnfiguratin. T save, simply exit the tl, r click n anther nde. Gedatabase Cnfiguratin Tl (v2018r2) 30
Imprt Feature Classes frm Schema The Imprt Feature Classes frm Schema tl prvides a quick way t cnfigure Lucity t wrk with specific pre-cnfigured gedatabases. This tl has stred cnfiguratins based n linking Lucity t the Esri Lcal Gvernment Infrmatin Mdel and Lucity gedatabase schemas. This tl des nt create the feature classes in the gedatabase. It simply creates cnfiguratin recrds in the Lucity gedatabase cnfiguratin t recgnize feature classes and fields based n ne f these standardized schemas. This tl des nt create r update any Dmains. This must be dne after the imprt using the Dmain Cnfiguratin tl. T imprt feature class cnfiguratins frm a default schema: 1. Right-click n the gedatabase cnnectin nde that cntains the feature classes yu wish t lad the mappings fr and click Imprt Feature Classes frm Schema. 2. The fllwing frm will appear: Gedatabase Cnfiguratin Tl (v2018r2) 31
3. Select a schema. Yu can either select a Lucity gedatabase schema r an Esri s Lcal Gvernment Infrmatin Mdel schema. 4. Select the schema versin/release. Fr Lucity, this will be the Lucity versin number (7.4, 7.5, 7.6, etc.) Fr Esri, this will be the versin fllwed by the release date. Fr example, there have been tw releases f the 10.1 Lcal Gvernment Infrmatin Mdel, ne n 7/12/12 and 11/5/12, these will be listed as 10.1_071212 and 10.1_110512. 5. Select the feature class(es) yu wuld like t lad the schema mappings fr. 6. Preview by selecting a specific feature class n the left side. The Field Mappings grid will shw which fields in the feature class will be mapped t which fields in Lucity The Spatial Relatinships grid will shw the default spatial relatinships fr the feature class Nte: Yu are unable t mdify the defaults at this time. Hwever, nce yu imprt the schema, yu can then mdify the feature class cnfiguratin just like any ther feature class. 7. Click the Imprt Schema Mappings buttn nce yu are ready t imprt the settings 8. The Validatin results windw will appear and prvide feedback n the imprt prcess. Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 32
Delete Multiple Feature Classes Lucity versins prir t 7.5 were ppulated with the Lucity gedatabase schema. Yu may find that yu are nt using the Lucity default gedatabase schema r yu may nly be implementing a few f the feature classes. Instead f deleting these feature classes ne by ne, yu can use the Delete Multiple Feature Classes tl t perfrm a mass delete. 1. Frm the tree n the left f the Gedatabase Cnfiguratin Frm, right-click n the gedatabase nde that cntain the feature class mappings yu wish t delete and select Delete Multiple Feature Classes. 2. The fllwing dialg will appear. Check all prducts yu wish t delete the feature classes fr. 3. In the grid n the right, the prgram autmatically checks all feature classes that are assciated t the selected prduct type. If yu wish t ver-ride the default selectins check the Edit default selectin checkbx. 4. Click OK t delete the marked feature class cnfiguratins. Imprt Feature Class Alias Names Aliases are alternate names fr feature classes that prvide a unique identity. They are used by the Lucity Webmap, Lucity Viewer, Lucity Mbile fr Andrid, and any ther Lucity GIS applicatin that interacts with map/feature services t identify which feature classes are linked t Lucity. These Lucity mapping applicatins check the feature classes laded int them and check the display names f thse feature classes against the aliases names listed in the Gedatabase Cnfiguratin. Aliases can be setup in a few different ways. This tl is designed t update the gedatabase cnfiguratin with the default alias names fr the gedatabase cnnectin as listed in ArcCatalg. Gedatabase Cnfiguratin Tl (v2018r2) 33
1. Select the gedatabase cnnectin r the feature class nde 2. Right click n the selected nde and select the Imprt Feature Class Alias Name(s) tl 3. The imprt will start immediately, and a lg screen will appear that prvides additinal infrmatin including imprt errrs. Set Update Length/Area Flag t True By default, when yu add a new feature class the Update Length/Area flag is set t false. This prperty determines if the feature class s field linked t the Lucity length/area field shuld be updated with the Esri shape length/area if the gemetry is mdified in the map. Yu may wish t ensure that all feature class cnfiguratins have this prperty set t true. Instead f inspecting each feature class cnfiguratin individually t check this value, yu can run this tl t set the value t true fr all feature classes. 1. Frm the tree n the left f the Gedatabase Cnfiguratin Frm, right-click n the gedatabase nde that cntains the feature class cnfiguratins yu wish t update and select the Set Update Length/Area Flag t True. Nte: This ptin is nt available fr replica gedatabases 2. The fllwing dialg will appear fr cnfirmatin: Gedatabase Cnfiguratin Tl (v2018r2) 34
Update Feature Class Services Use this tl t facilitate the prcess f defining feature class level services fr multiple feature classes: 1. In the Lucity Gedatabase Cnfiguratin tl, right-click n the gedatabase nde that cntains the feature classes in which yu want t assciate t a service and select Update Feature Class Services. 2. The fllwing dialg will appear. 3. Select either the Gedatabase map service r an Alternative feature service. a. Nte: The Alternative feature service drp dwn will nly cntain services defined as editable in UI Admin GIS Services mdule. b. The Assigned Feature Classes list will shw the feature classes currently assigned t the selected service. c. The Unassigned Feature Classes list will shw the feature classes currently nt assigned t the selected service. Items in red indicate the feature class has anther service defined at the feature class level. Gedatabase Cnfiguratin Tl (v2018r2) 35
4. Select the feature class(es) frm the Unassigned Feature Classes list that yu wuld like t assciate t the selected service. a. Alternatively, yu culd select feature class(es) frm the Assigned Feature Classes list t disassciate them frm the selected service. 5. Use the << and >> t assciate and disassciate the selected feature classes. Once dne, click the Save buttn. Feature Class Schema Tls There are varius tls available that can be applied n individual feature classes r all feature classes in a gedatabase cnnectin that alter the feature class schema. T use any f these tls yu will be prmpted t enter gedatabase credentials that will have the necessary permissins t make schema changes and yu must be able t acquire an exclusive lck n the feature class. Gedatabase Cnfiguratin Tl (v2018r2) 36
Add Lucity AutID Field Starting with versin 7.1, this field is n lnger required; hwever, fr best perfrmance it is strngly recmmend this field exists in each feature class. Once the field is added and mapped t Lucity, the Lucity extensin will maintain it. It requires n data input frm the user. Use this tl t create this field in yur feature class(es) and map it t Lucity. Add Lucity In DB Field Starting with versin 7.1, this field is n lnger required. It is a simple Blean field that indicates if there is an assciated feature in the Lucity database. Once the field is added and mapped t Lucity, the Lucity extensin will maintain it. It requires n data input frm the user. Use this tl t create this field in yur feature class(es) and map it t Lucity. Add Mdified/Synched Fields This tl can be used t create 3 fields in yur feature class(es): Last Mdified Date, Last Mdified By, and Last Synch Date. Once these fields are added and mapped t Lucity, the Lucity extensin will maintain them. It requires n data input frm the user. Add/Remve Attribute indexes Use this tl t add r remve attribute indexes t a field in yur feature class. This is primarily fr unique ID fields (Lucity Aut ID r Cmmn ID) t ptimize prcessing and speed up the perfrmance f Lucity GIS tls. 1. If yu are using an enterprise gedatabase, yu will be prmpted fr yur admin credentials: Gedatabase Cnfiguratin Tl (v2018r2) 37
2. If yu run this tl against an individual feature class, rather than the entire gedatabase, an additinal ptin is given t add r remve an index frm any f the fields in the feature class. Otherwise, yu nly have the ptin t add r remve the index frm each feature class s Lucity Aut ID and/r Cmmn ID fields. 3. Results f prcessing are written t the validatin windw. 4. Here is an example f attribute indexes created by the tl: Gedatabase Cnfiguratin Tl (v2018r2) 38
Set Field Alias Equal t Lucity Field Captins This tl can be used t update the alias name fr the feature class fields linked t Lucity. The alias names will be updated t match the Lucity field captins. Set Feature Class Alias Equal t Lucity Mdule Name This tl can be used t update the alias name fr the feature class linked t Lucity. The alias names will be updated t match the Lucity mdule name. Fr example, a feature class linked t the Sanitary Structure Inventry mdule will have its alias updated t Sanitary Structure. Dmain Tls Dmain Cnfiguratin Fields in the gedatabase that are linked t a Lucity Cde/Type field (pick list) shuld cntain a gedatabase dmain. A dmain prvides the same functins in ArcMap that a picklist prvides inside f Lucity. Dmains ensure data integrity and help with data ppulatin during an edit sessin. T ensure data integrity between Lucity and the Gedatabase the picklist values shuld match up t the dmain values. The Dmain Cnfiguratin Tl in the Gedatabase cnfiguratin allws users t quickly cmpare dmains t picklists and fix and differences between the tw. 1. T access the Dmain Cnfiguratin screen, right-click n either a gedatabase r feature class nde in the tree lcated n the left-hand side f the Gedatabase Cnfiguratin brwser. 2. If yu are integrated with an enterprise gedatabase yu will be prmpted with the fllwing: This screen is asking the user t lgin as the Dmain Owner. Dmains within a gedatabase can nly be edited by the riginal creatr (dmain wner). Often, nt even system admin accunts can edit a dmain if they weren't used t create it. Make an authenticatin chice and enter the username and passwrd if needed. Click OK. Gedatabase Cnfiguratin Tl (v2018r2) 39
3. When this tl is run it validates the Lucity picklists and GIS dmains fr all fields mapped between the tw systems. The validatin prcess is tracked and displayed in the resulting dialg: 4. The tp sectin shws the validatin prgress and can be reviewed by using the scrll n the right. The bttm sectin prvides the results in a tabular frmat allwing yu t easily review and reslve any cnflicts. 5. Click the Manage buttn t assist with the reslutin f any cnflicts. Reslve Dmain Discrepancies 1. After clicking the Manage buttn n the Dmain Cnfiguratin grid results the fllwing frm will appear: Gedatabase Cnfiguratin Tl (v2018r2) 40
The grid n the tp left shws the GIS dmain values. The grid n the tp right shws the Lucity picklist values. Discrepancies are shwn in red. Within this windw yu can: add/edit/delete GIS dmain values, add/edit/delete Lucity picklist values, reppulate the GIS dmain values t match Lucity, and reppulate the Lucity picklist values t match the GIS dmain. The GIS Cde field is used t link a Lucity Value t a Dmain value with a different cde. This is used when neither the picklist nr dmain values can be changed. It can als be used t link tgether number picklists/dmains t alpha-numeric nes. When Shw current values and recrd cunts is checked, tw read-nly grids appear at the bttm allwing yu t view which f the dmain s values are currently being used in GIS (left) and Lucity (right), and hw many recrds in each are using them. 2. After making changes yu must click Apply Changes buttn at the bttm f the grid fr the changes t save. 3. Click Clse when yu are finished. Yu will be returned t the Dmain Cnfiguratin results frm. Nte: The dmain yu just mdified will still be listed as having a discrepancy. Yu must click the Revalidate buttn n the tp menu if yu wish t have the frm refreshed. Update GIS Dmains t match Lucity picklists Yu can perfrm a mass update that will verwrite all the GIS dmains with values frm the related Lucity picklists. If a dmain desn t exist fr a field, it is created in the gedatabase and linked t the feature class field. By default, the dmain name is given the Lucity table name and Lucity field name. Fr example, if a GIS field is mapped t sewer pipe s material field the assigned dmain name will be SWNET_NT_MAT_CD. If multiple feature classes are mapped t the same field and there isn t already a GIS dmain assigned t these fields this tl will nly create ne dmain and assign it t all GIS fields linked t the Lucity field. If the GIS field type desn t match the Lucity field type (GIS field is text, Lucity is numeric r vice versa), the Lucity GIS Cde is required befre the GIS dmain can be updated. Gedatabase Cnfiguratin Tl (v2018r2) 41
1. Frm the Dmain Cnfiguratin Results frm, click Sync Dmains>>Update GIS dmains t match Lucity picklists. 2. The tl will start prcessing the GIS dmains, results are shwn in the upper sectin f the Dmain Cnfiguratin windw. Please refer t the results fr any issues. Update Lucity picklists t match GIS Dmains Yu can perfrm a mass update that will verwrite all the Lucity picklists with values frm the related GIS dmains. If a Lucity picklist value is hardcded (unable t be altered) the tl will attempt t find the equivalent GIS dmain cde using the descriptin. If it finds the matching GIS dmain value it uses the Lucity GIS cde field t stre the crrespnding GIS dmain cde. If the GIS field type desn t match the Lucity field type (GIS field is text, Lucity is numeric r vice versa), the Lucity GIS Cde will be used t stre the crrespnding GIS dmain cde. The Lucity picklist cde will be autmatically assigned a sequential number. 1. Frm the Dmain Cnfiguratin Results frm, click Sync Dmains>>Update Lucity picklists t match GIS dmains Gedatabase Cnfiguratin Tl (v2018r2) 42
2. The fllwing prmpt will appear. Select Yes, if yu want t delete Lucity picklist values that aren t in the GIS dmain. 3. The tl will start prcessing the Lucity picklists, results are shwn in the upper sectin f the Dmain Cnfiguratin windw. Please refer t the results fr any issues. Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 43
Update Parent Linking Dmains In many feature classes there will be fields that link a feature t a related feature in anther feature class. It des this by string the related feature's LucityID. Fr example, a park bench might stre the ID f the Park that it is in. This prvides imprtant cnnectin infrmatin fr Lucity but is less useful t users because it just displays a number. The Update Parent Linking Dmains tl creates user-friendly dmains fr these fields. While the field will still stre the linking ID, the dmain culd display parent recrds: Facility ID number, Name/Descriptin, Facility ID and Name/Descriptin, r Name/Descriptin and Facility ID. 1. T update parent linking dmains, right-click n either a gedatabase r feature class nde in the tree lcated n the left-hand side f the Gedatabase Cnfiguratin brwser and select Update Parent Linking Dmains 2. The fllwing prmpt will appear. 3. Select the descriptin ptin and click OK. a. Nte: When the D nt shw this prmpt again ptin is checked any additinal parent linking dmains that are cnfigured at this time will use the same ptin. 4. If there currently is nt a dmain assigned t the GIS field the fllwing prmpt will appear. Click Yes. 5. The dmain will be created and/r updated. The prcess will be updated in the Validatin Results windw. Gedatabase Cnfiguratin Tl (v2018r2) 44
Update Street Name Dmains Lucity breaks ut street address infrmatin int the fllwing fields: Building number, building suffix, street directin, street prefix, street name, street type, and street suffix. These fields in Lucity are assciated t a library which requires them t be handled a little differently than a typical Lucity picklist. T ensure data integrity it is highly recmmended that yu cnfigure a GIS dmain fr these fields that match the crrespnding Lucity picklist. 1. Right click n yur gedatabase nde in the tree lcated n the left-hand side f the Gedatabase Cnfiguratin brwser and select Dmains>>Update Street Name Dmains (r MUTCD r Tree) 2. After yu click Update Street Name Dmains, yu will be prmpted t chse the dmain wner. 3. Chse a dmain ptin and click OK. A series f messages like the fllwing will appear: 4. Click Skip, Select, r Create New t navigate thrugh each dialg. If the dmain desn t already exist, yu can chse the Create New ptin fr the tl t create the dmain 5. When yu click Select n the last dialg, the validatin results will be generated. Gedatabase Cnfiguratin Tl (v2018r2) 45
All street name dmains are created using the values as they are defined in the Lucity Street Name List. The fllwing shws an example f what is created fr each dmain: Street Directin (Lucity.StreetNameDirectin) Nte: this dmain will autmatically get assciated t all fields linked t a Lucity street directin field (typically *_ADR_DIR) Street Prefix Type (Lucity.StreetNamePrefixType) Nte: this dmain will autmatically get assciated t all fields linked t a Lucity street prefix directin field (typically *_ADR_PT) Street Name (Lucity.StreetNameName) Nte: this dmain will autmatically get assciated t all fields linked t a Lucity street name field (typically *_ADR_STR) Street Type (Lucity.StreetNameType) Nte: this dmain will autmatically get assciated t all fields linked t a Lucity street type field (typically *_ADR_TY) Gedatabase Cnfiguratin Tl (v2018r2) 46
Street Suffix (Lucity.StreetNameSuffix) Nte: this dmain will autmatically get assciated t all fields linked t a Lucity street suffix field (typically *_ADR_SFX) Street Name Cmpsite (Lucity.StreetNameCmpsite) Nte: this dmain will autmatically get assciated t all GIS cmpsite street name fields. These are GIS fields that have been mapped t Lucity using the cmpsite ptin (green line shwn belw) Street Name List (Lucity.StreetNameList) Nte: this dmain will autmatically get assciated t all fields linked t a Lucity street list field (typically *_ADR_ID) Gedatabase Cnfiguratin Tl (v2018r2) 47
Update Street Light, MUTCD, and Tree Dmains Fields in the gedatabase that are linked t Lucity fields string the fllwing infrmatin shuld have a special dmain assigned: Street light library cdes Street sign cdes (MUTCD) Tree cdes These fields in Lucity are assciated t a library which requires them t be handled a little differently than a typical Lucity picklist. T ensure data integrity it is highly recmmended that yu cnfigure a GIS dmain fr these fields that match the crrespnding Lucity picklist. 1. Right click n yur gedatabase nde in the tree lcated n the left-hand side f the Gedatabase Cnfiguratin brwser and select Dmains>>Update Street Name Dmains (r Street Light, MUTCD, r Tree) 2. After yu click Update Dmains, yu will be prmpted t chse the dmain wner. 3. Chse a dmain ptin and click OK. A series f messages like the fllwing will appear: 4. Click Skip, Select, r Create New t navigate thrugh each dialg. If the dmain desn t already exist, yu can chse the Create New ptin fr the tl t create the dmain Gedatabase Cnfiguratin Tl (v2018r2) 48
5. When yu click Select n the last dialg, the validatin results will be generated. 6. If updating a Tree dmain, yu will get ne extra prmpt t select tw fields (separated by a dash - ) t be used as the dmain s descriptin. The Tree Library cde will be used as the dmain s cde. Update Wrk Categry, Maintenance Zne, and Alternate Zne Dmain A dmain tl exists fr creating a dmain fr GIS fields linked t the Lucity default wrk categry field (*_BR_CD), maintenance zne field (*_MZONE_CD), and alternate zne field (*_AZONE_CD). These fields are used t assign a default wrk rder categry, maintenance zne, r alternate zne, s when a wrk rder/request is created against the asset it will autmatically be assigned t that categry f wrk, maintenance zne, and alternate zne. Since these fields are nt typical cde/type picklists, the standard Dmain cnfiguratin tl will nt wrk fr these fields and requires the use f these tls. These three ptins wrk the same, s here is ne example using the update wrk categry tl: 1. In the Lucity Gedatabase Cnfiguratin tl, right-click n the gedatabase nde and select Dmains>>Update Wrk Categry Dmain. 2. The fllwing dialg will appear: Gedatabase Cnfiguratin Tl (v2018r2) 49
3. The dialg is prmpting fr dmain wner credentials. Dmains within a gedatabase can nly be edited by the riginal creatr (dmain wner). Enter the prper credentials and click OK 4. The fllwing message will appear asking fr the dmain that crrespnds t the default wrk rder categry cde. If this is the first time the tl has been ran and yu currently dn t have a dmain created, click the Create New buttn; therwise select the existing dmain and click Select. 5. Once cmplete a prmpt will appear and yu can view details regarding the prcess in the results windw. The fllwing shws an example a Lucity.WrkCategry dmain created by the tl: Gedatabase Cnfiguratin Tl (v2018r2) 50
Validatin Tls Once a gedatabase is cnfigured it is gd idea t check t make sure that there are n prblems with links between Lucity and the gedatabase. This helps ensure that all the expected data will be transferred. T run a check there is a Validate tl within the gedatabase cnfiguratin. This tl can either be run against the entire gedatabase r an individual feature class. Validatins in the Lucity Gedatabase Cnfiguratin tl nw include checks against map and feature services. One way t validate a service is t run the Test Cnnectins buttn fund in the Edit Map Service sectin f the Cnnectin Prperties tab fr the gedatabase. This test will: Validate a cnnectin can be made t the service with the URL and credentials prvided Analyze each layer wihin the service t determine if it has a cnnectin t Lucity. Results, including any errrs, are reprted in the validatin results frm. An example f the results are shwn belw. Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 51
The ther map and feature service tests ccur as part f the Validatin tls that are available in the gedatabase and feature class menus. There are three parts f this validatin: 1. Validates setup in Lucity. This part checks t make sure required fields are ppulated, and Lucity fields are valid. 2. Validates setup in gedatabase. This includes testing the cnnectin t the gedatabase. Validates that the feature class exists, fields exist, data types are cmpatible, etc. 3. Validates setup in map service. This test is skipped if bth the Use Feature Service Fr Updates and Enable Lucity Spatial system settings are FALSE. This sectin will validate the fllwing: a. A cnnectin can be made t the service. b. The feature class exists in the service c. The feature class fields exist in the service and validates a sample paylad Part f the service validatin is t verify the service layer fields exist. The Lucity tls interact with services using the Esri REST API, in which field names are case sensitive. If a cnflict in case is fund during the validatin a prmpt like the fllwing will appear: Gedatabase Cnfiguratin Tl (v2018r2) 52
Yes- will update the case in Lucity. N- n changes will be made. Nte- this may cause failure when attempting t read r update that field via the map service. Cancel- n changes will be made, and further case cnflicts will be ignred fr this validatin run. Once the validatin prcess is cmplete yu will receive a prmpt indicating if the validatin passed r nt. Refer t the validatin results windw fr specifics. The fllwing is an example f the validatin results: Ntes: Gedatabase Cnfiguratin Tl (v2018r2) 53
Integratin Summary Reprt Smetimes it can be helpful t have a cncise verview f hw a feature class is linked t Lucity. This is accmplished using the Integratin Summary Reprt tl. This tl generates a Crystal reprt f all f a feature class s infrmatin that pertains t its integratin with a Lucity mdule, such as (but nt limited t): assciated wrkspaces, field mappings, number generatrs, spatial relatinships, and scheduled tasks, and all relevant details within each. 1. T launch an integratin summary reprt, simply right-click the gedatabase r the feature class, and select Integratin Summary Reprt. 2. If ran against an individual feature class, the reprt will nly cntain ne page fr that feature class. If ran against the entire gedatabase, the reprt will cntain as many pages as there are feature classes linked t Lucity. Gedatabase Cnfiguratin Tl (v2018r2) 54