Welcome to the Syniti Ideas Portal!

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.

Automatically add table aliases to "shell" rules

When Migrate generates update rules, it would be VERY useful for it to automatically alias the table, and add that alias to the columns. See the current shell rule that gets generated: What I’m proposing is to replace the full table with “s.” and aliasing the column as “s” It may not seem like much, but in Postgres when there is no visual view designer, it becomes very cumbersome when you have to type out the table names for every column. And I end up repetitively aliasing and swapping in “s.” hundreds of times throughout the rules and reports. *Similarly, any source report would get “s.” and target report would get “t.” - And one last thing… can we add “WHERE s.zactive = true” to all update rules? I believe that’s standard methodology?

jay.hornback@syniti.com About 19 hours ago

1

Future Consideration

Make ETL Report 'Column Translation' default configurable

When you add an ETL report, the Display section has a Column Translation selection, which is defaulted to ‘Both’. I would like this to be configurable because on our project the customer has asked that we always switch it to ‘Technical’. They do not like that ‘Both’ adds 2 rows to the report download. So I end up having to change this default value on every report.

jay.hornback@syniti.com 19 days ago

1

Unlikely to Implement

Predelivered functions / sp to support Release copy backend code

In order to reach an end-to-end executable process as per Release copy feature, delivery consultants need a set of predelivered functions / stored procedures to support backend code promotion including: Compare objects & ETL jobs of 2 releases (with optional filter to focus on “development area”, “source”, “dataset” only) Returns excel import formats for template Generates SQL scripts to promote custom objects to the new development area, code adjusted Highlights missing dependencies, e.g., source tables

Guillaume Dutey About 1 month ago

4

Planned

Enhance MIG_EXPORT_ETL to identify autogen vs manually added ETL tasks

Adding one or various columns to MIG_EXPORT_ETL table populated to identify how the tasks was added (AutoGen / Manual) would help with comparison during Release copy and Quality Assurance checks. Note: as per support ticket ETL reports - identify the rules added manually – Software Support there is no clear way to identify rules which have been manually added.

Guillaume Dutey About 1 month ago

1

Planned

Migrate Target Report - Display Field description in the "Error Log Msg"

Users are requesting an option to include the field Description alongside (or instead of) the technical field name by default, so they don’t need to update it manually. For example, instead of “BUKRS IS NULL,” the message would read “Company Code (BUKRS) is null.” This would make validation easier, especially for business users who may not be familiar with technical field names.

Ana Garcia Rubio (Syniti) About 2 months ago

2

Extending existing System Report

Client would like to enhance the existing report Home > System Reports >> All Snapshot Tables with following fields: to include the following additional information: Execution context INITIATED_BY START_TIME END_TIME Outcome and metrics STATUS PROCESSED_RECORDS FAILED_RECORDS WARNING_COUNT LATENCY_SECONDS I could not find the table which stores this data. This information I think is beneficial for the client. Please look into this enhanced system report.

ash.tallapally About 2 months ago

2

A List Over Limit error displays when the user selects a list box item in excel integration.

I understand that excel is limited to only 3000 entries in the list box. The default limitation is ok, however, I think we can have a setting like we had in ADM that will allow us to increase/modify this default setting to allow more values in the dropdown depending on the configuration in the project.

Divya Navandar About 2 months ago

1

Enhancement Request: Enable Escape Key to Close Popup Windows in SKP

Currently, when interacting with popup/modal windows in the Syniti Knowledge Platform (SKP), users are unable to close the popup by pressing the Escape key on the keyboard. This deviates from standard web application behavior and impacts usability, accessibility, and efficiency for end users—especially for power users accustomed to using keyboard shortcuts. Request: We propose enhancing this experience by enabling Escape to close popups. However, if a user has unsaved changes within a popup, pressing Escape should trigger a prompt/warning before the popup is closed, allowing the user to cancel the action or continue and discard changes. Enhancement Details: Support Escape key as a shortcut to close popups and modal dialogs throughout SKP. If unsaved changes are detected within the popup: Intercept the Escape key event. Display a warning dialog: “You have unsaved changes. Are you sure you want to close this popup and discard your changes?” Offer “Cancel” and “Discard changes” options. This ensures alignment with broad web application standards and reduces accidental data loss. For popups where Escape/cancel is not appropriate (such as critical workflow confirmations), allow exceptions as appropriate.

santosh.srirangam@synniti.com About 2 months ago

2

Planned

Metrics for Scorecard & Milestone automation

Automated Metric Refresh & Persistence Logic Current Limitation: Currently, the Metric Scorecard and PMO Dashboard rely on manual developer intervention to trigger refreshes. This manual dependency introduces a significant risk of "stale data" and human error, which undermines the reliability of the PMO Dashboard. Business Justification: In a Data Governance environment, real-time accuracy and data integrity are non-negotiable. Relying on manual updates is not a scalable solution and contradicts the principles of automated governance. Proposed Feature/Solution: Automated Refresh Scheduler: Implement a backend feature to auto-populate and refresh metrics at defined intervals (e.g., hourly or daily). Event-Driven Triggers: Enable the system to automatically recalculate the Scorecard upon the completion of specific data jobs or migration cycles. Impact: Making this feature available will ensure high-fidelity tracking of projects, reduce manual overhead, and provide leadership with a "single source of truth" that is always current.

Sunil Bhardwaj About 2 months ago

2