Views:

RELEASE NOTES: March 13, 2025

 

akoyaGO release notes give all users information about bug fixes and enhancements in the current release. This document describes all changes as of 3/13/2025. Documentation is 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. 

 

*Special announcement* the Contact form has been replaced with Contact with Accounting and Contact without Accounting, depending on which app your organization uses. After the March 2025 Release, akoyaGO will no longer support the Contact form. It will remain in the app for now to allow you to move your customizations to the new form. In a future release, we will remove the Contact form from the app entirely. 

 

akoyaGO

 

  • Bug Fixes
    • The Fund field has been removed from the nonaccounting payment quick create form.
    • We have fixed a bug in which team users were not able to delete personal views or dashboards.
  • New Features
    • Mailing Lists, an alternative to Marketing Lists, has been implemented in akoyaGO. Please review the Mailing Lists knowledge article on GOsupport for more information.

 

 

akoyaGO with Accounting 

 

  • Bug Fixes
    • General (affects all workspaces)
      • We have fixed a bug in which team users were not able to delete personal views or dashboards.
    • Grants Management
      • We have updated the logic in historical request payments (most likely created during data migration) so that updating the payment date or payment account will not update the payment status. Payment status will remain “HISTORY”. 
      • We have fixed a bug in which the special request status of In Review did not clear if the Deny grant command bar action was taken. 
      • We have fixed a bug in which the Special Request Status was not clearing when a Request was approved via population of the Original Grant field, rather than using the approve/deny button. Users will now be prompted to choose whether they want the special request status to clear or not upon approval via Original Grant.
      • GOverify: We have fixed a bug in which organizations that were previously verified but now have a status of revoked were not updating the Tax Status field in the GOverify tab of Constituent.
    • Donor Management
      • We have updated the logic in historical gift payments (most likely created during data migration) so that updating the payment date or payment account will not update the payment status. Payment status will remain “HISTORY”. 
      • Users will no longer be allowed to manually create recurring gifts. This table is for recurring gifts created via GOdonate only.
  • Enhancements
    • Grants Management
      • In request payment records, the payments and requirements have been split into two separate subgrids.
      • Requirement Received Date/Time has been added as a column in the Requirements subgrid on Request.
      • Users are no longer able to update the GL Memo in request payments if the payment is part of an unposted journal batch. Please see the Business Central Memo and Description Guide knowledge article for more information.
      • We have enhanced the validation when an interfund grant is created from a fund record. The fund from which the interfund was created will be populated as the grant fund and the gift fund will be blank.
      • Default Payment and Requirement views on Request records have been updated so that only active payment/requirement records are being displayed. 
      • The following system views have been improved:
        • Pending GOfund Requests (for GOfund users) - this view has been renamed to "Pending Recommended Requests". Various columns have been added for data visibility and the filter of Request Status = Pending has been removed.
        • Pending Grant Requests - updated the filter from "grant amount does not contain data" to "original grant does not contain data".
        • Pending LOIs - Added a filter for status = active.
        • Pending Requests - added a filter for status = active and changed filter to "original grant does not contain data".
        • Pending Requests with Submission Status (for GOapply users) - removed extraneous columns, changed filters to "original grant does not contain data", "status = active", and "request type = grant".
        • Pending Scholarship Requests - removed extraneous columns, changed filters to "original grant does not contain data", "status = active", and "request type = scholarship".
    • Donor Management 
      • Users are no longer able to update the GL Memo in gift payments if the payment is part of an unposted deposit. Please see the Business Central Memo and Description Guide knowledge article for more information.
    • Fund Management 
      • Scheduled Distributions: (Please see the Scheduled Distributions knowledge article for more information)
        • Scheduled Distributions can now be created via Quick Create action.
        • The scheduled distribution form has been rearranged for improved user experience. 
        • A new field – Distribution Override Date, allows the user to specify the date to be used for the next set of records created by the Scheduled Distribution. This can be used in case the user needs to adjust the date slightly (e.g. to process on a week day when next distribution date falls on a weekend) or to skip a distribution.
        • A new field -- Distribution Type has been added to the form. Because this field will be null in each existing Scheduled Distribution record, you will need to run a flow to populate it for all active Scheduled Distributions. Please see the Scheduled Distributions - Populate Distribution Type workflow knowledge article for instructions.
  • New Features
    • Mailing Lists, an alternative to Marketing Lists, has been implemented in akoyaGO. Please review the Mailing Lists knowledge article on GOsupport for more information.
    • Request Payment Voids, Refunds, and Adjustments are now done through a command bar button on gift and request payments. Please see the Request Payments Voids, Adjustments, Refunds knowledge article for more information. This feature includes a new field on request payments called Refunded Amount – this field has been back populated in your site to account for reversals where the reversal type was refund that were processed before this change was implemented. 

 

 

