Posted: 11 May 2016 4:47 EDT Last activity: 1 Jun 2016 9:20 EDT
OnChange event is triggered at the same time attempt to run Flow-action
There is such a situation: in the section, there are two properties (let's call them A and B) and the "Submit" button. On event OnChange in property A, property B will computed. By clicking "Submit" is performing validation properties property B. When the user is entering some value into the text field in property A, and, without taking over from the field, hit "Submit" button, OnChange event is triggered at the same time attempt to run Flow-action, and, as a consequence, with validation. Because OnChange processing is not time to change the context, the validation does not work properly and the user leaves the form of a blank field B.
Could you tell me, please, what I can resolve this problem in solution.
I think the problem can be solved by blocking the "Submit" button for the user triggered Pressed Any Key events for the field A. If it is the normal solution, tell me, please, how it can be done.
Message was edited by: Marissa Rogers - Added Category, moved from Mesh Help
Without tabbing out of property A if we directly submit the button, click event itself will not be honored. For some reason both of them are getting fired for you. Can we have disabled when condition on the button based on property B ?
The operator put some value in prorerty A. After that he leaves focus from A. It's cause calculating an filling property B immediatelly. Next. He put new value in property A and press button "Submit". In this case value of property B doesn't calculate and form closes.
On Change of Property A, call 2 actions - Run Script and refresh Section. In run script action, call setBusyIndicator function, which will display a Throbber image on screen. then refresh section will update the UI with the current value.
So, when users clicks on Submit button, the validation configured would considered the latest value.
Please let me know whether it works for your use-case or not.
Glad to know that you have found the resolution for the issue. Appreciate you taking time to update the thread with this information. Sharing the solution on the community will help users who come across a similar question.