Dynamic Value Table Changes

[tnjtr2]

Dynamic Value Table - https://solutions.arcgis.com/shared/help/attribute-assistant/documentation/methods-all-methods/

• [ ] Add Pole Number to Luminaires (Signals? Bike/Ped Signals)
• [ ] Arm autopopulates Circuit_Number?
• [ ] Camera autopopulates Circuit_Number
• [x] --Pole autopopulates the Base Type?-- (Not appropriate, since this is referring to what exists in the materials)
• [ ] SLCabinet autopopulates Circuit_Number?
• [ ] Cable populates Start/End on Geometry change?
• [ ] How do we get Circuit Number to autopopulate on more assets?
• [ ] Rethink when "attached_to" field populates on all assets. Should it be on Create, Geometry and Manual?
• [ ] Electrical Sign autopopulates Signal Cabinet Number
• [ ] Arm AngleStopLight and AngleG should update with Geometry
• [ ] Trench, conduit and cable should autopopulate start/ends on poles and fiber termination where there is no access point base
• [ ] Bike Ped signal attaches to old pole. What might be different about these rules?
• [ ] Luminaires only attached to old pole. What might be different about these rules?
• [ ] URDs Fixture_Type are strings limited to 5 characters
• [ ] Can trench ends not connect to SL and Sig Cabinets?
• [ ] Can conduit ends not connect to SL and Sig Cabinets?
• [ ] Can trench start/end on trench?
• [ ] _INTERSECTING_FEATURES_
  • [ ] Should all line start and ends operate with the SP and EP methods?
  • [ ] Should all point features operate with the H method?
• [ ] EVP should be attached to Arms
• [ ] Electrical Sign autopopulates angles on arms