Advice for Simultaneously working on (Form)-Models

Hello everyone,

as a team, we often work in parallel on our A12 models. Some of these are quite central and it is inevitable that several developers will work on the same document or form model at the same time. In this case, we come to the point, where the divergent versions of the model need to be merged back together. This often leads to conflicts. We find this problematic when the conflicts affect the same areas of the document. Especially in the form models. Since the conflicts are resolved in plain JSON and the reference to the specific fields is not immediately recognizable due to the generated id’s (button-12345). The problem is amplified when the conflicts occur, for example, in dependent fields or something similar.

Does MGM have an established procedure for working on models in parallel? Is there possibly a best practice or even technical optimizations that we are not yet aware of (possibly only in upcoming releases, e.g. directly in the SME) or is there a specific toolset for resolving conflicts?

In planning, we are actually currently trying to schedule work on a model sequentially. However, this seems a bit antiquated and can lead to delays and bottlenecks.

I look forward to your reply.

Best regards

Hey @mathias-early-ravine, thanks for your question.
From a modeling perspective we advice NOT working on the same model in parallel. A12 doesn’t provide an out of the box functionality for conflict handling/ management
I suppose your use case would be possible in general, but requires a custom solution in terms of preventing and/ or resolving conflicts.

Best,
Nico (BPS-Team)