Oracle Cloud ERP(SaaS) Technical Interview Questions- Extensions (Configuring and Extending)
- What are the changes can be done in Cloud ERP?
- Configuration
- Application Extension
- Personalization
- Are Configurations, Application Extensions , Personalizations Preserved during new release ?
- Yes, Configurations, application extensions, and Personalizations are preserved when you move on to a newer release update
- Tools in the Cloud SaaS for Configuring and Extending
- Page Composer: Configure application page components, such as page content, layout, and more for other users.
- Visual Builder Studio: Extend application page components for certain applications.
- Application Composer: Create fields, objects, and relationships between objects.
- User Interface Text: Edit text that appears on multiple pages.
- Appearance: Change the look and feel of the application pages.
- Page Template Composer: Edit global page template.
- Structure: Configure the Navigator and the icons on the home page for navigation.
- Announcement: Create, edit, and delete announcements displayed on the home page.
- How to determine which task to use, based on the requirement?
| Task | Tool or Work Area |
| Add, move, delete, show, or hide components on a page, including fields | Page Composer or Visual Builder Studio |
| Add validation to a field | Page Composer |
| Add external content | Page Composer |
| Change a page layout | Page Composer or Visual Builder Studio |
| Add business logic to display certain layouts | Visual Builder Studio |
| Manage saved searches | Page Composer |
| Modify dialog box content | Page Composer or Visual Builder Studio |
| Modify attributes for a flexfield on a page | Page Composer |
| Change properties for UI components on a standard page | Page Composer or Visual Builder Studio |
| Edit variables, constants, and events as needed | Visual Builder Studio |
| Configure the UI Shell template | Page Template Composer |
| Update a UI text across all pages, such as to change “buyer” to “customer” on all pages where the term “buyer” is used | User Interface Text |
| Change the look and feel of application pages | Appearance |
- What programming language is used in the above tools
- Mostly none, but there are chances a Groovy Script, Expression Language (EL) is used
- Who works on the above Tools?
- It can be functional or technical, based on the complexity, requirement etc.
- How do we migrate the changes from one instance to other?
- It can be Manual or Automated – It’s again case to case basis, always validate the oracle doc for it
- What is Sandbox?
- It’s a test area, where we do our changes and validate, if it is as per the requirement
- The content is not visible to other users, until it is published
- How to Verify Whether a Page Can Be Extended Using Visual Builder Studio
- If you see the Edit Pages in Visual Builder option in Settings and Actions menu of a page, that means you must use Visual Builder Studio to make changes to that page. If you don’t see the option, that means the page can’t be modified using Visual Builder Studio.
- Here are a few things to know about using Visual Builder Studio:
- If you need to make changes to the data model, you must first use other configuration tools, such as Application Composer, and then use Visual Builder Studio to make the changes in the UI.
- You can make additional changes to the data model later using a sandbox and associate that sandbox with the workspace (your private work area) in Visual Builder Studio.
- When you’re ready to merge your application extension changes with the mainline repository, you should publish the sandbox. Publishing the sandbox before merging your application extension changes can help avoid potential problems resulting from using two different data models. The application extension changes are then automatically deployed to a test environment.