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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
We need a Tool to Identify the Cause of HIPAA X12 Compliance Exceptions
Tool to Identify the Cause of HIPAA X12 Compliance Exceptions
NASCO routinely receives very large HIPAA X12 transmissions from their business / trading partners. (Very large meaning millions of segments and tens of thousands of transactions.) Onl...
ITXA: Enhancements to WTX Map Service
WTX for integration server gives us the WTX Map service for map translation . we needed it to enhance the functionality of the WTX map service to be able to accept the multiple input and provide multiple outputs dynamically.
Catching informations about WTX maps dynamically at runtime
The product functionality should be enhanced to make it possible for WTX maps to catch following informations dynamically at runtime 1. its own map name2. the associated WTX system, sub system and component to clearly identify the map3. on which i...
format string parser
Please add a parser/validator of format srings into the compiler, so that WTX developers are being notified of invalid format strings that won't work in the WTX engine.
Make the "use ellipses button" a display option
The Map Designer provides a way to use ellipses when draggin'-n-dropin' type references into a rule. This is very nice to make rules more compact and usually improves readability. However, "getting back" to the referenced type is sometimes an issu...
Include SSL library for zLinux Secure Adapter Collection.
We are using Message Broker and WTX Integration Server + Secure Adapter Collection to contact web services and transform the results. Unfortunately the SSL library (mercssl.so) is not included for zLinux like it is for other platforms. Please incl...
use ressource registry for mdq login data
In order to address the different configuration items between production, integration and development environment, WTX offers a ressource registry. We can define the different names of a queue manager, for example: $QMN in production resolves to Q...
static nature of calling TX maps from Java
currently, the APIs to call maps via Java works well. However, when a map is instantiated, it is via static method. Further attempts to instantiate the same class throws an error. IBM to look at this and see if there is someway to relax this behav...
DFDL support in ITX
The use of DFDL for data format definition is getting popular especially in IBM products. Please add DFDL into ITX as a standard
Enhance ITXA EDI Deenvelop service to return ProcessData by document
SPE Deenvelope service does not handle Multiple GS correctly. Currently, in cases where BP is invoked, we have a similar structure in the returned ProcessData. However, it only includes the EnvelopeID, so there is not enough information to use for...
Do not place IBM confidential, company confidential, or personal information into any field.