Hi Jaison,
when you upload the file to a workflow, the file gets stored and managed in the underlying Content Services Component and you can access it from there in Workflows using the UI elements (coach views) and service flows which the Content Management toolkit provides.
The default option for storing process instance related content is using the "internal" object store (also often called BPM document store). When designing your BAW solution, you can define at the level of the process application whether you also will allow the creation of (virtual) folder structures to manage process instance related documents.
Alternatively you could define a separate object store at the level of the content management component (FileNet Content Manager) which would allow you to persist files beyond the active lifecycle of the process instance. Again, you could create folder structures in this content repository if it is needed to manage the documents and you could even provide access to these documents using the Content Navigator client if users are supposed to access the documents outside the context of a process instance.
That said, it's best practise to avoid storing process instance related files into separate locations, e.g. a file system. However, if you need to do so, you can for example use the file systems related service flows available in BAW which allow you to write data to a filesystem (for a traditional installation) or a persistent volume (for container based deployments). However, this requires the filesystem/PV to be accessible to the BAW server. If this ootb component does not fit your need, you could write your own code and package it up in toolkit in order to e.g. write data to some filesystem on a remote server.
I hope this answers your question. If not, please feel free to explain your use case in more detail.
Best regards,
Michael
------------------------------
Michael Kirchner
Leading Technical Specialist - Digital Business Automation
IBM Technology
Germany
------------------------------
Original Message:
Sent: Thu September 22, 2022 08:59 AM
From: jaison chipuka
Subject: Working with files in Business Automation Workflow
Hi Michael,
I want to save the document to a specific folder after i have uploaded it.
Like writing to a separate filesystem
Regards
------------------------------
jaison chipuka
Original Message:
Sent: Fri September 16, 2022 12:01 PM
From: Michael Kirchner
Subject: Working with files in Business Automation Workflow
Hi Jaison,
can you please explain a bit more what you want to achieve?
The BPM file uploader coach view is intended to store a document into the BPM document store where it is associated to the process instance for which you added this document. Later on you can use for example the BPM document list coach view to access this document (in context of the process it was uploaded to).
Why do you want to save to document to a filesystem and return the path to the file? Do you want to perform further actions on the document?
Best regards,
Michael
------------------------------
Michael Kirchner
Leading Technical Specialist - Digital Business Automation
IBM Technology
Germany
Original Message:
Sent: Thu September 15, 2022 11:38 AM
From: jaison chipuka
Subject: Working with files in Business Automation Workflow
I am trying to upload a document to the process instance. using BPM file uploader. After uploading I'm getting the document ID and setting it to ECMID but I'm now failing to save the file on to the filesystem. How best can I upload the document to the filesystem and return the path of the document.
------------------------------
jaison chipuka
------------------------------