Resolved an issue where date-only fields in Data Central Listings incorrectly displayed a default time of 12:00:00 AM. The system now accurately reflects imported date values without appending an unnecessary timestamp, ensuring the Listing matches the raw data as expected.

Update: Additionally, removed the default time display (12:00:00 AM) from date fields in the Subjects panel and standardized the date format in the Queries panel to "dd mmm yyyy" (e.g., 12 SEP 2025) for Candidate Date, Open Date, Answered Date, and Closed Date. Previously, this format applied only to Open and Candidate.

Resolved an issue in Data Central and the Issues module where user profile settings for displaying Variable Labels were not applied to the Configured Fields (either via Orchestrator or Data Central) in the Issue Details panel. Although field labels were correctly shown when creating an issue, they were not displayed when viewing issue details (it always displayed field name). The system now honors the user’s display preference for field labels in the Issue Details panel. This fix does not apply to the Related Details column which will continue to only display the field name.

Certain queries opened from elluminate to Rave could not be answered or closed due to a "datapoint context value does not match current value" error. The Open Query process has been updated to ensure the correct FormRepeatKey is used, aligning query records accurately with Rave's audit trail and preventing context mismatch errors.

Resolved an issue where users incorrectly encountered an error stating that an eIQ Review model was not enabled for the study when configuring a Review Plan in Data Central Configuration. This occurred when multiple Review Objectives referenced different eIQ models, causing their review material statuses to interfere with each other.

This update includes several enhancements across RACT and RBQM to improve clarity, usability, and monitoring capabilities:

• RBQM Issues Card: A new RBQM Issues card has been added to the Risk Management page, providing at-a-glance visibility into Issues metrics.

• Abbreviations for KRIs and QTLs: Abbreviations can now be added to global KRIs and QTLs to simplify identification during configuration.

• Legend Panel in RBQM: A legend panel has been added to provide clear visual cues for users.

• Data Sources in Assessments: While conducting assessments in RACT, users can now enter data sources for KRIs and QTLs. These are also included in exports, improving transparency.

• Terminology Update: The ‘Risk ID’ in study-level RACT has been updated to ‘Risk Assessment ID’ to standardize terminology.

• Dynamic Risk Assessments: Risk statements now dynamically adapt to event, cause, and impact text.

• Refined Risk Level Scoring: Scoring logic has been refined so that higher scores indicate lower detectability, aligning with industry best practices.

• AI Risk Manager Audit Trail: Audit logging for AI Risk Manager Assistant has been updated with greater detail to improve traceability and accountability.

• Multi-Selection Support: Functional Plans, Critical Data, and Critical Processes now support multi-selection, consistent with Mitigations.

• Finalize Button Update: The ‘Finalize’ button in RACT is now labeled ‘Review and Finalize’ to better reflect its intended use.

We addressed an issue where some rules appeared with a “Running failed to execute SQL” despite the preview showing successfully, particularly during first-time or large runs. The status logic has been corrected so progress is reported accurately.

Resolved an issue where bulk editing Protocol Deviations without selecting a new Protocol Deviation Assessment Plan (PDAP) unintentionally removed previously assigned PDAPs. Now, when updating multiple deviations elluminate preserves existing PDAP entries unless a new one is explicitly selected.

Resolved an issue in Data Central where the x-axis label in combo charts displayed the variable name instead of the configured label when dynamic dimensions were applied to one dimension but not the other. The system now correctly displays the configured dimension label, matching the behavior seen in tooltips and ensuring visualizations are clearly labeled as expected.

Addressed an issue in Data Central Visualizations where using “Select All” in a Dynamic Filter only selected values available at the time of creation. As a result, new values introduced after a data refresh were not included. This has been corrected so that “Select All” now dynamically applies to all current and future values.

Resolved an issue in Data Central listings where date fields were being formatted as d/m/yyyy instead of mm/dd/yyyy, causing the right click, Filter By Rows to incorrectly return no results.

Addressed an issue in Data Central where, in certain cases with Data Variance enabled, the Record Details panel did not display the historical values.

Resolved an issue in Data Central where the "Use Default Filters" setting did not apply to the Issues, Queries, or Record Details panels. When enabled, this setting now correctly applies the following default filters:

Issues Panel → Status = Open, In Progress, & Answered
Queries Panel → Status = Open & Answered
Related Issues → Status = Open, In Progress, & Answered
Related Queries → Status = Open & Answered

