We created a Behaviour for our Service Desk "Create Request" form that populates some read-only fields based on the content entered in a text field.
The problem is that if the end-user enters a value to the text field then clicks directly on 'Create', the "create" request is sent to the server before the read-only fields are updated.
We can see that the Behaviour is executed because the fields are updated before the screen transitions, but it's as if the browser didn't wait for the Behaviour to complete execution before firing the "create" request.
This causes an immediate problem for when the read-only fields were initially empty, as they're mandatory. The "create" request is refused saying that these fields must be filled, which is confusing since the user sees values in them.
But it can get worse if the end-user modifies the text field after having entered something valid. The request could actually be created with the wrong, previous values.
Any ideas on how to solve this pickle?
Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their Jira Cloud instance. ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events