Mandating Fields on Action Button in 24.1

Hi Etienne,

In 24.1 is there a way we can mandate the fields based on action buttons. The reconfirm step does not seem to work for our requirement as it limits the fields to a certain number. Mandating these fields via status dependency does not help either since it wont let users save the request without filling in all the questions.

Parents
  • 0  

    If you want different fields to be mandatory depending on the action button pressed, I think that you can only use the reconfirm step. If it doesn't allow you to reconfirm enough fields (how many do you have to be mandatory here exactly?) then please submit an idea to allow including more fields on the reconfirm screen.

  • 0 in reply to   

    Hi Etienne,

    We would really like to make the fields mandatory on action button click rather than reconfirm. As the reconfirm/Required page does not carry forward the sections or help text of the field .  I had submitted few ideas over the years 

    Idea ID: 2875059: To revamp the reconfirm page

    Idea ID: 1795848:  Make UI rules available for specific action buttons

Reply
  • 0 in reply to   

    Hi Etienne,

    We would really like to make the fields mandatory on action button click rather than reconfirm. As the reconfirm/Required page does not carry forward the sections or help text of the field .  I had submitted few ideas over the years 

    Idea ID: 2875059: To revamp the reconfirm page

    Idea ID: 1795848:  Make UI rules available for specific action buttons

Children
  • Suggested Answer

    0   in reply to 

    Hi Urva,

    The problem of making field mandatory depending on the button clicked means that we cannot give the indication on whether the field will be mandatory or not on the request details page - at least not until one of the button is clicked.

    This would make for a somewhat confusing UI, and my advice would be to create some intermediary workflow steps such as "initiate Action A" which would be between the current step and the actual action A, and for which the fields mandatory for action A would be made mandatory.

    This would require an extra click, but I assume that even with action-specific mandatory fields the users would have to fill in some missing fields anyway after clicking button, so they would click on the button "for nothing" at least once before knowing which fields would then be mandatory - so in reality adding this intermediary step would not often result in extra clicks.