Oracle Fusion HCM Experience Design Studio: A Complete Practical Guide
When working on Oracle Fusion HCM implementations, one of the most powerful tools for tailoring user experience without customization is Oracle Fusion HCM Experience Design Studio (EDS). This feature allows consultants to personalize UI behavior based on business requirements, user roles, and transactions — all without touching core code.
In real-time implementations, Experience Design Studio becomes critical when clients ask questions like:
- “Can we hide certain fields for specific roles?”
- “Can we default values based on business units?”
- “Can we enforce validations dynamically?”
This blog provides a complete, practical, consultant-level understanding of Experience Design Studio in Oracle Fusion HCM, including configuration, real-world use cases, and best practices.
What is Oracle Fusion HCM Experience Design Studio?
Oracle Fusion HCM Experience Design Studio (EDS) is a rule-based UI configuration framework that allows you to:
- Modify page behavior dynamically
- Show/hide fields
- Make fields required or read-only
- Set default values
- Apply conditional logic based on roles, data, or context
Unlike traditional customization approaches, EDS works within the Oracle SaaS framework, ensuring upgrades are not impacted.
Why Experience Design Studio is Important in Oracle Cloud
From a consultant perspective, EDS solves a major problem:
Clients want flexibility, but Oracle SaaS restricts direct customization.
EDS provides a controlled customization layer, enabling:
- Faster implementation
- Reduced dependency on technical teams
- Upgrade-safe configurations
- Improved user experience
In most real projects, EDS replaces 60–70% of UI customization requirements.
Key Features of Experience Design Studio
1. Rule-Based UI Personalization
You can define rules based on:
- Roles
- Business Units
- Legal Employers
- Transactions
2. Page Composer Replacement
EDS is the modern alternative to older UI tools like Page Composer.
3. Conditional Logic
Supports IF conditions like:
- If Role = HR Specialist → Show field
- If Country = India → Make field mandatory
4. Sandbox-Based Deployment
All configurations are done in sandbox mode, ensuring safe testing.
5. Transaction-Level Control
You can target:
- Hire an Employee
- Promote Worker
- Transfer Employee
- Termination
Real-World Business Use Cases
Use Case 1: Country-Specific Mandatory Fields
A global company wants:
- PAN Number mandatory only for India employees
Solution:
- Create EDS rule based on Country = India
- Set PAN field as required
Use Case 2: Role-Based Field Visibility
HR Admin should see salary fields, but Managers should not.
Solution:
- Condition based on Role
- Hide salary field for Managers
Use Case 3: Default Values for Business Units
When creating employees for a specific BU, location should auto-populate.
Solution:
- Configure default values using EDS rules
Use Case 4: Restricting Termination Reasons
Different countries have different termination reasons.
Solution:
- Filter LOV values using EDS conditions
Architecture / Technical Flow of Experience Design Studio
Understanding how EDS works internally helps during troubleshooting:
- User accesses HCM page
- Oracle checks assigned roles and context
- EDS rules are evaluated
- Matching rules are applied
- UI is dynamically adjusted
Important Note:
- Rules are evaluated at runtime
- Multiple rules can be applied simultaneously
Prerequisites
Before working with EDS, ensure:
- Sandbox access is enabled
- Required roles are assigned:
- Application Implementation Consultant
- Human Capital Management Application Administrator
- Functional knowledge of:
- HCM transactions
- Business units
- Roles and security
Step-by-Step Configuration in Oracle Fusion
Step 1 – Enable Sandbox
Navigation:
Navigator → Configuration → Sandboxes
- Click Create Sandbox
- Enter Name:
EDS_Config_Sandbox - Enable:
- Page Composer
- Structure
Activate the sandbox.
Step 2 – Navigate to Experience Design Studio
Navigation:
Navigator → My Client Groups → Experience Design Studio
Step 3 – Select Transaction
- Choose a transaction like:
- Hire an Employee
- Promote Worker
Example:
Select Hire an Employee
Step 4 – Create Rule
Click Create Rule
Enter:
- Rule Name:
India PAN Mandatory - Description: PAN required for India employees
Step 5 – Define Conditions
Example Condition:
| Field | Operator | Value |
|---|---|---|
| Country | Equals | India |
Step 6 – Configure Actions
Choose field: PAN Number
Set:
- Required = Yes
- Visible = Yes
Step 7 – Save and Publish
- Click Save
- Publish the rule
Step 8 – Exit Sandbox
- Test before publishing to production
Testing the Setup
Example Test Case
Scenario:
Hire employee in India
Steps:
- Navigate to Hire an Employee
- Select Country = India
- Try submitting without PAN
Expected Result:
- System should throw validation error
- PAN field must be mandatory
Validation Checklist
- Rule triggers correctly
- No impact on other countries
- No performance issues
Common Implementation Challenges
1. Rule Not Triggering
Cause:
- Incorrect condition setup
- Role mismatch
Solution:
- Validate condition logic carefully
2. Multiple Rules Conflict
Cause:
- Overlapping rules
Solution:
- Use priority and proper naming
3. Performance Issues
Cause:
- Too many rules
Solution:
- Optimize and consolidate rules
4. Sandbox Issues
Cause:
- Changes not published
Solution:
- Always publish after testing
Best Practices from Real Implementations
1. Use Naming Conventions
Example:
EDS_HIRE_INDIA_PAN_REQEDS_PROMOTION_ROLE_RESTRICT
2. Minimize Rule Complexity
Avoid:
- Too many nested conditions
Prefer:
- Simple, focused rules
3. Test Across Roles
Always validate:
- HR roles
- Manager roles
- Employee self-service
4. Document All Rules
Maintain:
- Rule name
- Purpose
- Conditions
- Impact
5. Avoid Overuse
EDS is powerful, but:
- Don’t use it for everything
- Use only where required
Frequently Asked Questions (FAQs)
1. Can Experience Design Studio replace Fast Formulas?
No.
EDS is used for UI behavior, while Fast Formulas handle business logic.
2. Is EDS upgrade safe?
Yes.
EDS is fully supported in Oracle SaaS and does not break during upgrades.
3. Can we use EDS for all HCM modules?
EDS supports most major transactions like:
- Hiring
- Promotion
- Transfer
- Termination
But not every page is supported.
Expert Tips
- Always test rules in lower environments
- Use role-based conditions carefully
- Combine EDS with security roles for better control
- Avoid duplicate rules for same transaction
Summary
Oracle Fusion HCM Experience Design Studio is one of the most practical tools available for consultants to personalize user experience without technical customization.
From real-world implementations, it is clear that:
- EDS reduces dependency on developers
- Improves user experience significantly
- Helps meet business requirements faster
However, success depends on:
- Proper rule design
- Thorough testing
- Clear documentation
For deeper reference, always review official Oracle documentation:
https://docs.oracle.com/en/cloud/saas/index.html