Fenergo will be deprecating a set of legacy REST integration surfaces across TM Alerts and Financial Crime Reporting. All deprecated endpoints have direct GraphQL equivalents available via the Supergraph and the FCR Supergraph subgraph.

What Does This Mean for You as a Fenergo User?​

Once these changes are in effect, the following REST endpoints and standalone GraphQL APIs will no longer be available:

TM Alerts​

• Standalone TM Alerts GraphQL API (/tmalerts/graphql) — superseded by the Supergraph.
• Alert assessments — assess transactions, complete assessment.
• Comments & activity trail — comments and file attachments.
• File upload — create alert file upload URL.
• Alert reads — get alert by ID, journey, or entity.
• Nested reads — transactions, comments, and alerts-by-transaction.

Financial Crime Reporting​

• Standalone FCR GraphQL API — superseded by the FCR Supergraph subgraph.

Why Are We Making This Change?​

These legacy REST surfaces have been superseded by GraphQL equivalents that offer greater flexibility, consistency, and performance. Consolidating integrations onto the Supergraph reduces surface area, simplifies maintenance, and ensures all clients benefit from a single, unified API layer.

What Action Do You Need to Take?​

If your integration relies on any of the endpoints listed above, you should migrate to the equivalent GraphQL operations via the Supergraph before the change target date. Your Fenergo Client Partner can provide guidance on the available GraphQL alternatives.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Fenergo will be removing the Alert Metadata Configuration section within the Reference Data domain. Due to low usage, this section is no longer required and will be retired at the end of May 2026.

What Does This Mean for You as a Fenergo User?​

Once this change is in effect, the Alert Metadata Configuration section will no longer be available within the Reference Data domain.

Why Are We Making This Change?​

This section has seen low usage across the platform and is no longer considered necessary. Removing it allows Fenergo to streamline the Reference Data domain and reduce unnecessary complexity for users.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Fenergo will be removing the Alerted Transaction tab in the Alerts Dashboard. An extension of the information available here will be available in Advanced reporting so this tab is no longer useful. Furthermore, removing this information from the Alerts page will enhance the performance of the page. All transaction are available from the Entity profile transaction tab.

What Does This Mean for You as a Fenergo User?​

Once this change is in effect, the Alerted Transactions tab will no longer be available in the Alerts dashboard. Alerted transaction information is available in Advanced Reporting.

Why Are We Making This Change?​

There are multiple reasons for this change, firstly the need for this tab has been mitigated by adding Alerted Transactions to Advanced Reporting, secondly removing this information will have a positive impact on the performance of the Alert Dashboard.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Planned Target Date: June 4th, 2026

Fenergo will be introducing limits on the number of journeys that can be in progress simultaneously for a single entity. This change is designed to protect platform performance and prevent unintended automation from generating excessive workload.

What Does This Mean for You as a Fenergo User?​

Once this change is in effect, the following limits will apply per entity:

• A maximum of 1,000 total in-progress journeys per entity.
• A maximum of 500 in-progress journeys of the same journey type per entity.

If either limit is reached, the system will reject new journey creation requests with a 400 Bad Request API response. A validation error will be returned within Fenergo indicating whether the total limit or the per-journey-type limit has been exceeded.

If you encounter one of these errors, review and resolve existing in-progress journeys for the affected entity before attempting to create new ones.

Why Are We Making This Change?​

This change has been introduced to maintain system stability and mitigate the risk of uncontrolled journey creation caused by configuration or process issues. By capping the number of in-progress journeys per entity, Fenergo can ensure consistent platform performance across all clients and reduce the impact of accidental or automated over-creation of journeys.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

The recently released Document Metadata Policy Trigger Condition feature has been removed from the platform. Following release, we identified an issue that affects environments with high volumes of documents, and in order to protect the platform stability for all clients we have made the decision to remove this feature at this time while we work on a more robust solution. If you have already begun configuring this feature, please reach out to your Fenergo representitive who will be happy to advise on alternative approaches in the interim. We apologise for any disruption this may cause.

Change Target Date: End of April, 2026

Fenergo will be introducing an update to the permissions required to interact with and complete the Significance Engine Results and Significance Agent Results Task Types. This communication serves as notice before the change is rolled out to production environments.

The updated implementation will introduce a new dedicated permission, Significance Task Edit, which will be required to override Significance outcomes and complete the task.

What Does This Mean for You as a Fenergo User?​

Once this change is enabled, users will require the Significance Task Edit permission in order to interact with and complete the Significance tasks.

For any tenants already using Significance Task Types, users who currently have Significance Rule Access will continue to be able to view, edit, and complete the task. This is to ensure continuity of access during the transition period.

