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:
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 product management 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.
Additional Information
To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps
Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
IBM Employees:
The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io
Hi,
Would like to check that if there is any update regarding this enhancement request?
Hi Paul,
Thanks for your prompt response.
Your scenario is correct. User 1 can either 1) use the ‘set to ready’ function in overview page to change company status to ‘ready’, or 2) enter into company workflow, click submit button under ‘Submit’ tab (even when there is no visible form under ‘Populate’ tab due to forms security).
Client would like to be able to restrict access/security by submission, for example user 1 has access to submission 1 only. Upon login to controller web, only submission 1 is visible to user 1. Alternatively, if the afore mentioned is not possible, prevent/prohibit users from using ‘set to ready’ function or ‘submit’ button to update company status to ‘ready’ where they are not supposed to.
So we understand the scenario to be like this: 2 users and 2 submissions. 1 user has access to the forms in Submission 1 and the other user access to the forms in submission 2. The issue we think you are saying is that User 1 can set the submission 2 to ready even though they do not have access to the forms in submission 2. Is this correct?