Enhancements:
1. Add Areas in Azure DevOps widget under projects.
- An ‘Areas’ drop-down selection field is added within the Azure DevOps widget. Now, the users can choose the ‘Areas’ drop-down list based on the ‘Project’ selection. Similarly, users can choose the ‘Test Case’ drop-down list based on the ‘Areas’ selection. This enhancement works with all FDRs, Validations, and QPTs.
2. Paginated Filter Reports in Power BI.
- Users can now apply filters on any selected column/columns from the ‘Power BI’ data table. There are two parameters for the ‘Paginated Report Filters’ such as ‘Key’ and ‘Value’ and the users must select these two parameters to apply the filters accordingly.
3. Redesigning all Reporting Dashboards other than Scenario Execution History to enable data loading with ease.
- Four new options such as Last 30 Days, Quarter data, Half year data, and One year data were added to all Reporting Dashboards such as Data Quality Metrics, Data Quality Dimensions, Row Counts Compare, Reconciliations, and Asset Inventory to enable easy data loading. This enhancement is not included in the ‘Scenario Execution History’ Dashboard as it loads only the past 30 days’ data.
4. How to address User response metrics.
- Two parameters such as ‘Response time for UI/UX’ and ‘DB Time’ are added in the Reporting Dashboards to measure and display the time taken to load any dashboards session page data based on the request from the User end.
5. Oracle JDBC Connection Profile – New params for SSH tunnel.
- An ‘SSH’ tunnel with SSH Host, SSH Username, and SSH PEM FILE are included within the Oracle JDBC connection profile.
- Previously, there was only an option to import external Queries through excel but now users can import external Queries from the desired data sources available from the QPT Profile drop-down list.
- Before saving and executing the required selected Queries, previously, the users filled different Threshold values (Pass, Information, and Warning) individually for every single Query but now users can click the ‘Cascade’ button option after filling the threshold values of one query and can later apply the same to the rest of the Queries.
- After executing the Queries, the user is navigated to the QPT ‘Summary’ tab. Previously, from the ‘Summary’ tab, the options such as Email and Excel (Download Summary Details) were in disable mode but now they are enabled.
- Previously when the user clicked the email option from the QPT ‘Summary’ or ‘Details’ tab, only the QPT results Excel (Download Summary Details) was delivered to the email address but now the QPT result body is also delivered along with the Excel.
7. Enable ‘Execution History JSON’ only for admin users.
- If the user loads any session from the ‘Execution History’, that particular session’s ‘Execution History JSON’ is enabled and is only visible to an Admin pro-user and is disabled for Display (power) and Non-Admin users. This enhancement is included in all Query Chains, Scenarios, and Jobs.
8. Need to show differentiation for Auto-Generate Queries in explorers.
- Now users can differentiate between Auto Generate Queries and normal/manual Queries in explorers. When users wish to add an existing Query to use it in any Query Chain or FDR, they must be able to differentiate between the Queries generated through the Auto Generate process or normal/manual process.
- When users edit any Auto-Generate Query from the explorer and save it, then it will be converted to a normal/manual Query.
9. Where Used List for Email Templates.
- If the user uses an Email Template in any Query Chain, FDR, TDR, or Validation, then the where-used list details of that particular Email Template are visible when the user is about to delete it from the ‘Custom Email Template’ session page.
- If the user deletes a specific Email Template after using it in any Query Chain, FDR, TDR, or Validation, then the user notices the ‘Email Template’ drop-down list is set to ‘Default’ within its ‘Email Settings’ widget.
10. UI changes for Where Used List.
- Now users can see a tabular grid pattern instead of the tabs view for the Where Used List option that contains columns such as Type, Name, Path, Created By, and Created On.
11. Adding the ‘Metadata’ button in the Query Builder ‘Results’ tab.
- A ‘Metadata’ button is newly added within the Query Builder ‘Results’ tab that displays the Metadata in a tabular grid pattern with columns such as ‘Column Name’ and ‘Data Type.’
12. Job designer source widgets grid selection issues.
- Previously, when the user selected any source widget/widgets and simultaneously applied filter application, the ‘Show Selected’ toggle view would have not shown the selected source widgets but only the filtered results under the ‘Show All’ toggle view. This enhancement is included in Job Designer widgets such as FDR Scenarios, Validation Scenarios, Bulk Data Validation Scenarios, TDR Scenarios, and Query Chains.
- Now the user can view the selected source widgets from the ‘Show All’ mode and selected source widgets from the filtered results under the ‘Show Selected’ toggle view.
13. Add select query and redirect to the source page in variable explorer create page.
- Now the user can view the selected query from the ‘Variable Builder’ create page and at the same time can be able to redirect to the source page where it was used previously.
14. Ability to show mapped objects on top in TDR.
- A button named ‘Arrange Object Pairs By Mapping Order’ in the ‘Count Compare’ or ‘Data Compare’ widgets maps the randomly mapped objects in the top order.
15. A Search provision is included in User Groups.
- A ‘Search’ field is added for both the ‘Users’ and ‘Profiles’ sections within the ‘User Groups’ session page to enable the search functionality.
16. Folder path issue sorted out within the designer header.
- Previously, the user was unable to see the created (Query, Scenario, or Job) folder path view within the designer header but now this issue has been rectified and the user can see the exact folder path.
17. Explorer’s column resize option.
- The fixed columns in all the individual explorer grids (Query, Scenario, and Job) can now be dragged or resized based on the user requirement.
- During ‘BOBJ’ execution, ‘User prompt Inputs’ was added which acts as a filter application executing the filter results.
19. Complex filter in SAP ECC.
- A ‘complex filter’ is included in the ‘SAP ECC’ profile. When a large volume of data set is reconciled between source and target, one of the recommended approaches is to validate data at an aggregated level. If the intersections at aggregated level fail to reconciled, you can get more granular in your next level of reconciled, and in the process only select intersections that did not reconcile at aggregated level.
- ABAP SQL does not handle Concatenated select in WHERE clause. A new feature was enabled to select data using ALL ENTRIES in ABAB. As an example, in the complex filter input column names like ERSDA and ERNAM, provide corresponding values separated by ‘|’ and multiple values speared by ‘,’ as an example 20040123|BOHNSTEDT,19950904|CADCPIC. This will enable narrowing down the selection based on the combinations provided.
20. ‘Update’ button option is removed and ‘Save’ option saves all the profile edits.
- An ‘update’ button option is removed from the ‘Profile’ edit page and the user can use the ‘Save’ button to save all the values (Source Name, Connection Parameters, and Additional Settings) including the ‘Profile Name’.
- ‘Catalog’ and ‘Content’ are the two navigators used with the ‘Hana’ profile. Now the user can use these navigators for query executions.
22. Tableau reports validation in TDR.
- ‘Tableau’ is added as a Data Source in TDR (Technical Data Reconciliation). Now, the user can select Tableau reports for bulk data validations. Note only Published reports can be validated and default filter values will be considered during validation.
23. Variable code optimization.
- The variable code optimization is done on the ‘Data Retention’ page which is a part of the ‘ADMIN CONSOLE’ module. The variable loader status is initiated only when the user clicks the ‘Variable’ button option.
24. Changes in the logging service.
- Changes in the logging service in order to stop using the older log4j library to avoid the vulnerabilities recently documented by NIST.