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) ![alt text][1] [1]: http://answers.axonivy.com/upfiles/cmsFileUpload.png

two possible workarounds which should work: - remove the library attribute and copy the PDF into the engine webcontent folder: [engineDir]/webapps/ivy - persist the PDF in the CMS and load it from there via `<pd:documentViewer `<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) ![alt text][1] [1]: http://answers.axonivy.com/upfiles/cmsFileUpload.png

two possible workarounds which should work: - remove the library attribute and copy the PDF into the engine webcontent folder: [engineDir]/webapps/ivy - persist the PDF in the CMS and load it from there via `<pd: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) ![alt text][1] [1]: http://answers.axonivy.com/upfiles/cmsFileUpload.png