In Review
128Under consideration
Enhancement Request – PostgreSQL Editor Results Section Usability
We would like to request a few usability enhancements in the PostgreSQL Editor – Results section, based on our day‑to‑day usage. Observations / Current Limitations In the query results section, the horizontal scroll bar is only visible when scrolling to the very bottom of the page. This makes it inconvenient to view wide result sets with many columns. There is no option to copy multiple selected columns or the entire result set at once, unlike standard SQL editors (e.g., pgAdmin, SQL Developer). Currently, copying data is limited and time‑consuming for analysis and sharing. Requested Enhancements We request the following improvements in upcoming releases: Always‑visible horizontal scroll bar (or a fixed scroll bar at the top of the results grid) to easily navigate wide result sets. Ability to select and copy multiple columns, multiple rows, or the entire result set in one action. Option to copy results with column headers. These enhancements would significantly improve productivity and align the PostgreSQL editor experience with commonly used SQL tools. Please let us know if any of these features are already planned, or if additional inputs are required from our side. Thanks, Srikanth Vavilala
Cloud Replicate - WHERE CLAUSE
Include the where clause to the replications_export file. Display an icon in the replications grid a where clause is configured on the replication. Provide a way to mass add a where clause to all replications, i.e. MANDANT at Source level for SAP extractions using ODBC connection.
Display both Total number of rows and number of filtered rows when a filter is applied
When no filter is applied in a grid, the total number of Rows is displayed. This is, for example, from Dataset Design. It displays there are 48 rows. After a filter is applied, the number of displayed rows is reduced, but the grid still displays the same number (48). It would be useful to display both the number of filtered rows and the number of total rows, so we can get a clear picture of how many records are affected by the filter we have applied vs the total number of rows in the list.
Client is looking for detailed information in the Rejected Mapping Email Notification in Mapping approval mail.
Client is looking for detailed information in the Rejected Mapping Email Notification as we receive for any Mapping Changes. Client is expecting a detailed message for "Rejected Build Status" - Currently we are getting this email notification as below : Client is expecting a detailed message same as what they are receiving for any mapping changes as shown below: Can you please help with this?
Release Copy - Allow for select copy actions to overwrite an existing Releases
Allow for select copy actions to overwrite an existing Releases
Personal Identifiable Information and sensitive information tagging through metadata scanning and profiling
Utilize existing open source libraries ( https://microsoft.github.io/presidio/structured/ , https://pypi.org/project/pii-Scanner/ , or similar) to identify columns likely to contain PII during the metadata scan or profiling, and then add tags to the data element to allow clients to filter and flag columns that may require additional handling or security. This could also allow for tagging for the type of data like phone numbers, emails, address data, or more. This is an extremely common request we get from clients when demoing Catalog, metadata scanning, and profiling. This data could then be carried over into snapshot management, dataset design, mapping, and reporting in Migrate.
Object Runbook
I would love to see this included in ADMM similar to what they did with the validation script. Another thing driving the business/project users to our tool. The other benefit to this is a majority of the content can be pulled straight from ADMM. Runbook templates Possible Format a. [Object Name] Runbook b. Doc history Version Date Summary of changes Section Page Author - Pull from ADMM Stakeholders (Developer) c. Doc Info Work Stream - Pull from ADMM Dataset Design Project Phase - Pull from ADMM Dataset Design Object Name - Pull from ADMM Dataset Design Business Owner - Pull from ADMM Stakeholders Conversion Owner - Pull from ADMM Stakeholders (Developer) d. Object Definition for [Object Name] Object Description - 1-2 sentences describing what the object does. Project: Workstream + Object Name - Pull from ADMM Mapping ETL Jobs - Pull from ADMM Mappings Workflows (if necessary) Transaction Codes (if SAP, otherwise how to access target system) - Pull from ADMM Dataset Design Object Dependencies Objects that depend on this object e. Source System Information Source System Tables - Pull from ADMM Mappings f. Target System Information Target System tables - Pull from ADMM Dataset Design g. Detailed Steps for Processing Conversion Object Preload process (Example) a. Run Dataset Transform(s) b. Run Report Transform(s) Conversion Loading of Data (Example) a. Run Export Transform(s) b. Go to LSMW Project Subproject Object c. Read Data d. Convert Data e. Start IDoc Creation f. Process IDoc's Postload process (Example) a. Run Readbacks b. Run Postload Transform(s) h. Object Contacts - Pull from ADMM Stakeholders
Reflect Filtered Selection Count in Panel Headers
When we are in Mappings (or any screen really), it is very common to have a filter applied to one or more of the panels. For example, on a large project each user is often filtering datasets based on subject area or developer, or we are filtering the sources and targets based on the data issue we are currently reviewing. When we apply one of these filters, the count at the top never changes. If a project has 100 datasets, and I filter to show datasets in the OTC subject area and have 9 datasets shown visually, the count at the top still says just 100. It would be more accurate if the count in the top changed to say just 9, or something like 9 / 100.
Allow sorting & filtering in all the columns of the Replications grid
In Replicate Preview I can’t filter and sort all columns. Sorting & filtering columns “Last Refreshed” and “Record Count” can be very helpful, as we may need to check which were the most recent replications or the ones with more records / no records without having to export the data to Excel. Ideally, date & time display format for the “Last Refreshed” column should be customizable. It would be very nice that filtering for “Last Refreshed” column was similar to that existing in Excel, in which data is grouped by Year / Month / Day.
Enhanced Data Interaction Layer for Syniti UI
Summary Introduce a lightweight, non-invasive UI enhancement layer that improves how users interact with and interpret data within the existing platform. This solution overlays additional visual cues, intelligent filtering, and usability improvements without modifying the core application. Problem Statement Users working within the current interface face several friction points: Difficulty quickly identifying key data signals (errors, flags, statuses) High cognitive load when scanning large datasets or dropdowns Inefficient navigation due to lack of smart filtering or prioritization Repetitive manual effort to interpret or locate relevant information This results in: Slower task execution Increased risk of oversight or error Lower overall user efficiency and satisfaction Proposed Solution Implement a client-side enhancement layer that augments the existing UI with: 🔹 Visual Enhancements Dynamic color coding for key fields (e.g., status, errors, boolean flags) Priority-based highlighting (e.g., TRUE/FALSE overriding other styles) Improved contrast and readability for dense data grids 🔹 Intelligent Interaction Smart dropdown filtering with fuzzy/wildcard search (e.g., PMWC*CRCO) Auto-suggest top matches with preview lists Keyboard-driven selection (Enter to select best match) 🔹 Real-Time Responsiveness Lightweight refresh logic tied to DOM updates (MutationObserver-based) Efficient rendering using throttling (e.g., requestAnimationFrame) Adaptive updates as new data loads dynamically 🔹 User Productivity Features Quick-select panels for common values Reduced need for scrolling and manual searching Faster identification of actionable data Use Cases Data migration validation (preload/postload analysis) Error identification and remediation workflows Dropdown-heavy configuration tasks Large dataset navigation and filtering
In Progress
16Actively being built
Access to ADMM data
Very often we are asked to create reports from ADMM data. In ADM we were able to get any information since we had access to its database but now we are limited to the data in MIG views in which we don't have all the tables and sometimes the views doesn't have all the fields from its tables. I would really like to have all the tables from the system available to be refreshed via MIG views to enable us creating any report needed by the client and solutions via construct. Some examples: User / role: There's a view with this information but the Support told me it is deprecated and will probably be deleted. This view should be updated with the correct information Design: MIGALLDATASET_TABLES doesn't have the dataset ID, index, datasource,… Mapping: Missing views for dataset's target and source tables (with index, active flag, …)
Mass Update/Insert Column Translations
The UI for editing Column Translations in ADMM appears to only support updates one at a time. It would be great to have a way to mass insert/update column translations from an Excel file.
Import/Export Table List for Snapshot Management from Excel
For adding new S4 targets the process to add individual tables is extremely cumbersome. Importing and exporting from/to excel would alleviate a lot of the time involved in executing setup.
[L'OREAL] durable service credential for the Service API, including SQL Editor DDL
Where we stand: with the API key we read and write data maps and query the OData views, and the full loop has now run live on the AI - POC release — an AI-generated rule written in, read back, compiled to SQL, the ETL build triggered, and the view deployed. Everything beyond the data-map write, however, rides the interactive session token (concento-authtoken), which we measured at 300 seconds of life and which only a person completing SSO + MFA can mint. That single constraint is what separates a working PoC from an unattended service. 3. A durable service credential for the Service API, including SQL Editor DDL. Our solution is being deployed as a service on Google Cloud, where no interactive browser session exists — so a 300-second, human-minted token rules out any scheduled, unattended, or CI operation. We need an API key or OAuth client-credentials flow for this surface, with the ability to execute DDL through the SQL Editor (ALTER VIEW) — that is how a backed-up view is restored, and the path is already proven working from our code.
[L'OREAL] Public read access to compiled SQL / _UPD_ view DDL
Where we stand: with the API key we read and write data maps and query the OData views, and the full loop has now run live on the AI - POC release — an AI-generated rule written in, read back, compiled to SQL, the ETL build triggered, and the view deployed. Everything beyond the data-map write, however, rides the interactive session token (concento-authtoken), which we measured at 300 seconds of life and which only a person completing SSO + MFA can mint. That single constraint is what separates a working PoC from an unattended service. 2. Public read access to compiled SQL / UPD view DDL. On our test object, 10 of its 11 rule tasks have their logic stored only as view SQL in the database, with no rule in Syniti (104 fields across the release). COMMAND_TEXT being null means this SQL is invisible to the API key. Our safety procedure around every build — capture all view definitions before, verify byte-identical after, restore on any regression — therefore works today only through the session-authed SQL Editor. Without a durable read path there is no automatable backup, and a build is an unrecoverable risk.
[L'OREAL] public ETL trigger
Where we stand: with the API key we read and write data maps and query the OData views, and the full loop has now run live on the AI - POC release — an AI-generated rule written in, read back, compiled to SQL, the ETL build triggered, and the view deployed. Everything beyond the data-map write, however, rides the interactive session token (concento-authtoken), which we measured at 300 seconds of life and which only a person completing SSO + MFA can mint. That single constraint is what separates a working PoC from an unattended service. 1. A public ETL build trigger. Build/rebuild is only reachable via the internal rebuildTasks endpoint on a session token — confirmed by your team as out of public scope. Until it's public, a generated rule takes effect only when a person is present.
Add mapping status to Excel import template
Enable end user to decide mapping status through excel datasets & mappings import feature with a dedicated column. Allowed values (same as dropdown list on mapping screen): New In-Progress Design Required Complete
Match UI issue.
In match review, the field sort feature only works on existing records in display and not the complete dataset. if the display shows 20 records and dataset contains 100 records, the sort only sorts the 20 records on display.
SKP Quality - Save All Errors Parameter (Execution datastore different that Report cache datastore)
In DQ, the Save All Errors parameter is only allowed to set if Enforcement Implementation datastore is same as Report cache (as in Parameters). By design, the Report Cache datastore must be different than the Execution datastore (working db). Need to have a Save All Errors parameter to change it accordingly to the design principle.
SKP Catalog/Quality - use REST API to set asset ID numbers
As Data Quality is now more widely used, some customers will deploy it with multiple tenants of SKP. This poses a problem when trying to keep the Catalog asset ID numbers aligned. For Eli Lilly, the chief concern is the Rule ID, but the same issue exists for the other asset IDs. It is too unwieldy to have different ID numbers for the same assets between their multiple SKP tenants. Please enhance the SKP REST API to allow users to specify a Rule ID value when creating or modifying a Rule using the SKPv2 REST API. The standard documentation (linked below) doesn't list any means of specifying the Rule ID. This is a critical issue for Eli Lilly, who is using the REST API to transfer Rules from one tenant to another, and they need the Rule ID to stay the same. create a Rule (POST) modify a Rule (PUT)
Completed
55Recently shipped
Orchestrate - Add ETL tasks/steps
when creating a task in Orchestrate there is no possibility to add ETL tasks. Currently I'm in need to create a weekly process where first we run SRCECC (full)-this was also requested in other ideas - and sequentially run ETL tasks.
Ability to download data assets
Ability to extract data set, fields description, maps, etc. in the excel/pdf (printed-friendly) format.
Tenant ID Visible to End Users
Many CS provisioning requests and support troubleshooting steps require knowledge of which tenant a user is logged in to. Enabling the end user to determine and provide their own tenant ID, perhaps via Administration, would expedite this process for both internal and external parties.
Show Data Profiling results in Migrate
SKT allows a system to be profiled. Enable Migrate to be able to show those profiling results for tables and columns in Migrate. It would be useful to see those results in the Datasources, in Dataset Design, and in Field Mapping.
Asset Reporting
Specifically, I want to be able to view assets which are not aligned to a goal or initiative, do not have an assignee, or where I have not added any sponsors. For example, let's say I added ~50 policies in a relatively short time frame. I want a quick way to ensure I have aligned all of those policies with the appropriate initiative/goal/assignee/sponsor. Rather than reviewing 50 records, I would like to run a report that can show me policies which are missing an initiative/etc. so I can quickly remediate them.
Search term should allow Wildcards
Client wanted to find all assets that included "meins" SKP search using meins returned 0 records. Search using MARA.meins returned 11 records. Client expected to be able to find the 11 records by searching with a wildcard (* or %) so that they could easily find all the relevant records to make an informed decision. Update: The search was from the homepage. The User tried miens, *miens, .meins and %meins as searches execting to find rules and possibly terms that included the sequence of characters in the asset name, description, additional information or implication fields. The system returned results when the search characters were found as a full word (a series of sequential, non-space characters preceded and followed by a space character) in one of the searchable fields. Somehow searching for account pulls up hundreds of results that include the DataSet "Vendor: Payment Transaction Accounting" but Searching for Cust only brings up one result: the term Customer Account Group. That term does not seem to include the use of cust as a stand-alone word.
Allow the Datasource to be changed in Field Mapping
Large companies often have many copies of the same application running in different divisions or plants. For example, a company might have 1 instance of Maximo running at each of their manufacturing plants. These all need to be mapped as sources with mostly the same mapping rules. It's possible that sometimes the mapper will choose the wrong datasource and map it completely. Then they realize they mapped the wrong source and need to change it. This is possible, but not super common. A more common usage would be as we copy a RELEASE we then need to update the copied mappings from one source (MAXIMOA) to the new source (MAXIMOB). By changing the Datasource we would need to cascade down the change to the Primary Table ID (GUID) to be the same table in the new datasource. Recommendation: Allow RELINTERFACESOURCE.DATASOURCE_ID to be changed to the new Datasource ID. a. The list of new DATASOURCES should be limited to only datasources with the same APPLICATIONID and which contain the same table name referenced by the PRIMARYTABLE_ID. ie. if we are mapping MAXIMO1.ITEMS then show any other Maximo datasources that also have an ITEMS table… Upon changing the datasource, update the PRIMARYTABLEID to the new table id from from the new datasourceid. Update CORDATAMAP for all child records (based on INTERFACESOURCEID) to have the new DATASOURCEID, but only if the datasourceid is the same as the OLD datasource ID. Note that some mappings might be from a Different Datasource_ID so we can't just update all the mappings. Update RELMAPLINAGE.DATASOURCE_ID using the same logic as for the mapping screen. Don't trigger an additional info message as these If there are OTHER datasources referenced by CORDATAMAP.DATASOUCEID or RELMAPLINEAGE.DATASOURCEID - pop up an informational message to alert the user to verify all existing mappings as some secondary datasources have been used in mappings. Set the MAPSTATUS to 'In-Progress' and BUILDSTATUS to 'New'
Rule Asset - Additional Information attribute
It would be useful to have an Additional Information attribute in the rule asset just like there is in the term asset. Some rules require decision tables and this would be a great place to store that information.
Add dspCompose to Enforcement Profile for Data Quality
Currently, the Enforcement Profile is the only method for linking Entota Cloud rules to the implementation of those validation rules in DSP components. dspCompose is missing from the drop-down of applications in the Enforcement Profile. It is very important for impact assessment that we know all of the places that a particular Entota Cloud rule has been implemented and that we have traceability bi-directionally.
Enable Usage Level field in Mappings
Client wants to use field Usage Level drop down to define if the field is Local or Global. Once used, they want to have it in mapping fields banner as attached screenshot, so they can filter the fields based on Local or Global value in that Usage Level.