Changelog 3B CLM v5

New

• 3B Templates: This version is releasing a brand new template builder interface
• 3B Templates: We have added the ability to embed URL Merge Tags to a 3B Template. This feature enables you to create a merge tag and pre-populate it from URL parameters. (DEV-39)
• Contract Redlining: We have completely re-implemented the redlining solution.
• 3B Templates: We now support Multiple Submitters for 3B Templates, just like 3B Sign. Simply assign a submitter to an input field or signature field and from the publisher, pick "Start Collaboration". This will create a Redline Request. Add Collaborators as necessary and assign an "Order" to each collaborator.
• Templates, Sign, Redlining bring refreshed UI and UX
• 3B Templates: Added the ability to disable confetti, stop field jumping animation, stop scrolling of fields into view, hiding the reject button
• 3B Templates: Added a new mode that allows you to configure a template and rely on the embedded fields rather than on the mini submission form at the bottom of the page by Disabling Submission Form (DEV-319)
• 3B Sign: We now supports multi-select fields fully
• 3B Sign: We now allow you to edit picklist options/values for Select / Multi-Select field types. If you link a select/multi-select field to a Salesforce field, you will see the options pre-populate from the object field's definition.
• 3B Templates: We have added a new "View Only" mode for templates. Great if you want to simply generate a template and display it to the user.
• DEV-161 - You can now customize the label of the Reject button in 3B Templates

Improvements

• Faster page loading for Templates, Redlining and Sign
• 3B Templates: The settings icon now opens a modal that allows you to Customize Templates Behaviour and Labels
• 3B Templates & 3B Sign - enhanced mobile experience
• 3B Templates: We have added the ability to control page zooming for PDF. This allows you to configure how zoomed the page will be on the final PDF, enhancing the PDF output
• 3B Templates: Now, function expressions and templates are searchable in the builder (DEV-320)
• 3B Templates: New styling added for user inputs and merge tags
• 3B Sign: Field options are now in a pop-up for easier options management
• 3B Sign: Submission of a document now shows drop-down / multi-select options in the center of the screen
• 3B Templates & 3B Sign: Field scroll was scrolling the page too much. Now, field scrolling will bring the field in the top 30% of the device's screen

Fixes

• DEV-128 - Replacing PDF in 3B Sign could cause fields to be lost & hidden. Now, when we replace a document in 3B Sign, any fields will remain.
  • In addition, if we delete a document in 3B Sign, any fields attached to the document's pages will also be deleted
• DEV-86 - In preview mode, we were creating submissions
• DEV-269 - Preview mode of 3B Sign was buggy and was failing to generate a preview
• In some scenarios, 3B Templates could cause a trailing page to be generated in the final PDF file
• DEV-154 - 3B Redlining: The generated redlining requests could have a different look and feel than generated documents. In addition, child repeatable sections could break 3B Redlining.
  • We worked hard on unifying our document parser, and now, redlining documents and regular template documents will look exactly the same
• DEV-94 - 3B Sign: changing between submitters could be sticky
• DEV-347 - UI /UX improvements added to 3B CLM including better mobile support
• DEV-271 - Font background was not printed in the final PDF in 3B Templates
• DEV-250 - Fixed an issue where input fields could be incorrectly indented on a 3B Template
• DEV-189 - Fixed an issue Replacing documents in 3B Sign
• DEV-188 - Fixed an issue where a repeatable section could break a document's generation if characters in certain order were seen by the parser
• DEV-135 - Fixed an issue where some checkboxes become un-selectable
• DEV-234 - Fixed an issue where adding merge tags in link elements inside of repeatable section could break the parser

Other

• A bump on dependent packages ensures additional security.

Post-Upgrade Actions

• There are new fields on the Collaborator object - add them to the page layout
  • Make the Order field on Collaborator "Required" if you are upgrading a client from a previous version. Action not needed for new installations.
• Fields have been deprecated on the Template object - cease use

Link: TBC