Views:

RELEASE NOTES: April 24, 2025

 

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 4/24/2025. Documentation will be updated or created to reflect these changes. If you have questions, please contact your account manager or akoyaGO Support. Please be aware that you may need to refresh your browser, clear your browser cache, or log out/log back in to see the following changes after the day of the release. 

 

akoyaGO

  • Enhancements
    • Letter generation will now generate a Word document rather than a PDF. Note: the compiled PDF will still exist on the Letter Template Session, but the document that gets created for each record will be a Word document so that users can edit any given letter before sending it, if needed.

akoyaGO with Accounting 

Special note: We have created a new security role called Send to Accounting. This role is required for any user who will Send to Accounting or process Reversals/Adjustments. We have deployed and assigned this security role to all existing users with akoyaGO with Accounting Admin and akoyaGO with Accounting Team user roles. This role has not been assigned to users with read-only access. Field-level security will still be considered during the send to accounting process for the time being. Organizations with custom security will need to assign this role to the proper users.

  • Bug Fixes
    • Grants Management
      • Interfunds: We have fixed a bug where if a user updated an Interfund Grant after the associated payment records had been created, it triggered the G/L account defaults to update on the payments incorrectly (e.g. using the gift default instead of the interfund gift default).
  • Enhancements
    • General (affects all workspaces)
      • Letter generation will now generate a Word document rather than a PDF. Note: the compiled PDF will still exist on the Letter Template Session, but the document that gets created for each record will be a Word document so that users can edit any given letter before sending it, if needed.
    • Donor Management 
      • Quick-create has been enabled for Donor. 
      • We have added validation on gift fee fields on gift payments so that users cannot add the same gift fee twice on one gift payment. 
      • We have updated the calculated gift fields on Donor and Fund to exclude the Non Gift gift type. These fields include: 
        • On Donor:
          • Total giving this year
          • Total giving last year
          • Total giving [2-5] years ago
          • Consecutive giving years
        • On Fund
          • Total giving this year
          • Total giving last year
          • Total giving this fiscal year
  • New Features
    • Donor Management:
      • Gift payment voids, adjustments, and refunds has been implemented. The gift payment reversal process (business process flow) has been deprecated. 

Business Central

  • Bug Fixes
    • We have fixed a bug in which read-only users were not able to see Activity Totals on the Business Central home screen. 
  • Enhancements
    • We have updated the document no. logic for gift payments. Going forward, the Document No. will capture the gift payment reference number (GPMT-######). The payment type/Check Number will be captured in the "Description" field in Business Central, as well as the External Doc. No. field. 

GOapply

  • Bug Fixes
    • We have fixed a bug in which the ‘create a new account’ link on the log in screen would disappear after the user attempted to log in with the wrong credentials.
    • GOapply form editor date fields will no longer accept dates earlier than Jan. 1, 1900. This is because this is the earliest allowable date for this field type.
    • We have fixed a bug in which uploaded images were not being moved into the Status Tracking Attachments and therefore were also not moved into documents on Request.
    • We have fixed a bug in which bulk import of users was not validating that each user contained all required fields; this resulted in user errors on log in attempts. 
    • We have fixed a bug in which the auto-advance to next phase function was creating corrupt status tracking records if the “next phase” already existed as a status tracking record on the request. Going forward, this function will check to see if a status tracking record for that phase already exists on the given request record and, if so, will not create a new status tracking record for that phase.
    • We have fixed a bug where, in the case that two files with the same name were uploaded, one was overwriting the other. GOapply submissions (including third party submissions) now accepts files with duplicate names and recognizes them as separate files. 
    • We have fixed a bug in which an inactive CRM constituent was mistakenly attached to a GOapply applicant during registration. Going forward, GOapply registration will never connect a user to an inactive record.
    • We have fixed a bug in which, during registration, searching for organizations by tax ID was returning only the parent constituent if multiple constituents shared a tax ID. GOapply registration will return results for all existing constituents with the given tax ID (if applicable).
    • We have fixed a bug in which submission errors were occurring on phases that contained a multi-select field inside of a panel. 
    • We have fixed a bug in which the Matched Scholarships menu option was appearing regardless of whether GOapply Scholarship Automatch was enabled or not.
    • We have fixed a bug in which confirmation emails were not being sent to applicants who had been advanced to a subsequent phase. This was because the GOapply Settings was not being filled in on the GOapply Status Tracking record that was being created as part of the process.

  • GOapply Reviewer bug fixes:
    • We have fixed a bug in which the list of applications was not respecting the sort order of the view (view name: GOapply Review). 

  • Enhancements
    • We have added two new phase types. 
      • Other: This is a phase that will not create a requirement on Request. If you have Reporting Phases and do not want a related Requirement to be created, our best practice is to use the "Other" phase type. 
      • The second new phase type is called Award Agreement. Once submitted, this phase will populate a new date/time field on Request called Agreement Received (Summary tab, Award section).
    • Users can now print or download a PDF of an in-progress application that will include all fields that they have filled out at that time. These files will be watermarked with “DRAFT”. 
    • We have removed the GOapply Settings field from GOapply User records. Because of this, GOapply users will be able to log in to other sites if the organization is utilizing multiple GOapply sites. 
    • The workflow “GOapply Bulk Import Users” has been converted to a command bar button on the GOapply Add Users table. Functionality for this feature has not changed.
    • Request Received and Requirement Received fields which were previously deprecated and replaced with date/time fields have been restored. The date/time fields will continue to be filled upon GOapply submission, as will the previously deprecated fields. 
    • The GOapply app has been deprecated and removed from all security roles. All GOapply work going forward should be done in the GOapply workspace.
    • GOapply users created via the GOapply Add Users table will all be automatically approved and the Email Confirmed field will be set to Yes.

  • GOapply Reviewer enhancements:
    • The list of applications in a review group will now have a column for Score so that reviewers can see the score they have given for each application.
    • The workflow “GOapply Duplicate Review Group and Reviewers” has been converted to a command bar button on the Review Group table. Functionality for this feature has not changed.

GOfund

  • Bug Fixes
    • We have fixed a bug in which the submission PDF for grant recommendations was not appearing in the timeline of the request nor the request documents, and, as a result, the GOfund log for that activity did not generate. 
    • We have fixed a bug where comments from the interfund grant recommendation form (Grant to = Established fund) were not mapping to the comments field on the associated Interfund record.
    • GOfund donations: We have fixed a bug where the stripe fee was not included on the GOdonate Transaction when a donation was made from GOfund.
  • Enhancements
    • The Purpose field on grant/gift history views now truncates at 50 words. Users will have the option to expand/collapse the purpose when it exceeds 50 words.

GOdonate

  • Enhancements
    • The GOdonate Process Completed Donation on-demand workflow has been moved to our code. This workflow was running automatically once the GOdonate Transaction contained a donor and existed as an on-demand workflow in the case that it failed and needed to be re-run manually. The on-demand workflow has been deprecated. 
    • For recurring gifts, the Next Occurrence date will be based on the most recent transaction, rather than the date when the recurring gift was created. This is because, in cases where days passed between the donor setting up the recurring gift and the GOdonate transaction being processed, the Next Occurrence date would be inaccurate.
    • GOdonate Transaction is now being captured by a lookup field on associated Gift and Gift Payment records.
  • New Features
    • GOdonate basket: This feature allows users to add up to six gifts to their basket and checkout just once. To support this feature, we have also updated the GOdonate – Donation Confirmation Email template. 

 

Keywords: release notes, product update notes, April 2025 release notes, April 2025 product update