Migration of QPP-NG from v4.3.2 to v4.3.3

Changes in APIs

Newly Introduced APIs

Pinning/Unpinning APIs

This release introduces a new set of APIs designed to provide explicit and robust control over the pinning and unpinning of child components (asset relations). These APIs offer developers the ability to programmatically manage the relationships between assets with enhanced validation and detailed error reporting.

The key additions are as follows: 

  1. preparePinningData: This API validates the first-level child relationships of a given asset, ensuring that no child component is in an editing (checked out) state before pinning, thus maintaining data integrity. 

  2. upsertAssetRelations: This API handles the creation and updating of asset relations. It validates the accessibility of parent and child assets and allows overwriting existing relations, providing flexibility in managing dependencies. 

  3. pinAll: This API pins all first-level child components of a specified parent asset and branch. It performs validation to prevent pinning checked-out components and provides a message upon successful pinning. 

  4. unpinAll: This API unpins all first-level child components of a specified parent asset and branch, allowing for the removal of pinning constraints. 

Migrating to these APIs will provide improved validation, flexibility, and performance in managing asset dependencies, replacing any previous implicit mechanisms with explicit control over pinning and unpinning operations. Detailed information can be found in the Quark Developer Portal.