April 30, 2026 Release Notes

akoyaGO release notes give all users information about bug fixes and enhancements in the current release. This document describes all changes as of 4/30/2026. 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.

Summary

This release includes a focused set of updates across akoyaGO, GOdonate, and GOfund workflows, along with improvements to GOapply and GOmanager experiences. The goal is to reduce friction for day-to-day foundation operations, make donation and scholarship experiences clearer, and prevent common errors that create rework.

akoyaGO New Feature – Conditional Logic in Letter Templates

With this update to the Letter Templates feature in akoyaGO, you can now include if/then logic directly in your Word templates.

This means your letters can automatically adjust content based on the information you enter, helping you produce more accurate, consistent communication without having to manually edit templates each time.

Conditional logic is especially helpful when foundations need different wording depending on a recipient’s details, program type, eligibility status, or other conditions.

For daily workflows, this improvement helps:

• Reduce repetitive template editing
• Improve consistency across outreach and correspondence
• Save time when generating letters for different scenarios

akoyaGO with Accounting - Interfund and accounting integrity improvements

1. Generate General Ledger lines for interfund transfers

Interfund transfer postings in Business Central now generate exactly two G/L lines, correcting a prior behavior that created extra lines.

• What’s changing:
  1. Exactly one line reflects the deduction from the gifting fund.
  2. Exactly one line reflects the credit to the receiving fund.
  3. No extra vendor/customer lines are produced.
• Why: cleaner accounting outputs and fewer reconciliations.

2. Prevent creation of interfund payment/request records until sent to accounting

Related Request/Gift/Payment records are no longer created until the user clicks Send to Accounting.

• What’s changing: record creation is tied to the Send to Accounting action.
• Why: it prevents partial or premature records that can lead to rework.

3. Deprecate old Interfund workflows and BPFs

Older Interfund creation and reversal workflows are being deprecated and turned off to align users with the newer process.

• What’s changing: specific Convert/Create/Send/Update workflows are labeled Deprecated and turned OFF in the solution.
• Why: reduces confusion and prevents use of outdated automation paths.

4. Update Interfund conversion workflow for the new send-to-accounting process

The Convert to Interfund workflow now aligns with the newer process so it doesn’t attempt to create child records too early.

• What’s changing:
  1. It adds timeline notes explaining the conversion.
  2. It deactivates the payment.
  3. It marks request special status as canceled.
• Why: prevents broken links and inconsistent record creation.

5. Interfund grant adjustments and void actions

5.1 Users can void and adjust interfund grants with correct GL behavior

For interfund grants with valid payment statuses, users can now void (reversal) or adjust.

• What’s changing for Void:
  1. Users provide a Reversal Date.
  2. The interfund grant is reversed in Business Central using two G/L lines.
  3. Related records update accordingly (request denial, linked payment status, reversal amounts/dates, gift adjustment value).
• What’s changing for Adjust:
  1. Users provide adjustment details (dates, fund transfers, gift and grant accounts/functions).
  2. The system reverses the original and creates a new interfund grant record.
  3. The new record is immediately sent to accounting.
• Why: foundation staff can correct interfund activity without manual accounting cleanup.

5.2. Locked interfund grants after Send to Accounting

Interfund grant records that already contain a payment status are now locked from modification.

• What’s changing: fields become read-only after the record is sent/reversed.
• Why: protects accounting integrity and prevents accidental changes.

akoyaGO - GOverify

1.1.1. Prevent GOverify runs on GOverify Exempt records

Users will now see a clear banner-style alert when they try to run GOverify on records marked as GOverify Exempt.

• What’s changing: the action is blocked with a straightforward message.
• Why: it prevents wasted time and confusion when a record isn’t eligible to be processed.

GOapply Major Feature Update – Organization Profile

Organization Profile Updates for Applicant Panels

1.1 What changed for applicant submissions

The Organization Profile experience has been improved so that when an Applicant Panel is used, users no longer need to re-enter organization details that already exist in the system. When the Applicant Panel loads, the application now automatically pulls in the most current Organization Profile information—reducing duplication and preventing mismatches between the application and the organization’s saved record.

This update also strengthens validation at the moments that matter most:

• The Organization Profile must be complete and valid before users can proceed through flows that depend on organization data.
• If the Organization Profile is incomplete, the user is redirected to the Organization Profile page to complete the required details, and then the system checks again after saving.
• If the information is still not valid, the user is prompted again until the profile meets the requirements, or progress is blocked with a clear, helpful message.

