<h4>Release Date: August 8, 2026</h4> <h3>Multiple Impact Types per Recipient</h3> <p>Impact now supports assigning multiple impact types to a single recipient for the same fund. Previously, each recipient was limited to one impact template per fund — if a donor's scholarship award included both a narrative quote and a Q&amp;A page submission, those had to be managed separately or as workarounds. With this release, a recipient can hold impacts under multiple templates simultaneously, giving institutions full flexibility to capture and report on all relevant impact types for each award relationship.</p> <ul> <li><p>Recipients can now be associated with more than one impact template for the same fund</p></li> <li><p>All bulk import types (Fund Recipients, Horizontal/Vertical Thank You, QA Page, Narrative Quote) have been updated to support multi-template recipients without generating errors</p></li> <li><p>The Bulk Image File will now require the impact version to support multiple versions per recipient.&nbsp;</p></li> <li><p>The Recipient Types page has been redesigned to display and manage the full set of impact templates associated with each recipient type</p></li> </ul> <p style="text-align:left"><img alt="" class="fb-img" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/3b75c78c-8a1f-4ac7-9eea-739d808f9fcd/h/547.png" style="" width="624"></p> <h3>NEW Classic 2.0 Template Guide</h3> <p>The Classic 2.0 Template Guide is now published and accessible directly within the Manage Designs section of the Impact Administration interface. This guide provides detailed documentation on the Classic 2.0 design — including page layouts, available content zones, font and color options, and configuration recommendations — making it easier for administrators to build and refine report templates without needing to reference external documentation.</p> <h3>Report Template Builder: Improved Image Upload Experience</h3> <p>The image upload experience in the Report Template builder has been significantly improved.&nbsp;</p> <ul> <li><p>File validation feedback is shown immediately on upload — invalid file types or sizes are flagged before the upload completes</p></li> <li><p>A built-in crop tool allows administrators to frame and adjust images directly within the template builder</p></li> <li><p style="text-align:left"><img alt="" class="fb-img" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/2b49839b-35d6-4823-837f-3ea617107fea/h/547.png" style="" width="569"></p></li> </ul> <h3>New Font Option: PT Sans</h3> <p>PT Sans has been added to the available font options in Manage Designs.</p> <p style="text-align:left"><img alt="" class="fb-img" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/543c9d97-8efb-4db6-b218-d9dd0a6eedb5/h/547.png" style="" width="323"></p> <h3>"Recipient Type" Column Removed from Impacts Tab</h3> <p>The "Recipient type" column has been removed from the Impacts data grid on the Recipient Detail page. Because this column displayed the same value on every row (a recipient has only one type), it was redundant alongside the existing "Impact type" column which shows per-impact template information. Removing it reduces visual noise and makes the grid easier to read.</p> <p style="text-align:left"><img alt="" class="fb-img" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/aaefa8c8-3565-44e7-884e-bf69e156c886/h/547.png" style="" width="975"></p> <h3>PDF Rendering</h3> <h4>Configurable Footer on Fund Financial Pages</h4> <p>Fund Financial pages in Impact reports previously displayed an auto-generated footer containing the Constituent ID and Fund ID.&nbsp;A new configuration option within Administrative System Settings view now allows institutions to suppress the Constituent ID and Fund ID footer on Fund Financial pages. The default setting suppresses the footer, so institutions will receive this improvement automatically on their next report generation without any action required.</p> <h4>Justified Text Spacing</h4> <p>Justified text across several page types was being rendered with cramped word and letter spacing, making paragraphs difficult to read. A new Left Justify setting has been added that corrects the spacing behavior. The setting is configurable at the Administrative System Setting level for institutions that prefer left-aligned body text over justified alignment.</p> <h4>Overview Page Heading Width</h4> <p>The heading on the Overview page was being constrained to 3.2 inches when it had 4.2 inches of available space, causing headings to wrap unnecessarily. The heading now uses the full available width with margins consistent with the body paragraph text.</p> <h4>Non-Printable Characters in Fund Names&nbsp;</h4> <p>Fund names containing non-breaking spaces (a hidden character sometimes introduced when copying and pasting data) were causing rendering artifacts in generated PDFs. These characters are now automatically sanitized to standard spaces before PDF generation, ensuring fund names are displayed correctly in all report outputs.</p> <h4>Recipient Photo Placeholder Removed</h4> <p>When no recipient photo was available for a fund, the PDF renderer was displaying a grey placeholder image in the recipient photo zone. This placeholder has been removed — if no photo is supplied for a recipient, the photo zone will be blank rather than displaying a grey box. This is working for Message Page, Statistics, Performance, Impact Pages&nbsp;</p> <h4>Low-Resolution Image Field Handling</h4> <p>Report templates were degrading output quality when image fields contained low-resolution source images. The rendering process has been updated to handle low-resolution images gracefully, producing the best possible output quality from the available source material without distorting or blurring adjacent content.</p> <h3>Defects/Bugs</h3> <h4>Report Batch — Constituent &amp; Fund Selection Fix</h4> <p>When building a report batch and selecting constituents or funds across multiple pages of results, previously selected items from earlier pages were silently dropped from the batch. This meant batches could be generated with fewer recipients than intended — without any indication that records had been excluded.</p> <p>This has been resolved. All selected constituents and funds are now correctly included in the batch regardless of how many pages of results the user navigated through during selection.</p> <h4>Report Batch — Navigation to Live Progress Screen</h4> <p>After initiating batch generation, users were being routed to the "Generate Drafts" screen instead of the live batch progress view. This has been corrected — batch generation now navigates directly to the live progress screen so users can monitor generation status in real time.</p> <h3>Other Updates</h3> <h4>Send to ODDER Issues Resolved</h4> <p>Impact reports can now be delivered directly through ODDER, EverTrue's digital delivery platform. More to come on this feature in future updates!</p> <h4>RE/NXT Nightly Sync — Missing Constituents</h4> <p>We are aware of an issue where not all constituents are syncing on nightly RE/NXT loads. Some records that should be updated overnight are not coming through as expected. Our engineering team is actively investigating the root cause. If your institution is experiencing missing constituent records, please contact <a href="mailto:support.impact@evertrue.com" rel="nofollow noopener noreferrer">support.impact@evertrue.com</a> so we can prioritize your case.</p>…

