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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
It is also important to record details of who indicated made the change.
a useful front-end would allow someone to provide:
loginid of who made the change (gathered from the user session)
optional reason e.g. known problem X
optional associated helpdesk call freeform string e.g. SR123 (on the customer's helpdesk system) - for traceability
ability to remove the flag e.g. if I had patched the code/rule preventing the message being processed and then wanted to retry it
I would prefer an action based attribute e.g. donotprocessflg
administrators could mark a message as "do not process" and then the kafka crontask can avoid that and the message can be removed naturally when it becomes too old.
A "do not process" flag is particularly important for interface issues where a source system is sending messages that Maximo/Manage can never process.
In those cases it could be months/years before a fix is put in place. Administrators could create an automated task (auto script based crontask) that looked for the these failing messages and automatically mark them as "do not process".
In some cases the source system will never be changed and administrators just have to live with the incoming messages.
This enhancement is particularly valuable for large customers who experience lots of failures e.g. people trying to submit updates to workorders that have already been closed in Maximo.
IBM could really add value by providing sample crontask code that could be adapted to provide the functionaliy described above