🧠Introduction
Oracle Fusion Cloud supports no-code UI personalization
using Sandbox and Structure tools. Known as Form Personalization, this
method safely customizes navigational tiles, labels, and task names—without
altering core application or upgrades. You can preview all changes in a sandbox
locally before publishing them application wide.
📌 Common Use Cases
- Personalization
& UI Tweaks: Change menus, tile labels, panels, and visibility of
components while testing safely in sandbox.
- Testing
New Functionality: Activate or disable Dynamic Flexfields,
personalization, customized roles, and dashboards like Infolets or theme
changes.
- Security
Extensions: Build and test new CRM or custom business objects and
configure data security before deploying.
✅ Use Case: Renaming a Tile and
Task in Purchasing Screen in Fusion Application
|
Change |
From |
To |
|
Tile |
Negotiations |
Negotiations / Solicitations |
|
Task name |
Create Negotiation |
Create Negotiation / Solicitations |
This change reflects corporate terminology, improves clarity
for end‑users, and retains upgrade compatibility.
|
Before Change
: |
After Sandbox
Changes |
|
|
|
|
|
|
🔧 Step-by-Step
Implementation
1. Create and Activate a Sandbox
- Navigate
to Fusion Application → Navigator → Configuration → Sandboxes.
- Click
Create Sandbox, assign a meaningful name and description.
- Select
Structure as the personalization tool and activate it.
2. Launch the Structure Editor
- In
the active sandbox, open Structure to view the UI component
hierarchy.
- Navigate
to Procurement → Negotiations.
3. Rename at Page and Panel Levels
- Edit
the Name property at the page level to "Negotiations /
Solicitations".
- Under
Panel Tabs or tasks, locate "Create Negotiation", update
to "Create Negotiation / Solicitations".
4. Save, Preview, Publish
- Save
and close the editor.
- Preview
changes using sandbox’s preview mode to ensure accurate display.
- Publish
the sandbox when confirmed, and have users sign out/sign in to refresh the
UI.
🧩 Best Practices &
Tips
- Always
create a separate test-only sandbox before moving to an
integration/publish sandbox.
- After
activating, log out/log in to prevent customization cache issues.
- Avoid
publishing outdated sandbox before an Oracle patch or upgrade—stale
sandboxes may conflict.
- Use labels
for rollback or version control.
- Limit
simultaneous multi-user editing in one sandbox—manage changes to reduce
conflicts.
✅ Summary
Oracle Fusion’s sandbox framework is a powerful tool with
wide range of capabilities to create secure, isolated environment to customize
UI, security, and Oracle flexfield functionality—without impacting live fusion
application. With support for versioning, rollback and conflict detection sandboxes
streamline change management and ensure safe deployment to Production.
