How do I create deep links in Oracle Sales for both the Classic and Redwood user experiences?

In Oracle Sales, you can create deep links that work for salespeople using any of the available user interfaces. For a salesperson in the Redwood User Experience, the link opens an opportunity in a Redwood UX page. A salesperson clicking the same link in the Classic version of Sales opens the opportunity in a Classic UX page.

Here's the link pattern:

https://{{pod_name}}/fscmUl/redwood/application-components/application/container
            /deeplink?&id={{object_id}}&puid={{object_public_unique_identifier}}&resource={{object_rest_resource}}

Here are the substitutions you must make in the pattern:

Pattern Substitutions	Explanation
{{pod_name}}	Pod instance name
{{object_id}}	The primary key of the object record that you're opening
{{object_public_unique_identifier}}	The PUID (Public Unique Identifier) of the object record that you're opening
{{object_rest_resource}}	The REST resource of the object

To link to activities, you add the recordType parameter with a value of either TASK or APPOINTMENT.

The application uses multiple factors to decide which interface to open for a user. The application checks:

• The value of the profile option Navigation from Notifications to Sales in the Redwood User Experience (ORA_ZCA_CX_REDWOOD_NAVIGATION). For new customers, this profile option is automatically set to Yes.

• If the user has the privilege ZBS_NOTIFICATION_DRILLDOWN_VBCS_PRIV.
• If the Sales in the Redwood UX and Digital Sales Next Gen UI features are enabled in Setup and Maintenance.

• If a Dispatcher rule exists to redirect the link to another page.

  The deep link logic integrates with the Dispatcher tool in Application Composer. You can use the tool to redirect links to open other UI pages in the Redwood User Experience. For example, you can open the Edit page instead of the Details page when a user clicks on a account name link.

  For details, see the topic How do I change the navigation links to open a different page in Oracle Sales in the Redwood User Experience?

The application uses the following logic to decide which UI to open for a user:

1	If the profile option ORA_ZCA_CX_REDWOOD_NAVIGATION is set to Yes, then the link opens a Redwood page.
2	If any valid Dispatcher rules apply. The Dispatcher rules are optional and available only for the Redwood User Experience.
3	If the user has the privilege ZBS_NOTIFICATION_DRILLDOWN_VBCS_PRIV then the application checks to see if the Sales in the Redwood UX feature is enabled. If the doesn't have the privilege, then the application opens the Classic UX page.
4	If the Sales in the Redwood UX feature is enabled, then the application opens the Redwood UX page. A Dispatcher rule can specify which page the application opens.
5	If the Sales in the Redwood UX feature isn't enabled, then the application checks if the Digital Sales Next Gen UI feature is enabled. If the Digital Sales Next Gen UI feature is enabled, then the application opens the Digital Sales UX page. (This UX is being deprecated.) If the feature isn't enabled, then the application opens the Classic UX page.

For more details, view the Dynamic Links video on Oracle Cloud Customer Connect.