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.
-
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...
-
Claim Level Reject at the Provider, Subscriber or Patient Level
We have received the explanation that claim level rejection works as designed in the 2300 Loop of the 837 and does NOT have rejection capability in the Provider, Subscriber and Patient Loops. Based on our competitors’ capabilities and our client n...
-
ITX 10 Design Server import into B2Bi (no ITX-A installed)
We need something in the Design Server to help us deploy the .sl and compiled maps to a B2Bi Server (ITXA is not in use here.)
-
Support ITX on Alpine Containers
This would benefit those who want to use a smaller container image that is more secure with fewer Linux library dependencies.
-
ITXA - Inactive Partner Report
Create a reporting process or last envelope modified date so inactive partners can be identified. Inactive partners can be partners with no activity greater than 30 days or 60 days (possible configurable parameter).
-
USE OF -F OR -FILE PARAMETER SHOULD NOT BE NEEDED IF USING THE THIRD PARAMETER IN THE GET() FUNCTION AS SEEN IN ITX 9.0.0.2
On ITX 9.0.0.3, the document says, The -FILE command is optional on input cards and GET rules. (For example, the workbook name is not required if a map uses the File adapter to read an Excel workbook and passes the data in memory to the Excel adap...
-
Option to fail map warning return codes
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.
0
Not under consideration