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

Question

Question

Forms Submit and setting fields

asked on December 5, 2014

Is it possible to set a field's value on a form once the submit button has been pressed and the form is validated?

Can you use an expression/value that may not exist in initial context, e.g., {/dataset/_instance_id}?

0 0

Replies

replied on December 7, 2014

It seems this is not doable right now. Can you share with us the use case for such feature?

0 0
replied on December 8, 2014

I don't think it's possible directly after the form is validated, but you could create a second form in the Process and add the jQuery needed so that when it is viewed at the next step it would populate the field with the value you are looking for.

0 0
replied on December 8, 2014

Thanks for the replies! Here is the use context: We have a form where a preparer sets fields and submits. This form gets routed to a reviewer who validates and possibly modifies values on the submitted form. The reviewer also sets additional fields that are originally hidden, and selects approvers for routing. The reviewer can edit anything on the form. Lastly, the approvers approve the form in a read-only state. The approvers can see everything on the form.

 

Rather than create 2/3 forms (we have about 60-70 fields), we want to hide the reviewer section until the form is (at least) in the reviewer's queue. I was contemplating ways to do this. A good approach seems like populating a Request ID field on form submit. Using this approach, we could hide the reviewer section until the Request ID field is no longer blank.

 

What other approaches exist to accomplish such scenarios? What are the recommended approaches? I understand that Forms passes values from form-to-form (say that three times fast), but in our case, this would be double or triple the forms to maintain. We are still in a development phase, and it would be less than ideal to make the same change to 3 separate forms. We'd like the ability to be able to hide/show sections based on user queue or form state/action context. Suggestions welcome :)  Or possible product enchancements :)

 

Thanks!

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

Sign in to reply to this post.