Product Updates

Allow the suppression of the verification email when a portal user is added in Fen X via the quick link task or via portal user management User Guide Reference: Configuring the Fenergo Portal > Suppressing Automated Verification Emails in Fenergo Portal

When calling the create batch endpoint, if the new batch is in the same journey as another existing batch with resolved matches, the match resolution of the repeated matches will be reused. More details can be found on the Reopening Screening Processes and Screening Resolution Reuse section of the Screening User Guide. Note that this new feature does not apply for WCO matches as the described behavior is inherently supported natively. Affected Endpoints​ POST /api/batch

Enhancement to DocuSign integration to allow support for Advanced Electronic Signature (AES) and Qualified Electronic Signature (QES). This feature also includes a revamped recipient-selection UI and option to automatically retrieve certificate of completion. User Guide Reference: eSignature User Guide

V1 of Logging Centre APIs which are a part of Integration Hub Create Query Get Query Results Search Logs by Entity & Journey Opt In & Out of Logging Centre

Added a new boolean field called CommentsMandatory to the Screening Configuration, set to true by default. Added a new endpoint called PatchConfiguration to the Screening Command API, which enables updating the value of the new CommentsMandatory field. Note that PatchConfiguration currently supports updating only this one field. To update other fields within a Screening Configuration, please refer to the other endpoints in this API. New endpoint: PATCH /api/configuration Affected Endpoints​ POST /api/configuration GET /api/configuration GET /api/configuration/lite

New API endpoints to expose received Events in Integration Hub GET /v1/events/\{eventId\} - Get an ingress event with related entities POST /v1/events-by-filter - Get events within a date range GET /v1/events/\{eventId\}/messageUrl - Get original or processed event payload

Changed the endpoint GetRequirementSetVersionLightById to include IdvName and UBOThreshold properties as part of requirements in the response Affected Endpoints​ GET /policyquery/api/requirement-set/{setId:guid}/version/{versionNumber:int}/light

Added a new property called DocumentTaskVersion to TaskDto for configuring the document version in Combined Policy Task. DocumentTaskVersion - determines the document task version based on the captured version number. Affected Endpoints​ POST /journeycommand/api/journey-schema POST /journeycommand/api/journey-schema/{journeySchemaId} PUT /journeycommand/api/journey-schema/{journeySchemaId}/version/{versionNumber} GET /journeyquery/api/journey-schema/{journeySchemaId} GET /journeyquery/api/journey-schema/{journeySchemaId}/version/{versionNumber}

Georgina from the Fenergo product team introduces the ability to include Related Party entity data in the Conflict Resolution task. This feature provides users with visibility of entity data changes made and published in parallel journeys that conflict with changes made for related parties within the current journey. Users can decide to accept the latest data or retain the current journey’s data. For more details, please refer to the user guide.

Related Party Entity Data can now be included in the Conflict Resolution task. This provides users with visibility of data changes that are made and published in parallel journeys that conflict with changes made in the current journey, and allows the user to accept the latest data or retain the current journey's data. User Guide Reference: Conflict Resolution and Proposed Changes User Guide->Related Parties Conflicts

Calculated Time Periods can be used in Policy and Product Policy. A Calculated Time Period is a date subtracted from another date, this is different to a calculated date field, as the output is a time period. For example 25d. User Guide Reference: Calculated Fields User Guide

Description: This feature extends our current bulk upload capabilities support the bulk upload of products to an entity. Clients will be able to add new products and edit existing products via bulk upload. This feature also strengthens the validation logic for all entity types in bulk file to include mandatory data requirements. User Guide Reference: Bulk Upload User Guide > Bulk Uploads Overview > Important Notes

Users can be suspended, this will prevent them from logging in until they are reactivated. User Guide Reference: User Administration User Guide

A new option has been introduced in the Related Parties task in Journey Builder that will allow the restriction of entity group associations to only be permitted to members of the entity group. Once enabled, the search will return results from verified members of the entity group in journey. User Guide Reference: Related Party Management->Related Party Management Configuration User Guide

Takura introduces Dun and Bradstreet as a new out-of-the-box external data provider in Fenergo. This update allows users to search and enrich client records efficiently. The walkthrough demonstrates configuration and usage, highlighting how Dun and Bradstreet integrates seamlessly with existing functionalities. Users can now view and manage collateral information directly within the deals task. For more details, refer to the user guide.

Josh from the Fenergo product team introduces a feature that displays collateral in the deal main entity view, enhancing credit decision-making and user experience by consolidating essential information. He demonstrates the configuration, showing how users can customize the view and columns. This feature prevents the need to navigate between tasks, streamlining the process. For more details, refer to the user guide.

Added a query endpoint returning entity drafts for a list of provided Entity Ids and Journey Id: POST /entitydataquery/api/v2/get-entity-drafts-light

Josh from the Fenergo product team introduces a new feature that prepopulates financial items in the financial analysis task, reducing manual data entry. This feature ensures data quality while enhancing efficiency. Josh demonstrates the configuration and functionality, showing how predefined financial items appear automatically, maintaining existing validation standards. For more details, refer to the user guide.

Address Country SecondaryIdentifier now only applies for Individual entities in WCO, as WCO does not support Address Country for Company Affected Endpoints​ POST /api/batch

Aligning with recent enhancements to Policy, Product 'Date' requirements can now be configured with a validation time zone. This can be used with three validations: No Past Dates, No Future Dates and Disallow Todays Date. When setting a 'Default Value' for a date requirements as 'Default to todays date', the default value will be set according to the date in that time zone (when triggered). If there is no value selected in 'Validation Time Zone', UTC will be used to determine the date in these circumstances. Note: The 'Date Range' validation in product requirements can reference relative values like 'Today', however this will continue to follow UTC for the time being. User and Configuration Guide Reference: Product User Guide - Product Enablement User Guide

The extension of Teams Limits to 80 Teams; the extension of Access Layers Limits to 900 Access Layers & the extension of Dynamic Access Layer Rule Limits to 380 Rules. User Guide Reference: User Administration User Guide

Aligning with recent enhancements to Policy, 'Date' requirements in Deals can now be configured with a validation time zone. This can be used with three validations: No Past Dates, No Future Dates and Disallow Todays Date. When setting a 'Default Value' for a date requirements as 'Default to todays date', the default value will be set according to the date in that time zone (when applied). If there is no value selected in 'Validation Time Zone', UTC will be used to determine the date in these circumstances. Note: The 'Date Range' validation in deal requirements can reference relative values like 'Today', however this will continue to follow UTC for the time being. User and Configuration Guide Reference: Deals User Guide refers to: Policy - Basic Policy User Guide - Data Validation

Portal users will be able to add one or many products during a journey and provide details about the type of product and any additional data requirements. User Guide Reference: Portal Functional User Guide > Manage Products

All API endpoints will now return Problem Details with HTTP Status Code 400 (Bad Request) if EventNotifications service is not enabled for tenant making API call.

The Integration Hub highlights all FenX integration services in one location for easy access and provides screens for technical users to troubleshoot any issues related to these integrations in their tenant. Includes initial support for Event Ingress and Event Notifications (Webhooks). User Guide Reference: Integration Hub User Guide