FNorelli
Well Known Member
There is an Adobe Acrobat reader plug-in for merging JDE .pdf files with Create!Form project templates. Every Citrix server has a merge plug-in. When a user views the output of a JDE batch job using Work Submitted Job | View PDF, there is an Adobe option is available for the user to ‘Merge’ that .pdf with a Create!Form template. Otherwise, if a user prints the output without viewing it first, the .pdf merge happens automatically before the output is sent to a print device.
With a web implementation , If the user directly prints the .pdf from WSJ, the merge will happen automatically, just like on the Citrix server. HOWEVER, if a user decides to view the PDF first, a copy of the .pdf is displayed from the web server using the local workstation’s Adobe Acrobat reader. This will NOT have the plug-in for merging. There is no way for the user to merge the raw JDE .pdf with a CF template.
To get around the issue, simply install the Adobe plug-in on the user’s workstation. This will add a merge option to the local Adobe application. However, given that there will be 400 + users on the JDE web implementation, each one will need their own copy of the plug-in. This becomes an administrative nightmare. First off, the plug-in must be manually installed. Next, the plug-in is based on a specific Adobe version. Since Acrobat is a free application downloaded from the internet, users can freely update the software making the plug-in is vulnerable to users initiated updates.
So my question is simply "if you are using a JDE web implementation along with Create!Form, how are you handling the Adobe merge plugin issue"?
Thanks,
Fred
With a web implementation , If the user directly prints the .pdf from WSJ, the merge will happen automatically, just like on the Citrix server. HOWEVER, if a user decides to view the PDF first, a copy of the .pdf is displayed from the web server using the local workstation’s Adobe Acrobat reader. This will NOT have the plug-in for merging. There is no way for the user to merge the raw JDE .pdf with a CF template.
To get around the issue, simply install the Adobe plug-in on the user’s workstation. This will add a merge option to the local Adobe application. However, given that there will be 400 + users on the JDE web implementation, each one will need their own copy of the plug-in. This becomes an administrative nightmare. First off, the plug-in must be manually installed. Next, the plug-in is based on a specific Adobe version. Since Acrobat is a free application downloaded from the internet, users can freely update the software making the plug-in is vulnerable to users initiated updates.
So my question is simply "if you are using a JDE web implementation along with Create!Form, how are you handling the Adobe merge plugin issue"?
Thanks,
Fred