BrittanyHuber
commented
9 years ago tested in SHA DEV - all site selection features were succesfully pipelined into assets and verifed that they were created as assets within the selected version
Closed BrittanyHuber closed 9 years ago
BrittanyHuber
commented
9 years ago tested in SHA DEV - all site selection features were succesfully pipelined into assets and verifed that they were created as assets within the selected version
A few issues were encountered with the piplining process in SHA DEV.
Step 5 of the process "Review Information" the SSID is presented as the GUID string instead of the 7 digit/two letter code (ie. 1200001UT). When pipelinign a swale the "Planned ID" is presented as the GUID. Also, the Strategy Type is still the coded value (ie. FPU) instead of planting trees/urban tree planting.
When searching by Site Selections > All Site Selections > then selecting a feature to pipeline, the system only presents you with the options of the last feature you pipelined. For example, if you pipelined a tree site last then the system will present only LUCHANGE_BMP options to pipeline. If you select Impervious surface removal from this list, the system then presents you with every feature from the search results instead of just the pavement removal feaures.
Outfalls - take a while to pipeline EFF_BMP's/Retrofits - unsuccessful attempts to pipeline Streams - unsuccessful attempts to pipeline All other site selection types were successfully added, however I was unable to verify that the features were actually created into assets.
Dialog boxes that pop up to either tell the user that the feature has successfully been pipelined or failed to pipeline have to be clicked out of 3-5 times before they disappear.