The Domain Review Configuration for Data Central has been enhanced to preserve existing review statuses on domains that have been disabled for review. Previously, any review statuses would be lost whenever a domain was disabled for review after users had marked any records for review. This presented scenarios where incidental changes to the list of domains configured for review would cause the loss of key items like Review Status, Comments, Annotations, and other record-driven features in Data Central.

This enhancement will prevent the loss of those items by retaining any existing context linked to the record, this will persist in the backend during subsequent imports of the domain that has been disabled but will not actively update the review status from those imports as though the domain were still enabled for review. This means that if or when the domain is re-enabled for review that the review statuses of the records will match when the domain was last reviewed.

SMA 24.1.2,

SMA 24.2.2

CDA 24.1.5,

CDA 24.2.3

CDA 24.1.5,

CDA 24.2.3

CDA 24.1.5,

CDA 24.2.3

CDA 24.1.5,

CDA 24.2.3

User feedback indicated a need to handle special characters in imported PDAP files and to relax restrictions related to case-sensitive fields. In response, a new system setting has been added that allows users to provide eClinical Solutions (eCS) with a predefined list of restricted special characters. Once provided, an eCS representative will configure the backend setting for the URL, enabling validation that rejects any imported, added, or edited PDAP entries containing any of the specified special characters.

Additionally, the import process has been updated to relax the case-sensitivity requirements for picklist-driven fields. Fields such as Level, Identification Method, and columns related to the importance of the PD will now accept case-insensitive values without issue. Users should no longer encounter validation failures due to minor casing differences.

User feedback provided additional insight that some sponsor organizations, due to their internal processes, require unique PD Codes for each entry in the Global and Study PDAPs. This requirement conflicts with the current PDAP structure, where the PD Code field is optional. To better support both the existing structure and this additional business need, the import process for the Global and Study PDAPs has been enhanced. Users will now see a validation message when importing a PDAP file that contains duplicate PD Codes.

Please note,  This validation does not prevent the import of duplicate codes. Instead, it provides an early warning, allowing users to review and correct the file before ingesting its contents into a configured PDAP within elluminate.

Previously, field names with spaces were not recognized due to missing brackets in the underlying SQL syntax. This update ensures Orchestrator’s compatibility with processing field names with spaces.

User feedback indicated some difficulty with the default order of columns on the Protocol Deviations Dashboard in Data Central. The feedback indicated the most valuable columns for viewing and reviewing PDs were listed too far into the dashboard and required users to frequently scroll to view the critical information. To address this, the order of the PD Dashboard has been adjusted. Columns to help identify PDs like Site, Subject, and date information have been moved up in view to help assuage these concerns.

In addition to these changes, some adjustment to column headers on the PD Dashboard have been made to better align the intent of the columns in the UI. The “Importance Classification” column has been updated to “PDAP Importance” and the “Importance” column has been updated to “Source Importance”. This should help to highlight the difference between the two where the first is the Importance of the PD from the PDAP and the latter being the original Importance mapped in from the PD’s origin system.

User feedback had indicated that some of the titles and displayed statuses on the Protocol Deviation edit modal were unclear and contributing negatively to the overall user experience. More specifically the title and label for the button to select the applied PDAP from “Select PDAP Standard” to “Select Applied PDAP Entry” to be more clear that overall standards are not being selected, but individual entries from the study PDAP.

In addition to this change, another modification was made so that users editing Protocol Deviations in “Re-Review” status will now display that status value in the status selection dropdown in the PD edit modal. The display value was previously “Select…” which had confused users as it is neither the initial status value on the PD record nor one of the statuses that could be assigned to a Deviation. To address this, “Re-Review” will now populate as the starting value when editing PDs in that status selector drop-list. Users will not be able to save a PD in this status as it is only system-assigned. To save any updates to the PD a user will have to select a non re-review status to save.

Users reported concerns about cancelled Protocol Deviation (PD) records retaining applied PDAP values. To improve the clarity and cleanliness of reviewed PD data, the editing functionality has been enhanced. This update allows users to remove any applied PDAP content from one or multiple PD records during the editing process. As a result, a clear visual distinction is maintained between cancelled PDs and other reviewed deviations.

Users were experiencing unexpected errors trying to export a very large dataset from exporter for a given study. The source of the errors was determined to be in process to generate the .zip archive created for exported data. More specifically where the size of the file generated was overflowing the limit of a configuration used for those .zip files. This handling has been adjusted to better support large file exports.

Users should still be aware that certain file formats, such as excel, have limitations on the amount of data that can be stored in a file. The given example of excel has a maximum of 1,048,576 rows per sheet but other options like CSV or text will allow full-file exports.

