Multiple Button Bar issue; validation on 'cancel/back'
Is there a 'best practices' for button bar? only one per display?
I've attached an example where i tried to put two of this activity in one Display form. There is a 'Back' button on top, and a 'Submit' button on the bottom...
The back button is setup as not the default, and to not cause validation,
The submit button is setup as default and to cause validation.
Other oddities:
- Multiple buttons can be set as the 'Default' button... (not a big problem, but Designer should either prevent (radio button) or warn?
- I noticed, while trying to move one of my button bars, that it would update in the Designer, but not when run through the viewer, and the button didn't respond to 'enter' even though it was the default... In this scenario i completely removed the button bar, and re-added and the issues went away.
-
Hello Ryan,
The Button Bar form element has been the source of many discussions and may change in the future. I'll file the issues that you've mentioned as this is currently not functioning correctly.
You should be able to use multiple Button Bars on a form.
Out of curiosity, in the second oddity that you mentioned, was this based on an old workflow (e.g. a workflow created a month ago)?
Thanks, Stefan
0 -
Yes it was one of the first workflows i setup. (still in Beta)
0 -
There is potential for outdated configuration from the Beta to still be present, but I've filed an issue to look into it as well.
0 -
Is there a way to clear/clean Beta Items?
I did some more moving around, and my Button Bar is misbehaving again... Now i can't seem to leave the DisplayForm without it 'Validating'
0 -
You could use the Create Date as specified in AGOL for the workflow for any workflows prior to August 30, 2017.
0 -
Maybe its the way i asked it,
Are you recommending, i delete any items prior to that create date? Re-import from JSON good enough or start-fresh...
Hack fix: The broken 'buttonbar' offending button, was missing a 'validates' property, i added it manually to the json and it seems to work now...
0 -
I haven't seen any specific issues from workflows within the Beta period. I don't think re-importing them would resolve this issue but starting fresh may.
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
7 commentaires