2023-10-26 Release Notes

RELEASE NOTES: October 26, 2023

akoyaGO release notes give all users information about bug fixes, enhancements, and new features in the current release. This document describes all changes as of 10/26/2023. Documentation will be updated or added to reflect these changes. If you have questions, please contact your account manager or akoyaGO Support.

akoyaGO

• Bug Fixes
  1. We have implemented a change wherein the country code US will be replaced with United States in all address fields in Contact and Constituent records.
  2. GOverify: The GOverify summary information was not clearing after an EIN or Tax ID was removed from the record. This has been fixed. Removing the EIN/Tax ID will clear out the GOverify summary.
• Enhancements
  1. The Fund Handling Note will now appear on Request, Gift, and Payment & Requirement quick create forms when applicable.
  2. We have added a new system view on Contact called Fund Statement Recipients that compiles all contacts who have the Fund Statement Recipient fund connection role.
  3. We have removed Payment/Requirement Number and Request Number from the Payment/Requirement form, as they are already in the header.
  4. We have enhanced the logic behind alternate addresses. In order to utilize the new logic, ensure the workflow "Update address to alternate (OLD)" is deactivated.
  5. The workflow "Set most recent and largest gift ID on donor" has been enhanced to include instances of change of donor.
  6. We have added three new duplicate detection rules. These new rules will not look at inactive records. They do, however, need to be published. akoyaGO Admins can find them in Advanced Settings > Data Management > Duplicate Detection Rules > publish all unpublished rules.
  7. We have updated the field label on the Percentage field of the Scheduled Distribution form for clarity. We have also added a helpful tooltip to the field.
  8. Inline edits are now available in the Connections entity. This is to make up for bulk editing not being possible in Connections. Inline connection editing should be used for Starting date, Ending date, and the permissions settings on Donor Portal Access (GOfund) connection types. 
  9. We have made improvements to the Dashboard that shows all things GOapply Reviewer. This dashboard was previously named "GOapply Application Review Dashboard" it is now named "GOapply Reviewer Dashboard"   
  10. We have enhanced the payment creation process so that Amount fills in with the Balance rather than Grant Amount to ease the administrative burden on grants with multiple payments.
  11. Timeline entries for Contacts, Constituents, Requests, Gifts, Funds, and Donors will now be sorted by date created instead of last updated.

Business Central

• Bug Fixes
  1. We have fixed a bug wherein Fund Fees and Spendable Allotment processes were timing out and users were not being informed when the processes were completed.
  2. The Auditor Report, when filtered by a Fund Class that contained a space (i.e. two words), was not returning results. This has been fixed.
  3. The Fund filter was hidden on the Fund Statement report set up dialog box. We have promoted it so that it is no longer hidden.
  4. Users were unable to remove the picture from their Company Information once it had been added. This has been fixed; users can remove the picture from their Company Information.
  5. The Show if no Activity filter in the Auditor Report didn’t include balance. It has been changed to include fund balance and renamed to ‘Show if no Balance or Activity’.
  6. Users with the Akoya User permission will no longer be able to reverse JIA lines directly from the General Ledger. JIA batches must be reversed by the batch (all entries) and can only be done from within that JIA batch.
  7. We have fixed a bug that was causing negative amounts in the 1999 to pull into the deposit form as $0 in the Credit Amount.

• Enhancements
  1. Fund Statement report: We have added the comparison options Current Year to Date (YTD), Current Fiscal YTD, Prior Fiscal YTD, and Prior Fiscal Year. These changes have been documented in a Fund Statement whitepaper that can be found on GOsupport.
  2. We have added the ability to use Power BI in Business Central. Users may see a prompt from Power BI on their Business Central home page.

GOapply

• Bug Fixes
  1. The GOapply Duplicate Application workflow was neglecting to duplicate the Transcript and Recommender form definitions when applicable. This has been fixed.
  2. We have removed programming in the document move flow that created subfolders of the Request in Sharepoint, as this was causing errors for some users. 
  3. On the Scholarship tab of Request records there were Transcript and Recommendation fields. We have removed these fields as they were superfluous. 
  4. Changes to the title location on questions in GOmanager resulted in the changes reverting back to the default settings. This has been fixed; changes to the title location will hold.
  5. We have improved the logic behind organization user registration. If a user enters an invalid EIN or Business Number during the registration process, the system will prompt them to enter the info manually.
  6. We have removed instances of the word “application” from the submission message that the applicant sees.
  7. The Invite Contact workflow was not available in contact records even when it was turned on. This has been fixed.
  8. Filled in data in applications was being lost when the user chose to save a draft. This has been fixed.
  9. We have fixed a bug where the resubmission of a GOapply submissions was resending the confirmation email to the applicant. This functionality has been removed. Upon resubmission (Diag dropdown in Status Tracking), applicants will not get an additional email.
  10. We have fixed a bug that was causing file upload restrictions by file type to fail. 
  11. We have fixed a bug wherein if a non-acceptable file type was uploaded by the applicant, they were not able to correct the error.
  12. .xlsx files were not being stitched to the submitted pdf. This has been fixed 
• Enhancements
  1. GOapply registration now includes search by name for organization users.
  2. A new setting in GOapply Settings allows Lead Reviewers to have the option to award or deny requests and, if awarded, determine the amount awarded. This determination will also map to the request or the review group. This process has been documented in the GOapply Reviewer Admin Guide.
  3. We have added an option to the document move flow settings to include a custom flow. If your organization utilizes a custom workflow to move GOapply documents, please use this option in the Documents and Attachments Setting from now on.
  4. A new workflow had been added to Request called Create all requirements - GOapply. This workflow (when run on demand) will create all subsequent status tracking records for all remaining reporting phases. This can be run on a single request or from a request view (for multiple requests). It will create requirement records for up to three interim reports and one final report. The payment/requirement record(s) will also be created and populated in the Status Tracking (Payment or Requirement Number lookup field). 
      

GOfund 

• Bug Fixes
  1. We have added a check to the GOfund Daily Invitation Check workflow for when the End Date precedes the current date. This is to fix the scenario where a GOfund connection was created that had already ended, but the user was still getting an email when they weren’t supposed to. 
  2. The Timing of Grant Helper Text was not paired with its field on the recommend a grant form. We have moved it on the page so it displays directly under the Timing of Grant field.
• Enhancements 
  1. We have enhanced the process that sends an email confirmation to grant recommenders. This process will now run anytime GOfund Recommender in the Request contains data upon creation. This process is named “Send confirmation email to GOfund Recommender” and will be turned OFF when we push out the update. We intentionally do not have this process turned on because the email needs to be customized prior to being turned on. You will need to open the process in PowerApps in order to edit the email. A user from your foundation should be added to the “From” line, and the body of the email should be edited to include your foundation’s information.