Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post 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


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Not under consideration
Components Swift
Created by Guest
Created on Jul 3, 2019

Possibility to display changes made in SYSADM before approval

We have activated Dual Authorization in FTM SWS as part of our CSP. We would like Approvers to be able to list, what was actually changed by person, who comitted the changes. 

list -ou % -qo O -lo NCSV - shows all configuration for that OU.

  • Admin
    PAUL HANILY
    Reply
    |
    Jul 8, 2022

    This idea is not under consideration at this time because of other higher priority items.

  • Guest
    Reply
    |
    Dec 6, 2019

    absolutely agree.

    In order to list a configuration entity, which is in status "committed" (ie approval is pending) or in status "approved" (ie. deploy is pending), some query options in addition to the list options must be used, but without helping much.

     

    Query options are:

    m - for modified state

    o - for committed state

    d - for deployed state (the default)

    a - for approved state

    z - for "approval rejected" state - ie. where an approver didn't approve the changes.

     

    For example:

    list -ou SYSOU -lo ncosvyw - qo o

     

    ….shows the configuration available for SYSOU in state “committed”, where the list options give you following information:

    • the name of the OU (query option n)
    • the CT name (query option c)
    • the CO name (query option o)
    • the Attribute name (query option s)
    • the assigned value (query option v)
    • the state of the OU (query option y)
    • the "existance state" of the CO (query option w)

     

    But please note - the list result returns ALL configuration, which are available for the OU, not only those configuration objects which have been changed/added or removed and for which the approval is pending. This is MISLEADING.

     

    If the approver wants to know, which changes have been done, he needs to additionally list the currently “deployed” configuration:

    list -ou SYSOU -lo ncosvyw -qo d

     

    …and manually COMPARE the list outputs to determine the changes made.

     

    The query option which applies to list a configuration entity in "approved" state (ie. deploy is pending) is -qo a.

    The same mimic applies here - a list will always return all configuration for the whole configuration entity, and needs to be compared with the currently “deployed”.

     

    From a usability point of view, this is error prone.

    I’d like to raise the urgent need to get a possibility to directly list only the changes which have been doneand waiting for “commit" and those waiting for “approve” and those waiting for “deploy” separately.

     

    Thanks & regards