This blog will be the 1st in a serie of (likely 3) blogposts. All regarding the different approaches we tested with during our project in which we had Oracle BPM processes which were very content (a lot of documents) rich.
- Using attachment documents with Oracle BPM Human Tasks
- Using a Content Server documents with Oracle BPM Human Tasks
- Integration of Oracle BPM and Oracle WCC/UCM (soon)
First basic proof we needed is to make sure we can start a Oracle BPM process containing a document which then can be shown on the Human Task as attachment.
Lucky for us Manh-Kiet Yap wrote an excellent blogpost regarding this feature
We start the Oracle BPM instance with a SOAP XML message containing a document in Base64 format:
<soapenv:Body> <zaak:startCase> <bo:BO_CaseTrigger> <bo:caseTrigger> <v1:CaseType>someInfo</v1:zaakType> <v1:documentNaam>request.pdf</v1:documentNaam> <v1:document>JVBERi0xL.......olJUVPRg==</v1:document> </bo:caseTrigger> </bo:BO_CaseTrigger> </zaak:startCase> </soapenv:Body>
On the call to the Human Task we use the following mapping:
For the attachmentscope we select BPM, the other option is TASK and I actually think this would be sufficient since the attachment info is already in the process. But just to make sure, we select BPM as mentioned by Kiet in his blogpost.
- Attachment file names that use a multibyte character set (MBCS) are not supported
- Attachments of up to 1998K can be uploaded. You can modify this setting by setting the context parameter in
<context-param> <param-name>org.apache.myfaces.trinidad.UPLOAD_MAX_DISK_SPACE</param-name> <param-value>1998</param-value> </context-param>
Reference and all credits: