Skip to main content

Document Management – Changed

Direct callers of the Document Management Command API v2 could get a false "Entity DocumentModel with id {id} not found" error on these endpoints when acting on a document whose real entity type is Screening (or any other type with no dedicated mirrored route) — entity type was previously derived only from the route name (product/deal/else Entity). Each endpoint now accepts an optional documentEntityType query parameter; when supplied, it is used to resolve the document's entity type instead of the route name. Omitting the parameter reproduces the previous behaviour exactly, so this is fully backward compatible. (AB#552592)

Affected Endpoints​

  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}
  • DELETE /documentmanagementcommand/api/v2/documentmanagement/{id}
  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}/access-layers
  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}/clone
  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}/requirement-ids
  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}/datakey
  • PUT /documentmanagementcommand/api/v2/documentmanagement/{id}/updateDocumentUploadedByUserName
  • PUT /documentmanagementcommand/api/v2/documentmanagement/error/{id}
  • PUT /documentmanagementcommand/api/v2/documentmanagement/custom-error/{id}