<h3>Release Date: July 1, 2026</h3> <h2>In-House PDF Rendering — Transition Away from Third-Party PDF Engine</h2> <p>We have completed a significant behind-the-scenes platform transition: Impact has fully migrated its PDF report generation away from the legacy third-party Silicon Publishing (Nucleus) rendering engine to a new EverTrue in-house PDF renderer.</p> <p>What does this mean for your institution:</p> <ul> <li><p>Report PDFs are now rendered within EverTrue Impact platform — no external dependency on a vendor.&nbsp;</p></li> <li><p>Existing workflows - including uploading recipient images, creating report templates, proofing templates, and generating report batches - continue to work exactly as before.&nbsp;</p></li> </ul> <h2>Self-Service Manage Designs &amp; Colors – Available to Customer Administrators</h2> <p>Impact administrators can now manage report designs and brand colors directly within the Impact Administration interface, without requiring EverTrue support team involvement. <a href="https://app.storylane.io/share/ft3e3tfq73xm" rel="nofollow noopener noreferrer" target="_blank">Click here to see a demo!&nbsp;&nbsp;</a></p> <h3>Designs and Default Colors&nbsp;</h3> <ul> <li><p>View all available report designs and click into any design to configure its settings.&nbsp;</p></li> <li><p>Set template fonts - choose heading and body fonts to be applied across reports for that design.</p></li> <li><p>Option to use default colors — when checked, design-level colors inherit from your organization's Default Colors settings rather than requiring manual entry per design.</p></li> <li><p>Set template colors - configure Primary, Secondary, and Body/Paragraph brand colors at the design level, with support for HEX, RGB, and CMYK color formats.</p></li> <li><p>A live color preview swatch updates as you enter values, with all three format equivalents (HEX, RGB, CMYK) displayed beneath for print production accuracy.</p></li> <li><p>Mark any design as inactive to hide it from non-admin users in the report template picker - inactive designs remain visible and manageable by administrators and can be reactivated at any time.</p> <ul> <li><p>Existing Customers will see their previous Vendor rendered Classic Design shown as inactive following the July 1st release - these will not be visible to end users but remain accessible to administrators.</p></li> </ul></li> </ul> <h2>⚠️ Important: What Changes for Your Institution</h2> <p>There are a few important workflow changes that will need your attention.&nbsp;</p> <ul> <li><p><strong>Approval process</strong> — Any generated reports that have already been produced can proceed through the approval workflow without requiring regeneration. Users will still be able to approve batches that were created using the inactive design even after this release - no action is needed to complete your existing approvals</p></li> <li><p><strong>Re-running report batches</strong> — Report batches tied to the inactive vendor design will not be able to be re-run. If a batch needs to be regenerated for any reason after July 1, it will need to be recreated using a report template created from active design.&nbsp;</p></li> <li><p><strong>Copying last year's reports for fall reporting</strong> — The workflow of copying a prior year's report template to use as the starting point for fall reporting will no longer be available for the inactive design. You will need to create a new report template for the active Classic.&nbsp;</p></li> </ul> <h2>Bulk Import - Class Year Validation Now a Warning Instead of an Error</h2> <p>When performing a QA Page bulk import, a missing or non-numeric Class Year value previously caused the import to fail with a hard validation error, blocking the entire import batch. This validation has been updated to a warning across all Impact databases - imports will now proceed successfully, and the Class Year issue will be surfaced as a non-blocking warning for review. This change reduces friction for institutions whose recipient data does not include a Class Year for all records.</p> <h2>Report Batch PDF Not Generating for Funds with No Recipient Photos</h2> <h3>What was happening:</h3> <p>When generating a report batch or proofing a template for a fund that had no recipient photos associated with it, the PDF would fail to generate entirely. The PDF rendering process was relying on image mapping data to look up the Fund ID and Template ID - if no images existed for a fund, that lookup returned no results and the generation process halted.</p> <h3>What was fixed:</h3> <p>The PDF generation process has been updated to retrieve the constituent package XML directly from the stored report data tables rather than depending on image mapping data. The Template ID is now passed explicitly during batch generation rather than being inferred. As a result, report PDFs will generate correctly for all funds regardless of whether recipient photos are present.</p> <h2>PDF Report Pages Overflowing into Footer</h2> <h3>What was happening:</h3> <p>In certain report templates, recipient content was overflowing beyond the designated page area and spilling into the footer section. Additionally, a fund purpose section heading was appearing on reports even when no fund purpose content had been entered for that fund.</p> <h3>What was fixed:</h3> <p>Page overflow handling has been corrected to ensure recipient content stays within its designated page boundaries. The fund purpose heading is now conditionally rendered -it will no longer appear when no fund purpose has been entered for a fund.</p> <h2>Future roadmap&nbsp;</h2> <h3>Recipient Collection for Donor Relations / Stewardship Professionals&nbsp;(available in late 2026)&nbsp;</h3> <p>We are currently developing the ability to collect multiple impacts per recipient and new flows to better manage recipient collection with statuses and approval views with editor and preview enhancements. We are building a foundation that will support future enhancements in 2027 to collect impact directly from recipients. <a href="https://app.storylane.io/share/n1f1hjjwlsht" rel="nofollow noopener noreferrer" target="_blank">Click here to see a demo!</a></p>…

