major
nice-to-have
minor
#25217
Layout-Export führt zu invaliden Komponenten-Referenzen bei Referenzierung einer bestehenden Komponente
#25327
Modell-Editor: Falsche Kompositionsmarker, wenn Container-Typ in Diagramm von Content-Typ gezogen wird
enhancement
Currently, a migration can consist of an SQL phase (before replay) and an optional replay.
Improvement
Migration phase following an optional replay, which allows for versioned changes at the KnowledgeBase level.
Usage
InsertMigrationPostProcessor into a migration description:
#!java
public interface MigrationPostProcessor {
void afterMigration(Log log, KnowledgeBase kb);
}
New " post-processors" section:
#!xml
<migration>
<version .../>
<dependencies>
...
</dependencies>
<processors>
</processors>
<migration>
</migration>
<post-processors>
<post-processor class="..."/>
</post-processors>
</migration>
See doc:AutomaticDataMigration
Test
No test.