Configure the Expenses Root Menu

You can configure the navigation menu to allow users to access Expenses Agent from the application home page. This ensures users see the right Expenses entry point, and supports pilots.

Note:

This configuration is required only in the following scenarios:

• If you've already customized your root menu and need to control how Expenses entries are displayed.
• If you’re running a pilot program to incrementally onboard a subset of users (for example, within a business unit) for the Expenses Agent adoption.

If neither applies, this step can be skipped.

Here's how you can configure the navigation tiles:

1. Sign in as an Application Implementation Consultant.
2. Navigate to Configuration > Sandboxes.
3. Enable the Structure tool and click Create Sandbox.
4. Enter the sandbox details. For example:
   • Name: Expense Root Menu Configuration
   • Description: Navigation setup for Expenses Agent
5. Click Create and Enter.
6. Navigate to Tools > Structure, and expand the Me menu.

7. Update the Show on Navigator render conditions.

   If you previously used Fusion Expenses, you may see two Expenses links in the Navigator. These represent different experiences and must be configured so that only the appropriate one is displayed to users.

   Render conditions for general availability (all users)

   • Standard Expenses tile (first Expenses link)

     Set render condition to:

      #{!(Offerings.isFeatureEnabledForImplementation.ORA_EXM_SEQUOIA_EXPENSE or Offerings.isFeatureEnabledForImplementation.ORA_EXM_TOUCHLESS_EXPENSE_DOCIO)}

     Note: This ensures the standard Expenses experience remains visible only when the new capabilities are not enabled, preserving the existing user experience.

   • Expenses Agent tile (second Expenses link)

     Set render condition to:

     #{Offerings.isFeatureEnabledForImplementation.ORA_EXM_SEQUOIA_EXPENSE or Offerings.isFeatureEnabledForImplementation.ORA_EXM_TOUCHLESS_EXPENSE_DOCIO}

     Note: This ensures the new Expenses Agent experience is shown only when the relevant features are enabled.

   Pilot-only render condition variants (limited users)

   If you're running a pilot with a subset of users (for example, in a test environment), use the following conditions to control access.

   • Standard Expenses tile (first Expenses link)

     #{!Offerings.isFeatureEnabledForImplementation.ORA_EXM_TOUCHLESS_EXPENSE_DOCIO or Profile.values.EXM_TOUCHLESS_EXP_DOCIO != 'Y' }

   • Expenses Agent tile (second Expenses link)

     #{Offerings.isFeatureEnabledForImplementation.ORA_EXM_TOUCHLESS_EXPENSE_DOCIO and Profile.values.EXM_TOUCHLESS_EXP_DOCIO eq 'Y' }

8. Publish the sandbox changes.