Workflow Steps
Overview
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.
- Workflow Steps use profiles to define access rights, transition notification, and transaction views. The Commerce system automatically creates a default profile for each workflow step. You can customize the default profile and create additional ones to support different transaction access rights.
- Profile permissions can be granted based on user access type, user groups, or previous performers. In addition to these permissions, you can add auto-forwarding rules to workflow steps to support a collaborative sales environment, one in which multiple users can work on the same transaction.
- Auto-forwarding rules direct the system to share transactions between members of certain user groups. You can create auto-forwarding rules for each workflow step and base them on any number of criteria.
View One-Page Step Administration Example
Standard Process Workflow Steps
Administration
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.
Notes
Notes:
-
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
In Oracle CPQ 23D, CPQ adopted Oracle CX Sales variable naming conventions for custom items. When an administrator creates a new custom Commerce item, the "_c" suffix is appended to the variable name. The new naming convention for custom variable names provides more consistency for integrations with Oracle Sales.
Beginning in Oracle CPQ 24C, customers can submit a service request to disable the "_c" suffix on variable names for custom Commerce entities (Actions, Analytics, Attributes, Data Columns, Integrations, Library Functions, Rules, Steps, etc.). The "_c" suffix is enabled by default for standard and legacy Commerce processes.
- Customers can submit a Service Request (SR) on My Oracle Support to disable the "_c" suffix on variable names for custom Commerce entities
- When the "_c" is disabled, the "_c" variable name suffix will not be required for newly created custom Commerce entities.
- Disabling the "_c" variable name suffix for custom Commerce entities will not change existing variable names.
- The "_c" suffix setting will not impact existing variable names when cloning a Commerce process or migrating Commerce items. Target variable names will be the same as the variable names from the source Commerce process.