In this release, we made changes to one of the essential features. And the reason for that is to make the process of building Documents more structured and comfortable.
What feature are we talking about? Query Builder! No need to worry - you can still find Query Builder in its place with all the functionalities it provides. But we made it even more powerful!
Check these Release Notes and corresponding documentation pages to complete the picture in your head.
You can use the following link to install or upgrade the application.
From now on, you can define variables that are used in the document straight in Query Builder instead of adding them as an element from Template Builder.
For that purpose, we added a separate section in the Query Builder tab and called it Global Variables.
Go to the Query Builder tab, add a new Global Variable, and it will appear in the Template Builder, ready to be inserted into the document.
You now don't have to create a new Salesforce formula field each time you need a value that you can't get directly from a Salesforce field. Use Expression Fields, and keep your Object Model clean!
The Link element is now fully functional in Template Builder for DOCX files. So you can easily insert links in your template document using Template Builder and generate the document using Maven Documents.
There are some things we want to clarify.
-
New Document Solution will by default now use Global Variables defined on the Salesforce side.
If you would still like to generate Documents as you did before v4.0 - with Variables defined as the mmdoc: variable elements, you can switch the useGlobalExpressions flag to true with the instructions laid out here.
-
After the app is updated, you should manually remove the "Reuse File" field from the "Document Solution" layout and add the corresponding field to the Button Configuration layout. And if you had the "Reuse File" checkbox marked, after the upgrade process, you have to check it again but in the "Button Configuration" settings.
- The issue with deleting old Document Requests
- The non-descriptive error message appears in the “Query Builder” tab
- The “Allow Preview__c” field is not included in the exported JSON file
- The “Hidden” attribute is not working on some elements on Azure Template Builder
- New lines in the “Text Area” fields are not visible in the generated document
- The generation process ends in an error if there’s the Section Break inside the hidden “ Paragraph” element
- Issues with expressions evaluation on Orgs that have Enhanced Domains
- Code execution hits Salesforce limits and leads to an error
- Playground sometimes is not loading properly
- Expressions with wrapper functions were giving false results sometimes
- A spinner used to stuck in the Result section of Playground after evaluating an expression
- Aliases of Salesforce Fields and Objects were not shown properly in Template Builder
- The “File successfully uploaded” message appears on Azure Template Builder even if the file wasn’t uploaded on Salesforce
- Template Builder used not to work on Scratch Orgs on Azure because of the wrongly assumed prefixes
- An "Invalid argument: Id" error appears in the metadata synchronization process
- The Repeater element behaves differently on Google and Azure Template Builder
- Manual changes in the text of the template document or enabled spell-checking won't affect the generation process anymore.
- Error messages in the generation process are now more descriptive
- A spinner is added to the first Playground load
- Code wrap is disabled in Playground
- Text folding is now available in Playground
- Multiple expressions can be evaluated at the same time in Playground
- There is no need to refresh the page to continue using Playground if an error occurs
- In Playground, context can be refreshed without the {!recordId} variable defined
- Error messages in the Result section of Playground are now shown as a toast message and became more descriptive
- The data shown in Expression Builder will depend on the location you opened it from
- Inserting a Query or Function in Expression Builder does not overwrite the Expression text area
- Validation of the Microsoft Word background paragraphs is added