This section provides use case and explains how you can assign auto-included lines items for collaboration. 

CPQ displays the collaboration icon () next to an auto-included standalone or bundle line items if the APTS_EnableCollabForAutoIncludedLines admin setting is set to True. If you initiate a collaboration request for the parent product, CPQ automatically adds auto-included products as part of the collaboration. You can also create a collaboration request for auto-included products independent of the parent product. CPQ does not support collaboration request creation for auto-included option products; in this case, you must send the parent bundle for collaboration.

Prerequisites

  • The APTS_EnableCollabForAutoIncludedLines admin setting is set to True.
  • An Inclusion constraint rule is configured so that Product A auto-includes Product B and Product C.

Use Case 1: Create Collaboration Request for Product A

  1. You select Product A and create a collaboration request for it.
  2. While creating a collaboration request for Product A, CPQ automatically adds Product B and Product C as part of collaboration.
  3. Collaborator verifies Product A with Product B and Product C in the collaborator cart.
  4. Collaborator makes necessary changes to Product A, B, C and resubmits the configuration for merge.
  5. After you merge the configuration, changes to Product A , B, C are updated in the main cart.
  6. You can verify Product A, Product B, and Product C in the main cart.

Use Case 2: Create Collaboration Request for Product B, C, or Both

  1. You select Product B, Product C, or both and create a collaboration request for them.
  2. Collaborator verifies Products B, Product C, or both in collaborator cart.
  3. Collaborator makes necessary changes to Product B, Product C, or both and resubmits the configuration for merge.
  4. After you merge the configuration, changes to Product B, Product C, or both are updated in the main cart.
  5. You can verify Product A, Product B, and Product C in the main cart. The merge does not impact Product A in the main cart.

Use Case 3: Create Collaboration Request for Product A where Collaborator Deletes Auto-Included Products

  1. You select Product A and create a collaboration request for it.
  2. While creating a collaboration request for Product A, CPQ automatically adds Product B and Product C as part of collaboration.
  3. Collaborator verifies Product A with Product B and Product C in the collaborator cart.
  4. Collaborator makes necessary changes to Product A, deletes Product B, and resubmits the configuration for merge.
  5. After you merge the configuration, changes to Product A are updated and Product B is deleted from the main cart. CPQ displays a constraint rule message for Product B.
  6. You can verify Product A, Product B, and Product C in the main cart.

Use Case 4: Create Collaboration Request for Product A, Product B, and Product C

  1. You select Product A, B, and C and create a collaboration request for them.
  2. While creating a collaboration request, CPQ does not automatically add Product B and Product C as part of collaboration because you have manually added them.
  3. Collaborator verifies Products A , B and C in the collaborator cart.
  4. Collaborator makes necessary changes to Product A, B, and C and resubmits the configuration for merge.
  5. After you merge the configuration, changes to Product A, B, are C are updated in the main cart.
  6. You can verify Product A, Product B, and Product C in the main cart.