Update Documentation for migration

Issue-ID: POLICY-4812
Change-Id: I8adbb39765bba68d0ca33d048c4b96c991129669
Signed-off-by: FrancescoFioraEst <francesco.fiora@est.tech>

1 files changed, 30 insertions, 0 deletions

diff --git a/docs/clamp/acm/plantuml/system-dialogues/MigrateAcInstance.puml b/docs/clamp/acm/plantuml/system-dialogues/MigrateAcInstance.puml
new file mode 100755
index 00000000..184e872a
--- /dev/null
+++ b/docs/clamp/acm/plantuml/system-dialogues/MigrateAcInstance.puml
@@ -0,0 +1,30 @@
+@startuml
+participant Rest
+participant "ACM Runtime"
+participant "ACM Database"
+participant Participants
+
+group Create New Composition type for Migration
+Rest -> "ACM Runtime" : Composition Definitions
+"ACM Runtime" -> "ACM Database" : Saved Definition
+Rest -> "ACM Runtime" : Prime Definition
+"ACM Runtime" -> Participants:  [ASYNC] Prime Definition
+end group
+
+group Migration per Instance
+/'Instance migration from source to target composition type. '/
+Rest -> "ACM Runtime" : Migrate Instance\n(InstanceId, sourceCompId, targetCompId, instance properties)
+note top
+Instance migration from source to target
+composition type.
+end note
+alt "instance Id and Composition Ids exist"
+  "ACM Runtime" -> "ACM Database" : Definition Validation
+  "ACM Runtime" -> "ACM Database" : instance and AC Element will be set\nin a transitional state (MIGRATING),\n new instance properties will be saved
+  "ACM Runtime" -> Participants : [ASYNC] Migration message from source to target composition
+  "ACM Runtime" -> Rest : Instance migration has been requested
+ else
+  "ACM Runtime" -> Rest : 400 Bad Reqest
+end
+end group
+@enduml