Functional Consultant's Guide to VBS

Prerequisites

Before you begin, confirm all four items:

• You created a Visual Builder project, or you are a member of an existing project.
• You have the security roles needed to extend Redwood pages.
• Your Fusion environment is already connected to Visual Builder Studio.
• Your technical or release team understands who can create, commit, and deploy changes.

The fastest way to start editing

1. Navigate to the actual Redwood page in Oracle Fusion that you want to extend.
2. Open the User Menu in the upper-right corner.
3. Select Edit Page in Visual Builder.

This opens the correct page directly in Visual Builder Studio and avoids a confusing manual search through the project. The option applies to Redwood pages; if the page is still Classic, this is a good reason to evaluate its Redwood replacement.

Stay in Express Mode

Express Mode primarily presents three areas: Configure Fields and Regions, Configure Validations, and Journey Codes.

Configure fields, regions, and form rules

This is where most functional configuration happens. You can show or hide fields, make fields required or read-only, set defaults, conditionally display regions, and apply logic based on other field values.

Create a form rule

1. Select the plus sign to create a rule.
2. Choose whether the rule always applies or applies only when defined conditions are met.
3. Add the field or region behavior, then give the rule a clear, durable name.

Conditions can use values such as Business Unit, Requisition Type, or Purchasing Category ID.

Not every List of Values field works in logic

Some fields appear in the List of Values while you build a rule but are not supported reliably in rules or validations. Search Oracle guidance for “Extending Redwood Pages” and use documented examples as the source of truth.

Customer Connect example for extending Redwood Self Service Procurement ↗

If the limitation affects your design, you can review and upvote the Customer Connect idea for Category Name validation rules ↗.

Configure validations

Validations can display inline error text, show pop-up messages, block submission, or provide nonblocking warnings and information.

1. Select Create Validation.
2. Define the condition.
3. Write a clear message that tells the user what happened and how to fix it.
4. Choose a severity: Error blocks submission; Warning allows submission; Info provides guidance.

Example validation

Guided Journeys

Journey Codes allow an administrator-provided Guided Journey to be attached to an entire page, a section, or a specific region.

Preview and publish safely

Preview every change

Use the Play button in the upper-right corner to launch a runtime preview. Always test required fields, conditional visibility, validation triggers, default values, and submission behavior. Do not assume the logic works simply because the rule saved successfully.

Understand the deployment model

Visual Builder Studio uses a CI/CD pipeline model. Functional consultants do not log into Production, open Visual Builder, and make changes there directly.

1. A development or test pod is connected through the project and deployment setup.
2. Changes are created in Visual Builder Studio against the appropriate environment.
3. Changes are committed and pushed through the controlled pipeline.
4. Deployment promotes the approved changes to Production.

This provides version control, governance, an audit trail, and controlled promotion. Always coordinate publication with your technical team or release manager; that is why this functional guide intentionally does not include step-by-step production deployment instructions.

Best practices

• Stay in Express Mode for functional work.
• Follow documented Oracle examples.
• Preview before committing.
• Document every rule and its business owner.
• Keep conditions simple and readable.
• Avoid overlapping rules where possible.
• Use IDs when Oracle examples use IDs.
• Coordinate deployment with the release team.