BMQL is a SQL-based query language.

BMQL queries can be written to fetch data from Commerce attributes.

BMQL cannot be used to update data tables.

BMQL does not support Aggregate Functions.

The file name exceeds character limits.

CSV files are not valid file extensions that can be uploaded by using FTP.

The “_” used in the file name is invalid.

The apostrophe used in the file name is invalid.

the number of occurrences of the old that will be skipped from the beginning

the number of occurrences of the old that will be replaced from the beginning

an array of the new values

an array of the old values

by adding a column to Commerce Layout Editor

by adding a column to the Line Item Details layout in the Commerce Layout Editor

by adding a column and mapping it to the field in the line item grid in Commerce Layout Editor

by adding a field to the part database

Punch-Ins are links that hook into a specific Commerce process in the system. They can be used to navigate directly to a given Commerce process in your application. They can also be used to jump into a specific Commerce process from an external website.

Punch-Ins are links that hook into specific product families in the system. They can be used to navigate directly from a product family to another in your application. They can also be used to jump into a specific product family from an external website.

Punch-Ins are links that relate into specific parts in the system. They can be used to search directly for a given part in your application. They can also be used to search for a specific part from an external website.

Punch-Ins are links that hook into specific pages in the system. They can be used to navigate directly from one page to another in your application. They can also be used to jump to a specific page from an external website.

Punch-Ins are buttons that take you to specific pages in the system. They can be used to navigate directly from one page to another in your application.

defining an advanced BML (CPQ Cloud Language) function for that attribute

setting the message type as Static Entry when selecting an attribute to populate

setting the message type as Table Column when selecting an attribute to populate

defining a static text message for that attribute

by writing a Constraint rule

by writing a Hiding rule

by writing a Recommendation rule

by writing a Pricing rule

Proxy log in as superuser, go to the list of partner organizations, and select the partner organization and delete it.

Go to the list of partner organizations, perform a proxy log in as the superuser of the partner organization, go to the list of users, select all active users, and click Inactivate.

Proxy log in as superuser, go to the list of partner organizations, and select Denied in the Access drop-down list.

Open the list of partner organizations and set the value of Maximum Users to “0”.

Click the Add button on the User Administration List page; enter values for the required fields (Login, Password, Email, First Name, Last Name, and Phone Number); set the Type field to Admin; click the Add button to add the user to the system; click the new user’s name on the User Administration List page to edit the user; select the Add New Users check box; and click the Add button to save the changes.

Click the Add button on the User Administration List page; enter values for the required fields (Login, Email, and First Name); click the Add button to add the user to the system; click the new user’s name on the User Administration List page to edit the user; select the Create/Modify Users check box; and click the Update button to save the changes.

Click the Add button on the User Administration List page; enter values for the required fields (Login, Email, and First Name); set the Type field to FullAccess; select the Create/Modify Users check box, and click the Add button to add the user to the system.

Click the Add button on the User Administration List page, set the Type field to Admin, click the Add button to add the user to the system, click the new user’s name on the User Administration List page to edit the user, select the Create/Modify Users check box, and click the Update button to save the changes.

Click the Add button on the User Administration List page; enter values for the required fields (Login, Email, and First Name); set the Type field to FullAccess; click the Add button to add the user to the system; click the new user’s name on the User Administration List page to edit the user, select the Create/Modify Users check box; and click the Update button to save the changes.

(key) = (/library/book/@lang)(value) = (en)(value) = (fr)

(key) = (/lang/book/library)(value) = (en)(value) = (fr)

(key) = (/library/book/@lang)(value) = (English)(value) = (French)

(key) = (/library/book/@lang)(value) = (Spring in Action)(value) = (J2EE Blueprint)

Enable the Table of Contents option for selected heading styles.

Enable the Table of Contents option for all heading styles.

Assign a heading style set to the Table of Contents layout.

Create headings by using the Heading element for the section content in your template.

Assign page numbers to all heading elements.

Trigger an email action to notify users by custom defining the email’s subject and body, which contain the transaction details, by using the advanced function available in the Revise action.

When a transaction needs to be revised, allow the transaction owner to send a parallel email to approvers, which should include the necessary transaction details.

Switch the system-generated email-to-email template, which will include the desired transaction information when approvers are notified.

A host company FullAccess user create groups for partner organizations; however, the superuser of a partner organization can only assign users to existing groups.

The groups of a partner organization are maintained by FullAccess users belonging to the partner organization.

