Configure Quick Actions

Use the Navigation Configuration page to create, edit, and configure quick actions.

For groups with associated quick actions, use the Quick Actions tab to create more quick actions or make changes to the existing ones, such as rename, show or hide, and reorder them.

Create Quick Actions

You can either create a quick action afresh or duplicate an existing one.

Create Quick Actions Afresh

Follow these steps:

  1. Activate a sandbox that has the Structure tool in it.

  2. Click Navigator > Configuration > Structure.

  3. On the Navigation Configuration page, click any group (for example, Me and My Team) that has quick actions enabled.

  4. On the Edit Group <Group Name> page, click the Quick Actions tab and click Create.

  5. Enter a name for the quick action.

  6. In the Image field, search for and select an icon for the quick action.
  7. In the Group field, select the quick action group you want to place this quick action in.
    Note: The Group drop-down list displays quick action groups (for example, Hiring and Onboarding) based on the group (for example, My Team) you selected on the Navigation Configuration page.
  8. From the Visible list, select Yes, No, or EL Expression.
    • Yes: The quick action appears on the home page.
    • No: The quick action doesn't appear on the home page.
    • EL Expression: The evaluation of the EL Expression decides whether the quick action will appear on the home page for specific user roles.
  9. If you have selected EL Expression from the Visible list, click the Edit icon next to the Visible list. Then enter a value or expression and click Validate to make sure that the validation result is True. Don't include spaces or double quotes in the EL expression.
  10. From the Mobile Enabled list, select Yes or No to specify whether the quick action will be available for mobile devices. This setting isn't applicable for the panel or banner layout.
  11. Select any of these link types:
    • An application page.
    • A Static URL of an external page (outside your application) where the host, port, or context root doesn't change.
    • A VB Studio page, which is built using Visual Builder Studio and Oracle Java Extension Toolkit.
  12. Based on the link type, specify the required details to configure the link.
  13. Click Save and Close.

Create Duplicate Quick Actions

To create quick actions by duplicating an existing one, follow these steps:

  1. Activate a sandbox that has the Structure tool in it.
  2. Click Navigator > Configuration > Structure.
  3. On the Navigation Configuration page, click the group (for example, Me and My Team) that includes the quick action you want to configure.
  4. On the Edit Group <Group Name> page, click the Quick Actions tab.

  5. From the list of quick action groups, expand the required group and click the quick action you want to duplicate.

  6. On the Edit Quick Action page, click Create Duplicate and edit the duplicate quick action as required.
  7. Click Save and Close.

Configure Links for Quick Actions

While creating a quick action or editing an existing one, you can determine what the quick action links to.

Use the Create Quick Action or Edit Quick Action page to link a quick action to any of these link types.

  • Your application page.
  • A static URL of an external page (outside your application) where the host, port, or context root doesn't change. Static URLs don't require lookups.
  • A VB Studio page, which is built using Visual Builder Studio and Oracle Java Extension Toolkit.

Link to Application Pages

To link a quick action to one of your application pages, do these tasks:

  1. Select the Application Page link type.
  2. Enter the task flow ID.
  3. Enter the focus view ID of the target page.
  4. From the Web Application list, select the name of the web application.

    You entered this application name while creating this application using the Setup and Maintenance work area.

  5. For secured access to the target application page from the quick action, 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.

  6. If the page takes task flow parameters, then you can enter a semicolon-delimited string of name=value pairs (for example, org=m1;context=s1) in the Task Flow Parameters field.
  7. You can use Expression Language (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.

Link to VB Studio Pages

To link a quick action to one of your VB Studio pages, do these tasks:
  1. Select the VB Studio Page link type.
  2. By default, the focus view ID is displayed as /index.html.
  3. From the Web Application list, select the name of the web application.

    You entered this application name while creating this application using the Setup and Maintenance work area.

  4. For secured access to the target application page from the quick action, 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.

  5. Enter the VB Studio flow that your VB page is grouped in.
  6. Enter the name of the product family your VB Studio page belongs to.
  7. If the page takes task flow parameters, then you can enter a semicolon-delimited string of name=value pairs (for example, org=m1;context=s1) in the Task Flow Parameters field.

    You can use Expression Language (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.

Link to Static URLs

You can link a quick action to an external website or application that has a constant host, port, or context root. To link a quick action to a static URL:
  1. Select the link type.
  2. From the Web Application list, select the name of the web application.
  3. 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.

Edit Quick Actions

When using the news feed home page layout, you can configure quick actions using the Structure work area.

You can do these tasks:
  • Change the name and visibility settings of quick actions.
  • Change the display order of both the quick action groups and the quick actions within the group.
  • Designate quick actions as frequently used so that they appear as quick links on the home page.

If you configure a quick action that is included in multiple groups, the changes will apply only to the quick action under the configured group. For example, if a quick action is included in both the My Team and Me groups, and you modify the quick action under the My Team group, the changes apply only to the quick action under the My Team group (not under the Me group).

Configure the Name and Visibility Settings of Quick Actions

  1. Activate a sandbox that has the Structure tool in it.
  2. Click Navigator > Configuration > Structure.
  3. On the Navigation Configuration page, click the group (for example, Me and My Team) that includes the quick action you want to configure.
  4. On the Edit Group <Group Name> page, click the Quick Actions tab.
  5. From the list of quick action groups, expand the required group and click the quick action you want to configure.
  6. On the Edit Quick Action page, change the name of the quick action.
  7. From the Visible list, select Yes, No, or EL Expression.
    • Yes: The quick action appears on the home page.
    • No: The quick action doesn't appear on the home page.
    • EL Expression: The evaluation of the EL Expression decides whether the quick action will appear on the home page for specific user roles.
  8. If you have selected EL Expression from the Visible list, click the Edit icon next to the Visible list. Then enter a value or expression and click Validate to make sure that the validation result is True. Don't include spaces or double quotes in the EL expression.

  9. Click Save and Close.

Reorder Quick Actions and Configure their Groupings

You can reorder quick action groups as well as quick actions within a group. You can also move a quick action to a different group.

  1. Activate a sandbox that has the Structure tool in it.
  2. Click Navigator > Configuration > Structure.
  3. On the Navigation Configuration page, click the group (for example, Me and My Team) that includes the quick action you want to configure.
  4. On the Edit Group <Group Name> page, click the Quick Actions tab. You can do these reordering tasks using the icons in the Order column.
    • To reorder any quick action group, click the Move Up or Move Down icons for the required group.
    • To reorder the quick actions within a quick action group, expand the group and click the Move Up or Move Down icons for the required quick action.
    • To move a quick action to a different quick action group, expand the group, and click the Move To icon for the required quick action. On the Move To: Group dialog box, click the quick action group you want to move the quick action to.
  5. Click Save and Close.
    Note: The reordering of quick actions within a quick action group affects only how the quick actions are displayed for your users on the home page. But when the users click the Show More link under the Quick Actions section of the home page, the quick actions are alphabetically sorted, and your reordering isn't reflected there.

Configure Frequently Used Quick Actions

  1. Activate a sandbox that has the Structure tool in it.
  2. Click Navigator > Configuration > Structure.
  3. On the Navigation Configuration page, click the group (for example, Me and My Team) that includes the quick action you want to configure.
  4. On the Edit Group <Group Name> page, click the Quick Actions tab.

  5. From the list of quick action groups, expand the required group and click the quick action you want to configure as a frequently used action.

  6. On the Edit Quick Action page, select the Add as a quick action link on home page check box.
  7. Click Save and Close.