Process Administration

The Processes page displays a list of available processes, along with various navigation options, descriptions for the available Processes, and the date and time the processes were last deployed.

To access processes, navigate to:  Admin > Commerce and Documents > Process Definition

The Process Administration page provides information and settings for a Commerce Process.

To access a Commerce Process Administration page, navigate to:  Admin > Commerce and Documents > Process Definition > Process Name.

The following options are available on the Process Administration page:

1. Create a Process and save it.
2. Add main and sub-documents to the Commerce Process.
3. For each document, create attributes, actions, and views.
4. Develop XSL views for Print, Email, and Change History actions.
5. Customize Process actions for the Transaction Manager.
6. Create the Transaction Manager Column layout using Data Columns.

7. Design the Process workflow steps.

   In each workflow step, create participant profiles to control user access. Participant profiles must be further defined using:

   • User access rights
   • Transition rules
   • Document views

8. Set up forwarding rules within workflow steps to automatically forward Transactions to groups upon creating or saving a Transaction.
9. Create timers to automatically perform Commerce actions and auto-forwarding rules to support collaborative workflows.
10. Deploy the Commerce Process.

Complete the following steps to create a new Commerce Process.

1. Navigate to the Admin Home Page.

2. Click Process Definition in the Commerce and Documents section.

3. Click Add.

   

4. Enter a name in the Process Name field.

   The Process name you choose is used as the navigation link to the Commerce Manager.

5. Enter a unique Variable Name.

   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.

6. Enter a Description for the Process being added.

7. Select a Process Type.

   Notes:

   • The Process Type is not available for releases prior to Oracle CPQ 23B.
   • Standard Process is typically the only available option.

8. Use the Page Length drop-down to select the number of transactions you want to display on the Transaction Manager page.

   Note: This setting does not control the number of transactions displayed on the Redwood Quotes List UI.

9. Select the Auto Fill Options for new transactions.

   • None: New transactions are NOT auto-populated with user or accounts information.
   • User Information: New transactions are auto-populated with user information.
   • Accounts Information: New transactions are auto-populated with Accounts information.

10. Select dates in the Fiscal Year Start Date fields.

    The first field represents the month and the second field represents the day of the month.

11. Select the Quotes List Layout setting.

    • Select Redwood to enable the Redwood Quotes List UI.
    • Select Legacy to enable the legacy Transaction Manager.
12. Next to Secure Attribute Encryption Key, click Choose File to select a public key for secure attributes.

13. Select Stages to enable subsets of transactions within different phases of the transaction lifecycle.

    • Quote - the default phase of the transaction lifecycle.
    • Order - enables the ordering phase of the transaction lifecycle.
    • Agreement - enables the agreement phase of the transaction lifecycle.

    Notes:

    • Upon upgrade to Oracle CPQ 24D all current transactions are set to the Quote stage.
    • The Order stage is automatically enabled when a new Standard Process is created.
    • Once the Order stage is enabled for a Standard Process it can't be disabled.
14. Select the Transaction Editing Mode:
    • Collaborative Editing - Multiple users can edit a Transaction at the same time.
    • Transaction Locking - Single user can edit a Transaction at a time and it is locked when opened. Additional users can view the locked Transaction but cannot edit.
    • Single User - Single user can edit a Transaction at a time. Additional users are not blocked from starting a new editing session which supersedes existing sessions.

15. Click Add to save the Process and return to the Processes page or click Cancel to return to the Processes page without saving your changes.

16. After the process is created, proceed to Edit a Commerce Process to set the following parameters:

    • Execute Action If Associated Integrations Timeout
    • Tab Label
    • For Collaborative Editing or Transaction Locking modes:
      • Let Other Users Perform Unlock Actions
      • Actions to Automatically Unlock Transaction
    • Transaction UI Layout

Complete the following steps to modify a Commerce Process.

1. Navigate to the Admin Home Page.

2. Click Process Definition in the Commerce and Documents section.

3. Click the Process link in the Name column.

4. If desired, modify the Process Name.

   The Process name you choose is used as the navigation link to the Commerce Manager.

5. If desired, modify the Description.

   

6. Select the Execute Action If Associated Integrations Timeout option to allow an action to execute when an integration XSL or a middleware integration times out. By default, this checkbox is unselected.

   When selected, the action continues regardless of any associated integration timeout. A warning message displays to the end user, and Oracle CPQ logs information about the integration that timed out.

7. Select an attribute from the Tab Label drop-down.
8. Use the Page Length drop-down to select the number of Commerce Transactions you want to display on the Commerce Manager page.

9. Select the Auto Fill Options for new transactions.

   • None: New transactions are NOT auto-populated with user or accounts information.
   • User Information: New transactions are auto-populated with user information.
   • Accounts Information: New transactions are auto-populated with Accounts information.

   The first field represents the month and the second field represents the day of the month.