Business Central

  • Bug Fixes
    • We have fixed a bug in which request payments that were previously financially voided then reissued were updating the Payment Status to 'Received'. Payments in this case will be Payment Status Paid.
  • Enhancements
    • When a check is financially voided from the check ledger, the sync back to CRM will happen immediately, so users will be able to see the payment status of the payment change to Received faster.
    • The new fund statement layout is now the default layout when running fund statements. The old layout can still be manually chosen from the report dialog.

 

GOapply

  • Bug Fixes
    • We have fixed a bug in which individual type GOapply Users were getting stuck in the status of Pending Approval during the registration process. Individual GOapply Users will be automatically approved during the registration process.
    • We have fixed a bug in which fields that were mapped in the first phase of an opportunity were not pre-mapping in subsequent phases where that field is present.
    • We have removed Header font types from the html editor field in Form Editor because these font types were not rendering correctly in the submitted PDF.
    • We have fixed a bug in which, when using the Duplicate Opportunity workflow, the Summary and Description text fields were not visible to applicants on GOapply.
    • We have fixed a bug in which the Impersonate user function was not adhering to the GOapply User’s site setting if multiple GOapply sites are being utilized.
    • We have fixed a bug in which read-only fields were not updating after the Update Form Definition function was run.
    • We have fixed a bug in which mapping was failing on a date field that had an invalid format but the error was not recorded on the GOapply Status Tracking record. Going forward, mapping errors will be recorded in the timeline of the GOapply Status Tracking record.
    • We have fixed a bug in which, when Requested Amount existed as a pre-mapped field, advancing to the phase with that field would cause the payment/requirement creation workflow to run and resulted in Requests having duplicate payments and/or requirements.
    • We have fixed a bug wherein the Registration Type GOapply setting was not preventing users from logging in based on their user type in cases where a single organization has multiple GOapply sites.
    • We have fixed a bug in which users were not able to see the list of opportunities if the GOapply site was different from the site they registered in (if utilizing multiple GOapply sites). 
    • We have fixed a bug in which new users who were registering their organization and chose a country other than the US or Canada, the country was not reflected in the Constituent record that was created in akoyaGO CRM.
    • We have fixed a bug in which individual users were able to register multiple times with the same email, causing duplicate GOapply User records. Users will now be alerted if the email they are using is taken by another GOapply user.
    • In response to certain users being unable to utilize the "Advance to Next Phase" button, we have given all team and administrator  user roles the ability to utilize this feature 
    • GOapply Reviewer bug fixes:
      • We have fixed a bug in which reviewers were able to access the review group even after the deadline had passed. In this instance, the reviewer had bookmarked the URL for the review group. Going forward, the Review By date will prevent this.
  • Enhancements
    • The Update Form Definition workflow has been moved into the code and can now be run via a command bar button on GOapply Status Tracking records/views. Please see the GOapply Admin Guide for more information.
    • Constituents can now be invited to apply for opportunities through a command bar button on Constituent records. Please see the GOapply Invitation Only Applications knowledge article for more information.
    • Address fields have been removed from the individual GOapply registration form because users outside of the US or Canada were not able to enter other countries in the required Country field.
    • The Advance to Next Phase command bar button now allows you to select which phase you want to advance to.
    • Registering GOapply Users will now be able to select from the full list of countries.
    • When impersonating a GOapply User, you may now choose the GOapply site in which you want to impersonate (if utilizing multiple GOapply sites).
    • Users will no longer be able to make changes to a phase that is part of a currently published opportunity. This goes against GOapply best practice. To edit a phase form, you now must unpublish, make your changes,   then re-pubish.
    • We have updated security roles so that only GOapply Admins and users with System Admin or System Customizer will be able to edit GOapply Users. All other roles will only have read-only access.
    • In response to certain users being unable to utilize the "Advance to Next Phase" button, we have given all team and administrator  user roles the ability to utilize this feature.
    • GOapply Reviewer enhancements:
      • Adding requests to a review group can now be done through a command bar button on Request and Status Tracking records. This process will also validate that the phase is submitted and matches the phase set on the Review Group record. See the GOapply Reviewer Admin Guide for more information.
      • Duplication of review groups can now be done through a command bar button on Review Group records.
  • New Features
    • Scholarship Automatching is now available in GOapply. This feature works with scholarship eligibility criteria in your CRM to match applicants with scholarshps they are eligible to apply for. See the Scholarship Automatch knowledge article in GOsupport for more information.

