Hello,
I'm looking into using the CMF to support a number of different actions available to users in a back office application. As far as I can tell the documentation only considers a single workflow. I was wondering if I am supposed to create separate _CS modules for each workflow, with a CaseDefinition static entity for each. Or can I create multiple CaseDefinition records in a single _CS module.
The biggest issue I can see are the other configurations like the CaseStatusConfiguration. The SetupCaseManagementApplication() service action doesn't seem to have a way to account for that. I reckon I could separate StatusConfigurations and setup timers for each Definition.
Would this be a viable solution or am I missing something?
Turns out I did miss something. The SetupCaseManagementApplication action takes EspaceId as an input. As far as I can tell, it uses that to look for an entity in that module with a primary key of type CaseId. And it doesn't like it when there are multiple entities with CaseId as it's primary key.
Hi @Herre Bijl , Have you found our a way forward for this? Even my understanding comes to same point that if I have 30 different types of case in my requirements, I should have 30 different CaseDefinition entities under 30 unique eSpaces & that doesn't seem to be correct. Have you got any pointer for this? Or anyone who has has used cmf, can they please comment on my understanding and if I am wrong please guide me how to achieve that. I have to create cmf for 30 different types of cases with different SLAs & different statuses.
Any update on the above? I am also facing similar issue.
Yeah, that's what my previous post was about. What I ended up doing was having a single CaseDefinition and an entity set up with Case Identifier as its Id. That entity contained some info about which process was started. Then in the specific subprocess associate the case with that process and the related entity had a CaseId attribute.
This worked pretty well, but I will note that for me each Case had the same Statusses and transitions.
Thank you @Herre Bijl for the detailed information.