Please welcome Maven Documents version Summer '22.
We know that our product helps you create all kinds of documents, based on your customer's Salesforce data and improve sales performances. So it is our obligation to make Maven Documents easy and comfortable to use according to all your needs.
With the new features included in this release and some improvements to the old ones we, at Maven Mule, hope to make your daily work with Maven Documents even more productive and pleasant.
After upgrading the Maven Documents application following steps should be made:
From now on a user will be available to add an existing DOCX file to the Document Template the way it is possible to do with Google Doc/Sheet files.
If a user has no license assigned, an error is thrown (“User generating Document Request does not have Maven Documents User Package License assigned. Please assign a Package License and try again”).
Unsupported characters and spaces would be automatically removed while the user writes down Aliases for the objects or fields. Now when a user is writing the Alias for an object or a field in the Query Builder only supported characters will be left while unsupported ones would be deleted. Supported characters are the Latin letters in upper and lower cases and digits from 0 to 9 included.
In the previous version, it was possible to select the compound fields, like {!Account. BillingAddress} for example, in the Query Builder. As a result, a user could have some unexpected outcomes in the end document.
We made it fixed and now a user won’t be able to select such compound fields as “Address” or “Geolocation” in the Query Builder. But this does not mean that the fields that are included in the compound field are forbidden.
For example, ‘BillingAddress’ will not be provided as an option on the ‘Account object’, but ‘BillingStreet’, ‘BillingCity' and the others are.