10. Select dates in the Fiscal Year Start Date fields.
11. Select the Quotes List Layout:
    • Select Redwood to enable the Redwood Quotes List UI.
    • Select Legacy to enable the legacy Transaction Manager.
12. Next to Secure Attribute Encryption Key, click Choose File to select a public key for secure attributes.

13. Select Stages to enable subsets of transactions within different phases of the transaction lifecycle.

    • Quote - the default phase of the transaction lifecycle.
    • Order - enables the ordering phase of the transaction lifecycle.
    • Agreement - enables the agreement phase of the transaction lifecycle.

    Notes:

    • Upon upgrade to Oracle CPQ 24D all current transactions are set to the Quote stage.

    • The Order stage is automatically enabled when a new Standard Process is created.

    • Once the Order stage is enabled for a Standard Process it can't be disabled

14. Select the Transaction Editing Mode:
    • Collaborative Editing - Multiple users can edit a Transaction at the same time.
    • Transaction Locking - Single user can edit a Transaction at a time and it is locked when opened Additional users can view the locked Transaction but cannot edit.
    • Single User - Single user can edit a Transaction at a time. Additional users are not blocked from starting a new editing session which supersedes existing sessions.

15. If applicable, select Let Other Users Perform Unlock Actions to allow users who did not lock a Transaction to unlock the Transaction using Document-level Unlock Actions.

16. If applicable, select actions from the Actions to Automatically Unlock Transaction drop-down to define actions that automatically unlock a Transaction when performed by the user who locked the Transaction.
17. Enable Transaction UI Layouts:
    • Select Redwood to enable the Redwood Quote UI layout (available beginning in Oracle CPQ 24D).
    • Select JET Responsive to enable the JET Responsive Transaction UI layout.
    • Select Legacy Desktop to enable the legacy layout.

18. Click one of the following actions:

    • Apply to save the Process and refresh the page
    • Update to save changes and return to the Processes page
    • Cancel to return to the Processes page without saving your changes.

Complete the following steps to enable the Order and/or Agreement stage(s) for a Commerce Process.

1. Navigate to the Admin page.

2. Click Process Definition in the Commerce and Documents section.

3. Click on the Name link for the applicable Commerce process.

4. Select the Order and/or Agreement option(s) for the Stage setting.

5. Click Apply or Update.

Complete the following steps to deploy a Commerce Process.

1. Navigate to the Admin Home Page.

2. Click Process Definition in the Commerce and Documents section.

3. Select Deployment Center from the applicable process Navigation drop-down, and then click List.

4. Select the Deploy Event Type.

5. Select the Send Confirmation Email To:

   • Do not send email, or

   • Email to and enter the email address of the person you want to receive the deployment confirmation email.

6. To schedule a deployment, enter the desired date and time (in mm/dd/yyyy hr:mm AM/PM format) in the Scheduled Time field.

7. Click Add Event.

   

8. If desired, you can cancel the scheduled deployment by selecting the new event and clicking Delete.

   You cannot remove an event if the deployment has already started.

9. Click Refresh to display the updated information on the page.

Complete the following steps to delete a Commerce Process.

1. Navigate to the Admin Home Page.

2. Click Process Definition in the Commerce and Documents section.

3. Select Deployment Center from the applicable process Navigation drop-down, and then click List.

   

4. Select Delete Process from the Deployment Center page for the Commerce process.

   

5. A confirmation of delete message displays indicating that the process and all related data and transactions will be deleted. Click OK to proceed with the deletion or Cancel to not perform the delete action.

   

   Recovery of the Commerce process and its associated data is not possible. Make sure you want to move forward with the delete option before you click OK.

6. Enter the date and time to schedule the delete event and click Add Event. The Commerce Process delete action is scheduled to delete.

   

Oracle CPQ 24D provides the ability to limit attribute size for potentially large attributes on a transaction. Size limits can be implemented for Rich Text, Text Area, History, and File Attachment attributes. Additional size limitations can be implemented to limit total allowed size of large attributes for a transaction and a transaction line

When large attribute size limitations are implemented for a CPQ site the individual attribute value size limits, transaction size limit, and transaction line limit are displayed on the Commerce Process Administration page. User errors are also displayed for the following user actions:

• A user attempts to add an attribute value that exceeds limitations

• A user tries to save or open a transaction with large attributes that exceed the transaction or transaction line limitation

The following large attribute size limitations are automatically provisioned for new site implementations:

• Rich Text – 32 kb
• Text Area – 32 kb
• History - 32 kb
• Main Document - 100 MB
• Sub Document - 5 MB