Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X
We've been using the Print Preview function to preview PDFs; it seems a little quicker than the Compose > PDF method. However, graphics do not show up when we do this. Do you know why? It doesn't seem to matter if the graphic is local or on Windchill.
We are using Arbortext 5.4 M130 version.
This doesn't sound familiar, but a wild stab in the dark: are the graphics you cannot see in EPS format? Are you using the FOSI engine for styling? If so, it is possible that the EPS files do not have an embedded preview therefore the print preview feature cannot display the graphic (as I don't believe Arbortext can process EPS except when producing PDF).
Hello Gareth,
We are using APP engine for styling. We Setup a publishing engine separately so, when we select Compose > PDF method it ping's the publishing engine and brings the PDF copy with graphic ( No Error). If for the same object/file used the Print Preview method it is publishing pink pages with missing graphic.
We are uploading graphics with .iso format.
If you are somehow doing the print preview locally (eg. avoiding the PE server) then I can understand how you get the problem. However you should be doing print preview via PE, which in the case of APP returns a PDF anyway.
Cheers,
Gareth
We are not disconnecting PE server connection. but, I am trying to understand is when we do Compose > PDF it publish properly. Same when we do Print Preview it is having an error as mentioned above. Is this because print preview will try publish locally? If, it try to publish locally what is the difference?
If you have "peservices" set to "on" then in fact I think the print preview should go through the server. Does your print preview come back in PDF form?
If print preview does not come back in PDF form then it is a local print preview request. The different with a local print preview is you have to ensure you have the exact same "custom/doctypes" folder as PE, and also the same network access rights and so on to ensure that Arbortext can reach the graphics.