Users had reported issues trying to export some data from elluminate where certain fields were being truncated during the export. The source of the issue was determined to be the format of those fields during the point of import. The offending domain was initially imported as a SAS dataset which applies the format and informat attributes. When this domain was later re-imported, it was imported as a text file instead of a SAS file. Text files do not carry metadata contents and as a result were skipped when considering the format and informat attributes for the fields in the domain.

This caused a scenario where the new text file had a larger field length for some columns compared to the original SAS file imported, however, the format attribute was not reset on this import causing those fields to respect the original formatting when exported in SAS format, unexpectedly truncating the fields in the export. This import processing has been updated to always respect the context from the latest imported file, regardless of it containing metadata or not. Users should no longer experience issues exporting data that has had input file format changes.

Users were experiencing issues trying to export domains to a configured sFTP, Box, or Amazon S3 file storage system specifically in cases where the exported file name is not unique within each export. The issue was observed when users were regularly exporting these identically named files expecting to replace the prior transport stored on the storage system, instead of the expected replacement of the prior transfer a new file with the same name and a ‘-1’ was repetitiously appended to the end of the filename. For example, expecting the output file to be “Example.xlsx” users were receiving “Example-1.xlsx” and “Example-1-1.xlsx” on subsequent exports.

The source of the issue was determined to be an error occurring during the export within an intermediate step where the exported file was orphaned on an internal shared drive that is used to process exports. This cause a conflict in later exports where that shared drive expects there to only be the file actively being exported. To prevent internal conflicts the ‘-1’ was being appended to the subsequently exported files resulting in users seeing those incorrect filenames on their storage systems. This handling has been fixed to properly clean up any files that would have been left on that shared drive causing the incorrect filenames. Users should be able to regularly export files with identical names and replace the prior transfer of the file as expected.

Resolved 2 issues related to Annotation columns in Data Central:

When filtering on an Annotation column and marking records as reviewed, all records within the domain were incorrectly marked as reviewed instead of only the filtered records.

Filtering or sorting on an empty Annotation column did not function correctly and returned 0 records, even when matching records existed.

Both issues have been addressed to ensure proper filtering, sorting, and record review functionality.

Resolved an issue where the first ODM import following the creation of queries by Orchestrator caused those queries to be temporarily unavailable in the system until a subsequent import occurred. As a result, the Orchestrator was unable to take actions such as closing queries during that period. Queries now remain consistently available after creation, ensuring proper handling by the Orchestrator.

Resolved an issue in Data Central where the Pending Date in the exported Issues panel file was not properly formatted as a date field. Additionally, improved header formatting by adding appropriate spacing to the 'Pending Date' and 'Pending By' column labels.

Users were experiencing issues trying to run manual file-based import definitions. Once a file was uploaded, the import would not properly stage the file prior to the user selecting to integrate. Instead, these imports were getting stuck in processing and not updating the UI with the contents of the file staged to import. The source of this issue was determined to be a change in the underlying data needed to run imports, more specifically, these older import definitions contained additional backend metadata that was no longer needed to run an import from other efficiency changes in elluminate. When these imports were attempting to run, they were unable to obtain those now unnecessary pieces from the backend, resulting in the import not completing it’s steps to stage the data for the user to integrate. This handling has now been enhanced to account for older configured file import definitions, these imports should run as expected regardless of when the definition was configured on the URL.

Users experienced unexpected errors when running multiple simultaneous validator jobs on their data. These errors were determined to be caused by deadlocks on necessary resources in elluminate backend database to output the validation results. A deadlock is a situation in an application or computing system where multiple processes are waiting to access the same system resource to complete their execution. The handling of these resources has been enhanced to prevent unexpected overlap between validation jobs, no further deadlocks should occur when running multiple validations in a similar timeframe.

A character limit of 50 has been enforced on the Field Name in the Fields Config to ensure compatibility with export functionality. Users can now only create or edit custom fields with names up to 50 characters. This prevents errors during data export caused by longer field names.

Fields marked as Critical in Metadata are now easily identifiable within Data Central via a distinct Critical icon (octagon with exclamation inside) and dark orange font color. These visual indicators appear in listing headers, the Record Details panel, and the Visualizations Chart Designer field list. This enhancement improves visibility of critical fields, helping users focus their review on the most important fields for a more efficient and targeted data review.

When creating or reopening an issue and selecting 'Send Notification to the User,' users now have an additional option to Defer Notification. This allows users to delay notifications and send them at a more convenient time, instead of relying on the standard task schedule.

