You are viewing limited content. For full access, please sign in.

Question

Question

Any way to have a section on a form always show no matter what page your on?

Forms Layout Designer
Updated April 10
asked on April 9

It is common to have to hide pages with required fields when someone is choosing an option like Deny, Withdraw, Cancelation, etc rather than Approving or moving forward with a form. Otherwise the cancelation action button will not work as their required fields are not filled out.

In this case we often use a field combined with a field rule where the task user can select they are about to withdraw and it hides pages with required fields they previously would have had to fill out.

Is there any CSS magic to make this section always show regardless of what page your on that way we can keep it near the action buttons at the bottom of the form.

0 0

Replies

replied on April 9

There is not a way that I'm aware of, but I made this feature request back in 2018.
Feature Request: Ability to Show Fields on Every Page When Using Pagination - Laserfiche Answers

1 0
replied on April 9

Pages are physically removed from the DOM so you would not be able to use any CSS to make this possible.

I would like to look at "clone" fields that can replicate other fields/sections automatically without requiring and wiring of new fields/variables by hand. 

Adding fields above pagination is an interesting idea, I don't hate it haha. I think the new form designer could technically allow it after a conversation with the dev team, but at that point we might as well make a "page" field type and let you put it wherever you want. That I don't know if it is possible or not but I can ask the team

0 0
View 3 previous replies
replied on April 10

Another alternative would be to have action buttons which can bypass required fields. We are using field rules because it is currently the only way to bypass required fields.

0 0
replied on April 10

For that particular use case I want to add pages/the entire form to field rules as well as a "Do not validate" option, as  well as adding the submission buttons to field rule clauses. 

 

Technically right now, you can:

  1. Use a hidden field to control show/hide for required Sections that you want to bypass
  2. onFormSubmission check if you "Withdraw" or "Reject Button" was clicked, asynchronously flip the state of your hidden field from #1, and allow submission to continue
  3. This will hide a bunch of the form on submission, but you can replace the HTML over top of the entire form by editing the description and say "submitting" or something like that, and then submit.

It is only a few lines of code, and a few field rules!

1 0
replied on April 10

Oh I see, that way no field is required for the user that get's hidden by the rule itself.

It is interesting that $('.Submit').on('click' completes all code and rules before the execution of the button itself.

0 0
replied on April 10

Correct, obviously some combination of fields indicates the form shouldn't be required or you do it on "Reject". But this keeps you from hiding the entire form from a user based on a Field and instead save it for the submission action.


Well this is onFormSubmission for the form designer not the classic designer. And yes it support asynchronous code execution and executes your business logic before the rest of the internal submission logic!

0 0
replied on April 10

Don't forget to add the ability to require a value in the built-in task comments field based on which action button is selected as well wink

1 0
replied on April 10

Oh that would be huge, often times we want to require comments related to certain actions and we depend on that variable being populated. It also would prevent accidental clicks if they meant to click approve and left the comments box empty.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...