Hi,
I am facing an issue with the server action "PrintToPDF_Advanced" when using this server action in application that has a SEO URL rule. When I use the server action the PDF gets generated but I get a screen where I have to perform a login.
The server action has an URL parameter where I put the original name of the application and not the SEO friendly URL.
When I am not using the SEO URL but the real DNS I am not facing this issue. The PDF gets generated and no login is required. Is the component compatible when using SEO rules? And did you encounter this problem yet?
Looking forward to your response,
Kind regards,
Vaisel
Hi Vaisel Fremouw,
Can check for the screen which is to be printed is tick with Anonymous.
Regards,
Amreen
Hi Amreen,
Thank you for your response but the screen is not checked with anonymous, it works when it is checked but that is not a desirable option as the page then is exposed to the web.
Hi Vaisel,
It work like that only. You can checkin documentation.
I have seen the documentation and several posts about this topic but the weird thing is that is has worked and it doesn't work anymore.
On our production environment we have an old version of UltimatePDF and that one still works but on our development environment we encountered this behaviour.
Then I will recommend you to get it done through JS.
And try to connect with component owner if you want use this component only.
Any response from the makers of component?
I am still facing the issue stated above.
Kind regards,Vaisel
Hi Vaisel.
Please install Ultimate PDF Management component, and generate execution logs for this particular URL.
Ultimate PDF will only send the user's session cookies if the hostname is "safe" - for example, if it matches the hostname as configured in the Service Center Administration screen, or if the URL of the screen is a relative URL (e.g. "/PdfReports/MyReport").
I suspect some of those validations are not working when you're using SEO rules. In that case, the session cookies are not sent and you'll get a Login screen.
The execution logs should shed some light into it.