0
votes

We had built a custom workflow in our project and we are looking to migrate to a BPMN 2.0 standard workflow management tool. While doing our analysis, we chose Camunda as the preferred tool (Community Edition). However, we need to continue to support a feature to create an adhoc task. (task created outside of a workflow process)

Can anyone respond if that's possible? If yes, what are the downsides or things to lookout for if the approach is chosen.

2
What are the properties of the task? Or is it just to be documented?jklee
It will be a user task. Assigned to the user in an adhoc manner and hence the adhoc task. It need not be tied to a specific workflow per say.Karthik Shivkumar

2 Answers

1
votes

You can create a task without connection to a process via API (see https://docs.camunda.org/javadoc/camunda-bpm-platform/7.6/org/camunda/bpm/engine/TaskService.html#newTask() for Java API). You do not have any "Task Definition" in that case, so you have to provide all necessary properties (name, assignee, priority, duedate, ...) yourself. Afterwards it follows the normal task lifecycle though.

0
votes

I would build a generic process like this: Adhock task

Set task description and assigne Here, the creater can set any task description for the worker and assign the task.

Processing task The worker execute the task description and finish the task.

For creating the forms you can use embedded task form https://docs.camunda.org/manual/7.6/user-guide/task-forms/#embedded-task-forms