Deferred Issue Notifications can be easily managed in the Issues module using the Filter icon to apply a Quick Filter for either ‘All Deferred Issues' or 'My Deferred Issues.' Individual issues (or all issues) can then be selected, and notifications can be sent immediately using the 'Send Deferred Notifications’ (paper plane) icon.

Previously, deactivated studies were hidden from RACT pages, preventing access to their data. The RACT studies list has been updated to include inactive studies in a read-only state, while still allowing export of RACT reports.

Administration,

Data Central, Issues Module 

User feedback highlighted the risk of importing study PDAP documents into incorrect studies, potentially leading to data inconsistencies. This issue was particularly relevant when users inadvertently used study-specific PDAPs instead of the global PDAP. To prevent this, the following changes have been implemented:

The exported Study PDAP and Study PDAP templates now include the study title in the tab of the exported file.

All imported study PDAPs will be validated to ensure the tab name of the sheet containing the PDAP columns matches the study title configured in elluminate. This validation will prevent incorrect or accidental uploads.

Users previously reported they were experiencing errors trying to import ODM data from Oracle Inform EDC where particular values from the EDC system were of a greater length than allowed in some elluminate backend tables. This was addressed by updating those backend tables with codelist ID length limitations to expand and align the fields with incoming user data to prevent these issues from occurring in any current or future imports of Inform ODM Data. The original fix has been extended back to the 23.2 version to support sponsors on older versions of the platform. Users leveraging platform version 23.2 and up should no longer have these issues when importing from Inform EDC.

Users were reporting issues importing date fields from excel files where the date columns would be imported as a numeric value rather than the properly formatted date that exists in the excel file. This was determined to be caused by an issue in the excel parsing package used to ingest the data from excel files. This handling has been adjusted to prevent dates being incorrectly imported as their reformatted numeric counterpart from excel.

User feedback regarding the special character report that can be leveraged as an admin report or as part of a mapping previously only displayed the column names for any fields that had non-standard ASCII characters in any records. This has been enhanced to also add the column labels to the output, improving value to users who are unfamiliar with internal database names for EDC or other sourced data. This should now provide better visibility into the fields that come out of the special character report for all users.

A new field, InvestigatorEmail, has been added to the import process to handle the Investigators group listed in the Primary Contact field for both the StudySites and Sites forms. Additionally, the existing import fields, PrimaryContactEmail in Sites and ContactEmail in StudySites, have been renamed to PersonnelEmail.

Users found it difficult to understand the Importance Classification and any applied Importance Overrides from the Protocol Deviation Assessment Plan as displayed on the Protocol Deviations Dashboard. To address this, an ‘Importance Override’ column has been added to the PD Dashboard for side-by-side comparison, and an ‘Importance Override’ field has been added to the PD Details view for sequential display.

Users were experiencing slow performance when folders were moved to new locations in SCE, especially in the presence of large volume of folder content and many nested subfolders. To increase performance and prevent issues, the validation process for permissions and write conflicts has been optimized to avoid unnecessary processing and improve efficiency.

Resolved an issue in Data Central where, in combo charts with dynamic measures, the first measure was not being removed when unselected. Now, unselecting a measure properly updates the chart as expected.

Users were experiencing issues with imported datasets where certain columns with a name that is greater than the 50 character limit in elluminate. More specifically, these columns of illegal name length were incorrectly being assigned a maximum data length of 0 characters caused by the over-length column name. This resulted in the column being imported, but displaying as though it were blank when the input file contained data. The importer has been enhanced to better these scenarios with columns names of illegal length on import, and how the downstream data is handled in the elluminate backend and tools like Mapper, or SCE. Users should no longer experience issues with populated columns being imported as NULL or empty due to file metadata related problems like mentioned above.

elluminate Assist responses now include a clickable link that opens a draft Custom Listing for viewing the full results. Users can save this listing using the Save button in the toolbar. It will be saved as a Custom Listing within Visualizations.

The following missing email address columns have been added to the respective ODR views:

ContactEmail → StudySites
InvestigatorEmail → InvParticipation
PrimaryContactEmail → InvSiteAssoc
ProgramOwnerEmail → Program
PersonnelEmail → StudyPersons
PersonnelEmail → SitePersonAssoc
InvestigatorEmail → Org

Addressed various performance issues related to unnecessary grid refreshes in Data Central, improving overall responsiveness and efficiency.

