Do you have feedback regarding the current product, or new ideas for improvement?
Tell us how we can make the Syniti Knowledge Platform more useful to you.
Welcome to the Syniti Ideas Portal!
Planned
OAuth2 bearer tokens on /services/api
Hello everyone, We tested the 2026-11-03 release with our automation on the AI - POC release of the L'Oréal tenant, using the OAuth2 client credentials you provided for the Knowledge Platform. What works OAuth2 authentication: The client credentials (POST https://api.syniti.eu/oauth2/tokens) are now accepted as a bearer token on /v1, /odata and the new /v1/etl-jobs/* endpoints. An API key is no longer required. Build and compiled SQL: Both the Build endpoint (POST /v1/etl-jobs/{id}/rebuild) and the compiled SQL endpoint (GET /v1/etl-jobs/{id}/compiled-sql) return results that match the Service API byte for byte. Thank you for these additions. Where we stand Of the 45 Service API (/services/api) endpoints used by our automation: 20 are now fully covered by the public API or an OData view. 5 are partially covered, with one or more required fields missing. 20 have no public equivalent. The attached document provides a detailed breakdown of each endpoint, its purpose, how we use it and the closest available public API equivalent. However, the OAuth2 bearer token is still rejected (401) on /services/api. As a result, the 25 endpoints that are not fully covered still require us to rely on the browser session token (concento-authtoken), which expires after 300 seconds and has no dedicated issuing endpoint. What we need to finalise the integration Either of the following options would close the remaining gap: Accept OAuth2 bearer tokens on /services/api. This would be the simplest and fastest solution, requiring no further changes to the existing endpoints or our automation. Provide public /v1 or odata equivalents for the 25 remaining endpoints. The "What we ask Syniti" table in the attached document groups these into two priority levels: Priority 1 (18 endpoints): Essential to our Build-to-load workflow, which cannot run end-to-end without them. Priority 2 (7 endpoints): Required for the remaining automation capabilities. We would be happy to walk you through the document or arrange a joint test on AI - POC at your convenience.
Value Mapping New Layout - Search functionality
Hi Team, Siemens Client has requested if Search functionality can be added on the Value Mappings page which will enable them to select the Target System, Check table and ZSOURCE based on the search value rather than scrolling through the entire list.
API for user access management
[L’OREAL request] The purpose is to use an API to open and remove accesses to new/existing users based on following information (provided by external access management platform). Actions are done in Migrate module, below the list of mandatory attributes to handle by the API to reproduce this work : Migrate : User name Email address User group
Graph to display 'mapping changes counts'
Mapping rate of change is an important metric to determine overall project health as well as the basis for potential change orders. If the rate of mapping changes is very high late in a project or as you approach a go live, you can expect that volatility will lead to unexpected results, incomplete mappings, and failed validations. Also, as you look for reasons why change orders might be needed, extra or unexpected work late in a project related to mappings can form the basis for a factual discussion with the customer about the need. It is an important metric to keep track of in every project - and I believe (but am not certain) that the ‘History’ icon in mapping would provide the basis for this graph. If you click here, you’ll see ‘Object History’ at the column level. I think every time you make a change to a mapping, a record is inserted here. So the graph would take these records and “roll them up”. X axis - Time - either daily, weekly, or monthly. Maybe that would be configurable? Y axis - Count This graph would be useful to display/roll up at all levels: source, target, dataset, release You would also want to take into account things like the ‘Active’ button being on/off for a given source, target, and/or dataset.
Multilingual Data Translation Framework for Migration Objects
Enable ADMM to automatically translate source data fields stored in multiple languages into a common target language (for example, English) during migration processing. This capability should support any text-based fields, including addresses, master data attributes, and descriptive fields. Through integration with enterprise translation services such as Microsoft Azure AI Translator, ADMM could automatically translate source-language values into a user-specified target language, reducing manual effort, improving data quality, and supporting global SAP migration programs. Please refer Translation of text from different languages to a common language – Software Support (#160999) for any further reference.
Create ability to select specific objects to copy during a release copy
During the copy of a release, I would like to select specific objects to copy over. For example if I am copying a release that goes to MDG, I only need to get the Material Master object into that release and I do not need all of the transactional objects that go with that subject area. It would be beneficial to be able to remove object that are not needed during the process.
Unlikely to Implement
Adding Users to Security Roles via excel upload in CONSTRUCT
Client at L'Oréal has requested an enhancement that would allow administrators to add users to CONSTRUCT Security Roles through an Excel file upload, similar to the functionality currently available in ADMM. At present, CONSTRUCT does not support bulk user assignment to security roles via file upload.
In Progress
[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.
In Progress
[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.
In Progress
[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 Replications GET endpoint to Public API
Currently in the SKP API, we have Replications endpoint to create, update and delete. But NOT GET. Can you kindly add this endpoint ASAP please? This is required immediately for Astrazeneca ADMM implementation.
Data Catalog - Enable Quality Thresholds to be seen from Catalog Overview Dashboards
It would be helpful if the Quality Threshold for each asset is visible on the corresponding Catalog Overview Dashboard screens for all assets, when thresholds are applicable. At this time you can see them in the Quality Overview IF a Rule is applied, however, if no Rule has yet been applied to an asset, there is no other way to review the thresholds. Also not available on the Custom Dashboard You are also not able to see the Quality Threshold on the Asset Overview pages, unless you are in edit mode.
SKP Catalog/Quality - use REST API to read and create Asset Versions
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 move the Catalog Asset Versions. For Eli Lilly, the chief concern is that asset version history will be lost when moving from their SKPv1 tenant to their SKPv2 tenant, but the same issue exists if they should ever need to move to some “v3” tenant in the future. It is considered a high risk at Eli Lilly that they cannot move Asset Versions between tenants. Please enhance the SKP REST API to include a Version parameter when reading or creating the various Catalog assets that permit versioning. The current design always returns the latest version and there is no method for creating multiple versions of an Asset at once. SKPv2 REST API
SKP Catalog/Quality - use REST API to read and create Asset Comments
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 move the Catalog Asset Comments. For Eli Lilly, the chief concern is that historical data will be lost when moving from their SKPv1 tenant to their SKPv2 tenant, but the same issue exists if they should ever need to move to some “v3” tenant in the future. It is considered a high risk at Eli Lilly that they cannot move Asset Comments between tenants. Please enhance the SKP REST API to include a Comments block when reading or creating the various Catalog assets that permit comments. SKPv2 REST API
Ability to support multiple file formats in Syniti Drive
Currently we noticed limitations with the file formats being uploaded to Syniti drive. While majority are focused on the regular file format extensions, it would be greatly helpful if .zip files are also allowed in the drives. This allows developers to save multiple version of the custom code within ADMM. we had a scenario to upload the required and specific code to customer sharepoint, while for a developer it is more in detail including the configuration files and everything zipped and to be saved somewhere for the support personnel joining the team which is of more technical in nature. Can this be accommodated?
Replicate Update/Merge
Replicate needs the ability to not only insert new records from a file on SynitiDrive, but also the ability to update/merge records when keys match between the file and the table. Tested this an only inserts records. This would help eliminate the need for Excel Integration since users would have an option for mass insert and mass update of records
Custom Theme
Dear team, the new feature works fine but there are some complaints from the customer as we can not assign correctly corporative colors. Some examples; Terciary color , controls buttons color, but font remains black so when there are dark colors like the green below, it is visually difficult to handle. Perhaps we woud need to have the possibilty to manage either the font type (overall) or the font color Another topic is the icon and the background color in the home page and the difference with the Migrate home, client do not understand that difference as rest of modules keep same colour coherence in the header except migrate ( i assume that construct it is not up to date as it will the sooner or later deprecated) Thanks
Planned
Improve design of the uploading file for assignment of users to User groups in ADMM
Improve design of the uploading file for assignment of users to User groups. 2 ways of improvement : - Perform all relevant records of a uploading file. Today if 1 entry is wrong, all the file is rejected. - provide a report just after the load via pop up, with the following info : count of records OK, count of records Failed, and for each (OK and failed), the detail of the records. You can reuse the existing design in Construct, for the Loading file of "User release map".
Planned
e-signature in Construct 2.0
Hi, Can you kindly prioritize and implement the e-signature capability like the one we have in ADM into ADMM Construct 2.0 please? This is urgently required for my client to whom we are deploying ADMM in 3 months. Regards, Immanuel Michael