Support process applications (first iteration)

[nikku]

Supporting https://github.com/camunda/product-hub/issues/2458.

Introduction

Process applications are a feature of the Web Modeler that should be supported in the Desktop Modeler, too. Users should be able to work with and deploy process applications in the Desktop Modeler while still being able to work with and deploy single files at the same time.

Tasks

Beta Give feedback

1. Be able to create process application #4666
   enhancement in progress process applications +3
   
2. Be able to open process application #4675
   enhancement process applications ready +3
   
3. Be able to close process application #4687
   enhancement process applications ready +3
   
4. Be able to deploy process application #4667
   enhancement process applications ready +3
   
5. Be able to set Camunda 8 version in process application #4677
   enhancement process applications ready +3
   
6. Be able to add/remove resources to/from a process application #4688
   enhancement process applications ready +3
   
7. Be able to link resources in process application #4668
   enhancement process applications ready +3
   
8. Be able to open linked resources in process application #4676
   enhancement process applications ready +3
   
9. Process Applications UI #4664
   enhancement process applications ready +3
   

Out of scope

• Process Applications Sync Between Desktop and Web Modeler #4669
• Support versioning of a process application #4671
• Element Template Editor #4670
• Be able to configure preferences / settings / flags via UI #2913

---

Related to https://github.com/bpmn-io/internal-docs/issues/519

[philippfromme]

Architecture Discussion

I (@philippfromme) discussed with @barmac.

Key Points

• Process applications feature should be independent of React
• Process application files will be managed separately from tabs, rather than as a new supported file type that isn't opened in a tab
• No decision reached on supporting files only or folders

File vs. Folder Support

Files

Pros:

• Easier to implement (single file reading and writing already implemented)
• Flat list of files more closely resembles process applications in Web Modeler
• Potentially easier to use in both modelers

Cons:

• Deleting, renaming, or moving a file will break the process application

Folders (reading BPMN, DMN, and Form files only)

Pros:

• Adding a single folder automatically picks up all files within
• No need to explicitly add files
• Deleting, renaming, or moving a file will not break the process application

Cons:

• Requires folder reading functionality, which is currently not implemented

Next Steps

1. Create a diagram to visualize the proposed architecture at the C4 components level
2. Make a decision on whether to support files only or folders

@nikku I would appreciate your input.

[nikku]

I strongly support "folder reading support". We don't want to oversimplify our process applications feature, but support the full power of what pro-coders do:

• Resources relevant to the application may be arbitrarily nested within a certain root folder
• They may be moved, renamed, etc. and the app must react to that.
• In simple terms this can be accomplished by not only watching files (we already do this), but by watching a folder; we must watch it anyway in order to do smart background indexing (to derive intelligence)

[philippfromme]

Okay, we'll implement folders then. I'm also in favor of folders as I think with files only we'll end up wishing we'd implemented folders. 🤔