Case Management Style Processes

[Dai_Williams]

Hi!

Debating some process design with a colleague and looking for some input

We have a case management style application that we are migrating from a low-code tool to Camunda. We have designed the user interface, however, from a process perspective we are considering how certain operations might take place.

The particular scenario we are looking at the moment is as follows …

1. User Logs In
2. User accesses case
3. User wants to update datai Items linked to case in an ad-hoc fashion
4. User presented with data update form
5. Data updated to the database following form submission

For this scenario, the overarching Case process is not affected, what we have done is simply complete a data update. We want to carry this update via Camunda and invoke a process that writes the data to the database.

My question is based around how this process is designed -

1. is it a very simple stand alone process that is invoked,
2. is there any scenario where this is part of a wider process setup,

in the first option, I get to re-use that process in several places so this is where we are heading at the moment.

Thanks!

[claudio_rio]

This is somewhat complex discussion and it would require a lot of discovery sessions
But, speculating, I’ll will assume that the process to create the case is already in place and also that steps 1 to 4 are performed in a custom UI (I could see it as a User Task too). The update part could be a simple process that receives an update request, does the update and notifies (if required) some other party about the outcome. In this case the Update UI would not actually perform updates but just submit update requests.

However, what will happen to the case itself while the update is being processed will dictate if the update operation should be in a separate process or not. The lifetime of the operations is a good indicator of when they should have their own processes or if they belong to together.