<p>We are committed to ensuring your data flows seamlessly and accurately between your favorite tools. This month, our engineering team focused on optimizing the Blackbaud RE NXT integration to give you better control over your constituent data.</p> <hr> <h3>Enhanced Sync Logic for Blackbaud RE NXT</h3> <p>We have resolved a defect within the nightly integration process. Previously, the sync was pulling a broader set of data than intended, which could lead to cluttered constituent lists within Impact.</p> <p>What has changed? The nightly integration has been refined to be more selective. From now on:</p> <ul> <li><p>Targeted Syncing: Only constituents that have been specifically tagged in RE NXT will be included in the nightly sync to Impact.</p></li> <li><p>Cleaner Data: This update ensures that your Impact environment remains streamlined, reflecting only the specific donor segments you’ve designated for integration.</p></li> </ul> <h3>Why this matters</h3> <p>This fix provides a higher level of precision for your outreach efforts. By ensuring that only tagged constituents migrate over, you can trust that your Impact dashboard is populated with the exact records you need for your active campaigns and reporting.</p> <hr> <blockquote> <p>Note: No action is required on your part. These changes have been automatically applied to all accounts utilizing the Blackbaud RE NXT integration.</p> </blockquote>…

<p>Based on customer feedback, we have made an improvement in accessibility within Impact.&nbsp;This improvement brings updated “clear” controls for DataTable search in key areas, adding an "x" button in the search box. This update is shown below:</p> <p style="text-align:left"><img alt="" class="fb-img" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/a0807312-d976-4c83-870c-811b816c3b23/h/547.png" style="" width="1726"></p>…

