h3 Overview
TAS is responsible for providing attachment ability for humn task.
In B4P case, TAS will basically play the same role, and so far , no big logic change is found for B4P Humantask implementation, besides some changes on Attachment meta data and properites.
As a conclusion, most part of TAS will not be changed (or in another word reused).
<xsd:complexType name="attachmentMetadata">
<xsd:sequence>
<xsd:element
name="mimeType"
type="xsd:string"
minOccurs="1"
maxOccurs="1" />
<xsd:element
name="filename"
type="xsd:string"
minOccurs="1"
maxOccurs="1" />
<xsd:choice>
<xsd:element
name="localFileURL"
type="xsd:anyURI"
minOccurs="1"
maxOccurs="1" />
<xsd:element
name="payload"
type="xsd:base64Binary"
minOccurs="1"
maxOccurs="1" />
<xsd:element
name="plaintext"
type="xsd:string"
minOccurs="1"
maxOccurs="1" />
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="attachment" type="tAttachment"/>
<xsd:complexType name="tAttachment">
<xsd:sequence>
<xsd:element ref="attachmentInfo"/>
<xsd:element name="value" type="xsd:anyType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="tAttachmentInfo">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="accessType" type="xsd:string"/>
<xsd:element name="contentType" type="xsd:string"/>
<xsd:element name="attachedAt" type="xsd:dateTime"/>
<xsd:element name="attachedBy" type="htd:tUser"/>
<xsd:any minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
Current TAS only has two operations "add" and "delete".
In B4P case, two operations will be added, "getAttachmentInfos" and "getAttachments"
getAttachmentInfos
Get attachment information for all attachments associated with the task.
getAttachments
Get all attachments of a task with a given name.
