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 that 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, on cloud):
Cloud Pak for Automation - incl Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - incl BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - incl Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
A business partner has a requirement where they do not want the creator user to be the owner of a document, but they still need to apply permissions to the creator on that document. The current #Creator-Owner place holder is too broad for their needs.
They want the creator to have specific rights but not the default rights - the user should not have rights to change permissions on a created document. They are already working with security parents, and are aware that they could apply security changes with sweeps (takes too long with many millions of documents), or with an event action (requires coding).
The business partner has suggested creating a new P8 place holder #Creator, much like the current #Creator-Owner, that would apply a default set of permissions to the document ONLY as the creator, and not make the user the owner of the document. Currently there does not appear to be a way to make this happen with OOTB functions, as setting the #Creator-Owner to null in the document class Default Instance Security does indeed cause the document owner to be unset, but also does not apply the #Creator-Owner permissions listed in the DIS to the document.
The requirements for this #Creator place holder are:
- The creator of the document does NOT have (the currently given through Owner) implicit rights to the document.
- Applies permissions only to the user who created the document.
Although it is possible to change the permissions afterwards with a sweep or event action, this new #Creator place holder would make the product more user-friendly and provide an OOTB solution to this problem. The business partner has many use cases where they want to change the permissions *only* of the document creator during creation, but can't do it any other way without either a lot of rework, or custom code.
Do not place IBM confidential, company confidential, or personal information into any field.