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.

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 10 days ago

1

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 13 days ago

2

Create a way to execute a single ETL report in the background

In Migrate when you build a very heavy query and click the Refresh button, it will run for a max of 3 minutes regardless of what your report timeout and data source timeout have been set to. You do have the ability to kick off all reports from the Target > ETL page, and that will kick off a job queue and run it in the background. But I’m just trying to run a single report, and have it run one time. When you click the refresh icon, the status does change to the arrow/spin circle, but if you click off of the page I believe it cancels the job. And even if you stay on the page, if it takes longer than 3 minutes you get a 504 error. So we need a way to kick off these reports directly into the background (maybe from the Report Details?).

jay.hornback@syniti.com 19 days ago

1

Planned

More granular control of automated emails

There is a toggle button on the My Account page in ADMM to turn emails on/off, but this does not affect emails sent when you’re executing Snapshot Management jobs, ETL jobs, etc. Scenario 1: I’m running a Snapshot Refresh at the source level, and that contains 200+ tables. I receive 200 separate emails with no way to control it. Scenario 2: As I build out my target from mappings, I execute every rule individually. I get an email as each rule completes - with no indication of which rule was actually executed: We need a better way of #1 making the emails more informative and #2 having more control on the emails being sent. I know we can put Inbox rules in place to funnel emails into a folder but this is a workaround the customer is not happy with.

jay.hornback@syniti.com 27 days ago

Postgres: build function or procedure to assist in column changes

Postgres is a lot more restrictive when it comes to adding/deleting columns to views, changing column names of a table, changing data types of a column, etc. If the column is used somewhere else Postgres will not allow it. In some cases, like if you try to delete a table, it will tell you which views prevent you from doing that. You have to go find anywhere where the object is used, edit each view or drop all views, make your table change, then recreate the views. This is dangerous as if you have multiple nested views, or if you’re deep into a project and there are many views using a table, you risk losing your work, dropping and not creating in the same order, etc. My idea here is that we at the very least come up with a script to query the database metadata to assist in this effort. At a minimum, you input a table or column and it outputs the views where it is used. The max ask here would be for the SP to execute the change for you - it would store the drop and create view scripts in temp variables, then execute the drop script, make the column change, execute the recreate script.

jay.hornback@syniti.com About 1 month ago

2