Why Are We Making This Change?​

Following the recent separation of configuration and operational permissions, we identified the need to introduce a dedicated task permission, allowing configurators to better control which users can overwrite outcomes within the task, without granting access to underlying configuration.

This approach mirrors what we already do in other areas of the application and maintains the separation between configurational and operational users while providing greater flexibility and control over task interaction.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Beginning August 31, 2026, the Entity Profile Page V1 will no longer be available. Users will access and manage entity information exclusively through the Entity Profile Page V2 interface. This means the option to switch to or navigate to the Entity Profile Page V1 will be removed and Entity Profile Page V2 will become the only supported experience on this screen across all tenants.

What Does This Mean for You as a Fenergo User?​

From August 31st, 2026, users will no longer be able to navigate to the Entity Profile Page V1. All entity-related activities on this screen will be performed exclusively within the Entity Profile Page V2 interface. There are no permission changes associated with this update, and no action is required in advance of the removal date.

Why Are We Making This Change?​

Entity Profile Page V2 represents the strategic direction of the platform and provides a more modern and consistent user experience. Retiring the legacy Entity Profile Page V1 removes duplication in the interface and allows ongoing enhancements to be focused on a single, unified experience for the user.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Planned Target Date: End of February, 2026

Fenergo will be making changes to the user interface of the eSignature task. These changes will enhance the user experience of the task.

What Does This Mean for You as a Fenergo User?​

Once this change is enabled, users will see the new and improved user interface of the eSignature task. The functionality of the task will remain the same.

The new and improved UI of the eSig task includes:

• Adjustment of the margin around the eSignature Document Requirement grid.
• Wrapping of the 'status chip'.
• New 'Drag or Click to Upload' component.

The new and improved UI of the Send Documents modal in the eSig task includes:

• Highlighting the selected recipients.
• Adjusments to font, size and style of text.
• Wrapping of the 'signature type' chip.
• Recipients will appear in a list rather than a grid.

Why Are We Making This Change?​

To ensure a consistent and quality user experience, we are aligning the user interface of the eSignature task with designs created and approved by our user experience team.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Change Target Date: April, 2026

Fenergo will be making a change with regards to the requisite permissions needed to access the Significance Engine Results or Significance Agent Results Task Types. This communication serves as notice before the change is rolled out to production environments.

The current implementation ties the access and interactivity of the task with the same permissions required to configure the Significance Rules. This means that the operational users can also see the configuration.

The new implementation will remove any dependency on Significance Rule Access or Significance Rule Edit for task-level access and interactivity.

What Does This Mean for You as a Fenergo User?​

Once this change is enabled, users will be no longer require the Configuration Permissions in order to interact with the Significance task.

For any tenants already using Significance Task Types, the existing permission sets will apply until April 2026.

Why Are We Making This Change?​

Based on speaking to our clients, we want to be able to provide users with the ability to use the Significance task types without having the ability to view, edit or delete the underlying configuration. This approach mirrors what we already do in other areas of the application. For example, users may interact with policy via a data capture task but may not view the underlying policy configuration. By separating these permissions, we allow for greater separation between configurational and operational users.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Change Target Date: January, 2026

Fenergo will be making a change to implementation of Related Party Access Layer Inheritance. This communication serves as notice before the change is rolled out to production environments.

The current implementation allows for separate inheritance changes to be created per journey and restricts access to related party entities by extending the access layers of the root entity to all levels of its association hierarchy within the journey.

The new implementation will evaluate and pass down access layers using the overall association hierarchy instead of using the journey context. There is also a change where only Client entities or Offboarded Client entities will be the root for inheritance.

What Does This Mean for You as a Fenergo User?​

Once this change is enabled, any tenant that enables Related Party Access Layer Inheritance from that point on will utilise the new implementation for inheritance.

For any tenants where the current Related Party Access Layer Inheritance implementation is in use, once agreed, a migration will be performed to transition the inheritance to the new format.

Why Are We Making This Change?​

The existing implementation has created growing complexity which can cause overload in tasks that process hierarchies due to the inheritance processing. The new implementation introduces a much simpler inheritance logic that is easier to understand and reduces the amount of processing required. This lower processing complexity will mean faster evaluation for large hierarchies, and the simpler inheritance logic will be easier to maintain and scale.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Beginning in January 2026, Data Groups will be managed in a new, dedicated Data Groups section within the Policy domain of the Management menu. This means Data Groups will no longer be accessed from within the Policy configuration screen, but instead from their own centralised management area.

What Does This Mean for You as a Fenergo User?​

