Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
72:phase_freezes_prepare [2019/10/17 21:50] – emr | 72:phase_freezes_prepare [2024/02/15 00:00] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 6: | Line 6: | ||
* Process updates need to preserve the element identities. Do not use the "adopt elements" | * Process updates need to preserve the element identities. Do not use the "adopt elements" | ||
- | * The scrope | + | * The scope of the phase to freeze needs to be defined. |
* Children of a process element are paths of their parent and therefore must be part of the same phase as the parent element. | * Children of a process element are paths of their parent and therefore must be part of the same phase as the parent element. | ||
* Metrics cannot be frozen, as they can have arbitrary data sources. | * Metrics cannot be frozen, as they can have arbitrary data sources. | ||
Line 29: | Line 29: | ||
==== Configure Phase Freeze Support in the Metamodel ==== | ==== Configure Phase Freeze Support in the Metamodel ==== | ||
- | Phase Freeze needs to be enabled in the process metamodel in <font inherit/ | + | Phase Freeze needs to be enabled in the process metamodel in Process.xml. There you have to specify which subtypes of which element represent the entity to be frozen (phase root). In a typical case, you want to freeze a phase of your process, but not milestones which are also of type phase. Additionally, |
< | < | ||
Line 45: | Line 45: | ||
</ | </ | ||
[...] | [...] | ||
- | </ | + | </ |
</ | </ | ||
Line 149: | Line 149: | ||
moduleAssocToCommentSet); | moduleAssocToCommentSet); | ||
} | } | ||
- | Collections.addAll(moduleElementSet, | + | Collections.addAll(moduleElementSet, |
</ | </ | ||