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
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,
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 notification 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
Granting Navigational Access instead of full Read access to Business Entities above Security Context Point
Consider the below Business Entity hierarchy:
Level 0 BE -> Level 1 BE -> Level 2 BE -> Level 3 BE
If a users security context point is /Level 0 BE/Level 1 BE/Level 2 BE/Level 3 BE, then the user can still access the details of all the top level Business Entities in the primary parent path of 'Level 3 BE'. Instead of granting full READ access to the Parent BEs, wouldn't it be better to just provide Navigational access where you can navigate from Level 0 BE to Level 3 BE but the user cannot view details of Level 0 BE through Level 2 BE.
Yes, we can apply Field Level Security Rules, but just granting navigational access would be a much cleaner approach as there is a maintenance involved (to the rules) when new fields are added.
Do not place IBM confidential, company confidential, or personal information into any field.