1.2 Organization Profile can be managed outside an application

Authorized organization users can now update the Organization Profile at any time, independent of a specific application or grant cycle. This means organization details stay current without forcing users to wait for, or depend on, an active application to make changes.

1.3 Applicant Panel values are now mapped automatically

For applicant forms using the Organization Profile flow, Applicant Panel mappings are handled automatically:

• Applicant Panels on forms are mapped to the Parent Constituent of the logged-in organization user.
• The foundation/client cannot modify this mapping for this process.
• Other applicant panel mappings or panel types beyond the organization Applicant Panel are not supported in this workflow.

1.4 Submission-time re-check to prevent last-minute issues

Before submission of organization-data-required flows, the system re-verifies that the user still has:

• A valid Parent Constituent, and
• A valid Organization Profile associated with the Applicant Panel and organization context.

If anything has changed since the form was started—such as an organization profile becoming incomplete or a context becoming invalid—submission is blocked with a clear error message that instructs the user to fix the Organization Profile issue first.

1.5 Pending change requests: notice without blocking applications

If the Organization Profile has a pending change request, the user experience includes a disclaimer banner that is shown on the Organization Profile and/or related pages to communicate that changes are under review.

Editing behavior is also refined:

• Users associated with the same Parent Constituent are prevented from editing while the pending change request is in effect.
• Importantly, pending change requests do not block application progress on their own.
• If Organization Profile information is included in exported documents:
• Any appended content in generated PDFs includes a clear disclaimer and shows the proposed/requested changes.

1.6 PDFs now follow per-phase rules (and protect anonymous reviewers)

When users submit an application, the system generates the application PDF. PDF behavior regarding Organization Profile content is controlled by per-phase settings:

The most current Organization Profile may be appended as the first page, as the last page, or not appended at all.

Anonymous reviewer: PDFs will not include Organization Profile content.

GOapply usability and reliability fixes

1. Review portal PDF fixes (Safari)

GOapply reviewers using Safari can now reliably view review PDFs in the review portal.

• What’s changing: the blank/black screen issue on Safari is resolved.
• Why: reviewers can complete reviews without switching browsers or losing access to critical materials.

2. Scholarship automatch reopen behavior

When a scholarship automatch application is reopened, previously selected scholarships remain selected.

• What’s changing:
  1. Users no longer have to de-select and re-select scholarships.
  2. “Submit All” remains available for reopened applications, including situations involving automatic opt-in.
• Why: reduces repetitive work and avoids blockers that prevent advancing.

3. Fix reviewer PDF header and template display issues

Several PDF-related fixes improve the accuracy of reviewer-facing documents.

• Scholarship Name appears in the header of requested scholarship PDFs.
• Reviewers no longer see GUID text appended when a dropdown program mapping is used.

4. Make HTML editor numbered lists render correctly

Numbered lists created in the HTML editor now keep numbering and content on the same line rather than inserting an unintended line break.

• What’s changing: better list formatting in HTML editor content.
• Why: instruction text appears correctly to applicants.

GOapply form builder and authoring reliability

1. Prevent loss of question names and mapping overwrites

When questions are added inside panels in the Simple Form Builder, they will now be assigned unique question names by default.

• What’s changing: questions inside panels no longer overwrite each other when submitted.
• Why: foundation staff can build complex forms with confidence that responses will save to the correct panel context.

2. Advanced form builder fixes for currency branching logic

Currency questions used in branching logic no longer get an unintended period appended to the question name.

• What’s changing: branching logic evaluates against the original question name.
• Why: logic triggers correctly, preventing applicants from getting the wrong form behavior.

3. Deprecation of valueName attribute in advanced form editor

For GOmanager form editors covered by this update, the question-level valueName is no longer shown or set via the form builder UI.

• What’s changing:
  1. The valueName property can’t be set using the editor UI.
  2. If an affected editor saves a form containing question-level valueName, reopening may remove it from the saved definition.
  3. Existing lookup/autocomplete behavior that depends on nested configuration remains working.
• Why: helps prevent configuration errors and keeps existing mapping behavior stable.

GOapply and GOmanager data accuracy fixes (additional reliability)

1. Registration: lock all address fields for existing constituents

When a GOapply user registers by selecting an existing constituent, all address fields are locked, including Country.

• What’s changing: Country can no longer be edited while other address fields remain locked.
• Why: prevents accidental changes and inconsistent address data.

2. Fix number-field step rules to prevent invalid decimals

