Form Field Rules

APPROVED ANSWER

replied on May 5, 2014

You might want to consider using variables to create different forms for each approval step in the process.

For example, for your first approval step, you'd create a new form with the field variables for each field on your original form, plus your additional section. This video is a good introduction to using variables and shows an example of using variables this way.

4 1

replied on May 5, 2014

By creating another form for the approval step, you will not expose the hidden fields to the end user. The field rule will show and hide fields using javascript, you can still see the value of the hidden fields in the web page source. For security consideration it is better to create another form for approval step.

0 0

replied on May 5, 2014

Each approval step is supposed to be recorded on the same form but just on a different section whether it is approved or denied. By policy it is to be done on one form for each individual. The form is to have three sections one for the submitter and one each for two managers. The managers can view every section but the submitter shouldn't see the other two sections when filling out the forms

0 0

replied on May 6, 2014

Creating multiple forms could still work for you; you could create one "master" form that contains all of the information in the submission and approval steps and save that one to your repository.

If you only want to hide the manager sections from the original submitter, you can do that with some very straightforward JavaScript (but keep in mind what Lena said is still valid here).

For the following code to work, assign each manager section the managerSection CSS class.

$(document).ready( function() {
if($('input[name="routingResumeId"]').val() =="") {
$(".managerSection").addClass('hidden');
}
});

1 0

Question

Question

Answer

Replies

Sign in to reply to this post.