In this release, we mostly focused on fixing some issues that used to happen while working with the app. But it doesn't mean that we won't surprise you with some new functionalities.
This time we added the new "index()" expression and we made it possible to use the "base64" data type as a source for generating the "Image" element. It can be achieved by using the newly added "Source" attribute on the "Image" element
You can use the following link to install or upgrade the application.
¶ The "index()" expression in the "Repeater" and "Table" elements
This expression returns the index number of the repeating value from the Repeater or Table element.
By using this attribute on the "Image" element, you can render an image not only from the given URL but from the "base64" data type as well.
After updating the application, "Image" elements that used the "URL" attribute for rendering the image will still work. But the newly added "Image" element will only have the "Source" attribute which can process both the URL and the "base64" data type.
- The process of logging in with Template Builder ends in an infinite spinner when being logged out after two or more hours of inactivity
- Tapping the "Generate Document" button in the mobile Salesforce app ends in an infinite spinner
- The GraphQL filter on Query Builder doesn't work with some combination of conditions
- Fields that are added to the query and saved in Query Builder disappear from the Preview section after switching tabs on Maven Documents
- DOCX and XLSX files are not uploaded while importing the Document Solution
- The issue with refreshing context in Playground if the Query is filtered by the requestId variable
- The Rich Text Field element is not generated properly if it is the last paragraph of the document
- The Append mode attribute doesn’t work in the Repeater element in DOCX and XLSX files
- In DOCX files, the Table with TableRow and TableColumn elements inside is not generated if Indexes in their bodies are not sorted in the ascending order
- A new line in the Billing Street address field on Salesforce adds an empty new line in the generated Google document and breaks the generation process of XLSX files
- The Repeater element in XLSX files doesn’t blank the row with the Vertical Repeater's and the column with the Horizontal Repeater's opening tag if the Last Cell attribute is not defined
- Merged cells can’t hold the field from Template Builder in Google Sheets
- The Mode attribute for the Image and Code elements is available if the Inside Cell checkbox is unchecked
- If there are two or more parent-child relationships in the GraphQL filter in Query Builder, the document generation ends in an error
- When the Email Preview action is created, an error appears while sending the generated email from the Contact object
- The generation process ends in the TimeOut error if the generated DOCX file includes the tableColumn Expression
- In the email on approaching the Document Requests limit per GMT month, the number of allowed requests is written with the decimal point
- In Playground, changes in the Context section don't influence the evaluation results
- In Playground, changes on Salesforce are not reflected in the Context section after the section refresh
- If the Query Variable is used as a filter in Query Builder and includes Date/DateTime fields as a value, the generation process ends in an error
- In the generated document, the content of the Rich Text element inside the Table element is always placed at the bottom of the corresponding cell
- If the DOCX or XLSX file includes a query with a parent object which is empty on Salesforce, the generation process ends in an error