Simple Form Builder and mapped scholarship panel number fields now enforce the correct Step behavior.

• What’s changing: Integer-mapped fields restrict whole-number responses. Decimal-mapped fields enforce the appropriate decimal increment.
• Why: prevents mapping errors caused by invalid user input.

3. Prevent eGrant.net attachments tab from showing on requests

The eGrant.net Attachments tab is no longer shown on Requests.

• What’s changing: the tab is removed from Request experiences.
• Why: avoids confusion when users expect eGrant-related content.

GOfund UI Improvements

1. Reduce clutter on the GOfund home page

The GOfund home page can now be simplified by optionally removing the Grant Recommendation and Grant History boxes.

• What’s changing: a configuration option hides those home page elements while keeping navigation access.
• Why: fewer distractions for fund advisors and fewer questions about which option is “better.”

2. Make gift advice and grant recommendations easier to confirm

This release improves clarity and usability within grant recommendation flows.

• What’s changing:
  1. Grant Amount formatting adds commas for values greater than 999.
  2. The shopping cart supports “Recommend another grant” to reduce clicks when making multiple recommendations.
  3. Foundations can configure helper text across standard grant recommendation fields.
  4. Foundations can control whether the anonymous checkbox appears for grant recommendations.
  5. Foundations can optionally remove anonymous checkbox content from the form (with flexibility to place it elsewhere).
• Why: clearer data entry and fewer mistakes lead to smoother recommendations.

GOfund and donation operations configuration

1. Optional off-switch for one-time donation confirmation emails

Foundations can now suppress automated one-time donation confirmation emails for GOdonate and GOfund.

• What’s changing:
  1. A new DisableAutomatedConfirmationEmail setting exists on GOdonate settings.
  2. If enabled, one-time donation confirmation emails are suppressed.
  3. Recurring gift confirmation emails remain unaffected.
• Why: foundations control when and how donors are contacted.

2. Error handling and clearer guidance for external users

2.1. Friendlier GOfund error experiences

GOfund error pages are now designed to be more user-friendly for external users.

• What’s changing:
  1. Error messages are shorter and calmer.
  2. Pages include brief next steps (for example, contacting the foundation or trying again).
  3. Support/reference identifiers remain available for correlation.
  4. Accessibility and responsive behavior are preserved.
• Why: reduces confusion and helps donors know what to do next.

GOdonate Donation and checkout experience improvements

1. Edit checkout donation details with guided inputs

On the donation checkout page, users can now edit key donation details more safely and consistently.

• What’s changing:
  1. Fund selection uses a drop-down menu (no free-text entry).
  2. Dedication edits use a dedicated modal that mirrors the dedication section.
  3. Designated Purpose and Notification edits use modals that mirror those respective sections.
  4. Users can also edit the donation Amount.
  5. Related notifications are included as part of the flow.
• Why: fewer mistakes and a more guided experience during checkout.

2. Hide designated purpose during checkout when it’s disabled

If the foundation has disabled “Enable Designated Giving” in GOdonate settings, the Designated Purpose column no longer appears on the transaction review page before checkout.

• What’s changing: the Designated Purpose view is hidden when the setting is off.
• Why: the checkout page matches configured options and avoids confusion.

3. Show recurring gift start and end dates at checkout

Recurring gifts will now clearly show both start and end dates on the GOdonate checkout experience.

• What’s changing: start date and end date appear for recurring gifts on the checkout UI.
• Why: donors and staff can confirm schedule details before completing the gift. 

4. Remove weekly recurring gift options

Weekly recurrence is no longer available when creating or editing recurring gifts in GOdonate.

• What’s changing:
  1. The Weekly option is removed during creation.
  2. Existing recurring gifts can’t be changed to weekly on edit.
• Why: avoids unsupported or unexpected scheduling.

5. Cart and basket capacity updates

The shopping cart and basket experience has been improved to better support multiple donations.

• What’s changing:
  1. The basket capacity increases from 6 to 12 donations.
  2. When the basket is full, users now receive a clear message on the Shopping Cart page.
  3. The basket icon will show both the item count and the total dollar value.
• Why: users can understand cart status at a glance and avoid interruptions.

6. Improve donation and fund catalog browsing

Donors can more easily find and compare funds.

• What’s changing:
  1. Funds can be listed in an order that supports easier browsing.
  2. Fund catalog ordering can be changed (for example, to reflect fundholder name lookup expectations).
• Why: smoother discovery reduces support requests and helps donors select the right fund.