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 Future consideration
Workspace IBM MAS - Manage (Base)
Created by Guest
Created on May 28, 2021

RELATED IDEAS

ReportImport Cron Task Should Create CronTaskHistory Records

Maximo 7.6.1.2 changed the way new Reports are uploaded. Rather than check for Reports to be loaded every time a JVM starts up, Maximo 7.6.1.2 introduced a ReportImport Cron Task which is created in one of two ways:

- By UpdateDB.
- By executing the reportloader command utility.

When the ReportImport Cron Task is created, a corresponding ReportBatchImport Cron Task Instance, which is deleted once the Cron Task runs, is also created.

There is nothing to indicate that the Cron Task ran because the Cron Task Instance is created with the "Keep History?" checkbox unchecked so no CronTaskHistory record is created.

We would like to see the Cron Task Instance created with the "Keep History?" checkbox checked so we will be able to have a record of the Cron Task running.

We would also prefer to see the Cron Task Instance inactivated after it runs rather than deleted so we can see the Last Run Date and the History through the UI. If the Cron Task Instance is deleted, there is no row in the "Cron Task Instance" table on the main tab of the Cron Task Setup application to display the "Last Run Timestamp" and because the "Cron Task History" table is a child of the "Cron Task Instance" table, no rows appear in it either even though records do exist in the CronTaskHistory DB table.

Idea priority Medium
  • Post comment
  • Guest
    Reply
    |     Jun 9, 2021

    While on a call with Brian Garrett (IBM) regarding other BIRT Report issues, we were talking about the problem with the Cron Task only inserting new reports and not updating changed reports. Aside from the fact that there doesn't appear to be any information provided regarding changed reports in the Fix Pack or IFix ReadMe files or ListOfAPARs&ChangedFiles.xlsx, if clients have followed IBM recommendations and NOT changed out-of-the-box (OOTB) reports, they shouldn't have to go through a big effort to make sure they have the latest and greatest version of OOTB reports.

    The ReportImport Cron Task reads the mxe.report.birt.disableautoimport System Property to determine whether or not it should import anything. If this RFE is approved, we would like to extend it to also add a similar System Property to tell the Cron Task that changed reports should be updated in addition to inserting new reports.

    Brian suggested adding that feature to this RFE rather than creating a separate one.

    Thank you.

  • Guest
    Reply
    |     May 31, 2021

    This sounds like a useful RFE.
    Administrators can wade through the JVM log files looking for clues that the crontask ran but any evidence there can quickly disappear if the logs are rolling over quickly.

    Automatically logging crontasks is an importat step because it lets system administrators see the history e.g. when it ran and how long it ran for.
    there may be circumstances where a system administrator wants to understand how long a previous import ran.

    The standard crontaskhistory cleanup process can manage the records.

    I agree that the crontask should be made inactive - that would preserve the history.
    Is there a need for a new crontask instance every time?
    If not then just creatae one instance and then make that active again.

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.