<h4>SECURITY</h4> <ul> <li><p><strong>Clickjacking protection added:</strong>&nbsp;Impact now includes an HTTP security header that prevents the application from being embedded in unauthorized external sites — protecting logged-in users from a class of UI-based attacks.</p></li> <li><p><strong>File path vulnerabilities fixed:</strong>&nbsp;Multiple instances where user input could be used to access unintended files have been identified and resolved across the application.</p></li> <li><p><strong>Performance vulnerability patched:</strong>&nbsp;Problematic code patterns that could allow a specially crafted input to freeze the application have been rewritten, protecting against denial-of-service scenarios.</p></li> <li><p><strong>URL validation hardened:</strong>&nbsp;URL trust checks have been rewritten to properly parse and inspect web addresses, closing potential paths for redirect or request-forgery attacks.</p></li> </ul> <h4>ACCESSIBILITY</h4> <ul> <li><p><strong>Keyboard-accessible search clear buttons:</strong>&nbsp;Search fields in Balance and Impact data grids now include a clear button that can be reached and used without a mouse.</p></li> <li><p><strong>Recipient List page header fixed:</strong>&nbsp;A layout issue with the header on the Impact Template Recipient List page has been corrected.</p></li> </ul> <h4>DATA IMPORTS</h4> <ul> <li><p><strong>Large ZIP file support for recipient photo imports:</strong>&nbsp;Bulk photo imports now handle large ZIP files without errors.</p></li> <li><p><strong>Photo file size validation:</strong>&nbsp;Photo imports now check file sizes before processing and surface a clear error message if a file exceeds configured limits.</p></li> <li><p><strong>Class Year validation updated on Q&amp;A imports:</strong>&nbsp;Class Year is now a warning (not a hard error) on Q&amp;A page bulk imports, consistent with other import types.</p></li> </ul> <h4>BUG FIXES</h4> <ul> <li><p><strong>Duplicate import error fixed:</strong>&nbsp;Re-importing a recipient/fund/reporting period combination that already exists across multiple reporting periods no longer causes an error.</p></li> <li><p><strong>Fund Value now shows the correct value:</strong>&nbsp;The Funds view was incorrectly showing the contributed value instead of the actual fund value. This has been corrected.</p></li> <li><p><strong>"Null" constituent name display fixed:</strong>&nbsp;Constituent names were appearing as "null" in some cases. A fix has been applied.</p></li> <li><p><strong>Raiser's Edge NXT sync issue resolved:</strong>&nbsp;An issue preventing nightly syncs with the RE NXT integration has been resolved. Further improvements are in progress.</p></li> <li><p><strong>Flex page white space fixed:&nbsp;</strong>Unexpected white space on Flex pages has been corrected. If your template is affected, contact Support to apply the fix.</p></li> </ul>…

