This topic provides information on each Winter '27 Patch Release for Industries CPQ product area for the fixes made in Platform.
264.5
| Issue | Description |
|---|---|
During Replace Offer (Change of Plan), the system
does not populate the SubAction__c field with
Reassign on parent and intermediate line items such as Additional
Internet Services. The system correctly assigns only leaf-level
items and does not create an OrderItemRelationship for the
affected items. |
The fix corrects the hierarchy processing so that
all applicable items are updated with the correct
SubAction__c field status.
|
| Before replacing an offer, the system could treat explicitly disconnected products as Active, reassign them to the new offer, and incorrectly include them in cardinality calculations, resulting in a false cardinality violation message. | Preserves disconnected items during reconciliation so they remain excluded from reassignment and cardinality calculation. |
In the MACD Cart, the system was marking newly added draft items
Action = Add) as Disconnected instead of hard deleting
them.
|
The fix removes draft items correctly, while existing items continue to follow the standard disconnect process. |
Replace Offer could create relationship records
that were not relevant to ReliesOn attribute propagation. These
records could contain empty identifiers and cause
priceCart to fail.
|
Empty identifiers are now handled safely, and error messages identify the correct object when a query fails. |
When two sibling items under the same parent are
auto-removed in a single Standard AddToCart call, the cart UI
reflects only one of the two removals. This is caused by a
response-parity issue in the itemdeleted action
node. Standard Cart emits one itemdeleted record
per auto-removed child and stamps every child slot with the full
set of deletedItemIds. Classic Cart emits one
record per surviving parent carrying all removed subtrees and
stamps each slot with only its own deletedItemIds.
This difference in response shape causes the UI to miss one of the
two sibling removals. |
Align the Standard AddToCart item deleted response with Classic Cart behavior. Auto-removed siblings are grouped into one record per surviving parent, and each slot is stamped with only its own deletedItemIds. |