We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Problem: Currently within the Virtual Tables and SQL Virtual Tables there is no way to pass a Parameter externally within a Filter Condition. As an example if I am using a date filter in a VT or SQL VT that extracts the data for a given day or given month I would like to pass the date value as a parameter based on the business scenario and the criteria.
Currently there is no way to pass these values and can only use a static date. We can use System Date (SYSDATE) within the VT but is not useful as there will be lot of business scenarios and dependency jobs that will drive what Date needs to be used while executing the Jobs scheduled in Production
Current Workaround: The only work around is to manually update all the Virtual Tables (which can be either 30 or 50 or 100 per project) for every day run with the required date value.
Pain Points: This is practically impossible in the fully operated production environment as any change to the Production environment requires a change request and even if you automate the process to update the Virtual Table every day which is a cumbersome process and is same as changing the Production Code every day for every Data Rule run.
Proposed Solution: There should be a way to define the Parameter Files and Parameter Values on the Server which can be used within the Virtual Tables/SQL Virtual Tables/Data Rules and should be manageable from the Information Analyzer Thin Client/New Quality Console/ IA Workbench.
Ability to use the Parameters within the Data Rule Bindings for the Host Name, Database Name and Schema Name will be helpful during the Migration of the Data Rules across the environments.
Impact: This is the basic feature any tool is expected to have and is a major bug/flaw in designing the Information Analyzer product and lack of understanding of the practical implementation of the tool in Production environments.
Do not place IBM confidential, company confidential, or personal information into any field.