hi Guys
We updated our Environment Domain recently due to a compliance requirment. After the same the PDF generation stopped working. On viewing the logs and setting we can see that the ultimate PDF is still referencing the Old domain address
We found the Below in the App config in The ultimate PDF manager
<add key="OutSystems.Plugin.RESTConsume.f91e1f1e-5f11-4522-80b6-269e6be814c0.fdc4e647-f009-432e-827f-84a2880a820b.Effective_URL" value="https://olddomain" />
how do we change it to
<add key="OutSystems.Plugin.RESTConsume.f91e1f1e-5f11-4522-80b6-269e6be814c0.fdc4e647-f009-432e-827f-84a2880a820b.Effective_URL" value="https://newdomain" />
We tried republishing the forge componenet. there are no site properties for the Domain either.
Below is the Log it has references to the olddomain and newdomain
[2025-10-28T13:10:18.9804743Z] [info] Revision will be extracted from database if needed: Chrome 113.0.5672.35
[2025-10-28T13:10:18.9814755Z] [info] Reused existing revision
[2025-10-28T13:10:18.9834668Z] [info] Request is executing in node: olddomain/DEVICEID
[2025-10-28T13:10:18.9834668Z] [info] Using browser revision: 113.0.5672.35 at path: C:\Users\OutSystemsApplications\AppData\Local\Temp\.local-chromium\Chrome\Win64-113.0.5672.35\chrome-win64\chrome.exe
[2025-10-28T13:10:18.9834668Z] [info] Input URL: /UltimatePDF_Management/Troubleshooting
[2025-10-28T13:10:18.9834668Z] [info] Deployment zone address will be used: Oldurl.com
[2025-10-28T13:10:18.9834668Z] [info] Browser will retrieve the document from: https://olddomain/UltimatePDF_Management/Troubleshooting
[2025-10-28T13:10:18.9834668Z] [info] Browser will ignore HTTPS errors, because it's possible the server has an invalid certificate
[2025-10-28T13:10:18.9834668Z] [info] Browser will set a Base URL for relative hyperlinks: https://newdomain/UltimatePDF_Management/Troubleshooting
[2025-10-28T13:10:18.9834668Z] [info] Importing cookie from user session: osVisitor
[2025-10-28T13:10:18.9834668Z] [info] Importing cookie from user session: osVisit
[2025-10-28T13:10:18.9834668Z] [info] Importing cookie from user session: Users
[2025-10-28T13:10:18.9834668Z] [info] Importing cookie from user session: nr1Users
[2025-10-28T13:10:18.9834668Z] [info] Importing cookie from user session: nr2Users
[2025-10-28T13:10:18.9834668Z] [info] Page open...
[2025-10-28T13:10:25.1584122Z] [info] Page opened in 6175ms
[2025-10-28T13:10:25.1704165Z] [info] Page opened and ready in 6186ms
[2025-10-28T13:10:25.1714178Z] [info] input.html attached
[2025-10-28T13:10:26.2263994Z] [info] output.pdf attached
can you help guide?
When you change the environment domain in OutSystems, you need to ensure that all applications, including any third-party components like UltimatePDF, are updated to use the new domain correctly. Here's how you can handle this for UltimatePDF:
Update the Environment Domain in OutSystems: Ensure your environment's domain is correctly updated by following the proper steps to assign your new SSL certificate. Refer to the official OutSystems documentation for guidance on setting up your custom domain Use your SSL domain in OutSystems Cloud.
Check for External Endpoint Consistency: UltimatePDF might reference static URLs internally for certain assets, such as CSS, JS, or other dependencies. Update any hardcoded references to point to the new domain. This could involve modifying configurations or the source of your UltimatePDF_Server components.
Update Links in Your Application: If your apps dynamically generate URLs or reference static resources, you will need to correct these links to reflect the new domain.
Refresh Dependencies: After updating the domain, refresh your references in Service Studio to ensure that they point to the new configuration. Right-click the UltimatePDF dependency, refresh it, and then publish your module again. This will ensure all references are correctly updated.
UltimatePDF
Verify Configuration Settings: Ensure there are no issues with the configuration of UltimatePDF after making changes. Inspect your environment settings in Service Center and confirm that the server communication and paths are correct as per your new domain.
Test the Changes: Publish and test your application to confirm that UltimatePDF is now correctly generating PDFs and referencing the new domain without any errors. You can examine the logs in Service Center if errors persist during testing.
If you continue to face domain-related issues with UltimatePDF despite following these steps, it may be helpful to use the latest version of the UltimatePDF component from the Forge, as updates may include fixes for issues like yours Using UltimatePDF. Always ensure you are using the latest versions of components and confirm compatibility with your OutSystems environment.
For further action, you may also want to cross-check if the DNS records have propagated completely if the errors seem to persist due to mismatched domains Custom Domain for different environments.