Flag inspections that have moved forward in the ETL

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

Flag inspections that have moved forward in the ETL #231

Closed talllguy closed 6 years ago

talllguy commented 6 years ago

Related to #219

Consider flagging submitted (ETL3) inspections so if there are ongoing inspections from the same firm, inspectors don't inadvertantly edit the submitted inspection. A flag field could be ignored automatically by Survey123 inbox, e.g. WHERE FIRM_NAME = 'KCI' AND SUBMIT_FLAG IS NULL, where SUBMIT_FLAG is the attribute that controls the workflow.

Otherwise, how do the existing ones not get resubmitted?

talllguy commented 6 years ago

Sounds like the GDB_TO_DATE field is this flag! John explains in https://github.com/kcigeospatial/MDOT-SHA-NPDES-Next-Gen/issues/219#issuecomment-391567463

That explanation closes this issue. Thanks, @johnshiu !