The number of configurations completed for different product families by internal users and partner organizationusers.

The number of transactions for different Commerce processes created by internal users and partner organization users.

A list of active partner organization users with the most recent login date and time and the number of logins.

The numberof logins by internal users in the last 30 days and the percentage of active users logged in.

The total data size of the CPQ site occupied on the server.

The total number of partner organizations and the number of active partner organizations.

by providing conditional access criteria in the Restricted Access section of the home page setup

by setting up a restricted profile and user group in Commerce and hiding the add, reconfigure, and delete product options

by hiding the model Punch-In onthe home page by using JavaScript

by writing a Constraint rule at the Product Family level

Recommendation, Constraint, Hiding, RecommendedItem

Constraint, Hiding, Recommendation, Recommended Item

Constraint, Recommendation, Constraint, Hiding, Recommended Item

Hiding, Constraint, Recommendation, Recommended Item

Recommendation, Recommended Item, Hiding, Constraint

7,000

3,000

4,000

1,000

results = atoi (var);

results = atof (var);

results = stringtointeger (var);

results = stringtofloat (var);

Define different steps (for example, Pending A and Pending B) for each country. The participant profile of each step allows access through user groups (either Group A or Group B depending on the step). Using transition rules, make sure that quotes for Country A are always moved to steps belonging to that country.

Hide Transaction Manager in CPQ and make sure that all access to quotes is performed from the CRM system where you can easily define which quotes should be visible for different users.

Define two groups: Country A and Country B. Define a participant profile, Sales, for each step. Define an auto-forwarding rule which returns either “Group A~company~Sales” or “Group B~company~Sales.”

Define two groups: Country A and Country B. For each step, define two different participant profiles: Profile A and Profile B. For each profile, select one matching group.

https://testsite.bigmachines.com/rest/v1/commereceDocumantsExampleTransactions?totalResults=1000

https:///testsitebigmachines.com/rest/v1/commerceDocumantsExampleTransactions?pffset=1000

https://testsite.bigmachines.com/rest/v1/commerceDocumentsExampleTransactions?set=1000

https://testsite.bigmachines.com/rest/v1/commerceDocumentsExampletransactions?limit=1000

Bothattributes and library functions can be used as inputs for Formula Management.

Only attributes can be used as inputs for Formula Management.

Formulas can set both transaction- and line-level attributes.

Formulas cannot be run in sequence to perform multi-step calculations.

https:// /v2_0/receiver/commerce/oraclecpqo?WSDL

https://

https:// /ics/catalog

https:// /v1/receiver?WSDL