Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 IBM i
Created by Guest
Created on Jul 28, 2016

RDi Outline view separate Include values

Within RDi v9.5, the Outline view shows groups of Files, Data Structures, Fields, Constants, Indicators, etc. however when using modular development techniques with Copy/Include members there's no way to segregate these elements from the core source you're working on and those Copied/Included elements. It would be easier to navigate if there was a way to show included elements as separate branches within the tree structure. Those included elements could be shrunk down to focus on the core member you're working on at the time while still being available as needed. This information is obviously already available since RDi positions the core source to the Include/Copy line associated when clicking on an Outline view element. This would also be helpful by associating all subtypes as they're brought into the core source from externally described files rather than just stopping at input/update files able to be expanded to their field names. Our shop is trying to modernize from RPG/400 code to ILE RPG and the Outline view becomes less valuable when it's just a huge list of elements within each subtype that only lets you sort ascending and descending.


Use Case:

1. Within RDi, open a source member that makes use of Include/Copy members and compile/refresh the Outline view.
2. Either within "Global Definitions" or under each group type, provide a branch subset related to each Include/Copy member that shows the associated items. If the Include/Copy entries are under "Global Definitions", then within each expanded branch show the same subtypes as applicable. If the Include/Copy entries are instead listed under each subtype, then show the member name to be expanded to show its associated elements under that subtype.


Idea priority Medium
  • Guest
    Reply
    |
    Mar 15, 2022

    Thank you for taking the time to submit your request. After careful consideration, we know that we cannot deliver your requested enhancement in the near term, so it is being declined. However, your request does align with the future strategy of our product and we believe it may have future value, so we will add it to an internal list for us to keep in mind for the future.

  • Guest
    Reply
    |
    Jul 29, 2020

    We have reviewed this requirement and we feel it would be a beneficial enhancement to the product. We hope to be able to add it to our development plans in the future.

  • Guest
    Reply
    |
    Sep 21, 2016

    @sturowe
    We have nested includes as well and additional organization options beyond just an ascending/descending sort would still add value. A simple preference within the outline view settings to limit the number of nesting levels could provide the option of turning the feature off. Within the current function, even expanding the view to the full length of the screen adds no value when a subtype exceeds several hundred data points.

  • Guest
    Reply
    |
    Aug 12, 2016

    Another level of implied distinction in the outline might be overburdensome. There are so many distinctions now it is hard to locate things in the outline (is it a field, or an indicator, or a parameter?). I cannot imagine having to know the name of the originating include just to find something in the outline. Geez, we have several THOUSAND includes that are nested sometimes 12 deep or more.

    The beauty of the outline now is that it provides the list of all the stuff you have available to use without having to know where it originated.

    Perhaps some decoration or icon alteration on the item that labels it as "defined in the source member you are editing" versus "defined by including another source member" that the rest of us can TURN OFF because we don't care.

  • Guest
    Reply
    |
    Aug 4, 2016

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Reply
    |
    Aug 2, 2016

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Developer for Power Systems
    Component - RPG/COBOL Development Tools
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Application Development
    Operating system - IBM i
    Source - None

  • Guest
    Reply
    |
    Jul 29, 2016

    Creating a new RFE based on Community RFE #92337 in product IBM i.