This is an IBM Automation portal for Digital Business Automation 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
Cloud Pak for Automation - including Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - including Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager
Automation Decision Services (ADS) - including ADS, Operational Decision Manager
Robotic Process Automation
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
Specific links you will want to bookmark for future use
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.