Camunda 8 Collapsed subprocess

[GRajaMca]

Hello, Team.

I’m attempting to use Camunda for some of my business needs.
During the investigation, we considered employing the collapsed subprocess to properly segregate the workflow.
However, the Camunda modeller indicates an error stating that ASub Process> must be enlarged. I’m concerned about how to tackle this situation.

Note: I am able to deploy this process and run the job on my instance. However, I am concerned about this issue. Will it cause any issues, or will Camunda’s support be deleted, and so on?

I’ve also included a screenshot of the sample workflow and the problem message.
Could you please advise me on how to resolve this problem?

Thanks & Regards,
Raja Gandharaw.
saveUsers.bpmn (5.2 KB)

[Niall]

It’s probably better to use a Call Activity - the reason why collapsed embedded sup processes are a bad idea is because they can’t be expanded in Operate so if some is happening in there it won’t be visible. Using a Call Activity will abstract the section of the model you don’t want to see but keep it visible if someone wants to look into it in runtime.

[GRajaMca]

@Niall

they

Yes, you are right. i was using the call activity only but the main problem for me is versioning. when am going through call activity i won’t be able to mention the version. some of my users still want to use the older version, which is not possible with call activity.