Process Model - Document generation

What type of PDF document do you want to generate? There are a lot of services available in the process model based on your requirement you can use these smart services. For example, If you want to generate your document from the template then you can use pdf document from template smart service.

Hi,

When I used "PDF from HTML" to generate PDF document from HTML file, the PDF file which has been generated is not showing the image which is there on the HTML.

Any clue what might be the issue.

Thanks

I thin, for that you image should be available on your webserver.

Hi,

When I try to generate the PDF document using "PDF from HTML", the output is not looking like an image attached to the PDF and it is looking totally different.

Also, whatever image is there on the HTML document, same is not visible on the PDF.

Appreciate if someone advise on this issue.

AFAIK the PDF from HTML smart service is only (or at least mainly) used for creating a text-based PDF using fundamental HTML text formatting.  An image link in the source HTML file would not be interpreted into the resulting PDF as anything particularly useful - by default I'd guess it might just be ignored outright, that or you'd just see whatever HTML placeholder was there for the image. Remember that typical HTML files don't "store" images whatsoever, they merely link to images hosted elsewhere.  (I know there are exceptions where an HTML might store an image file encoded in base64 - this would be an interesting experiment, but I don't have any expectation that the Appian smart service would even be looking for this, much less interpret it correctly.)

I'm unaware of any supported way to force this smart service to incorporate images into the output PDF, though there may be others here with more experience there, who may know of additional tricks or work-arounds.

AFAIK the PDF from HTML smart service is only (or at least mainly) used for creating a text-based PDF using fundamental HTML text formatting.  An image link in the source HTML file would not be interpreted into the resulting PDF as anything particularly useful - by default I'd guess it might just be ignored outright, that or you'd just see whatever HTML placeholder was there for the image. Remember that typical HTML files don't "store" images whatsoever, they merely link to images hosted elsewhere.  (I know there are exceptions where an HTML might store an image file encoded in base64 - this would be an interesting experiment, but I don't have any expectation that the Appian smart service would even be looking for this, much less interpret it correctly.)

I'm unaware of any supported way to force this smart service to incorporate images into the output PDF, though there may be others here with more experience there, who may know of additional tricks or work-arounds.

Thanks Mike for acknowledging.

Just now I have generated a PDF using "PDF from single DOCX" the output is looking perfect and the document is looking like a proper PDF where as the PDF document which has been generated is totally looking different and even it is not looking like a PDF (just looking like a image).

Rao2022 said:

the output is looking perfect and the document is looking like a proper PDF where as the PDF document which has been generated is totally looking different

Sorry, I might need a bit more clarification on which thing you're referring to where here.  As-is, it sounds almost like you're saying "the output looks perfect but also the output looks totally different", or something.

I am trying to say ..... 

1. I have generated PDF using "PDF from HTML" and PDF file is not looking great.

2. I have also generated PDF using "PDF from single DOCX".

Now, I have expected same PDF output (Forgot about image) from both processes. But output looking totally different.

Yeah, there are different smart services that generate PDFs in different ways and were developed at different times in different plug-ins by different developers.