Details that have been captured during the case life cycle are required to be made available into a MS-Word (.docx) document, which is then downloaded from the case attachment by the users. The solution applied is the OOTB document generation feature made available as a smart shape.
The template document that is been uploaded (SRMF Final New) contains the tags as specified in the ‘View and Use fields’. Such tags that have been inserted into the template document, wherever relevant are expected to be replaced by their corresponding value as determined at run time for each case.
Case Properties that have been using the Rich Text Editor (RTE) control do not render within a tabular cell in the document.
Document-attachments of type .docx cannot be inserted into the main document as an OLE. Instead, the contents of the document that is intended to be inserted as OLE are appended to the main document.
Attachments are not rendered within the tabular cell in the document.
A page-list property referred into the first column of a table in the document will automatically append new rows appropriately as per the length of the page-list to render the values within a page-list property, but this behaviour is absent for attachments. How can all the attachments of a case, or, at least, the ones belonging to a specific category, be rendered dynamically without explicitly referring them using a subscript e.g. .pyattachments().<attachmentlink>
Steps to Reproduce
Please find attached an example template-document and the corresponding generated-document that cover the problems (a), (b) and (c) described above.