Is it possible to open pdf form as HTML (profile change) form in workspace

[srujan1981]

Hi Experts,

Is there any way to change the render form from PDF to HTML on fly? In workspace some of the forms are submitted and not in complete state. I have just changed the profile settings like render from PDF to HTML. But when I open in chrome browser still it is trying to open in PDF format instated of HTML.

Is it possible to open pdf form as HTML (profile change) form.

Thanks,

Srujan 

[Pulkit_Jain_ · Accepted solution]

@srujan1981 

It is possible to render an XDP form in HTML format always by switching the rendering of mobile forms from PDF to HTML. For details, see here.

Also, you can render the form as HTML5 form by opening the default render endpoint in the chrome browser on the fly as below:

https://<host>:<port>/content/xfaforms/profiles/default.html?contentRoot=<path of the folder containing form xdp>&template=<name of the xdp>

For example, http://localhost:4502/content/xfaforms/profiles/default.html?contentRoot=c:/xdps&template=sampleForm...

More information here.

[Kosta_Prokopiu1]

Hi @srujan1981, as Pulkit says it is possible to switch but that switch might not show on tasks that have already been instantiated. If you changed the profile for the XDP from PDF to HTML it should shiow on tasks that arrive in the worklist after the change was deployed. Tasks that have entered the worklist with the old profile continue to use the old profile until they step out and the process moves to another task.

[srujan1981]

Thanks!

[srujan1981]

@Pulkit_Jain_ Thanks for quick reply...

My question is users are already submitted the form as PDF format in workspace for approval request, now I made the changes in workspace to form action profile render as HTML. Now approvers are trying to open the form in workspace still it is pointing to old PDF profile not HTML profile.

Regards,

Srujan

[Mayank_Gandhi]

@srujan1981 You can update the render profile for new invocation using action profile and if it's not happening then try clearing the cache at the server level. If the expectation is that the existing user who initiated the flow gets HTML instead of pdf for ongoing processes, I don't think that will happen as the process id has already been created.