...
New Features
v10.1 brings Cloud customers several important enhancements to behind-the-scenes integration and PDF Snapshot generation, as well as the brand-new ability to validate the digital signature for a step assigned to email addresssome exciting new enhancements. We've upgraded our PDF Snapshot generator, so your printable PDFs will be more beautiful than ever. Digital Signatures are now available on workflow steps performed by email users, giving you confidence that your data is digitally secure from tampering as it routes through your workflow. is also offering a new Docuware Connector for customers who wish to integrate with their Docuware cloud ECM. To see all of the new features for this release visit our Detailed Release Notes page. Here are some highlights to get you started:
...
We are very excited to now offer the ability to authenticate the signature of an email user. Email-based signature verification allows designers to use Signed Sections, with all of the benefits of a legally-binding digital signature, for Workflow Steps assigned to email addresses. Signed Sections on workflow steps assigned to an email will display additional fields in the popup When an email user clicks to sign, the dialog will display fields to verify the signature and capture first and last name. Sections set to the Wet Signature type will also capture the signature drawing.
If the email entered does not match the email assignment, the error message "Does not match the email address in the notification" will be shown and the signature will not be accepted until the correct email address is provided.
A consent to digitally sign statement is provided above the Sign this section button. It reads "By clicking the button below, you consent to the use of digital signatures."
Signed sections that are authenticated based on the logged in user will display "Digitally Signed (identity verified)" above the signature. Signed sections that are authenticated based on email address will display "Digitally Signed (email verified) above the signature.
When the user signs and clicks Continue/Submit, a unique signature ID is created. You can see this ID under the signature on future steps and on the completed submission.
...
- Workflows will now combine form PDFs and then apply page numbers, so you will have consistent page numbers throughout the workflow PDF Snapshot.
Better support for the CSS page break classes, especially for controls like Textarea and Message that can contain a lot of white space and line breaks between the content in the control content.
- New CSS Classes:
The
f-page-break-inside-avoid
CSS class is now deprecated but continue to work if already set.New
f-break-children-avoid
CSS class which when applied to a group control it , will avoid a page break inside child controls.New
f-break-inside-avoid
CSS class to avoid a page break inside a specific control.The
f-page-break-inside-avoid
CSS class is now deprecated but continue to work if already set.
- Improved alignment and consistent printing of all control types
- Improved multi-language print support for Arabic and other RTL languages.
- Supports future enhancements
Cloud customers do not need to take any action to get all of the benefits of this feature. On Premise customers will need to install the Chrome or Chromium browser on same server where is installed. Instructions are included in the Upgrade Guide.
Docuware Integration
now provides a built-in Docuware Connector. Tenant Admins will configure the Docuware integration via the new Manage Connectors page.
...
When templatized strings are used in integration, such as Document Actions, they will now always send the control's submission document value and not the control's UI formatted value. In past versions, this behavior was inconsistent between forms and workflows. For example, date control values will be sent as yyyy-mm-dd regardless of the date format set in the designer. This consistency will reduce errors due to format incompatibility.
Repeat Control Value Separator for JSON Format
A new repeat control separator for templatized strings has been introduced that formats the control's value as a JSON array. JSON array format is commonly used when generating metadata for the Filesystem Connector and other integrations. To include values from repeating controls and multi-select controls in your metadata, designers can now use the built-in separator 'json' i.e. /{json|controlname}. This special separator resolves to JSON format. The same result can be accomplished by the JSON format, and is far simpler than the previous method of specifying the JSON format separator characters i.e. ["{","|controlname}"].
Migration Considerations
...
This enhancements in this release do not require changes to your existing installation setup, forms or workflows. However, On Premise Customers please note the additional Upgrade Guide step of ensuring Chrome is installed on the same server as your installation in order to use the new PDF Snapshot Generator.
Excerpt | |||||
---|---|---|---|---|---|
Planning Your On Premise UpgradeThe initial release of version 10.1 is released for On Premise customers on June 19, 2021. On Premise customers should review the topics below, the instructions in the Upgrade Guide and Supported Platforms before migrating. recommends that you perform a full installation of v10.1 when upgrading. v10.0 License
Before you begin the migration process:
|
...