Integration


This is an IBM Automation portal for Integration 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).


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

My ideas: webMethods Integration SaaS

Flow services should allow recursion

Use case: I need to iterate over a tree of documents returned by the SAP Signavio API (directory entry). I tried to write a flow service Process_Signavio_Directory_Entry processing one entry and then iterating over child entries, calling itself fo...
about 1 year ago in webMethods Integration SaaS Future consideration

Native Cross-Project Flow Service Integration Without API Calls

We want to structure our integrations across multiple projects by organizing them into distinct layers: one project per backend, several projects as a middleware layer, and multiple projects for the frontend API's. The frontend API's will use one ...
about 1 year ago in webMethods Integration SaaS Not under consideration

We can't copy paste flow steps from one flow service to another.

We can't copy paste flow steps from one flow service to another. Flowservices developers will benefit from it (increased productivity)
about 1 year ago in webMethods Integration SaaS Future consideration

Ability to use project variables in connector configuration parameters

When having a connector to a backend on two projects we have the problem that both connectors have a lot of the same configuration (endpoints, username, password). When a password changes we have to do the configuration multiple times. By using pr...
over 1 year ago in webMethods Integration SaaS Planned for future release

Make document types generated for (SOAP/REST) API flow services I/O reusable in other flow services

Hi, When creating SOAP or REST APIs also empty implementation flow services are created with populated "I/O" for inputs and outputs. These are based on the WSDLs or API specifications provided. The inputs/outputs are defined directly in the empty ...
over 1 year ago in webMethods Integration SaaS Planned for future release

Delete toggle Button in wm.io.Integration

In order to delete the inactive users in wm.io.Integration , We need the delete button option to be enabled for Admin Users to delete the users. Additionally, could you also please provide the delete users API so that we can automate the user clea...
over 1 year ago in webMethods Integration SaaS Future consideration

Creating document type without getting multiple sub document types

On premise WebMethods has the possibility to create a document type without getting all sub document types created as well. This is not possible in the cloud and for many larger xml schemas (such as the UBL standard) this can cause hundreds of doc...
over 1 year ago in webMethods Integration SaaS Planned for future release

Libraries of workflows and flow services shared between projects.

Currently we need to maintain identical flow services in 10 projects. The flow services perform the same function, and need to be kept identical when changed. It would be very timesaving and useful to use flow services from a shared library. I'm s...
over 1 year ago in webMethods Integration SaaS Planned for future release

Make it possible to use custom steps in flow services like the custom node.js transformers in workflows

Currently we can use flow services often with limitations, as our transformations are more complex to develop with them (about 100 steps) compared to creating a small node.js code block (about 10 lines of node.js code). There are some advantages o...
over 1 year ago in webMethods Integration SaaS Not under consideration

public API to resubmit failed instances

Hello, We need to implement a service to resubmit failed instances based on a workflowName. This would be particularly useful for us when dealing with a large number of failed workflows. Is there an API we can use to develop this type of service, ...
7 months ago in webMethods Integration SaaS Planned for future release

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.