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

Question

Question

When save second form as PDF, variable value not showing in Custom HTML

asked on September 19, 2014

I made a starting form(A) which to be submitted, and second form(B) to be saved as PDF in repository.

Some field values in A are included in Custom HTML in B.

When I use Service Task - Save to Repository in Process Modeler to save B as PDF, the field values in Custom HTML are not showing on PDF. 

 

I found that if I add user task to approve the form B before the service task, it works(custom html shows field values and save as PDF with them). However, we don't want to put the approval process.

 

What should I do to make it work?

 

0 0

Replies

replied on September 19, 2014 Show version history

Custom HTML doesn't work as the way the HTML probably is working needs the form to be loaded. What you could do, is try having the Custom HTML change when the first form has fields changed, and keep it hidden from view. This way it is ready to go when it is used in the second form to be saved as a PDF.

 

EDIT: Other option is create a fillable PDF and have a workflow kick off after the form is submitted that takes the values from the variables and inputs it into the right locations of the PDF. Then you save the PDF so it is not editable anymore and put it with whatever other documents relate to this form or wherever this form PDF needs to go

0 0
replied on December 27, 2014 Show version history

Hi Heejin,

 

I had a similar problem, I couldn't resolve it. I ended up doing what Kenneth described under his "EDIT" comment. 

  • Use javascript to copy the custom HTML data into a hidden field
  • Use the forms process to kick off a workflow
  • Pass all the data (including your hidden field data) to a workflow that fills out a PDF form

 

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

Sign in to reply to this post.