JMurk / Valve_Hydrant_Mobile_Issues

Water Valve Status Mobile Issues
0 stars 0 forks source link

Hydrant: Toggle between map and hydrant info: lose unsaved message #53

Closed rssidlowski closed 8 years ago

rssidlowski commented 8 years ago

When navigating between the map and the hydrant info pages, get prompted with the message below even if not editing (did not select the Edit button): loseunsaved

The system should not prompt with the message unless there are actually unsaved changes.

I clicked on the OK in the above and now unable to toggle to the map.

kanglu666 commented 8 years ago

this is how the app navigation designed. whenever you leave the form it shows the message.

rssidlowski commented 8 years ago

Is this correct behavior?

JMurk commented 8 years ago

That is probably how it was implemented, however for the user's convenience it should only prompt when there are unsaved edits.

rssidlowski commented 8 years ago

Lu, can you correct this?

yousifmalik commented 8 years ago

I added the code logic to detect any changes to form fields but the message still shows. Debugging it more, when identifying hydrant and switch to another tab (For example "Plans" or "Locate"), I found that the following fields are auto populated and therefore enable the message: OBJECTID HYDRANT_ID INSP_BY INSP_ORG INSP_DATE STATUS

When select item from history and enable edit without making any changes and navigate to another tab, all above fields and the following fields marked as changed fields: INSPECTION_ID GIS_VERIFICATION

Do we need to exclude these fields?

rssidlowski commented 8 years ago

Don't want to exclude these fields. I will try to get clarification on the workflow this afternoon and provide more clear guidance.

rssidlowski commented 8 years ago

This may no longer be an issue if the workflow is redone to default to most recent history inspection instead of having a new inspection when click on the arrow from the identify results. See #65.

slmessier commented 8 years ago

this issue does not apply due the current workflow having been updated. Since this issue no longer applies it will be closed.