GOfund

  • Bug Fixes
    • GOfund no longer supports attempts to repeat an interfund grant to a fund that is no longer active. 
    • We have fixed an issue with text wrapping on the description field that appears when a user selects an organization to grant to.
  • Enhancements
    • Fund categories will now be sorted alphabetically by Code on Interest.
    • We have updated the Charity Search functionality to disallow grant recommendations to organizations that have a Revoked status. Users will no longer be able to select revoked organizations from the Charity Search results list. As part of this change, the Charity Search results list will now display that status of each organization.
    • Columns displayed on the Grant and Gift history pages will now be sortable alphabetically or by date, depending on the data type, and users will be able to search the list by keyword.
    • We have added a GOfund setting to allow/disallow the Primary Fund Donor to be displayed on the fund summary.
    • When utilizing two-factor authentication, the email that contains the code will be recorded on the contact to which the email was sent.
    • Recurring grant recommendations (scheduled distributions) will no longer auto-create request payments. Request payments will not be created until the request is approved.
  • New Features

 

GOdonate

  • Bug Fixes
    • We have fixed a bug in which Fee Amount was not populating on subsequent payments in a Recurring Gift. Fee Amount was populating properly in the original GOdonate Transaction, but not on subsequent records created as part of the Recurring Gift process.
    • We have fixed a bug in which the profile dropdown options (Donation History, Recurring Donations, View My Funds, Manage, Logout) were not visible.
    • We have fixed a bug in which users who were trying to register for GOdonate, who already had an existing GOfund account, were not receiving the email verification request.
    • We have fixed a bug in which the Gift Date was not populating on the GOdonate Transaction record.
  • Enhancements
    • GOdonate fees will be captured differently when the donor opts to cover the fee depending on how the fee is set up.
      • When the fund paying the fee is the gift fund the donor covered fee is added to the donation amount and reflected in Total Amount and Amount 1. The actual Strip fee will be captured in Fee Amount and Fee 1.
      • When the fund paying the fee is other fund the donor covered fee is added to the donation amount and reflected in Total Amount. Fee Amount will reflect the actual Stripe fee. Amount 1 will reflect the donation amount. A new field called Other Fee Fund will reflect the fund selected to pay the fee, and the amount that the donor added to their donation to cover the fee will be captured in a new field called Fee Fund Amount. All of this is documented in the GOdonate Admin Guide.
    • GOdonate confirmation email activities will now set the Regarding as the GOdonate Transaction record.
    • GOdonate Transactions now contain a command bar button called Resync. This button is to be used for troubleshooting in cases where a bank account was used to make the payment in GOdonate.
    • For troubleshooting purposes, we have added a Resync button to GOdonate Transaction records. This can be used in cases where the stripe payment information does not update the GOdonate Transaction record when the payment was made via ACH/bank account. 

 

Keywords: Release notes, product update notes, March 2025