Content Block Name Mapping for Appended Content Library Items

Enhanced the Append Content Library Item endpoint with block name mapping functionality:

• Append Content Library Item: Added optional block_mapping property to the response for tracking content block name changes during the append operation.

The block_mapping response includes mappings for content block types (tables, images, and text blocks), showing both the original names from the Content Library Item and their new unique names in the target document. This enhancement enables developers to programmatically reference and manage appended content blocks in subsequent API operations, ensuring accurate block targeting even when name conflicts require automatic renaming.

Example response structure:

{
  "block_mapping": {
    "tables": [
      {
        "original_name": "Products_Table",
        "new_name": "Products_Table_1"
      }
    ],
    "texts": [
      {
        "original_name": "Legal_Disclaimer", 
        "new_name": "Legal_Disclaimer"
      }
    ]
  }
}

This changelog emphasizes the practical value of the feature - solving the problem of tracking content blocks after they've been appended to documents, especially when name conflicts occur and automatic renaming is applied. The feature is particularly valuable for automation workflows that need to reference specific blocks after appending content library items.

POST /public/v1/documents/{id}/append-content-library-item

• added the optional property 'block_mapping' to the response with the '201' status