Adobe Connect 11.8.1 Release Notes

Introduction

This document describes the fixed issues and new features in Adobe Connect v11.8.1:

New Features

• CAD-2349 / CAD-2350. The connector supports the Adobe Recommendations API in preparation for an upcoming release that will introduce recommendations during the change order process to drive upsell and cross-sell opportunities.

Fixed Issues

• CAD-2389. We resolved an issue where, in certain scenarios, Adobe return or change requests could become stuck in a "pending" state after the connector successfully processed an autorenewal update with Adobe. Although the operation was completed on the Adobe side, the request would not transition to its final approved state and no follow-up task would appear in the DevOps extension, requiring manual intervention to unblock the request.

• CAD-2388. We have identified and resolved an issue where Three-Year Commitment (3YC) requests were being automatically triggered for Adobe orders even when the 3YC field was not selected by the partner. Moving forward, the connector logic has been refined to ensure that expired commitment data does not persist or interfere with new purchase requests, ensuring that 3YC status accurately reflects the partner's selection at the time of order placement.

• CAD-2387. We have resolved an issue where certain renewal orders, particularly those with a zero-euro value, remained stuck in a "provisioning in progress" or "subscription prices recalculation" status due to a JSON processing failure. This defect has been addressed, ensuring that the fulfillment payload now includes complete and valid JSON data to allow for the successful completion of the provisioning workflow.

• CAD-2382. Fixed an issue where Adobe change requests could become stuck in the "revoking" state. In certain scenarios, when a revoke operation was initiated on a purchase request containing an inactive Adobe subscription, the process would fail due to an attempt to modify a subscription that Adobe no longer considers editable.

• CAD-2380. An issue has been resolved where certain Adobe subscriptions failed to automatically generate adjustment requests following their renewal on the Adobe side. Investigation revealed that scheduled tasks within the Adobe connector experienced unexpected execution halts, preventing the synchronization of renewal statuses to the CloudBlue platform.

• CAD-2365. Fixed an issue where Adobe scheduled change requests involving a 3-Year Commitment (3YC) recommitment could fail with the error "The three-year recommitment cannot proceed because there is no active 3-Year Commitment on the customer account." This occurred because the customer's benefits information was no longer available from Adobe at the time the scheduled request was processed on the renewal date, even though the recommitment had been properly accepted when the request was originally placed. The connector now handles this scenario correctly, ensuring that 3YC recommitment requests are processed successfully.

• CAD-2364. Fixed an issue where an automatic renewal request could be incorrectly rejected on Connect with the error "Manual renewable subscriptions in Adobe are not available for the asset items" when the subscription included SKUs in a scheduled status (i.e., newly added SKUs not yet processed by Adobe at the time of renewal). Instead of waiting in "Pending" status until Adobe completed processing of the scheduled SKUs, the connector treated them as unavailable and rejected the request outright. The connector now correctly handles scheduled SKUs during renewal, allowing the request to wait until Adobe-side processing is complete before proceeding.

• CAD-2362. We have resolved an issue within the Adobe purchase validation flow where partners were unable to complete new orders for existing customers who had previously been migrated via seamless move. Previously, the system strictly required a First Admin Email during validation even if the customer record already existed; however, because this field was non-editable and returned as empty for migrated accounts, it triggered a blocking error on the "Setup your purchase" page. The validation logic has been updated to ensure that additional purchases can proceed seamlessly without manual email re-entry or UI blocks.