SpringCM Release Notes. January 2018

Transcription

1 SpringCM Release Notes January 2018

2 Contents Announcements... 3 Global Navigation header coming in Redefining the Admin and User Experiences... 4 Workflows... 4 E-Signature Changes... 4 Enhancements... 5 Editable Permission Sets... 5 SpringCM Ideas Portal... 5 Workflows... 5 Document Preview... 6 Doc Launcher... 6 SpringCM Clause Library Office Add-in... 6 E-Signature... 6 Reports... 6 eforms... 7 Fixes... 8 Address Book... 8 Doc Launcher Forms... 8 Document Preview (Legacy)... 8 Login... 8 Preferences... 8 Spring CM-Salesforce Integration... 8 Workflow Designer... 8 Known Issues Feature Deprecations... 11

3 Workflow Designer SpringCM Track It Customized Actions No Longer Support External Icon URLs SpringCM Scan Single Sign On SOAP API Deprecations

4 Announcements Global Navigation header coming in 2018 We at SpringCM are excited to announce that a newly designed global navigation is on its way in We are improving the navigation in SpringCM by creating a logical hierarchy of global and local level navigations. The global navigation header will be consistent and persistent at the top of every page, while local navigation changes based on context. This marks the beginning of the separation of admin and end-user features to optimize the user experience based on your role. What's changing During our continuing efforts in user research, we learned that the Address Book and Forms pages are more widely utilized for Admin configuration and management processes. As a result, the Address Book and Forms pages will be hidden by default for your account. You will be able to change this setting from the Customize Navigation page. Future consideration: Due to the change in navigation header design, we will be introducing a new "Icon" image that can be uploaded in Account Preferences > Branding that's more ideally suited to the new Global Navigation. The full-sized "Logo" image will remain and will continue to be used in other places (e.g., s). 3

5 An optimized icon size will be communicated prior to the release so you can ensure your header image properly renders. Redefining the Admin and User Experiences At SpringCM, we are constantly innovating ways to improve your user experience and help you make your work flow. Based on the research we are constantly doing, we are in the opening phases of creating unique experiences for account administrators and users. We would like to thank our SpringCM Labs members and our valuable customers for their participation in all the research we have completed thus far as well as the research that we are in the process of doing. New arrangement of Preferences items We will be re-organizing the navigation in the Preferences section as part of our continued initiative to improve the usability of the product. Expect incremental updates to the Preferences page over the next several releases. The first of these updates will be deployed in the March 2018 release. Workflows Conversion to the new Workflow Designer format will be enabled in the March 2018 release. This means that the legacy workflow designer will be deprecated, and ALL workflows open in the new designer format. You can contact your SpringCM account manager to have the new Workflow Designer setting turned on in this release (January 2018) ahead of time if you want to work with the new functionality before it is mandatory. E-Signature Changes AdobeSign is no longer allowing wet/physical signatures to be returned via fax in their new signing experience. Adobe is making this change because fax solutions add noise and the resulting document often has significant fidelity loss. When this feature is retired in the fourth quarter of 2017, signers will need to download the document, print out, sign, scan the document, and then upload back to AdobeSign. AdobeSign will guide users through this process. 4

6 Enhancements Editable Permission Sets SpringCM now allows you, as a Super Admin, to create administrative permission sets. You start with a Full Subscriber set of permissions and build from there. Permission sets can be assigned to users in the Full Subscriber role from within the Address Book. This means that users who are assigned to this permission set will have access to any areas you indicate, but will respect the folder and document security that is set for Full Subscribers. Custom permission sets give your organization more flexibility when managing work in SpringCM. Permissions are grouped into categories based on functions. This can help you compartmentalize roles within your SpringCM account so that, for example, a user does not have to be a Super Admin to run a customized report. It also adds a layer of security to your SpringCM account by letting specific users view only certain areas of SpringCM while preventing other users from viewing everything. Document and folder security must still be set on the Documents page. Permissions are assigned to individual users in the Address Book. SpringCM Ideas Portal Super Admins can access the SpringCM Ideas portal so that you can make suggestions for future development consideration. Super Admins can grant access to other Full Subscribers and User Admins in their account. Navigate to Preferences > Account > SpringCM Ideas Portal so you can grant access to other roles in your account. You should make sure that your browser s pop-up blocker is turned off or set to allow popups from SpringCM in order to launch the Ideas page. Workflows Compare document versions The Compare Document Version With property has been added to the Compare Document Versions workflow step to give you more flexibility in version comparisons during workflows. This property gives you the option to compare a document against either the previous version or the original/first version. Previous Version is selected by default. 5

