Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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
Created by Guest
Created on Jul 2, 2019

Publish xml segments

As a user of the Programming Patterns publish feature, I would like more control over how the xml file is created. When selecting multiple segments, and including their 'referenced instances', the referenced instances are not in the correct order or even grouped with the segment that they belong to. For example, if I select two segments, the two rpp:standardsegment elements are printed first and then all of the elements (unordered) are printed. I would like the elements to be sub-elements of the segment and in the same order as the -ce for that segment.
The workaround is to publish each segment individually and then copy/paste the documents into a single xml document.
Attached is a screenshot of the published xml document showing the two rpp:standardsegment first, followed by all of the rpp:dataelement in a random order.

Idea priority Low
  • Guest
    Reply
    |
    Dec 19, 2019

    I know that is not the way it currently works. I was asking for it to be improved. Because there is almost no reason to use publishing in it's current state. I don't think it is a bug. I think it could be better.

  • Guest
    Reply
    |
    Nov 19, 2019

    We have evaluated this request and determined that it cannot be implemented at this time because this is not the way the publication works. The part "referenced entities" contains all the entities referenced by the original entity but there is no order in the published list. If you think there is a bug, you can enter a PMR and we will provide you explanation about this.

  • Guest
    Reply
    |
    Jul 2, 2019

    Attachment (Description)