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.

Rethink list boxes in Replicate scheduled jobs

There are a lot of things here that I think could be improved: 1) Sort the recurrence dropdown properly: monthly/weekly/daily/hourly 2) Add a recurrence of ‘one time/specific date’. ie: I want to execute a job one time in the future, on a specific date (calendar picker) 3) For Recurrence = Monthly, when = Specific Date, you can choose values 1-31. I’m not sure how valuable this is. What if I chose the 31st? Only 7 months have a 31st day…

jay.hornback@syniti.com 1 day ago

1

Planned

Allow more granular ETL Copy of Dataset Transform

When copying the ETL structure in ADMM, allow for more granular selecting of parts of the Dataset Transform. Example: I have an object with 34 tables and 1000+ update rules in Dataset Transform. I have changed the Target Transform for 1 table and I want to copy that change from Dev to Mock 2. There is currently no option to only copy the ETL for one table in the Dataset Transform, I am forced to copy the entire Dataset Transform. With the size of the object, this takes 15+ minutes to complete. Could this be improved to allow selecting specific Target Transforms to copy from the Dev ETL?

emily.burnside 2 days ago

1

Planned

Improve Release copy process

Some examples of current challenges: The current process is managed in a static pop‑up window. The Sources replacement step requires to manually update potentially dozens of target entries within the pop‑up, instead of substituting the source, e.g., ECC_US to ECC_EU. It does not allow copying by blocks, i.e. a full copy is the only option. Even if the job fails, a new release may be partially created. Idea for improvement: dedicated section for release copies including: Configuration and preview side by side Allow execution by blocks, e.g. copy by subject area, by dataset Dataset design copy decision, i.e. create a new datasets or reuse Process monitoring Backend code support Releases comparison post copy: datasets, mappings, reports, ETLs, code… This section could also manage additional features related to development reusability within Migrate.

Ana Garcia Rubio (Syniti) 2 days ago

Planned

Add Technical Field column to bulk edit screen

In Dataset Design there is a "Technical field" column in Data Elements Tab. It helps to identify which table each data element refers to - especially when various rows have same name value. When performing Dataset Bulk Edit, this column is not displayed, resulting confusion accross rows with same name value. Idea: add this non-editable column to Bulk edit screen

Guillaume Dutey 4 days ago

1

Ability to select and delete multiple tables in the Datasource in Migrate

Currently, If there are multiple tables that have imported metadata to a Datasource in Migrate, and user decides this is a mistake, they have to delete each table one by one - in some cases this could be thousands of tables. If we could add the same check box process provided within Value Mapping page to the Datasource details page, it would make maintenance of this part of the system easier.

Donna Knox 6 days ago

1

Security Role/Feature for Maintaining Comments (by business/functional)

We could use a new Role or Feature to allow us to “Maintain Comments” for Mappings while restricting maintenance of other fields on the Mapping screen. This will allow business/functional users (non-developers), such as SI analysts or client business analysts, to add comments on mapping changes or clarifications WITHOUT opening other mapping fields, e.g., Map Action, for unintentional changes.

Tony.Moreno 9 days ago

1

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 18 days 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 about 1 month 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 2 months 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 2 months ago

1