Release Notes May 2017

Transcription

1 Release Notes May 2017

2 About the Release Notes... 3 Release Overview... 3 Other Announcements... 4 SpringCM Login name change... 4 Workflow Step and Workflows Initiated Reports are being deprecated... 4 Adobe E-Sign Integration Change... 4 SOAP API Endpoints are deprecated... 4 Enhancements... 5 New Workflow Designer (Open Beta)...5 Doc Launcher Improvements...5 New Document Preview (Private Beta)...9 Folder Rules (Open Beta) Two-Step Verification with Google Authenticator Other Enhancements Fixes Known Issues... 15

3 About the Release Notes SpringCM Release Notes address new enhancements and fixes to the SpringCM platform as well as to the SpringCM desktop and mobile apps. The SpringCM team is always looking for opportunities to grow and innovate. Your feedback is essential to help improve our product as well as the documentation and online support. Please share what you like and what you don t by sending your feedback to built4me@springcm.com. Release Overview With this release, SpringCM customers can take advantage of many exciting, new features and enhancements that will improve the overall experience for end users, administrators, partners and customers. Please contact SpringCM Customer Success (success@springcm.com) if you have questions regarding these features in your account. Administrators are encouraged to share the information in this document with the users in their own organization. Unless stated otherwise, all enhancements and bugs described in the Release Notes are available to all users in the account.

4 Other Announcements SpringCM Login name change In the 4 th quarter of the year, SpringCM will be introducing a change that affects customers who are in multiple SpringCM accounts. Each login name will now only be associated with a single SpringCM account. When this change is implemented, a user will need to log in to each account separately. The username will be automatically updated to include the account id. For example, if John Smith (jsmith@springcm.com) is in two accounts 6576 and 17435, then two unique logins will be created (jsmith+6576@springcm.com and jsmith+17435@springcm.com). Workflow Step and Workflows Initiated Reports are being deprecated Workflows Initiated and Workflow Step reports will no longer be available in the SpringCM UAT environment after the May 2017 release is deployed. Any existing Workflow based report will no longer be available after this release. This change does not impact the SpringCM Production environment. In conjunction with the May 2017 release, all new accounts in the SpringCM production environment will not be able to create these reports. In the SpringCM Production environment, workflow based reporting will be available for accounts that have already created reports until the end of the 2017 calendar year. Adobe E-Sign Integration Change On May 5, 2017, we will be updating our integration with Adobe E-Sign and transition to using their REST API. You must update your Integration Key in SpringCM to ensure that no disruption in service occurs. The end user experience will not change when this update is made. This update will allow SpringCM to take advantage of any new features that Adobe may make on their platform in the future. SOAP API Endpoints are deprecated As of March 10th, 2017, SOAP calls made to the or uat.springcm.com endpoints will be deprecated. As of August 26th, 2017, SOAP calls to these endpoints will no longer be supported. To ensure quality of service and support for your integration, host names should be updated to a supported endpoint. These endpoints are defined below: Production: soapna11.springcm.com or soapna21.springcm.com UAT: soapuatna11.springcm.com

5 Enhancements New Workflow Designer (Open Beta) SpringCM has been long at work providing a fresh and modern experience at creating and managing workflow designs. Along the way, we focused on usability challenges that raise the barrier to entry, making it difficult for our customers to build their own workflows and extend their solution foot print. We are proud to announce that the new Workflow Designer has advanced to the point where we are now ready to start collecting feedback in the UAT environment. This beta will ensure that our designer best fits our customer s needs. In the May release, Customers who have workflow as part of their Spring CM Implementation can test drive the new designer in UAT. Later in the summer, after the feedback from our closed and open beta customers, the Workflow Designer will be released to all customers and conversion to the new designer will start in earnest. Please reach out to Customer Success or your Account Executive if you are interested in enabling this feature. Doc Launcher Improvements Doc Launcher Forms have moved to preferences The Doc Launcher Preference tab now includes Doc Launcher Forms. Here you will not only be able to manage your configurations but also manage your Doc Launcher Forms and Field Libraries. You must be a Super Administrator to manage and configure Doc Launcher Forms, Doc Launcher Configurations, and Field Libraries. The Doc Launcher Form grid includes sortable columns for Name, description, modified date, modified user, and which Doc Launcher configurations the form is used in. You now make copies of existing Doc Launcher Forms.

6 Doc Launcher Forms created before the May release will automatically be moved into Doc Launcher Forms preferences. The existing document will remain in the current folder in SpringCM and will need to be deleted by a Super Administrator. One to Many Chooser from Salesforce We have introduced another new feature in Doc Launcher Forms that allows the Administrator to create a dropdown that maps to a Salesforce object. This new enhancement supports many different use cases but the most common when generating a contract is helping the end user pick from a list of contacts who should sign the contract. Link to Salesforce Object when creating a Dropdown The first change that you will notice when adding a Dropdown in Doc Launcher Forms is that you must first choose the type of dropdown that you want to create.

7 Creating the Dropdown Creating the dropdown works much like defining a table mapped to a Salesforce object. First you will choose which 1 to Many relationship will be the basis for the chooser, then add fields, filters, and if necessary set the delimiter. In the example below, the full name, , and title will also be provided from each contact.

8 Field Libraries (Open Beta) As the building blocks for Doc Launcher Forms have been built out, we have also set out to further speed delivery. With this release, we have also added the ability to create reusable Field Libraries. You can now build a set of reusable fields that can be used in many different templates which improved your ability to deliver templates quickly. This feature will be officially released in the July release. Building these field libraries is exactly like building a Doc Launcher Form. Once the Library has been created adding it to a Doc Launcher Form is an extremely simple process. Once it has been added to your Doc Launcher Form, it is ready to go. Please reach out to Customer Success or your Account Executive if you are interested in enabling this feature.

