1. Configuring and Extending Applications
  2. Configure Links for Page Entries and Quick Actions

Configure Links for Page Entries and Quick Actions

When you create or edit a page entry or quick action, you can select the link type to determine the destination for users. Dynamic URL type is available for page entries only.

Link Type Description
Application Page

Any page within your application built with Oracle Application Development Framework (ADF).
Dynamic URL

The URL of an external page where the host, port, or context root might change. You can find the host and port details for a dynamic URL from a lookup based on the application name.
Static URL

The URL of an external page where the host, port, or context root doesn't change. Static URLs don't require lookups.
Static URL with secure destination

The URL for a partner application where secure tokens are appended. These tokens carry user identity and security information, enabling authentication without requiring users to enter credentials, such as user name and password.
VB Studio Page

A page built using Visual Builder Studio and Oracle Java Extension Toolkit.

Application Page

When you create or edit a page entry or quick action, you can link it to one of your application pages.

  1. From the Link Type list, select Application Page.

  2. Provide details for the fields.

    Field Description
    Task Flow ID (for a quick action)

    Enter the task flow ID.
    Focus View ID
    Enter the view ID attribute value associated with the target page. You can find it in the public_html/WEBINF/adfc-config.xml file of this application.
    Note: For a quick action, by default, the focus view ID is displayed as /FndOverview.
    Web Application

    Select the name of the web application, which is the application name that you used while creating this application using the Setup and Maintenance work area.
    Secured Resource Name and Application Stripe

    For secured access to the target application page, provide the secured resource name and the name of the policy store's application stripe. Here's an example of a secured resource name:

    oracle.apps.view.pageDefs.CaseList_Form_Attach_UIShellPagePageDef

    When a user clicks the link, the application checks the secured resource and the Oracle Platform Security Services (OPSS) policy store. Then the application determines whether the user has the privilege to view the page.

    You can get the application stripe from the jps.policystore.applicationid parameter in the application's weblogic-application.xml file. Examples of application stripes are crm, fscm, and hcm.
    • Page Parameters List (for a page entry)
    • Task Flow Parameters (for a quick action)

    If the page takes parameters or task flow parameters, then you can enter a semicolon-delimited string of name=value pairs (for example, org=m1;context=s1) in these fields.

    You can use EL to specify the parameters. If the EL evaluates to an object, the toString value of that object is passed as the value of the parameter. An application page may display or act differently based on the parameters that are passed in. For example, if you're opening a page from one group on the home page or Navigator, the parameter might be set to status=Open, whereas if you're opening the page from another group, the parameter might be set to status=Closed.

Dynamic URL

You can link a page entry to an external website or application that has a frequently changing host, port, or context root. Instead of updating the link to each application, you can update the details of the web application registration. This change affects all page entries that contain dynamic links pointing to that web application.

Suppose you want to link to a test version of an application; you use the dynamic URL link type. When you move the application from the test to the production environment, you just change the host and port details of the web application registration.

Before you start, make sure you add the application details on the Manage Integration of Additional Applications page to register the web application. These application details are used for configuring dynamic URL links for page entries.

  1. In Setup and Maintenance, click Tasks panel tab, and then click Manage Setup Content.

  2. Click Manage Integration of Additional Applications, click Actions, and then click Create.

  3. Enter the application details in the relevant fields. Ensure that the information you provide is complete and accurate. For example,

    • Begin the URL with http:// or https://.
    • Provide correct access credentials for the selected security policy.
    Note: You can't edit the Application Name and Partner Name once you save the details.

  4. Click Save and Close.

