Release Notes: June 3, 2026
This week’s release includes fixes across All Modules, Faculty Search (FS), Review, Promotion & Tenure (RPT), and Faculty Activity Reporting (FAR). Across all modules, we resolved issues that prevented updates to the Organization field in Dossier Basic Information from persisting and stopped the cookie consent banner from reappearing after logout. In FS, we fixed issues that prevented Letters of Recommendation created within applications from being properly attached to submitted materials and corrected evaluator names in application reports when Blind Review was enabled for Canadian‑hosted tenants. In RPT, we resolved issues where FAR vitas were missing on cases created from templates, workflow actions occurred outside assigned permissions, vita generation dates were inconsistent, character limits in rich text editors caused errors, cases created from archived templates were unable to close, and Staging users encountered errors when editing templates. In FAR, we resolved issues affecting access to attachments from exported Legacy Vitas.
All Modules
- Fixed: We resolved an issue where users were unable to update the Organization field in their Dossier Basic Information settings. Previously, after entering a new organization and saving, users received a confirmation that their personal information had saved, but the Organization field reverted to its prior value on refresh while all other fields persisted correctly. Users can now successfully update their Organization in Basic Information and have the change persist as expected, restoring accurate profile management for users who change institutions or affiliations.
- Fixed: We resolved an issue where the cookie consent banner (OneTrust) reappeared after every logout. The application's logout flow was incorrectly clearing OneTrust consent cookies and local storage, which are browser-level GDPR/CCPA preferences tied to the device rather than the user session. Users who had previously accepted cookie consent will no longer be prompted with the banner again after logging out or exiting an emulated session.
Coming Soon
- Email Links Update (The email link security upgrade is now scheduled for Jun 17, 2026): We are updating our outbound email configuration to remove email click-tracking. Some users at institutions with strict security or web filtering tools were experiencing certificate warnings or blocked links when clicking emails from Interfolio, because the click-tracking domain did not support HTTPS in all configurations. Post this change emails from Interfolio will contain only direct HTTPS links. This resolves certificate mismatch errors for affected users and has no impact on email delivery, bounce notifications, or other email functionality.
-
SFTP Security Policy Upgrade (Effective June 18, 2026): The SFTP security policy upgrade is now scheduled for June 18, 2026. This upgrade moves SFTP servers to AWS's TransferSecurityPolicy-2024-01, strengthening supported encryption and SSH security standards.
Nothing changes for your existing setup:- SFTP hostnames, usernames, passwords, and SSH keys remain the same
- Folder paths and file processing behavior are unaffected
Action required - Verify your SFTP client version:
Before June 18, confirm your client meets the minimum supported version. Upgrading to the latest available release is strongly recommended.
| Client | Minimum Version | Recommended Version |
|---|---|---|
| FileZilla | 3.6.0+ | Latest (3.66+) |
| WinSCP | 6.0+ | Latest (6.3+) |
| OpenSSH | 8.2+ | Latest (9.6+) |
| Cyperduck | 8.0+ | Latest (9.0+) |
| Transmit | 5.7+ | Latest |
| PuTTY/PSCP | 0.76+ | Latest (0.80+) |
| MobaXterm | 21.0+ | Latest |
| Bitvise | 9.0+ | Latest |
-
API - Improved REST error response codes: We are updating REST API error responses across the FIS to return more accurate HTTP status codes. Today, some validation issues and server-side failures appear as 400 Bad Request, which makes it harder for API clients to know whether a request should be corrected, retried, or escalated.
After this update, successful API responses are unchanged, but REST error responses will be more specific:
| Scenario | Before | After |
|---|---|---|
| Malformed request | 400 | 400 |
| Validation or input issue | 400 | 422 |
| Duplicate/conflict | 400 | 409 |
| Downstream/database/server issue | 400 | 500, 502, 503, or 504 |
Suggested Action:
- Clients using REST endpoints should review any custom integration logic that:
- treats all 400 responses as validation errors
- retries requests after receiving 400
- expects validation failures to always return 400
- parses raw exception text from error messages
- displays error text directly to end users
- Recommended handling after the change:
- 400: check the request format
- 422: correct submitted data and resubmit
- 409: handle as a duplicate/conflict
- 500/502/503/504: treat as a server or downstream-service issue; retry only where appropriate
If your organization has a custom REST integration, please review any logic that depends on 400 responses, retries 400 responses, or parses error-message text.
Faculty Search
- Fixed: We resolved an issue in Faculty Search where a Letter of Recommendation request created from within a Faculty Search application was not automatically added to the applicant's submitted materials. When an applicant requested a confidential letter of recommendation while editing their submission, the request failed to attach to the delivery, leaving it absent from the submitted documents for both the applicant and application reviewers. The letter of recommendation request will now be correctly linked to the application upon creation.
- Fixed: We resolved an issue in Faculty Search where application reports with the "Average Rating by Evaluator" or "Rating by Criteria and Evaluator" columns displayed "Unaffiliated Evaluator" instead of the reviewer's name when Blind Review was enabled on a position. This issue affected clients who are currently on our Canadian server. Admins running these reports will now see evaluator names alongside their ratings as expected.
Review, Promotion & Tenure
- Fixed: We fixed an issue where FAR vitas were not visible on cases created from templates, even when included in the template’s candidate requirements. This was caused by vitas not fully loading during case creation. FAR vitas included in a template’s candidate requirements will now reliably appear on the resulting case.
- Fixed: We fixed an issue where users could take action outside of their assigned workflow permissions, resulting in incorrect case access and progression. Workflow transitions could occur out of sequence, activity logs did not always reflect the correct order of actions, and in some cases the final case step did not align with the last recorded action. Users can now only take action within workflow steps where they have explicit permissions. Workflow transitions follow the configured sequence, and activity logs accurately reflect the true order of actions, with the final case step matching the last recorded workflow action.
- Fixed: We fixed an issue where the Vita generation date displayed in the case detail section did not match the date shown in Edit Vita notifications. Vita generation dates are now consistent across the case details and Edit Vita notifications, ensuring accurate and aligned information for administrators.
- Fixed: We fixed a follow up issue from the last release with character limit errors in RPT text boxes. Text boxes should be working as expected again with a 12k character limit.
- Fixed: We resolved an issue with allowing cases to be closed that were created from a now archived template.
- Fixed: We fixed an issue in Staging where users were encountering an error when trying to edit a template. The edit template experience is behaving as expected again.
Coming Soon
RPT New Case List: To match the Templates page, RPT Case List page is being redesigned for better performance and usability, with searchable and sortable columns, filters, and layout improvements. We will schedule Case List in a release after Templates List and update stakeholders here accordingly.
We are anticipating offering early access to interested clients in early June. If you’d like to turn on the New Case List at your institution before the global release, place contact your Customer Success Manager or Account Manager.
Faculty Activity Reporting
- Enhancement: We are improving the the experience, consistency, and safety of accessing attachments in exported legacy vitas. No matter what format a legacy vita is exported in, whether as a print version, Word document, PDF, or Web Link, attachment links will now work the same way across the board. If you already have access to your institution, clicking an attachment link in any exported legacy vita will allow you to download the attachment. If you’re not signed in, you’ll simply be prompted to log in first. This ensures that sensitive files are only accessible to the right people, while also making the experience of accessing these attachments more consistent.