Commerce Action Destination Tab (Doc ID 1660401.1)

Last updated on OCTOBER 02, 2017

Applies to:

Oracle BigMachines CPQ Cloud Service - Version 11.0 and later
Information in this document applies to any platform.
Information in this document applies to any platform.

Goal

You can create destination rules for the Modify and Add from Catalog type actions.


The Destination tab contains different options depending on the combination of the type of action and type of document.

 

 

Add from Catalog Action

The Add from Catalog action supports both simple and advanced destinations.  These destinations are specified with the use of URL. The user can pass information from commerce to the catalog by appending the data to the query string of the URL.

 


Modify Action

A modify actions destination tab contains the following options:
 

  • Parent Page - This option specifies that upon clicking the action, the user will be taken to the parent page. For example, on a modify action called Save on the sub-document; the destination could be set to parent page.  Upon clicking this action, the user would be taken to the respective main document (parent of the appropriate sub-document).

  • Same Page - This option specifies that upon clicking the action, the user will remain on the current page. For example, on a modify action called Save on the main document; the destination could be set to same page.  Upon clicking this action, the user would remain on the current document.

  • Custom Destination - This option specifies that upon clicking the action, the user will be taken to the URL specified in this field. The valid value for this field is the relative path to any page on the CPQ Cloud application. For example, /commerce/buyside/commerce_list.jsp would be a valid value for the custom destination as the user will be taken to favorites page.

    • Add from Catalog actions only support URL parameters for model punch-ins. The custom destination cannot be used to pass URL parameters to Quotes, as can be done with Modify actions.
       
  • Partner Object Id Attribute - This option specifies that upon clicking the action, the user will be punched-in to the appropriate object on the partner site. A valid value for this field would be the variable name of the attribute which stores the partner object Id information. For example, if a commerce attribute with variable name partner_opportunity_id contained the partner opportunity id, this attribute variable name would be in the Partner Object Id attribute field.

  • Advanced Destination - This option specifies that upon clicking the action, the user will be taken to the URL returned by running a BML function. The valid value return value for this function is a string. Any URL whose relative path is a page on the CPQ Cloud application would be a valid return value. For example, /commerce/buyside/commerce_list.jsp would be a valid value as the user will be taken to favorites page.

     

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms