Creating a subprocess again and attaching to parent process
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2016 02:34 PM
I am evaluating Activiti workflow for using it in our company. I wanted to know how do we handle some of the Business Use cases here.
We have a main 'application' business process and it has numerous steps. I am modeling the 'application' as main process and the steps as subprocesses. One of the step is 'photo upload'. As part of the parent process of 'application' the 'photo upload' sub process will be called. After the photos are uploaded, the subprocess is done. But the business team says that as part of the business, there should be option of uploading the photos again after they have finished them. In terms of Activiti workflow, it boils down creating another subprocess for photo upload and attaching to parent process of 'application'. Can this be done or can you shed some light on better approaches for this issue.
Thanks
We have a main 'application' business process and it has numerous steps. I am modeling the 'application' as main process and the steps as subprocesses. One of the step is 'photo upload'. As part of the parent process of 'application' the 'photo upload' sub process will be called. After the photos are uploaded, the subprocess is done. But the business team says that as part of the business, there should be option of uploading the photos again after they have finished them. In terms of Activiti workflow, it boils down creating another subprocess for photo upload and attaching to parent process of 'application'. Can this be done or can you shed some light on better approaches for this issue.
Thanks
Labels:
- Labels:
-
Archive
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2016 09:23 AM
Hi,
We have a very similar requirement as yours. The way we addressed is by saving the photos to alfresco and having the doc id inserted into one of the application tables which holds doc id and its corresponding process instance id. So no matter how many documents they upload, they all are relevant to just one process instance.
I recommend having a different Identifier(like application id or something) also to be saved along with doc Id and proc inst id so that you can fetch the documents easily when required at a later point of time when the process is completed.
We have a very similar requirement as yours. The way we addressed is by saving the photos to alfresco and having the doc id inserted into one of the application tables which holds doc id and its corresponding process instance id. So no matter how many documents they upload, they all are relevant to just one process instance.
I recommend having a different Identifier(like application id or something) also to be saved along with doc Id and proc inst id so that you can fetch the documents easily when required at a later point of time when the process is completed.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2016 06:17 PM
Thanks Asriharikiran for your input. We are following similar approach of using the processInstanceId saved in our db.