The groups of partner organizations are created by using the Bulk Upload utility or SOAP API calls.

Partner organizations use the same user groups defined for the host company.

Partner organizations have only users, but no user groups.

Use the Comment field to pass additional details.

Pass the additional details by storing them in a Price Book.

This is not feasible. Only Part Number, Quantity, and Price can be passed from Config to Commerce by using Recommended Item rules.

Concatenate the additional details to Part Number.

Use BOM Mapping rules.

migrations with the site as target

deployment of configuration product families

creation of data tables

modification of Commerce process objects

creation of configuration objects

uploading of files in File Manager

Creating separate BOM Item Mapping entries for each menu choice

Placing all the menu item choices in a single BOM Item Mapping table entry, separating each item with the ^|^ delimiter

Placing all the menu item choices in a single BOM Item Mapping table entry, separating each item with the *|* delimiter

Placing the menu choices in a separate CSV file and referencing the CSV file in the BOM Item Mapping table entry

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

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 number of 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.

ocpp-toolkit push -d /commerceAndDocuments/processDefinition/testProcess/

cpq-toolkit push /commerceAndDocuments/processDefinition/testProcess/

cpq-toolkit push --na-save-no-test /commerceAndDocuments/processDefinition/testProcess/

cpq-toolkit pull /commerceAndDocuments/processDefinition/testProcess/

Open Pipeline Viewer and verify the hierarchical JSON representation for the entire system data.

Use the Configuration ID value in the BML debugger to run the system configuration and validate the JSON response.

Check the Transaction XML to ensure all of the system models and child items have been correctly added.

Check the System Configuration log to ensure that the system has been configured correctly.

40

200

35

1000

Construct a return result stringin the following format and return this string: documentnumber-VariableName-value]

Add these values to a dictionary, along withappropriate keys, and return this dictionary.

Add all values to an arrayand return the array.

Return the values using multiple return statements.

Select the Child Section check box in the Section Properties panel for each subsequent section following the first section in the series.

Add each section to the template and manually remove the page breaks at the end of each section.

Add the first section in the series and select the Continuous Section check box in the Section Properties panel.

You do not have to do anything because this is the default behavior in Document Designer.

Select the Continuous Section check box in the Section Properties panel for each subsequent section following the first section in the series.

Write a Constraint rule to throw a runtime error on the Delete Action event.

Add an Advanced Validation rule on Delete Main Doc Action.

Ensure that all the parts are coming from a “mandatory” Recommended item rule.

Use CSS to hide the check box on Line Grid.

That the user is a Partner User

That the part number is valid

That the password used in the header of the SOAP call is correct

That the user has API access permissions

Live data tables do not need to be deployed after modification.

Web services are recommended to update live data tables over BMQL functions.

Insert, Modify, Delete, and Update are supported BMQL functions for live data tables.

Live data tables can be modified using UI, Web Services, BMQL, and Bulk Uploads.

Environments must have similar urls (for example, testcustomer and devcustomer).

Environments must be on the same major release (for example, 2016R2).

Environments must be on the same minor release (for example, 2016R2 update 2).

Administrators must have FullAccess logins for both environments.

Entities to be migrated must be deployed within 24 hours of the migration.

Step 5 is unnecessary. Session ID is not needed to log out.

The call in step 4 will throw an error.

Step 3 does not specify an action to execute; therefore, nothing is updated in the transaction.

The session will still be open.

The Commerce transaction should be updated with the new Ship To name.

The partner user approved the quote throughmobile approvals.

Integrations are not associatedwith theapprove action.

Thepartner user does not have accessto theattribute "status"in thepending stepwithin CPQ.

The partner user does not have the correctpartner info credentials.

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.

Test cases should be directly linked to business requirements.

Avoid using a test case tracking tool because it is time consuming to track all of the testing team’s efforts.

Perform isolated tests as well as intra-system and cross-system integration tests.

Create specific test data for accounts, opportunities, and contracts in the CRM system and use that data to perform end-to-end tests for CPQ Cloud quotes.

The Recommended Item rule is recommending a part that does not exist.

The Recommended Item rule is not firing.

The Recommended Item rule is recommending more than one-part number.

The Recommended Item rule is recommending an incorrect price for the part number.

SELECT and UPDATE

SELECT, INSERT, and DELETE

SELECT, INSERT, and UPDATE

SELECT

Both attributes 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.

Formula Administration

Util library function

Commerce library function

Auto Update