Skip to Main Content
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.

Status Not under consideration
Categories Integration
Created by Guest
Created on Aug 21, 2021

Allow asynchroneous processing for publish channels

When there are publish channels attached to an object in Maximo, system would run all logic in relevant user exists / filters / processing classes in the same thread where save() on the object was called. If outbound processing is complex, this causes delays in the UI.
E.g. when user save a Work Order, all this outbound logic is executed before control is passed back to the user.

If we take applications which can update records in bulk, e.g. Graphical Assignment specifically , if a user touched , say 50 Wos in there and clicked Save, system will run all logic for all publish channels for all these 50 orders before control goes back, this takes minutes.

It would be good to have a setting in the publish channel that would allow to run integration logic in background without delaying the UI.

Typical solution which is used in these cases is to put a flag on the record or in a separate table which would just say that records needs to be sent out, and then escalation would pick it and process.

A feature in the core product would have significant value.

Idea priority Medium
  • Admin
    Kim Woodbury
    Reply
    |
    Dec 3, 2021

    Thank you for your submission - this is not considered for a future releases. This goes against reliable messaging principles of publish channels which ensure transactional boundary between the save of the MBO and save to JMS/Kafka.