Domain Listing: Resolved an issue where the panel attempted to refresh the columns unnecessarily, reducing redundant updates. Additionally, the loading panel now properly displays when data is loading, informing the user that we are fetching the data.
Subjects Panel: Optimized column updates to occur only on first load or when changes are detected, reducing redundant processing.
Subject Filter: Fixed an issue where timeouts were not being cleared properly, preventing multiple unnecessary operations from triggering.

After user feedback reported unnecessary duplicate columns, limited field display length for some columns, and missing options to display necessary Protocol Deviation source system information, changes to the PD Dashboard and mapping process were deemed necessary. To better support client use of the dashboard, the following changes have been made:

Removed the ‘Classification’ column, which was redundant with the ‘Importance’ column.
Extended the ‘Reported Description’ and ‘External Comments’ fields to a new length of 2000 characters.
Created a new ‘Deviation Source’ column, which displays whether the PD is imported or manually created.
Repurposed the previous ‘External Source’ column, which now allows users to map the name of an external source system, process, or personnel that generated the imported PD record.

Due to user concern regarding the amount of manual effort required to apply Protocol Deviation Assessment Plan (PDAP) entries to all programmatically generated PD records, the Protocol Deviations Dashboard refresh process has been enhanced. Specifically, four new columns were added to the SourcePDs mapping, which populates the Protocol Deviations Dashboard.

These fields and their intended uses are:

PDAPEditLock: A True / False flag field to control whether users can manually apply a PDAP entry to the PD record.
PDAPCategory: An identifier for the Standard Category PDAP value to be matched and assigned to the PD record.
PDAPDescription: An identifier for the Standard Description PDAP value to be matched and assigned to the PD record.
PDAPCode: An identifier for the PD Code PDAP value to be matched and assigned to the PD record.
Through the SourcePDs mapping, users can now populate each PDAP identifier field. If a corresponding entry exists in the Study PDAP, the contents of that PDAP entry will be automatically applied to the imported PD record. Furthermore, users can be restricted from selecting new or different PDAPs than those automatically assigned.

Users were experiencing difficulty leveraging the full value of Global and Study PDAPs within elluminate's Protocol Deviation functions because imported file validations would reject an incoming file if any of the PDAP records in the imported file matched those already configured in the PDAP.

To address this difficulty and limitation, import file validation has been updated for both Global and Study PDAPs in the elluminate platform. Specifics for each are below:

Global PDAP Imports:

Imports of PDAP files with matching PDAP entries (both in the ingested file and the configured Global PDAP) are now allowed.
Existing global PDAP entries cannot be edited via import and will be skipped.
New global PDAP entries will be created as new records from the input file.
Study PDAP Imports:

Imports of PDAP files with matching PDAP entries (both in the ingested file and the configured Study PDAP) are now allowed.
Global PDAP entries imported into the study PDAP cannot be edited at the study level and will be skipped.
Existing Study PDAP entries that are not actively applied to a PD within the study can be imported with changes.
Existing Study PDAP entries that are actively applied to a PD cannot be edited via import and will be skipped.
New Study PDAP entries will be created as new records from the input file.

Users were experiencing difficulty with the traceability and clear identification of Protocol Deviations with applied PDAPs when their Importance Classification values were overridden. Some sponsors consider this a quality event, given the situational need to override the existing PDAP standard. Therefore, improved accessibility for sponsors was required.

To address the concern, the Importance Override field has now been moved to a separate option on the Edit PD window. This allows users to view the original Importance Classification while applying an override. Furthermore, the required comment field for saving a Protocol Deviation (PD) with an Importance Override has been renamed ‘Reason for Importance Override,' and its corresponding comment type is now ‘Importance Override.' These changes provide sponsors with immediate access to the context explaining why the PD’s applied standard was overridden.

Users were experiencing difficulty with the required import configuration needed to regularly update the Protocol Deviations Dashboard in Data Central for any imported protocol deviations. This difficulty was caused by the requirement that any imports refreshing the PD Dashboard needed to be initiated within that study. This forced sponsors who import their PD source data from a consolidated, cross-study source to configure extra imports and mappings to keep the PD Dashboard up to date.

To resolve this, the backend processing that updates the PD Dashboards in Data Central has been enhanced. It now allows imports into a Global Data Store to find all required ‘SourcePDs’ mappings dependent on the imported domain. For all studies where that mapping runs successfully, the PD Dashboard will be refreshed from the single global import.

Users were reporting difficulty with the Protocol Deviation (PD) Review workflow due to unexpected re-reviews. These re-reviews were caused by the system’s data change tracking being broader than sponsors intended. Specifically, the system tracked changes in a wider range of fields within imported PDs than sponsors deemed necessary for triggering a re-review.

