Hi Michel,
we don't want to use the CPE eventframework.
When users add documents, the entry template by configuration set the security folder. But in some cases the document is created in an activity step (use of Content integration) which doesn't include the security permissions update (CMIS limitation ?).
So in our workflow, we have a java service which sets the security folder thru the CPE API. The only annoying thing is that we need to store the CPE connection informations (URI, user, password, domain, object store) especially the password.
How is it possible to define the password with encryption in the workflow ? We don't want to manage a properties file for that.
That's why we ask about the usage of the 'BPM Target store' object. The requested password is already defined in it.
Thanks
------------------------------
Yannick Martin
------------------------------
Original Message:
Sent: Tue June 08, 2021 04:36 AM
From: Michael Kirchner
Subject: Override Content Management toolkit
Hi Yannik,
without knowing further details on the use case, I'd not recommend to introduce the workflow overhead to address this requirement. If you only want to apply the parent folder security to a document upon creation time, I'd rather recommend to use either a code module which leverages Java CPE API or even an event action based on the JavaScript API instead. Either way the CPE directly calls this code from the event (creation event for the document) and does not create a workflow instance for doing so. Actually, you may want to take a look at this link:
Example
Creating a toolkit which uses the CPE Java or GraphQL API to achieve the same as part of a workflow makes sense in case the workflow really triggers this action (i.e. a user approves a document and this would require that the permissions of the document need to be changed). In that case you already have a workflow and you want to manipulate a content object as part of the workflow.
Triggering a workflow from a content event (document creation or file to folder) just to perform a content operation (update permissions) in that workflow is a significant overhead which I would recommend to avoid, even though it is doable, of course.
Best regards!
------------------------------
Michael Kirchner
Leading Technical Specialist - Digital Business Automation
IBM Technology
Germany
------------------------------