Docupace System R2 2021 Release Notes
Connect 4.63 - Core 23.9
| Info |
|---|
This article shares the new features, updates, and fixes that are part of the Docupace R2 2021 release. |
| Tip |
|---|
Related Guides: |
Table of Contents
| Table of Contents | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Key Innovations to the Docupace System
New Features
This section tells about major improvements to the Docupace System.
eSign
Reference #: R2_2021_KEY1
| Info |
|---|
Change: Added an application preference that prevents users from merging eSigned documents. |
| Tip |
|---|
Benefit: Completed eSigned transaction information is protected from loss due to a merge. |
Description: Previously, if you attempted to merge an eSigned document with another document, the eSign information was lost.
To prevent this from happening, set the application preference pdf.edit.mergeSignedDocs.enabled to No.When a user clicks Merge, the system will fire a validation that checks for the following statuses:
Voided
Suspended
Timed Out
null
Next, the system will merge documents that have the statuses listed above. Otherwise, the system will display an error message.
Docupace Analytics
Reference #: R2_2021_KEY2
| Info |
|---|
Change: Created View Only Access to Docupace Analytics powered by Exago. |
| Tip |
|---|
Benefit: This feature enables users to view pre-built reports in the Docupace Analytics system. |
Description: To access these reports, you must have access to at least one of the EXAGO checkboxes in dB Realm:
EXAGO Report Creator and Report Creator SQL - allows creating reports
EXAGO Report Scheduler and Report Scheduler Admin - allows creating regular reports after defined intervals
EXAGO Report User - allows access to the Report tool
.png?version=1&modificationDate=1635877916733&cacheVersion=1&api=v2)
Accessing reports from Docupace
Reference #: R2_2021_KEY3
| Info |
|---|
Change: Created the ability to build custom reports in Docupace Analytics Powered by Exago. |
| Note |
|---|
Attention: This feature is available at cost. Please contact your Support Manager or Customer Success Manager for more information. |
| Tip |
|---|
Benefit: This feature allows users to build custom reports in the Docupace Analytics reporting system directly. |
Description: The following site preferences work together to create a Docupace Analytics user session:
application.reports.hostUrl
application.reports.configFile
application.reports.userID
application.reports.apiKey
jaccomo Data Exchange
Reference #: R2_2021_KEY4
| Info |
|---|
Change: With the jaccomo integration, you can now sync information to Work Items with JCORE. |
| Tip |
|---|
Benefit: Additional information can now auto-populate forms for new Work Items. Additionally, you can ensure your books and records system is always up to date. |
Description: If your site has the jaccomo integration enabled, you will see a Get From JCORE button on Work Items. Clicking this button auto-populates data into forms on your Work Item. Any information you update will sync back to JCORE after the Work Item has been successfully processed through the system.
.png?version=1&modificationDate=1636045327083&cacheVersion=1&api=v2)
NIGO/Reject app
Reference #: R2_2021_KEY5
| Info |
|---|
Change: You can now configure the NIGO and Reject transition buttons on the Work Item Screen to launch a NIGO/Reject app. |
| Tip |
|---|
Benefit: It is faster and easier to select NIGO reason codes, edit the notification email, and transition the WI. |
Description: Clicking the NIGO/Reject button on the Work Item page opens a an app. From there you can select one or more reason codes and edit the notification email template. After completing the app steps, the system moves the Work Item to the appropriate stop in the workflow.
.png?version=1&modificationDate=1636056967370&cacheVersion=1&api=v2)
.png?version=1&modificationDate=1636056967295&cacheVersion=1&api=v2)
Reference #: R2_2021_KEY6
| Info |
|---|
Change: Reason Code History is now its own section on the Work Item Details screen. |
| Tip |
|---|
Benefit: You can now easily see when a Reason code was added, when it was removed, the user that added/removed it, and the timestamp. |
Description: This release adds a new Reason Code History domain and creates triggers to add related information to the WI details screen. This trigger fires when a reason code is added to or removed from the Work Item.
A. The navigation menu item in the Work Item Details
B. The history of Reason Codes
.png?version=1&modificationDate=1637338499959&cacheVersion=1&api=v2)
Wealthbox
Reference #: R2_2021_KEY7
| Info |
|---|
Change: You can now create and update Client Folders in Docupace with information synced from Wealthbox. |
| Tip |
|---|
Benefit: It is faster and easier to create and update Client Folders with the information from your Wealthbox CRM system. |
Description: You can create client folders from a Contact in Wealthbox. This single signs you into Docupace to create the Client Folder. If you have already created a Client Folder in this way, you will update the information in the Client Folder instead.
User Experience
This section shares information about changes that have been made in this release that improve overall user experience.
Fixes
CIP Verification
Reference #: R2_2021_UE1
| Info |
|---|
Change: Fixed a bug that was causing preventing the CIP Verification action from firing. |
| Tip |
|---|
Benefit: The action now works as expected. |
Reference #: R2_2021_UE2
| Info |
|---|
Change: Resolved issue that caused the system to send emails to disabled users via Rep Email Recipients. |
| Tip |
|---|
Benefit: Added a new rule to EPacs Sending Email function. You can configure this feature by using the docupace.email.blockdisabled application preference. It blocks emails to disabled users. A site will work as before or block email to disabled users depending on this property value. Now any email that uses EMAIL2 in 22.7+ will be blocked if a user is disabled. |
eSign
Reference #: R2_2021_UE3
| Info |
|---|
Change: Resolved issue that caused some users to receive an error when attempting to use the eSign function. |
| Tip |
|---|
Benefit: Previously, when some users clicked on Actions >eSign button, the system displayed the following error message: “This user does not have valid e-sign credentials (user ID).” The eSign Transaction page now opens correctly to allow users to enter eSign Recipient data and send for eSign. |
Forms Matrix
Reference #: R2_2021_UE4
| Info |
|---|
Change: Fixed a bug that sometimes caused dropdown options in custom apps to not populate from the Forms Matrix. |
| Tip |
|---|
Benefit: The dropdown options now populate correctly. |
PDF Viewer
Reference #: R2_2021_UE5
| Info |
|---|
Change: Resolved an issue with populating forms when using the newest Chrome version. |
| Tip |
|---|
Benefit: Previously, Work Item forms did not populate for users accessing Docupace through the newest Chrome version. Now this issue is resolved, and forms are populating as expected. |
Report Builder
Reference #: R2_2021_UE6
| Info |
|---|
Change: Fixed a bug that caused new reports and changes to existing reports to not save. Existing reports were also inaccessible via the dropdown in the Reports domain. |
| Tip |
|---|
Benefit: The Reports feature now functions correctly. |
Starting Point
Reference #: R2_2021_UE7
| Info |
|---|
Change: Resolved an issue with creating Work Items with Starting Point for Multiple Clients. |
| Tip |
|---|
Benefit: Previously, some users experienced an issue when selecting Multiple Clients in Starting Point. The Wizard displayed all the clients correctly, but the Work Item would only generate with one of the clients. Now this issue is resolved, and all clients display as expected. |
Work Items
Reference #: R2_2021_UE8
| Info |
|---|
Change: Work Item Coversheets now open in a new tab. |
| Tip |
|---|
Benefit: This change makes it easier to return to your Work Item after generating coversheets. |
apps
This section shares information about changes to APPs, apps, and wizards within the Docupace system.
Fixes
Docupace Start
Reference #: R2_2021_WIG1
| Info |
|---|
Change: Resolved an issue where the Remove button did not correctly remove Additional Primary TOD Beneficiaries. |
| Tip |
|---|
Benefit: Previously, some users experienced an issue where clicking the Remove button cleared fields but did not actually remove the Additional TOD Beneficiary. After the fix is applied, the Remove button deletes the additional Primary Tod Beneficiary. |
© Docupace Technologies 2020