Hello,
We have a requirement to propogate the following connections when an Application is chosen to be compared and aligned between two repositories in mega
-Sent Message Flows and their associated content objects in mega
-Received Message Flows and any content objects associated to them
-Application Centric Diagram connected to that application
We went through the documentation a little bit, and created a custom perimeter with the following settings
Default major-minor behaviour- Abort
Default minor -major behaviour- Abort
Meta associations added to this perimeter-
Sent Message flow- (major to minor behaviour- standard, minor to major behaviour- standard)
Received message flow (major to minor behaviour- standard, minor to major behaviour- standard)
Message Flow/Content (major to minor behaviour- standard, minor to major behaviour- standard)
The result is that the message flows do get created, but -
- on the sent message flows, the application that should be connected to the " target element" meta association is missing / empty in the target repository
-on the recieved message flows, the application that should be connected to the " source element" meta association is missing / empty in the target repository
Request your advice on what we are missing - shouldnt the above meta associations be propogated as well?