7 Document Preview New permission settings We added the Minimum role required to display document attributes setting to Account Preferences > General > Document Viewing. Your options are Full Subscriber, Limited Subscriber, and Guest. If your account turned on the new document preview functionality, the Attributes tab does not display for role levels who do not have this permission. If your account continues to use the legacy document preview, all attributes on the properties panel do not display for role levels who do not have this permission. Doc Launcher Font family and font size editing fields have been removed from text fields in Doc Launcher forms and after initiating Doc Launcher. These fields will no longer be available for text that is copy/pasted into a text editor as well as text that is imported from Salesforce via Doc Launcher forms. The <RichText> tag by default inherits the font size and family from the Doc Launcher template. Removing the font family and font size fields from the text fields helps smooth the process of converting rich text from documents transmitted between Salesforce, SpringCM and Microsoft Word. This results in fewer errors that you would otherwise have to take the time to troubleshoot. SpringCM Clause Library Office Add-in Logging in from the SpringCM Clause Library Office Add-in will now occur through a dialog box instead of the add-in panel. This helps resolve potential login issues as well as extend support for online versions of Office 365. E-Signature The Name, Title, and Signature date tags have been added to the Alphatrust electronic signature configuration. Reports We added a toggle to the Users report so you can opt to show or hide deleted users in your account. The report defaults to False, but you can switch to True. 6

8 eforms Recaptcha Upgrade Google recaptcha, the widget that verifies you are not a robot when you are filling out an eform in SpringCM, has been upgraded to the newest version. The process is simplified with the newest version. When you access a public eform through its public share link, you now check a box to verify you are not a robot rather than typing characters into a text field. 7

9 Fixes Address Book The confirmation sent after Bulk User Import completes has been reworded to be more descriptive about the roles involved in your instance of the import process. Doc Launcher Forms You can now delete a library field that is not linked to a form field library. Document Preview (Legacy) Login Documents are now editable in the legacy Document Preview window if you have the Attributes option selected in Account Preferences > General under Select what displays in the information section. SpringCM windows no longer unexpectedly close if you are a OneLogin user and you click the Discard button on Save/Discard prompts. Preferences Smart Rules using the Bulk Attribute Import action now process dates, numbers, and decimals in the user s chosen localization format. Smart Rules using the Assign Attribute Value action now process decimal values based on the user s chosen localization format. Spring CM-Salesforce Integration Non-US phone numbers are no longer treated as a malformed string. Users with international (non-us) telephone numbers now sync without error. Workflow Designer A workflow loop no longer fails when a document is accessed multiple times using the Update Variable from CSV step. A workflow no longer fails if you change the electronic signature vendor during the execution. A workflow no longer fails if you preview and cancel a document multiple times from the Review and Send for Signature step with DocuSign as the e-signature vendor. This only applies to customers using the new version of Document Preview. 8

10 The Also Notify field on the Review and Send for External Review step no longer populates with the Recipient address. 9

11 Known Issues The following section lists known issues in SpringCM as of the January 2018 release. A decimal attribute field value not in a U.S. numeral format that is set in a document rule (Assign Attribute Value action) is changed when applied to a document. For example, the value ,12 in an attribute decimal field in a document rule gets changed to ,00 when applied to a document. Editing and saving an Excel XLSX document via SpringCM WebDAV may result in an error from Microsoft when you try to open it. XLS (Excel ) versions do not result in an error and can be opened. A user cannot edit a document with the legacy Salesforce package with the SpringCM Edit application. Building a search with attributes in the new dashboards does not allow you to pick a dropdown field. The left-hand panel of the public share page for a folder cannot be resized. 10

12 Feature Deprecations Workflow Designer "Advanced Workflow Queues" has been removed from the Edit menu on the Workflows page. You can access your queues from the Address Book. Administrator subtasks related to Approval workflows are being deprecated in the May 2018 release (18.3). Approval tasks in general are unaffected by this change. SpringCM Track It Due to declining customer demand, the SpringCM Track It for Salesforce application was deprecated at the end of The application has been removed from the Salesforce AppExchange. Customers can choose to continue using the current version of the application if installed in their Salesforce org; however, SpringCM will not enhance or bug fix the SpringCM Track It application. Customized Actions No Longer Support External Icon URLs Coinciding with the December 2017 release, customizing actions in SpringCM will no longer support external URLs for icons. SpringCM is adding additional icons that can be used as replacements. SpringCM Scan Due to changing market conditions, the SpringCM Scan was deprecated at the end of The application will be removed from the SpringCM download site. Customers can choose to continue using the current version of the application if installed on their Windows workstations; however, SpringCM will not enhance or provide any updates or fixes to SpringCM Scan in the future. Single Sign On Legacy single sign on has been deprecated in SpringCM. SOAP API Deprecations As of October 2018, SpringCM will be retiring support for legacy versions of the SOAP API. This includes versions v2, v3, v4, v5, v6, v7, v8, v9, v10, v11, v12, and v Customers who want to continue to use the SOAP API must upgrade to version v or consider moving to the REST API. For more information on converting from the SOAP API to REST, please see 11