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
Workspace z/OS Connect
Created by Guest
Created on Jun 12, 2017

Filter API's into ZCEE Server view

View all API's into ZCEE Server view must be "dangerous" and/or useless. Two ways to resolve that: 1- A user see only his API's (requires a notion of "belonging to a group")
2- A user can filter his view like RDz or RTC

Idea priority Medium
  • Guest
    Reply
    |
    Oct 13, 2017

    This RFE has been evaluated by development, and is being rejected as the requested capability already exists. Through use of the Authorization Interceptor and correct assignment of users to role-based groups for admin, operator, reader or invoker, and configuration of a these role-based groups for related sets of APIs and services, the desired behaviour can be achieved.