Update agreement by locating it via document ID

This operation updates a specific agreement by first locating it using its associated document_id. This is useful when the client knows the document storage identifier but not the agreement ID.

The operation accepts a document_id query parameter to uniquely identify the agreement, then applies the partial updates specified in the request body. The system will search for an agreement containing the specified document ID, and if found, apply the requested modifications. The operation returns a 204 No Content response on success.

This endpoint provides an alternative way to update agreements when the agreement ID is not readily available, making it convenient for systems that primarily work with document references rather than agreement identifiers.

Use Cases:

• Updating agreements referenced by document storage ID: When integration points provide document IDs but not agreement IDs, this endpoint allows direct updates without a prior lookup.
• Batch updating via external document references: Systems that track agreements through external document management systems can update agreements using their document storage identifiers.
• Cross-system synchronization: Update agreements based on document references from external systems (e.g., content management systems, document repositories) without maintaining agreement ID mappings.
• Document-centric workflows: In document-first business processes, update agreements using the document reference that users are familiar with.

Key Features:

• Document ID Based Lookup: Locate agreements by their associated document storage identifier rather than requiring the agreement ID upfront.
• Automatic Resolution: The system automatically finds the agreement associated with the provided document ID.
• Partial Updates: Modify only the fields you need; other agreement data remains unchanged.