<h4>NEW FEATURES &amp; IMPROVEMENTS</h4> <ul> <li><p><strong>Active Reporting Period Banner:</strong>&nbsp;A banner now appears at the top of the application showing the currently active reporting period. Administrators also see a direct link to the Reporting Periods management page for quick access.</p></li> <li><p><strong>Renamed "Recipient Reporting Periods":</strong> The label previously called "Reporting Periods" has been updated to "Recipient Reporting Periods" throughout the application for greater clarity.</p></li> <li><p><strong>Class Year no longer required on Horizontal Thank You &amp; Recipient List imports:</strong>&nbsp;Class Year validation is now a warning instead of a hard error on bulk imports, reducing friction for customers with non-standard class year data.</p></li> </ul> <h4>BUG FIXES</h4> <ul> <li><p><strong>Recipient Type is now locked when expected:</strong>&nbsp;For recipients attached to a Recipient List, the Recipient Type field is now correctly disabled, preventing unintended changes.</p></li> <li><strong>Bulk import now validates recipient type:</strong>&nbsp;If the import type doesn't match a recipient's type, the import will surface a clear error and stop, preventing silent data issues.</li> </ul>…

<h4>IMPROVEMENTS</h4> <ul> <li><p><strong>Template image size validation:</strong>&nbsp;Impact now prevents oversized images from being uploaded to report templates. This improves template performance and reduces errors during the proofing process.</p></li> </ul> <h4>INFRASTRUCTURE</h4> <ul> <li><strong>Database migration complete:</strong> All Impact customer databases were successfully moved to a new, higher-performance server environment with no interruption to service.</li> </ul>…

<h4>NEW FEATURES</h4> <ul> <li><p><strong>Proof confirmation dialog:</strong>&nbsp;When proofing a report template that has already been proofed, you'll now see a confirmation prompt before proceeding. This prevents accidental overwrites of existing proofs.</p></li> </ul> <h4>ACCESSIBILITY</h4> <ul> <li><p><strong>Data tables are more screen reader friendly:</strong>&nbsp;All data grids now use proper HTML table structure, making it easier for assistive technology to read column and row relationships.</p></li> <li><p><strong>Improved modal focus behavior:</strong>&nbsp;When a dialog is closed, keyboard focus now correctly returns to the element that opened it — a common need for keyboard and screen reader users.</p></li> <li><p><strong>Status messages announced automatically:</strong>&nbsp;Success, warning, and error alerts are now announced by screen readers as they appear, so users relying on assistive technology receive real-time feedback.</p></li> <li><p><strong>Dialogs properly identified by screen readers:</strong> Modal dialogs now include the correct accessibility attributes, so screen readers can identify their boundaries, titles, and purpose.</p></li> </ul>…

<h4>SECURITY</h4> <ul> <li><p><strong>Improved application security:</strong>&nbsp;A full vulnerability scan was completed and software packages across Impact were updated. Known security issues have been addressed. Image uploads are now restricted to authorized roles only, resolving a finding from a recent security audit.</p></li> </ul> <h4>ACCESSIBILITY</h4> <ul> <li><p><strong>Screen reader improvements:&nbsp;</strong>All form fields now have properly labeled inputs, making it easier for screen reader users to navigate Impact.</p></li> <li><p><strong>Links are easier to identify:</strong>&nbsp;Inline links throughout the application now include underlines, helping users with color blindness distinguish them from surrounding text.</p></li> <li><strong>Full keyboard navigation:</strong>&nbsp;All scrollable regions and interactive table controls can now be accessed and operated using only the keyboard.</li> </ul>…