To address this misalignment and eliminate unnecessary re-reviews, a new URL backend configuration option was implemented. This option allows sponsors to specify the fields within the imported PD columns that should be tracked for changes, thereby aligning the system with their specific processes. Sponsors can now select one or more of the imported PD’s Category, Description, Importance, Identified Date, Start Date, or End Date to be tracked. When changes are detected in these specific fields during import, the review status is updated.

Users were experiencing issues with data cuts not materializing and displaying an error symbol indicating the data cut failed and could not be used despite there being no noted issues with the advanced filter configuration driving the data cut. This issue was determined to be a problem in the timing of when the data cut is refreshed and the subjects landing page is updated from any imports.

To resolve the issue, the handling of both of these events has been corrected to prevent conflict when loading InForm data with data cuts active. Users should no longer have problems creating data cuts on Inform studies.

Users were experiencing issues importing data from a sFTP server caused by the sFTP access library changing. These changes to the library removed the ability to automatically parse the port number for the sFTP server to be accessed forcing sFTP connections to fail and error out during any imports.

elluminate has been updated to parse out the port number where available in the sFTP host connection string to allow for the use of non-standard ports with sFTP connections. Users should now be able to user configured sFTP servers that do not use the standard sFTP server port configuration.

The UnicodeCharactersBySchema stored procedure, which can be used in mapper to generate special characters report, does not allow for specifying the fields to be processed, or fields to be excluded. This enhances the stored procedure to allow for two new optional parameters:
@IncludeFields: a comma delimited list of fields. This parameter is optional. If supplied, only the
fields specified will be processed
@ExcludeFields: a comma delimited list of fields. This parameter is optional. If supplied, the fields specified will be excluded

Usage: To use the stored procedure in Mapper, create a mapping domain, add a SQL transformation, and enter code as follow:

To retrieve all values with special characters (Ascii codes less than 32 or greater than 126) from the “src” schema:
Exec cdr.UnicodeCharactersBySchema '{SchemaPrefix}_Src'

To retrieve all values with special characters from only the LabUnit and LabName fields:
Exec cdr.UnicodeCharactersBySchema '{SchemaPrefix}_Src','Subject',@IncludeFields='LabUnit, LabName'

To retrieve all values with special characters from all fields excpet the Site and InstanceName fields:
Exec cdr.UnicodeCharactersBySchema '{SchemaPrefix}_Src','Subject',@ExcludeFields='Site, InstanceName'

This fix provides the below updates :

Email Suffix Addition in UI: Added "Email Address" to the dropdown options for Personnel and Investigators. This will help to easily differentiate between individuals, especially in cases where multiple people share the same name. For example: "Last Name, First Name (Email Address)."

Import Table Updates: The import tables now include an 'EmailAddress' field to ensure accurate linking of relevant personnel and investigators to their respective data.

Import Updates for Primary Contact: Introduced new field “ContactEmail” to handle the import of the "Primary Contact" information in the 'Study Sites' and 'Sites' forms.

Primary Contact Field Now Optional in Sites Import: The mandatory check for the Primary Contact field during data import to the Sites top-level form has been removed.

This fix provides the below updates :

Added duplicate check functionality for 'Active Components' 'Additional Components' and 'Development Partners' sub-forms in the UI, ensuring consistency with the existing import process checks.

Implemented a unique key for the 'Investigational Product Alias' sub-form based on the combination of Product Name and Country in both UI and import.

Users ran into an issue where they entered 2 overrides in Data Central Config for the same domain which caused an error rendering the domain in Data Central, Sequence contains more than one matching element, and prevented users from deleting one of the overrides in Data Central Config.

To address this issue, we implemented 3 fixes:

Users can now delete overrides when multiple exist for the same domain.

A safeguard has been added to Data Central Config that prevents users from saving multiple overrides for the same domain.

The error message in the listing in Data Central has been improved to explain exactly what the issue is and where to fix it.

Users were experiencing issues getting updated Review Metrics in Data Central following imports. This issue was found in unique configurations where the importing of data was decoupled from triggering all mappings configured for the affected studies where the mappings would later be triggered by a separate automated task. In order to support this and other configurations elluminate has been enhanced to allow review metrics to also be refreshed from triggered mappings.

Users should now be able ensure that their DC review metrics are up-to-date via either an import or from executing mappings without newly imported data assuming the mapping outputs change enough to impact existing review statuses.