Embed Visual builder page in SaaS / Fusion with Page Integration
Oracle Visual Builder Cloud Service (VBCS) allows you to create and deploy web applications, and you may want to embed a VBCS page within another Oracle Cloud application, such as a SaaS application or Oracle Fusion Application. Oracle provides a feature known as Page Integration that enables you to achieve this integration. Below are the general steps to embed a VBCS page within another Oracle Cloud application:
Steps for Embedding a VBCS Page in SaaS/Fusion:
Publish Your VBCS Application:
- Before embedding, ensure that your VBCS application is published and deployed.
Configure Cross-Origin Resource Sharing (CORS):
- If your SaaS or Fusion application is on a different domain than your VBCS application, configure Cross-Origin Resource Sharing (CORS) settings in your VBCS application. This ensures that the SaaS/Fusion application can make requests to your VBCS application.
Obtain the VBCS Application URL:
- Get the URL of the VBCS application or the specific page you want to embed.
Open the SaaS/Fusion Application Page for Editing:
- Access the page in your SaaS/Fusion application where you want to embed the VBCS content.
Add an iFrame or Custom Component:
Use an iFrame or a custom component to embed the VBCS content within the SaaS/Fusion application page. The specific method might depend on the capabilities of your SaaS/Fusion application.
iFrame Example:
html<iframe src="https://your-vbcs-application-url" width="100%" height="800px"></iframe>Custom Component Example:
- Some applications may provide custom component options for embedding external content. Consult the documentation of your SaaS/Fusion application for specific details.
Adjust Sizing and Styling (if needed):
- Modify the size and styling of the embedded content to seamlessly integrate it into the SaaS/Fusion application page.
Test and Verify:
- Save your changes and test the embedded VBCS page within the SaaS/Fusion application to ensure proper functionality and appearance.
Considerations:
Security:
- Ensure that your VBCS application is configured securely, especially if it involves cross-origin requests.
Authentication:
- If your VBCS application requires authentication, consider how users will be authenticated when accessing it from within the SaaS/Fusion application.
Communication Between Applications:
- Determine if your applications need to communicate with each other (e.g., passing data between the embedded VBCS page and the parent SaaS/Fusion application). This might involve using APIs or other communication mechanisms.
Responsive Design:
- Ensure that the embedded content is responsive to different screen sizes within the SaaS/Fusion application.
Documentation:
- Consult the documentation of both your SaaS/Fusion application and VBCS for any application-specific considerations or limitations related to page integration.
Keep in mind that the process may vary depending on the specific SaaS or Fusion application you are working with. Always refer to the documentation provided by Oracle for your specific applications and versions.
No comments:
Post a Comment