search

kcigeospatial / MDOT-SHA-NPDES-Next-Gen

Code and issues related to the MDOT SHA NPDES Project. Project codes: Config = 31, Management = 32.
0 stars 0 forks source link

Tell users not to edit the Inspection Lifecycle fields #442

Closed talllguy closed 4 years ago

talllguy commented 4 years ago

Andrew, while working on #434 I noticed someone at WBCM had editing the lifecycle fields somehow. This should never happen as these fields are meant to be updated automatically via Survey123 or the ETL. Do you have any idea how they were able to edit them? The Survey123 tool doesn't allow it, so I have a feeling they have pulled in the Survey123 feature service.

chrome_AlWboG5Iwt

Please let all the firms know not to update these.

KCI-Ablowers commented 4 years ago

@talllguy the issue above is them removing the "2019" from the Lifecycle Date correct? That field is editable in Survey123 because of the hint "The year of this inspection. Only update if told by SHA." We should update the label and or hint to indicate this is intended to be the task/project/phase year range. I can see where a user maybe be confused and decide to update even though the warning is there.

image

talllguy commented 4 years ago

Ah, you're right. Curious how that particular highlighted one had the fields populated despite being 3.3.7, right? That makes sense. In the next email, would you let them know not to mess with those? The filters in the dashboard are based on that field.

KCI-Ablowers commented 4 years ago

Ah, you're right. Curious how that particular highlighted one had the fields populated despite being 3.3.7, right? That makes sense. In the next email, would you let them know not to mess with those? The filters in the dashboard are based on that field.

Agreed, it seems odd that it did not work that way in my testing. I will make a note to notify the crews of this when we deploy the tracker to all prod maps.