To link a page entry to a dynamic URL:

  1. From the Link Type list, select Dynamic URL.

  2. From the Web Application list, select the web application name and enter the destination for the web application.

    Let's look at an example:

    Suppose you want to link to a complete URL, http://example:9011/myApp/faces/Page1.

    1. From the Web Application list, select myApp. This list displays the application names that were added using the Manage Integration of Additional Applications page. Once you select the application name, the full URL that was added for this application (for example, http://example:9011/myApp/) is automatically used as the start of the dynamic URL.

    2. Enter the destination for the web application, for example, /faces/Page1. This value is appended to the full URL.

When users click this page entry, the target page opens in a new browser window or tab.

Static URL

When you create or edit a page entry or quick action, you can link it to an external website or application that has a constant host, port, or context root.

  1. From the Link Type list, select Static URL.

  2. Enter the URL destination. The URL must start with http:// or https://.

    For example, you can use a static URL to link to http://www.oracle.com.

When users click this page entry or quick action, the target page opens in a new browser window or tab.

Static URL with Secure Destination

When you create or edit a page entry or quick action, you can link it to a partner application (external) using a secure token URL.

  1. From the Link Type list, select the Static URL.

  2. Click Edit icon and select Secure Destination.

  3. From the Web Application list, select the name of the web application.

  4. Enter the destination for the web application. An HTTPS protocol is required to access the application.

  5. Enter the name of the secure token. All secure tokens have a predefined lifetime, and they expire after that duration. So, users must refresh the page to regenerate the tokens.

The partner application validates the secure token and uses it to authenticate web services within the user context. Using this mode of modified access, a partner can directly do a task or display information to the specific user without any additional authentication. When users click this page entry or quick action, the target page opens in a new browser window or tab.

VB Studio Page

When you create or edit a page entry or quick action, you can link it to one of your VB Studio pages.

Tip:

If an existing page entry or quick action links to the same page that you want your new page entry or quick action to link to, you can enter the same details for all fields, except parameters. View the existing details, such as Focus View ID, Web Application, and Secured Resource Name, and fill in the fields for the new page entry or quick action.

  1. From the Link Type list, select VB Studio Page.

  2. Provide details for the fields.

    Field Description
    Focus View ID

    Enter the view ID attribute value associated with the target page. You can find it in the public_html/WEBINF/adfc-config.xml file of this application.

    • If you're linking to VB apps that have a URL starting with fscmUI/redwood/, then you enter the focus view ID as /index.html. For other VB apps, the focus view ID isn’t required. But, because it's a required field on the UI, you need to enter the value as /index.html.

    • If you're linking to Fusion Applications, enter the focus view ID as /FndOverview.

    For a quick action, by default, the focus view ID is displayed as /index.html.
    Web Application

    Select the name of the web application, which is the application name that you used while creating this application using the Setup and Maintenance work area.

    If you're linking to VB apps that have a URL starting with fscmUI/redwood, select ORA_FSCM UI. For other VB apps, select one of these: ORA FSCM UI, ORA HCM UI, or ORA CRM UI .
    Secured Resource Name and Application Stripe

    For secured access to the target application page, provide the secured resource name and the application stripe name of the policy store.

    When users click the application link, the application checks the secured resource and the Oracle Platform Security Services (OPSS) policy store and then determines whether the user has the privilege to view the page. Here's an example of a secured resource name:

    oracle.apps.view.pageDefs.CaseList_Form_Attach_UIShellPagePageDef

    You can get the application stripe from the jps.policystore.applicationid parameter in the application's weblogic-application.xml file. Examples of application stripes are crm, fscm, and hcm.

    Tip:

    To secure the custom page entry in the same way as an existing page entry, copy and paste the secured resource name value from a predefined page entry. Similarly, for a custom quick action, copy from a predefined quick action. You can’t create a new resource.

    VB Studio Flow Enter the VB Studio flow that your VB page is grouped in.
    Product Family Enter the name of the product family your VB Studio page belongs to.
    • VB App UI
    • VB Page Name

    If you're linking to VB apps that have a URL starting with fscmUI/redwood, fill out these fields:

    • VB App UI: Enter the web application UI name, which includes a UI component in the form of VB pages and flows. For example, /digital-sales.

    • VB Page Name: Enter the UI component that users interact with. For example, /p/mycustomers/salesday.
    Page Parameters List

    If the page takes parameters, then you can enter a semicolon-delimited string of name=value pairs (for example, org=m1;context=s1) in this field.

    You can use EL to specify the parameters. If the EL evaluates to an object, the toString value of that object is passed as the value of the parameter. An application page may display or act differently based on the parameters that are passed in. For example, if you're opening a page from one group on the home page or Navigator, the parameter might be set to status=Open, whereas if you're opening the page from another group, the parameter might be set to status=Closed.