required checkbox
Peter_Miklian
Customer Advanced IT Monkey ✭✭✭
Hi,
we need to publish Request offering which won't allow user to create service request while they don't accept some terms.
But if we create required 'I agree' checkbox, ticket can be saved while leaving the checkbox unchecked, too.
The 'best' which I found out so far is required simple list (dropdown) with just 1 value 'I agree' :) Could you please advise how you handle such situations when you need user to accept license etc.? Thanks
Best Answers
-
Jeff_Lang
Customer Advanced IT Monkey ✭✭✭
@Peter_Miklian you could use either a boolean or dropdown for this, and have some custom code on the page that disables the save button if it is not checked or the correct item selected on the dropdown
5 -
Jeff_Lang
Customer Advanced IT Monkey ✭✭✭
@Peter_Miklian @Justin_Workman
I've done a quick change to the version of the toolbox we are using, and added an extra option for force a check box to be checked to be able to submit the request.
there is some other things added and fixed from the last version uploaded to github as well, i just haven't had time to get the new one uploaded, here is the updated version, and i'll get it uploaded to github with the full list of additions/fixes when i can
to force the boolean to be checked to be able to submit, put a "@ForceAcceptance" tag just before the boolean on the aro
5 -
Justin_Workman
Cireson Support Super IT Monkey ✭✭✭✭✭
@Peter_Miklian - Yes. I would say request a checkbox that requires checking in order to have a value so form validation will work the way you expect.
5
Answers
@Peter_Miklian - The simple list with True and False is the best way. A boolean control will always pass because despite that fact that it is required, false is a valid value.
@Justin_Workman Yes, I know that boolean 'False' is correct value, too.
Simple element with Yes/No is not exactly what correct - users selects 'No' (he doesn't accept license) so the ticket is created uselessly and will be cancelled by analyst. It would be the same as as boolean, no added value as 'No' answer would fill requirement, too.
We want to prevent user from saving SR without accepting terms, that's why I say list with 1 'forced' value 'Yes' is the only way now, although it looks silly.
@Peter_Miklian you could use either a boolean or dropdown for this, and have some custom code on the page that disables the save button if it is not checked or the correct item selected on the dropdown
In fact, it might be nice if @Jeff_Lang's suggestion was somehow part of the RO Toolbox @john_doyle
@Peter_Miklian @Justin_Workman
I've done a quick change to the version of the toolbox we are using, and added an extra option for force a check box to be checked to be able to submit the request.
there is some other things added and fixed from the last version uploaded to github as well, i just haven't had time to get the new one uploaded, here is the updated version, and i'll get it uploaded to github with the full list of additions/fixes when i can
to force the boolean to be checked to be able to submit, put a "@ForceAcceptance" tag just before the boolean on the aro
oops i forgot to force the save button to disabled when it first loads and this tag has been used, insert this after line 237 (right before the call to forceCheckboxAcceptance) to do that
$('button.btn.btn-link span.fa.fa-check').parent().prop('disabled',true);
@Jeff_Lang thank you for the customization but since Request Offering Query Picker was released natively in portal we do not need to use ROToolbox.
@Justin_Workman maybe add this option to ROQP modify true/false input? Should I create separate feature request? Thanks.
@Peter_Miklian - Yes. I would say request a checkbox that requires checking in order to have a value so form validation will work the way you expect.
I created feature request here, all users missing this feature can vote here: https://community.cireson.com/discussion/5331/required-checkbox/
Thank you.