Answers to: Show a generated case document in the userinterface

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Mon, 27 Jun 2016 08:52:25 -0400

The CMS is approach is not a static solution. You can write a new CMS entry with the PDF file at the end of your task instead of storing it in fils/application.

Comment by Spfl_ on Reguel Wermelinger's answer

Spfl_ — Thu, 23 Jun 2016 15:56:38 -0400

Hello,

thank you very much for your answer.

To summarize the requierement again: The PDF file will be automotically generated at the end of the task under the files/application folder, the documentViewer has no access to that location. But in my case it's necessary that the file will be generated as a case file and therefore dynamicly.

The workarounds you offered seem to be for static documents and therefore not an option for my case.

Thanks so far.

Answer by Reguel Wermelinger

Reguel Wermelinger — Thu, 23 Jun 2016 12:23:49 -0400

two possible workarounds which should work:

remove the library attribute and copy the PDF into the engine webcontent folder: [engineDir]/webapps/ivy . Just as you already tried, but ensure that you use the correct webcontent+library combination.
persist the PDF in the CMS and load it from there via <pe:documentViewer library="ivy-cms"> . The CMS store API is quite old and unhandy - but you get an idea how to use it when you look at the HtmlDialogDemos (ch.ivyteam.htmldialog.demo.input.FileUploadAdvancedModeDemo)