Release Date: March 4
GivingData Cloud
GivingData Cloud allows all documents uploaded to GivingData to be stored natively in the application-- therefore, a Microsoft subscription will not be required for document storage.
This is optional & available to all subscription levels with no additional cost. GivingData Cloud is primarily useful to new clients starting an implementation as well as clients not already using OneDrive or Box for document storage.
Setting up GivingData Cloud is easy and a time-saver; it can be enabled in your site with minimal setup by your foundation’s IT resource. Clients opting to use GivingData Cloud can save costs on their Microsoft subscription. They won't need an E3 Microsoft subscription, and can instead use a basic tier for their Microsoft needs.
GivingData Cloud provides secure Cloud based storage with no storage limits. Users also retain the ability to do the following:
- create new documents
- edit existing documents
- create document templates with GD merge fields
- publish documents to the Grantee and Board Portals
- batch download documents
- send documents for e-signature via DocuSign or Adobe Sign
When using GivingData Cloud, the main difference users will notice is when editing a document. After clicking into a document, it won’t open in Office online like it would with OneDrive or Box document storage. Instead, the document will download to the computer's desktop, and after editing, users will need to upload new versions of the documents to GivingData manually.
GivingData Cloud can work alongside the existing document linking options for Google Drive and Dropbox. However, GivingData Cloud cannot be used with an integration with OneDrive or Box; it provides an alternative document storage option. This is another reason why GivingData Cloud is primarily useful to new clients starting an implementation as well as clients not already using OneDrive or Box for document storage.
For more information on GivingData Cloud, check out this video.
Improvements
- Added the ability to view split percentage coding in Scenario Planning. Prior to the update, when filtering a Scenario Planning dashboard to a specific code, the full payment amount displayed in the year column even if the payment was split between more than one code. For example, if a user were to view Scenario Planning filtered just to the Education Program Area, then a $100 payment with split coding (60% Education, 40% Arts) would display as a $100 payment for Education and not just the $60 actually allocated to the Education program area. With the update, the amounts displayed in the year column will only reflect the amount of the payment allocated to that code. In the example above, $60 would display since it is allocated to the Education program area code. For more information, see this video.
- Moved sorting options for the fields Request Status, Staff Person, and Grant Year to their own columns in Scenario Planning. These fields can now be sorted in their own columns using the arrows next to the column label. Prior to this update, these fields were sorted using a dropdown on the Request column. For more information, see this page.
- Updated Chart View to show split percentage coding when sorting by a code. Prior to the fix, even if there were multiple codes applied within a code type, the entire payment/request is allocated to the primary or highest percentage code instead of being separated out by percentage.
- Added the ability to edit a Request's Anticipated Approval Date. To learn how to edit this field, see this article.
Notable Bug Fixes
- Fixed an error occurring when accessing the Tags & Coding tab on a Request.
- Corrected an issue occurring when batch editing the Request Status for a large number of Requests. Prior to the fix, the Request Status was never changed and the user received no notification.
- Resolved a problem with the Outlook Add-In not functioning.
- Fixed an issue with uploading documents when using Safari.
- Resolved a problem with selecting program area codes in the Group Requests By modal in Chart View.
- Fixed an error occurring when loading a dashboard or Super Search filtered on the Budget Fiscal Year property.
- Corrected formatting issues occurring when exporting a report to PDF.
- Resolved an issue with moving a workflow task to its desired place within a workflow.
- Fixed a bug occurring when adding a banking details Requirement to a Payment. Prior to the fix, users were unable to select a payment number in the modal since the dropdown to select a payment number was not functional.
- Resolved an error occurring when accessing the status of a document sent to DocuSign for e-signature.