Hi,
The 'Edit Action' button allows for users to manually or automatically update 1 or more fields in Tasks.
This action also validates against the Form present on the Tasks layer. Meaning if you have a required question in the Form and the field is null, the Edit Action button won't work in Field Maps. A validation error will be returned as the Form attribute requirements are not met - even though we aren't using the form.
For example, if I add a 'comments' field and make that required, the PickUp button doesn't work if the comments are null. But we don't expect the users to be populating that field when they are picking up the job.
This was lodged as a bug but closed 'as designed' (BUG-000181344).
I understand the expectation is that conditions should be used in addition to the requirements. However:
- This constrains a large number of workflows, or requires convoluted conditional requirements not based on a simple linear task status progression
- The requirement is not documented and non-intuitive to Field Maps designers or users
I just want the button to do what it's designed to do - change the assigned username - without having any validation against the Form itself. It's a different user editing experience.
Cheers,
Chris
