Return to main navigation Page
Participant Profiles are created for each step in the workflow. For each profile, you can define:
Assigning Users to Participant Profiles
There are 2 ways to assign users to Participant Profiles:
Here you can assign Participant Profiles based on:
Example: You could assign all
FullAccessWithESales users to a profile called Administrator, and all members of the Manager group access to the Approver profile for all quotes.
The Participant Profile seen by the user is the FIRST profile which evaluates to True. For this reason, you usually want to make an Admin Profile first.
You can use the Advanced Forward Rules to assign Participant Profiles to Groups, based on attributes in the quote. Participant Profiles will only be assigned when the step changes.
Example: If approvers are assigned to quotes according to a user hierarchy, you can define a quote attribute to store the name of the approver group (for example, Manager-East, Manager-West, and so on). In the Forward Rule, you can use that attribute to determine which groups to assign to the Approver profile for that quote.
The Expected format of return value is:
group~company~participantProfile [ |group~company~participantProfile ]*\
Defining Document Views
Document views determine what is visible to users in the participant profile. Choices for the document views depend on the entity. For tabs, the options are Show or Hide. For attributes, the choices are Read/Write, Read-Only, and Hide.
Defining Transitions and Notifications
Notifications: Notification emails can be defined for each transition; each recipient must receive the same message. Recipients can be defined using the Participant Profiles for the current step and next step, or by defining an advanced function to specify the email address.
Transitions: Transitions rules are defined per action per profile. Several transitions may be defined for the same profile and action. The first transition to evaluate as true will take effect.
An internal property gives CPQ Cloud customers the option to prevent Commerce read-only fields from being posted back to the server after a Commerce action is invoked.
While enabling this property will have nominal impact on performance, it is recommended not to post information back to the server when the data will not have changed since it was last posted.
To enable this property, open a ticket on My Oracle Support.