My question is related to configuration management in mega ? Configuration management is the traking of the object version .
A common scenario is multiple person woking on the same object or diagram, because they work on two different projects ?
Another scenario is the two architect one working on the existant version and other works on the to be state of the object, th object may be a simple application, a diagram, a POS
How to deal with these uses cases in a Mega with rdbms database ?
Solved! Go to Solution.
I would bring a clarification about my question with this simple use case :
I have to work on the recast of the architecture of a system of applications (group of application), I have to modify some applications attributes, add some message, modify diagrams, but i want to do that in a branch or a version because iam not sure if it will be validated and I have to discuss this with multiple person, so , I cant commit this on the basic repository,
So what to do, copy the database ? is there some versionning mecanism on mega ?, can we create a branch ofa bibliotech
Please share your experience !
If I understand, your question is 'how can I prototype customizations (metamodel, diagram types..)'?
A simple approach is this one
1) For small changes, work in transaction
A transaction can help prototype many customizations.
Note: so that changes are considered within the transaction, you will need to trigger the event 'refresh context'
However, you may need to dispatch your transaction as:
2) When working in transaction is not possible, build a specific development environment
You can use several environments if you have several working hypothesis.
A command files is valid for:
Trigger the event 'refresh context'
Best practises to extend metamodel