This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. 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.
From Eric Theriault,
Automation rules are not ideal for this use-case — specifically, it is possible for things to be dropped or missed for a variety of reasons, requiring further reconciliation, and I don’t think this is a fair use of the platform. Webhooks would be a viable alternative, however, this can yield to duplicate requests and also not have guaranteed deliver so for this use-case, it may not be ideal.
Automation Rules Best Practices
The Streaming API has a default connection timeout of 10 minutes, and the underlying queries have a 30-second timeout. Two implications for their design:
The query filter must be simple enough to complete within the 30-second query guardrail.
The integration should estimate the volume it intends to pull and split the work into batches/pages rather than attempting a single large fetch. For data sets in the millions of records, chunked retrieval is required, not optional.
For their reference while building, the common REST API failure modes and fixes are documented here: https://www.ibm.com/docs/en/targetprocess/tp-dev-hub/saas?topic=v2-troubleshooting-rest-api-issues .
Original email from Arindam
Hello Kathy,
Sorry for the delay in responding to your email.
We have a use case that requires fetching data from the ATP V1/V2 endpoints for a given entity whenever a change is detected in the source data, including any derived fields. We are looking for a webhook-based mechanism that can capture these changes and publish corresponding events to a Pub/Sub topic. Our downstream process will consume these events and update the warehouse tables accordingly.
The objective is to enable near real-time (NRT) refreshes of destination datasets, ensuring that downstream consumers always have access to the latest data for financial planning and reporting purposes.
Please let me know if you have any questions. Thank you.
Best Regards,
ARINDAM BHATTACHARJEE (HE/HIM)
SR. MANAGER - DATA ENGINEERING
TECHNOLOGY BUSINESS ENABLEMENT (TBE)
AMERICAN EXPRESS
M: +91-8272971344 | E: arindam.bhattacharjee@aexp.com