-
Type:
Improvement
-
Status: Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 2023.x, 2021.32
-
Component/s: BlobManager, Core, Retention
-
Release Notes Summary:Retainable simple blob list are now properly dispatched to the record blob provider
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform #81
When defining a blob list property such as:
<xs:complexType name="content"> <xs:sequence> <xs:element name="encoding" type="xs:string"/> <xs:element name="mime-type" type="xs:string"/> <xs:element name="data" type="xs:base64Binary"/> <xs:element name="name" type="xs:string"/> <xs:element name="length" type="xs:long"/> <xs:element name="digest" type="xs:string"/> </xs:sequence> </xs:complexType> <xs:complexType name="blobList"> <xs:sequence> <xs:element name="item" type="nxs:content" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:element name="repairQuotes" type="nxs:blobList"/>
and making this property retainable with:
<property schema="claim" name="repairQuotes" retainable="true">
the blobs added to a document on this property won't be dispatched to the record blob provider when the document becomes a record. With the above contrib, the xpath processed by the blob dispatcher will look like "repairQuotes/2"
The dev done in NXP-31397 took into account only the case of a list of complexes containing a blob such as "files:files" for which processed xpath looks like "files/1/file"
- is caused by
-
NXP-31397 Save retained properties in ecm:retainedProperties
-
- Resolved
-
