Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 Future consideration
Categories Modeling and UI
Created by Guest
Created on Jun 30, 2022

Enhance behavior of Table views using Branch

Currently the behavior of Table view when using Branch "|" is new row is created separately for each values. Example: context pattern: {FlowProperty} FlowProperty, {Comment} Comment | {Rationale} Rationale | {Requirement} Requirement table rows: FlowProperty Comment Rationale Requirement flowproperty_0 comment_1 rationale_1 requirement_0 flowproperty_0 rationale_0 flowproperty_0 comment_0 And expected behavior is to have one row in the table for each combination of values. context pattern: {FlowProperty} FlowProperty, {Comment} Comment | {Rationale} Rationale | {Requirement} Requirement table rows: FlowProperty Comment Rationale Requirement flowproperty_0 comment_1 rationale_1 requirement_0 flowproperty_0 comment_0 rationale_0 requirement_0 flowproperty_0 comment_0 rationale_1 requirement_0 flowproperty_0 comment_1 rationale_0 requirement_0 Kindly share your feedback.
Idea priority Low
Needed By Not sure -- Just thought it was cool
  • Admin
    SANTHARAM SUNEEL
    Reply
    |
    Aug 1, 2022

    Thank you for sharing the details will consider in the future.

  • Guest
    Reply
    |
    Jun 30, 2022

    Current behavior

    FlowProperty

    Comment

    Rationale

    Requirement

    flowproperty_0

    comment_1

    rationale_1

    requirement_0

    flowproperty_0


    rationale_0


    flowproperty_0

    comment_0



    Expected behavior

    FlowProperty

    Comment

    Name in Rationale

    Name in Requirement

    flowproperty_0

    comment_1

    rationale_1

    requirement_0

    flowproperty_0

    comment_0

    rationale_0

    requirement_0

    flowproperty_0

    comment_1

    rationale_0

    requirement_0

    flowproperty_0

    comment_0

    rationale_1

    requirement_0