Create UI-Based Smart Actions

If you're using the Redwood user experience of Oracle Sales, Service Center, and Help Desk, then you can create custom smart actions that navigate users to a new UI location.

To create a UI-based smart action:

1. Enter into a sandbox that's enabled for Application Composer.

2. In Application Composer, click Smart Actions, available under Common Setup.

3. On the Smart Actions page, click Create.

   Application Composer displays the Create Smart Action guided process in a new browser tab.

   

4. Select UI-based action and click Continue.

5. First, set the basic details for the action.

   1. In the Name field, enter a display name for the action.

   2. In the Object field, select the object for which you're creating the action.

   3. In the Action ID field, accept the automatically generated value or enter a unique value.

      This value must be unique across all smart actions.

   4. Click Continue.

6. Specify the availability for the action.

   1. In the Application field, select the application where the action will display, such as Sales or Service.

   2. In the UI Availability field, select the UI where the action will display in addition to the Action Bar. For example, select List page.

      Note: For the smart action to be available in Orchestration automation steps, in the Application field, select Sales and in the UI Availability field, select Sales Orchestration.

   3. In the Role Filter field, optionally select the custom roles that can view the action.

      If you don't select a role, then the action will be available to all roles.

   4. In the Condition region, optionally set conditions for the action to appear, such as only if a certain field's value is set to a particular value. For example, show a smart action only if a lead's status is Hot.

      • Define one or more conditions in a group.

      • You can define one or more groups of conditions.

      • In the Attribute field, start typing an attribute name and select from the available list. The list of attributes in this field includes all REST-enabled attributes.

        Enable attributes in your Adaptive Search setup to ensure this smart action condition works on list pages and in Workspace.

      If you don't specify a condition, then the action will always be available based on other parameters that you specify, like role and application.

   5. Click Continue.

7. On the Action Type page, provide action metadata for the type of action you're creating.

   This step is required for smart actions created for custom objects. If the ORA-REDWOOD-SALES-UI feature is enabled, then this step is also required for some standard objects.

   1. In the Type field, specify the type of action, such as Add, Create, and so on.

      Note: Any Show actions that you create are used only by Sales Orchestration flows, and aren't displayed in the Action Bar, list pages, or CX Sales Mobile.

   2. In the Target Object field, select the object that you're creating the action for.

      For example, if you're creating an Add Contact smart action on the Account object, then the Type is Add and the Target Object is Contact.

   3. Use the Field Mapping region to map one or more values from a parent object record to a child or related object record.

      For example, when users use a smart action to create a related object record, you might want the create related object record page to be prepopulated with additional values from the parent record.

   4. Click Continue.

8. On the Action Details page, in the Navigation Target field, select Local and then click Continue.

9. On the Review and Submit page, review the action's configuration and click Submit when ready.

Example of a UI-Based Smart Action for a Child Object

Here's an example of creating a UI-based smart action for a custom child object.

In this example, we'll create a Create Payment Lines smart action for a parent/child relationship between the Payment custom object and the Payment Line child object.

1. Create a sandbox.

2. In Application Composer, under the Common Setup menu, click Smart Actions.

3. At the top of the page, click Create.

4. On the Kind of Action page, click UI-based action and then click Continue.

5. On the Basic Details page, in the Name field, enter the smart action name.

   For example, enter Create Payment Lines.

6. In the Object field, select your child object's parent object. In this case, select Payment and then click Continue.

7. On the Availability page, in the Application field, select Sales.

8. In the UI Availability field, select List Page and click Continue.

9. On the Action Type page, in the Type field, select Create.

10. In the Target Object field, select the child object.

    For example, select PaymentLineCollection_c.

11. Click Continue.

12. On the Action Details page, in the Navigation Target field, select Local if this is a required field in your environment, and then click Continue.

13. On the Review and Submit page, click Submit.

Example of a UI-Based Smart Action for a Related Object (One-to-Many)

The previous procedure illustrates how to create a smart action for a child object. This procedure illustrates how to create a smart action for a related object (one-to-many).

Let's look at an example where the Payment custom object is in a one-to-many relationship with a custom object called Shipment. At runtime, users should be able to create shipments directly from a payment.

Note: To create a smart action for a related object, you must first retrieve the relationship name from Application Composer.

Let's create the Create Shipment smart action:

1. Create a sandbox.

2. In Application Composer, under the Common Setup menu, click Smart Actions.

3. At the top of the page, click Create.

4. On the Kind of Action page, click UI-based action and then click Continue.

5. On the Basic Details page, in the Name field, enter the smart action name.

   For example, enter Create Shipment.

6. In the Object field, select the one-to-many relationship's source object.

   In this case, select Payment and then click Continue.

7. On the Availability page, in the Application field, select Sales.

8. In the UI Availability field, select List Page and click Continue.

9. On the Action Type page, in the Type field, select Create.

10. In the Target Object field, under the Top Level Object heading, select the one-to-many relationship's target object.

    For example, select Shipment.

11. In the Field Mapping region, click Add.

12. In the Actions column, click the Edit icon and then set these field values:

    

    Field Mapping

    Column	Value
    Name	Select the field on the one-to-many relationship's target object that holds the source object's ID and relationship name. This is a standard field on the target object (Shipment). The format of the field name is always <Source object name>_Id_<Relationship name>. For example, select Payment ID PaymentShipment1M (Payment_Id_PaymentShipment1M). Note: You won't see this field on the target object in Application Composer.
    Type	Attribute
    Value	Select Record ID (Id). This is a standard field on the source object (Payment). This means that when users create a shipment, the create smart action defaults the payment's ID into the shipment record's Payment ID PaymentShipment1M (Payment_Id_PaymentShipment1M) attribute.

    When users navigate to the page to create a shipment, you might want the create shipment page to be prepopulated with additional values from the payment record. Here's how to configure the Create Shipment smart action to do that.

    Field Mapping

    What to Pass?	Smart Action Setting
    Pass a value from the source object record to the target object record	Let's say that both the Payment and Shipment objects have Email fields. You can configure the Create Shipment smart action to prepopulate the payment's email on the new shipment record. Name: Email (Email_c) Type: Attribute Value: Email (Email_c)
    Pass a hard-coded value to the target object record	You can configure the Create Shipment smart action so that it always passes a hard-coded value to the new shipment record. For example, maybe each time the Create Shipment smart action creates a shipment record, the shipment name is prepopulated as Manual payment. Name: Shipment Name (RecordName) Type: User-entered Value: Manual payment

    Here's a screenshot of the settings described above:

    

13. Click Done.

14. Click Continue.

15. On the Action Details page, in the Navigation Target field, select Local and then click Continue.

16. On the Review and Submit page, click Submit.