Disable Sapling/Tree Tag Fields Unless Tag Selected

[blcampbell]

Tag fields should be disabled until a tag has populated, otherwise clicking in fields can lead to errors since the record has not been populated.

Recommend that all fields to the right of the tag # should be disabled until this number is populated.

This prevents inadvertent clicking and the need to handle errors when a record isn't populating this section of the event form for saplings or trees.

[blcampbell]

@abrolis , @johnpauls , @lizmatthews03 -

Do you see any issues w/ disabling these fields before the tag is selected?

The issue is mainly one that appears during testing, but could occur for new field crewmembers.

Won't release this until 2020 release 2 at the earliest.

[abrolis]

@blcampbell I don't see any reason that these fields need to be active prior to selecting a tag for data entry.

[johnpauls]

@blcampbell That also looks good to me -but I am not exactly sure from the screen shot what part of the front end this is referring to.

[blcampbell]

@johnpauls The screenshot is the section of the event form which falls below where a user chooses either an unsampled tag or one that has already been sampled. There are 2 versions - one for saplings, one for trees.