You are here: Commerce Process > Commerce Documents > Commerce Actions

Commerce Actions


Commerce actions trigger events within documents to occur. The Commerce system creates a default set of actions for use in each document, and generates additional actions when Commerce documents include certain attribute types.

Both main documents and sub documents can consist of system-generated actions as well as user-defined actions, created based on supported action types. Because actions are required to carry out operations based on the business logic, they are comprised of components.

All Commerce actions are administrated from the Actions for Document page. You can customize system-generated actions by modifying action labels and creating action rules.

In addition to the system-generated action defaults, you can also create custom actions for the purpose of saving document data, directing the system to a different page, offering print or email options, and showing the change history for a document.

Users usually perform Commerce actions, but timers can be set up so the system can automatically perform Commerce actions after specified periods of time.

Action Display Types Description
Buttons Buttons signify most actions like send, respond, update, and so on.
Hyperlinks Hyperlinks designate specific actions, like r;open sub-document and r;view Account data.

ClosedOrder of Operations

ClosedComponents (Tabs)

ClosedUser-Defined Commerce Actions

FullAccess users can define actions in a Commerce Process. All the action types below are common for the main document and sub-document.

ClosedSystem-Generated Commerce Actions

ClosedMain-Document System Actions

ClosedSub-Document System Actions

ClosedGroup Sequence Number

End users can view recommended items and child line items with sequence numbers that are counted based on the parent line item's sequence.

Example: A parent line item can have a group sequence number of 1 and then the child items will have group sequence number of 1.1, 1.2, 1.3...and so on. This functionality is enabled when you add the _group_sequence_number attribute to the attribute list and the line item grid instead of _sequence_number.

ClosedEnabling Group Sequence Numbers


ClosedDestination Tab

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:

ClosedRules-Based Destination using an Advanced Function

ClosedCreating Destination Rules for a Modify Action

ClosedCreating Destination Rules for an Add from Catalog Action

ClosedPopulating a Multi-Select Menu in Configuration

ClosedDocument Views Tab

The Document Views tab allows the FullAccess user to control the display of an action to users in different steps of the transaction. The FullAccess user can make the action active or inactive in a certain step to a particular participant profile.

ClosedGeneral Tab

The General tab is the only tab that is common to all action types. It holds action information such as Label, Variable Name, Modifications and Validations.

ClosedIntegration Tab

The Integration tab (displayed only if the site is integrated to a partner) determines the order in which data is exchanged between CPQ Cloud and a partner application. The order in which the integration XSLs are specified in this tab determines the order in which data is either sent to or received from the partner.

ClosedModify Tab

The Modify tab is available for all 'Modify’ type actions (system-generated or user-defined). This tab controls the manner in which a transaction gets its data; it allows you to manipulate the values in the attributes by specifying behavior in this tab. The Modify tab contains a list of all attributes available in the current tab with five options for each attribute.

ClosedUsing the Modify Tab to Set Your Behavior

ClosedSpecial Tabs


ClosedAdding Commerce Actions

  1. Click Add at the bottom of the Actions List page.
  2. Enter a Name. This field will be used to link back to edit the action.
  3. Enter a unique Variable Name. Do not use any special characters on this field.

  4. Select your desired Action Type from the drop-down.
  5. Click Add to save changes and open Admin Action editor or click Cancel to return to Document List without saving changes.
  6. Edit the tabs available. Refer to the Tabs section above.
  7. Select one of the following:

ClosedDeleting Commerce Actions

  1. Mark the checkbox of the desired under the Select column within the Actions List page.

  2. Click Delete.

ClosedEditing Commerce Actions

  1. Modify the Label. The Variable Name field will appear in read-only format in edit mode.
  2. Modify the Description, if required. The description is for your reference and appears on the Actions for Document page.

  3. Edit the desired rules associated with the action.
    1. Edits are not visible until the process is deployed (or redeployed). All actions besides system defined actions can be deleted even after a process has been deployed.

ClosedFormulas in Reconfiguration Scenarios

The Reconfigure action is split into one parent (Reconfigure) and one sub-action (Reconfigure Inbound). This eliminates the need for conditionals to segregate logic.



Related Topics Link IconSee Also