RELEASE NOTES: March 23, 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 3/23/2023. Documentation has been updated or added to reflect these changes. If you have questions, please contact your account manager or akoyaGO Support.
akoyaGO
Bug Fixes
GOverify: we have modified how we handle organizations that are listed as inactive. Running GOverify on an inactive organization will leave all fields null in the GOverify record except for Constituent, Tax ID, and Date Exemption Checked. The Verification Note will read, “Not active according to Publication 78”. More information on page 6 of the GOverify whitepaper.
A bug was causing the Payee to not fill in as the default payee when the request was made via the quick create form from the constituent record. This has been fixed.
We have turned off the workflow that annually checks for GOverify runs because of redundancy and storage capacity issues.
The request titling process had a bug in it that caused scholarship titles to read as “Scholarship to (blank)”. This has been fixed so that when request type = scholarship, the title will fill in the primary contact of the request.
A bug was causing a GOverify warning banner on records that had been marked GOverify exempt. This has been fixed.
The system was throwing an infinite loop error when processing a gift payment with a fee whose fee type = flat. This has been fixed.
Team users in the akoyaGO non-accounting app were unable to run GOverify. This has been fixed.
Enhancements
GOverify will now run on tax IDs with or without the dash (US EIN only). The new functionality will insert a dash in the tax ID if there was no dash to begin with.
Updating the email address of a GOfund or GOapply user on their Contact record will update their GOfund and/or GOapply log in. A password reset is not required.
GOapply User Metrics Dashboard: A new dashboard was added that shows GOapply data such as recent submissions, recent log ins, and password reset requests.
Contact and Constituent records now include a field that describes whether the record is a Grantee, Donor, or Fund Holder or any combination of the three.
Requests can now be approved or denied with the click of a button in the toolbar of the Requests entity. This can be done in bulk from a view or individually. Approvals can be based on the requested amount or the recommended amount.
New Features
CRA Search: akoyaGO now supports CRA search when a Canadian Constituent does not contain a Tax ID. This function initiates after attempting to run GOverify on such a record. See the CRA Search whitepaper for instructions and more information. IRS search functionality is coming in a future release.
Foundation Matching: akoyaGO now supports matching gifts. A new entity called Foundation Matching Gifts has been added to your CRM, and matching gift records can be created in bulk or individually through a new workflow on Gift Payments. A whitepaper for this process is forthcoming.
Business Central
Bug Fixes
The field Akoya Fund Fee Batch in the G/L Setup had been allowing 20 characters when it should have only allowed 10. This has been fixed. The field will throw an error if more than 10 characters.
Enhancements
Multiple Accounts in Single Pooled Investment: we now support multiple money managers in a single pooled investment. Contact akoyaGO Support if you wish to have this set up.
Fund Fees, JIA and Spendable to Alternate Fund: We now support assessing fund fees or allocating spendable allotment or JIA to an alternate fund. The alternate funds are set on the Fund record in CRM.
Fund Groups: Fund groups has been added as an entity in CRM. There is a new field on Fund for a lookup to Fund Group. Fund Statements can be run as a group from within the CRM only. A future enhancement will include Fund Statements by group in Business Central. Documentation for this feature is forthcoming.
Fund Fee Assessment based on Fund Group: Fund Fees can now be assessed on the Fund Group level. Fund Fees will automatically assess as a group if the group is set up in CRM.
Comparison on Fund Statement: the fund statement now contains a comparison field. Comparison types are prior month, prior quarter, prior year, and prior year to date. Comparison can be set at the layout level or on a one-off basis when the report is run. Comparisons set on a one-off basis will override any comparison set at the layout level. When a comparison is set at the layout level, it will apply to fund statements in CRM and GOfund, as well.
Document number is now a column included in the Bank Statement Lines on Bank Reconciliations.
The Post option for the General Journal and posting printed checks is now under an option called Home in the action toolbar. Drop down the Post button to see all posting options.
GOapply V2
Bug Fixes
A bug caused GOapply submissions to create blank request records. This has been fixed.
We have modified the logic to properly move documents that are nested in other questions. This is defined by file upload fields that are inside a dynamic panel that is dependent on branching logic. These files were being ignored and were not moving to Status Tracking Attachments, meaning they would be absent from the Request and from GOapply Reviewer. This has been fixed.
A bug was causing file types that weren’t listed as the accepted file types to be uploaded by applicants. This has been fixed.
The EIN field in pre-mapped panels (Organization and Fiscal Sponsor) is now set to auto unmask = False so that US EINs input in those panels map to the CRM with the dash included.
A bug was causing files in the submitted PDF to be cut off or displayed incorrectly. This has been fixed. Files in the PDF will be listed as the file name where uploaded and attached to the end of the document.
Enhancements
GOapply Admins can now impersonate users. This action is done from the User record. See page 9 of the GOapply V2 Admin Guide for more information.
We enhanced the logic to look at phase type before filling in LOI Received or Request Received. LOI Received will only fill in when phase type = Letter of Inquiry and Request Received will only fill in when phase type = Application.
Canadian organizations now have their own composite panels called "Fiscal Sponsor/Payee - CRA" and "Organization (Applicant) - CRA" that accommodate Canadian business numbers and address fields.
New Features
Org Profile Form Editor: We have added a Form Editor for organization profile. This Form Editor is accessed in GOapply Settings and contains all "searchable" (as defined by PowerApps) fields in Constituent records, including any custom fields that you have on your Constituent form. See page 11 of the GOapply V2 Admin Guide for more information.
GOapply V2 Reviewer
Bug Fixes
A bug was causing the recommendation and transcript submitted forms to not appear in Reviewer when those forms did not contain attachments. This has been fixed; completed recommendation and transcript forms will be available for download on the reviewer application regardless of whether an attachment is present.
A bug was causing the application PDF to not load in Reviewer. This has been fixed.
Hide From Reviewer setting was not working for file upload question types. This has been fixed.
A bug was causing Review Response records to not be created. This has been fixed.
Enhancements
Reviewers will now see their own comments in addition to other reviewers' comments in the Reviewer Comments section.
GOapply Admins can edit the list of applications that a reviewer sees with a new CRM view called “GOapply Reviewer”. See page 15 of the GOapply Reviewer Admin Guide for more information.
GOfund
Bug Fixes
Users reported an error message upon attempting to reset their password. This has been fixed.
Enhancements
GOfund logic has been updated to use the address in the Foundation Constituent record defined in Department in the fund's contact information. The phone number and email address will be taken from the Contact defined as the Foundation Staff Contact on the individual fund record.
New Features
Fund Documents: GOfund now supports fund documents. Fund Documents live in your SharePoint and can pertain to individual funds or the GOfund site as a whole. Fund documents are supported by a new permission on the Fund Connection record as well as a new setting in GOfund Settings. These changes have been documented on pages 4, 11, 16 and 29 of the GOfund Admin Guide.
Export Gift/Grant History: GOfund users can now export the gift and grant history to Excel. This functionality is supported by a new view on Gift Payments called "GOfund Gift Export View". When the gift history is exported, it will include donor address fields and exclude if anonymous. This feature has been documented on page 28 of the GOfund Admin Guide.
Hide Spendable Balance: GOfund can now hide the spendable amount on select funds. This is done through a new field on Fund called Hide Spendable Balance in GOfund. Existing funds will default to showing the Spendable, if you want to hide the Spendable, select Yes in this field. See page 20 of the GOfund Admin Guide for more information.
FundWeb
Bug Fixes
A bug was causing grant recommendations made in FundWeb to create duplicate payment records. This bug has been fixed.