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:
Post your ideas
Start by posting 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Implement security for creating, modifying and removing ETT
IWS provited a detailed protection for the most objects via authority groups. Creating, modifying and removing ETTs in the database does not have similar security features as the authority groups implements. It is just possible to protect ETT elements by their name or the application name. Since our organisations changed over years, not an certain group of users just still manage ETTs and applications. All business groups plan, schedule and supervise their application by their own. However, all users which can create applications and therefore ETT objects have update permissions for all ETT objects in the database.
Actor: Users with update permissions for application of a certain authority group
Use case for the system:
Protecting ETT objects in the database for applications based on the update permissions of users for applications of different authority groups.
A User try to create/update/remove an ETT object from the database.
1) The user have update permission for the application which the trigger points to: The operation is permited by IWS.
2) The user does not have update permission fot the application which the trigger points to: The operation is denied by IWS.
Do not place IBM confidential, company confidential, or personal information into any field.