Change in the step name and in the class name that result from change at the UCM level should not be a surprise for the RAM designer in order to avoid a maintenance nightmare.

-- StephaneLeblanc - 01 Nov 2011

FormForFeature edit

Feature Name FeaMergeGeneratedWorkflowsWithManuallyWrittenRam
Sequence 650
Size 3
Description - If Step class diagram does not exist, create it
- If class does not exist, create it and map it with the corresponding reactive workflow class
- Manually written code shall NEVER be deleted/updated
- Do not clean up. That is, if a class diagram or a single class is not used anymore, it is the ram designer responsibility to delete it.
Author Stéphane Leblanc
Topic revision: r7 - 22 Mar 2012, StephaneLeblanc
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback