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


Status Not under consideration
Workspace App Connect
Created by Guest
Created on Nov 13, 2015

Include schemas in Retail Pack for validating POSLog messages with POS system specific extensions

Each point of sale system adds their own extension elements to the POSLog standard schema containing data that is captured by that point of sale system but may not have an element to map to in the out of the box POSLog schema.

In order to validate the content of these message extensions, you must have a schema with which to validate. No such schemas are included with the Retail Pack but some such schemas exist as they were provided upon request from IBM.

Idea priority High
RFE ID 79733
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Sep 19, 2022

    Idea / RFE Review. Unfortunately on this occasion we do not intend to take this suggestion further forward. This area is not a current business priority for us, and whilst the idea has been active since 2015 it has only gathered a single supporting vote.

  • Guest
    Sep 19, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Information Provided. Thank you for clarifying the use case. Perhaps one way forward in future would be for the pattern itself (or through actions applied after the instance is generated) to allow a user to provide further information about the extensions they would like to use. Potentially the pattern could also suggest potential extension options too. Status of the RFE is updated to Uncommitted Candidate.

  • Guest
    Nov 17, 2015

    The mapping of the data elements occurs in BizTalk and strict validation is enforced. Even if all the transformations occurred on the IIB platform - almost all do in this case - in order to map the element to the message box in BizTalk the element must be explicitly defined in the schema referenced by BizTalk. While the message coming out of IIB validates against the uncustomized POSLog schema, how would we know which elements to expect in the extensions in terms of names, data types, restrictions/valid values, and whether or not the element is optional or repeating?

  • Guest
    Nov 16, 2015

    Thank you for raising this Enhancement Request. The original intention of the development accelerator pattern in the Retail pack was to try and encourage the use of uncustomized POSLog schema as an industry standard canonical form, as it was felt this would have wider acceptance in the industry for downstream applications than to rely on data with IBM defined extensions. We also wanted to add value for implementations based on the 4690 point of sale input format, which may have been implemented with user-defined extensions, hence why the pattern accepts this input form of data but does not validate the extension elements on output. Typically we would like to encourage users to deal with data transformation within the context of the IIB message flow. So with this in mind, could you provide us some insight into the mapping actions which you would like to execute within Microsoft BizTalk so we can understand if there is scope for these to be brought into the use case within the IIB message flow ? This would help us understand if the requirement could be satisfied without needing to propagate the IBM user defined extensions beyond the IIB product boundary.