Lifecycle Status Coded Value Domain

The Lifecycle Status field requires a Coded Value Domain to properly map the description of the field to a target string value (this is covered in the Special Treatment of Lifecyle Status topic).

To configure the domain, follow the steps below. Note, Steps 1–6 are the same as creating any Coded Value Domain (this is covered in the Coded Value Domains topic), and they are included here for convenience. Configurations that are unique to the Lifecycle Status start at Step 7.

1. In Solution Center > Feeder Services > GIS Schema > Coded Value Domains, click the Add Coded Value Domain button.

2. Under Create Coded Value Domain, choose the geodatabase layer you would like to map, then choose the lifecyclestatus field.

   

3. For the Designer Domain, choose the LifecycleStatusType field.

   

4. Determine whether this domain mapping satisfies all subtypes or not. By default, all subtypes are selected.

   1. If you need to specify subtypes, click the Edit tool.

   2. Uncheck subtypes to remove them from the list.

   3. Click Apply.

5. Determine if this domain mapping should be the default for this feature class and field. If so, set Default to True.

   

   IMPORTANT: What does this default mean? First, if this domain mapping satisfies all subtypes, then this setting is actually unnecessary. It does no harm to set this case to true, but leaving it false also works. The default matters when you are dividing subtypes between different domain mappings. In that case, you need to choose which mapping acts as the default in case there is a subtype that was not accounted for in the schema. As an example, if there is more than one mapping for conductor material and streetlight conductors were never mapped, they use the default mapping. For consistency, we recommend setting a default domain mapping for all feature and object classes (even if the mapping satisfies all subtypes as described above).

6. To start mapping the individual domain values, next to Entries click the Add button.

7. For each coded value, choose the Designer Value, then map it to the appropriate Esri Name.

   

   
   

   For Lifecycle Status, the application offers these values out of the box:

   • Unknown

   • In Service

   • Out of Service

   • Proposed

   • Planned Installed

   • Planned Removal

   • Planned Uninstalled

   • Proposed for Removal

   • Proposed Retried

   • Removed

   • Retired

   • Under Construction

   • Abandoned

   • Decommissioned

8. If the values above do not satisfy your needs, you can add company-specific values. To do so, follow these substeps:

   1. Next to Entries click the Add button.

   2. Notice the new entry includes an Add Custom LifecycleStatusType button.

      

   3. Click the Add Custom LifecycleStatusType button.

   4. Type the custom type name (the image below is just an example), then click OK.

      

   5. Map the custom type to the appropriate Esri Name, as usual.

   6. Repeat adding custom types, if necessary.

9. When finished mapping the Coded Value Domain fields, click Save.