You will now navigate to Management → Policy → Data Groups to view, create, and maintain Data Groups. All existing Data Groups will appear in a familiar grid format, exactly as before. No functional changes are being introduced. There are no permission changes associated with this update.

In short: this is a navigation and usability improvement, not a feature deprecation or behavioural change.

Why Are We Making This Change?​

This enhancement provides a centralised, dedicated management space for Data Groups, improving clarity, usability, and overall configuration workflow efficiency. By separating Data Groups from the broader Policy configuration screen, we ensure a cleaner structure within the Policy domain and make configuration tasks easier for Fenergo configurators to manage and maintain.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Beginning in January 2026, the JSON Edit option within Scoping Conditions will be deprecated and will no longer be available. All journey configuration must be managed exclusively through the standard configuration user interface to ensure consistent, stable, and fully validated configurations across all environments.

What Does This Mean for You as a Fenergo User?​

You will no longer be able to manually edit journeys using the JSON edit feature. All journey configurations must be created and maintained through the UI-based editor.

Why Are We Making This Change?​

This change ensures that UI-based guardrails are applied to all configurations, keeping them aligned with platform standards. These guardrails reduce the risk of configuration errors, prevent broken journeys caused by incorrect tasks order, and improve overall system maintainability and user experience.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Change Target Date: End of week starting September 29th, 2025

Both Bank Account and Investment Account tasks will include the ability to capture or view the applicable access layers directly within their respective tasks.

What Does This Mean for You as a Fenergo User?​

• This new capability will apply to Bank and Investment Account tasks.

• There will be a change to the task interface.

• If Dynamic Assignment Configuration is enabled, the access layers will be driven on Dynamic Assignment Configuration.

• End of September:

  • The new functionality for Bank Accounts and Investment Accounts will be enabled on all production environments that have Investment Accounts enabled.

Why Are We Making This Change?​

This change is designed to provide greater clarity and control over account access.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Change Release Date: September 15th, 2025

Fenergo will be making an update to the interaction and display of Data Groups within the system. This communication serves as notice before the change is rolled out to production environments. This change is part of our ongoing efforts to streamline the user experience within the system.

What Does This Mean for You as a Fenergo User?​

• August 2025:

  • The change has been rolled out to lower environments for users to interact with and become familiar with the new format.

• September 15th, 2025:

  • The new look and feel for Data Groups will be enabled on all production environments.

Why Are We Making This Change?​

As the system continues to evolve, new display elements are being introduced. One of these was the introduction of a new table format, and in order to provide continuity and a cohesive user experience, we are rolling out this new table format within Data Groups. All tasks that utilise Data Groups will reflect this change once enabled.

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.

Fenergo is officially beginning the deprecation process for the Legacy Dashboards, including the My Journeys Dashboard, in favour of the Advanced Dashboards, which were launched earlier this year. This communication serves as a 6-month notice before the complete removal of the Legacy Dashboards UI and associated APIs. This change is part of our ongoing efforts to deliver a more modern, flexible, and user-friendly reporting experience.

What Does This Mean for You as a Fenergo User?​

• March 27th, 2026:
  • The Legacy Dashboards UI, including the My Journeys Dashboard, will be fully removed from the Fenergo platform.
  • Users with access to the Advanced Dashboards will be automatically redirected to the Journeys view within Advanced Dashboards upon login. If a user does not have Advanced Dashboard permissions configured, they will instead be redirected to the My Profile screen. Alternatively, the default landing page can be selected for a Team in the Security Configuration page ahead of this change if this is preferred.
  • The following APIs will also be permanently retired:
    • Dashboards Command API
    • Dashboards Query API

We strongly recommend all users and integrators transition to the Advanced Dashboards and update any dependent API usage well in advance of this removal date to ensure continuity of service.

Why Are We Making This Change?​

The Advanced Dashboards provide a significantly improved experience with more customisation, performance, and user-specific features. Highlights include:

• Dedicated Tasks Dashboard: Clearer task management and visibility.
• Saved Filters per User: Personalised filtering saved between sessions.
• Custom View Configuration: Dashboards can now be tailored by individual users, removing tenant-wide restrictions.
• Improved Navigation: 'Journeys' and 'Tasks' dashboards have been elevated to the main left-hand navigation for quicker access.
• Expanded Indexing Support: Tasks and Journeys Dashboard Indexes now support up to 150 fields, eliminating the need to mark fields as indexable in Policy.
• Pagination: No longer limited by assigned task count - full pagination support ensures better scalability.

For full details on functionality and setup, refer to the documentation: Advanced Dashboards

Need Help or Have Questions?​

If you have any questions or require support with this transition, please contact your Fenergo Client Partner, who will be happy to assist you.