IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM Engineering - Reporting
Categories Report Builder
Created by Guest
Created on Jan 30, 2023

RELATED IDEAS

Report Builder Admin should be able to see the reports running and stop long-running queries if needed

【Motivation】
ELM users happen to develop a heavy JRS report and run the report many times for test,
the request for execution for the report would fail with timeout error, and the process for LQE is occupied for a long time. That is because JRS creates a queue for "heavy" execution of the report (have the execution waiting) and each execution in the queue is executed one by one and fail with timeout.
This often happens In the customer's environment, that affects the efficiency of their business so much as a result.

【Functional Requirement】
1) Users get able to see the information below in JRS admin page.
(Just like users can see the running queries in Running Queries tab in LQE's Health Monitoring page)

- reports already completed (list)
report id/title, when is the execution requested, execution result(success/fail/cancel), when did the execution finist, data source(DWH/LQE)
- reports executing (list)
report id/title, when is the execution requested, execution time, data source(DWH/LQE)
- reports waiting for execution (list)
report id/title, when is the execution requested, wait time, data source(DWH/LQE)

2) For "reports waiting for execution" above, users can cancel the execution of a report.
If users cancel the execution of a report, the report would be in cancelled state and displayed in the "reports already completed" list.

Idea priority High
Needed By Quarter
  • Post comment
  • Admin
    FARIZ SARACEVIC
    Reply
    |     Feb 7, 2023

    JRS application components are primarily Report Builder (RB) and Lifecycle Query Engine (LQE). They operate in tandem where LQE is backend storage and RB is front end interface to create/maintain reports. Per your request, see the title 'Report Builder Admin should be able to see the reports running and stop long-running queries if needed', we evaluated your idea. As stated this functionality already exists as part of LQE and provides exactly what your request is 'to see the reports running and stop long-running queries if needed'. This is implemented as part of LQE as this is an appropriate JRS implementation location. Hence, our original response on Feb 4, 2023, is still valid.

  • Guest
    Reply
    |     Feb 5, 2023

    >You can find details under 'Improving the responsiveness of Lifecycle Query Engine queries' >https://www.ibm.com/docs/en/elm/7.0.2?topic=performance-improving-query-responsiveness.

    No, your understanding is incorrect.

    The functionality you mentioned above is provided as LQE functions.

    On the other hands, the functionality we mentioned in this submitted idea needs to be provided as JRS functions.

    The LQE functionality allows users only to block queries already running, while the JRS functionality allows users to block queries in the JRS query queue before running.

    It would save a lot of work of users and avoid many report queries from 504 timeout errors.

    Could you please reconsider the review result?

  • Guest
    Reply
    |     Feb 4, 2023
    As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion. The IBM Engineering team has carefully reviewed this idea, and based on our understanding, this functionality already exists. You can find details under 'Improving the responsiveness of Lifecycle Query Engine queries' https://www.ibm.com/docs/en/elm/7.0.2?topic=performance-improving-query-responsiveness.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.