Workflow Steps


Workflow administration is the final step in setting up a Commerce Process. Workflows are made up of steps, which define the states transactions can be in, as well as document permissions and routing. Commerce Processes can have any number of workflow steps.

For example, an RFQ process could have steps like "Submitted", "Quoted", "Accepted", "Declined" and "Expired". These steps could transition a transaction from an RFQ document, to a Quote document, then to a PO document.

ClosedView One-Page Step Administration Example

Example of One-Page Step Administration

ClosedStandard Process Workflow Steps

Beginning in Oracle CPQ 23B, the Standard Process is delivered for new Oracle Sales integrated site installations and is the default process when creating a new Commerce process. The Standard Process provides pre-defined workflow steps to manage quote approvals and order management.

The following steps are automatically created when a new Standard Process is created.These steps can be modified to meet customer workflow requirements. Note that steps cannot be deleted once a process is deployed.

Standard Process Workflow Seps


You can add, edit, and delete all steps, profiles, transition rules and timers from a single page. Steps and profiles are organized in a hierarchical tree structure for ease of administration. You can re-order your steps and profiles and move transition rules using drag and drop.

ClosedHow it's all related

Workflow Step relations

ClosedCreating Workflow Steps

Steps (document states) can be created individually from the Step List page. We recommend creating all of the steps in a workflow before managing profiles.

  1. Navigate from the Admin Home Page > Commerce and Documents > Process Definition > Select a Commerce Process > Steps.
  2. Enter a step Name and Variable Name. The name is displayed when you encounter the step. For example, Start.

    The Variable Name field populates automatically. Variable names can only contain alpha-numeric characters and underscores. The entry can be changed before saving, but after saving the value is read-only.

  3. Enter a Description for the step. For example, Default Step.
  4. Click Save.

    Dreate Workflos Steps dialog

    This displays the section where you can define forwarding rules for the step. Forwarding rules are used to give one or more user groups access to transactions during that step.
    To understand the concept of auto-forwarding rules, see the topic Forwarding Rules.
  5. Specify the following in the Forward Rule section:
    • Select No Forward Rule if you do not want to add a forwarding rule. This is the default section.
    • Select Simple Forwarding Rule if you want to add a forwarding rule that doesn't require BML.
    • Select a Profile from the drop-down provided.
    • Choose All Groups if you want to link this step to all the groups or select individual group names if you want to link this step to a few selected groups. Select multiple group names using the CTRL key from the names provided in the list box.
    • Select Advanced Forward Rule if you want to add an advanced forwarding rule and click Define Function. This opens the Commerce BML Editor window.
    1. Forward Ruld
  6. Click Save. The new step appears in the right panel.

    To edit workflow steps, double-click the Step name in the right pane.
    Steps are created in an inactive, pending state. After all components of a Commerce Process have been completed, the process should be deployed. For more information, see the topic Commerce Deployment Center.



  • All workflow step functionality can be administrated in Commerce Processes that have not been deployed. Steps cannot be deleted after a process has been deployed.

  • IDs and descriptions for all steps can be viewed easily after accessing the Workflow page. You can view them by clicking a Step name.
  • You can use the Filter feature to dynamically drill down through the Steps, Profiles, Actions and Rules. For example, you could type "Sales" into the Filter, and any Step Profile, Action or Transition Rule that has "Sales" in the name would dynamically display, improving the speed of maintenance.
  • When performing a Mass Update, users can filter which steps the update applies to.

Custom Variable Name Conventions

Beginning in Oracle CPQ 23D, CPQ will adopt Oracle CX Sales variable naming conventions for custom items. When administrators create new custom entities in a Standard or non-Standard Commerce Process, an “_c” suffix will be appended to the variable name.

  • The new naming convention for custom variable names provides more consistency for integrations with Oracle CX Sales.
  • This update only effects new custom entities, and there is no change to existing custom entities.

Related Topics

Related Topics Link IconSee Also