9 Other Enhancements Packaging a Doc Launcher Configuration will include Doc Launcher Forms and any Field Libraries that have been created. Any package that includes a Doc Launcher Configuration with Doc Launcher Forms will need to be re-created after this release. After selecting a column, you can now select Back to other columns. Add Column to the Left or Right has been removed. A Doc Launcher Form can now be used in the Salesforce ETL workflow step. When packaging a Doc Launcher configuration, you can now select an option to include attribute groups and attribute values for template documents. When defining a table, you can now add a non-repeating field from a parent object. When creating a Doc Launcher Configuration, only DOCX files can be chosen. New Document Preview (Private Beta) We have been hard at work since last summer building a responsive preview which will soon become the default interface for interacting with document content in SpringCM. With this release, we are now ready with the following: All key human workflow steps including Approve, Choice, Choose Documents, Choose Users, Edit, Send for External Review, Send for Signature. Form based steps are not yet supported. Activity Tracking if enabled in your SpringCM account Attributes Information Related documents where you can view, attach, or detach Ad Hoc sending for External Review Ad Hoc sending for Signature in the user interface Common actions such as Check In, Check out, Cut, Copy, Delete, Download, Edit, History

10 Please reach out to Customer Success or your Account Executive if you are interested in participating in this private beta. We expect to open this beta to everyone in the July release. Folder Rules (Open Beta) This release brings new changes to our Smart Rule capabilities. You can now trigger events when folders are created or folders are moved into other folders. The most common use case is to automatically create a set of templates folders for Salesforce objects. A typical example is to create a standard set of folders for every Salesforce Account that is loaded in the SpringCM File It widget. Folder Rules supports the following: Actions: Folder Created, Folder Entered Folder Filters: Has Attribute Group, Has Attribute Value, Has Name Like, in Folder, In Subfolder Events: Assign Attribute Group, Assign Attribute Value, Create Folder, Move Folder, Rename, Run Rule, Send , Set Security, Start Workflow

11 Please reach out to Customer Success or your Account Executive if you are interested in enabling this feature. Two-Step Verification with Google Authenticator As part of an on-going initiative to support public sector organizations and provide stronger security capabilities to larger organizations, Administrators can now enable 2-Step Verification with Google Authenticator. When an Administrator enables 2-Step Verification, all users will be guided through setting up 2-Step Verification with Google Authenticator and as part of every login will need to enter their authentication code. Administrators can provide a grace period of 30 days for users to set up Google Authenticator. If an Administrator resets 2 Step Verification from the Address Book, then the user will need to go through the 2-Step verification set up. Google Authenticator can be used with Android devices or ios devices. User Setup Once enabled in the account, the user will be prompted with a wizard guiding them through the setup process for Google Authenticator. Optionally a user can skip this set up for up to 30 days if a grace period has been enabled.

12 Login Access After setting up 2-Step verification, the user must always enter their passcode at each login. After entering their username and password, the user will be prompted for the passcode.

13 Other Enhancements SpringCM has also delivered the following enhancements in this Release: A user can now create a Word, Excel, or PowerPoint document on the fly and open it directly in Office On-line. If you are interested in using this feature, please reach out to Customer Success and it can be enabled in your account. Full Subscribers no longer see the option to Empty the Trash. A better message has been returned if the Connected App is setup incorrectly for File It, the Inbox Tracker, and the Activity Tracker. Changed the label for SXTerm to Term. OAuth now support multiple redirect URLS. The Append Text File step now supports CSV files. The Document Tracker Lightning Component now supports Salesforce Communities for Record Detail pages. The Create or Upload Step has been updated to include a Cancel output path. If you have not already done so, please ensure that you update your workflows to account for this new output.

14 Fixes Summary Component Fixed an issue where changing the workflow in a Doc launcher configuration would not allow you to save the configuration. Doc Launcher Fixed an issue where creating a Doc Launcher Configuration in an account Doc Launcher with a large number of metadata fields returned an error. Fixed an issue where the user is unable to select Save or Cancel after uploading a document with Doc Launcher in Internet Explorer 11. Doc Launcher Fixed an issue where the user needs to select Cancel twice in order to complete the action. Doc Launcher Fixed an issue where the Date chooser buttons are not visble on a small screen. External Review Fixed an issue where a user would be unable to preview a document from Salesforce the Inbo Tracker if the account is set up with Disable Password Login. Fixed an issue where authenticating to Salesforce with the Login Agreement enabled would occassionally time out. Salesforce Fixed an issue where deleting a connection from an org that is not integrated with SpringCM returns an error. Salesforce Fixed an issue where changing the connection for a Salesforce org from an NA11 account to a NA21 account does not delete the Integration user. Salesforce Fixed an issue where a document does not preview in Salesforce 1. Salesforce Fixed an issue where the recipient does not receive the when sending a SpringCM with a link to a document from an NA21 account. Fixed an issue ensuring that paging through large data sets of users returns them in the proper order. Fixed issue displaying WMV files. Fixed a typo in the send for signature page. Fixed an issue where only the final users comments were displayed. Send SpringCM Web Services Share Link E-Signature Workflow

15 Known Issues Summary When adding fields from a field library, you can add fields from a library linked to a different Salesforce object Fields added from a field library do not show the merge tag. Selecting Share from the new preview returns a system error. The Message Field in Send for External Review is not Rich Text Component Doc Launcher Doc Launcher New Preview New Preview Thanks for your continued support of SpringCM! Please contact your Account Executive or Success Manager for more information about the release.