Community
Participate
Working Groups
I set the multiplicity values of a newly created property of a class in the Property view: 1. At the Multiplicity LowerBound field, click on the "+" symbol, select LiteralUnlimitedNatural and leave the given defaults (Name and Label empty, Value = 0) and click OK in the "Create a new LiteralUnlimitedNatural" dialog. The multiplicity of the property in the Model Explorer is not (yet) updated. 2. At the Multiplicity UpperBound field, click on the "+" symbol, select LiteralUnlimitedNatural and at the Value field type 5 (or an other number) and click OK in the "Create a new LiteralUnlimitedNatural" dialog. The multiplicity of the property in the Model Explorer is updated and correctly shows e.g. mymember : MyClass [0..5] 3. Go drink a coffee, write an email, be busy in other windows (not Papyrus). Look again at the Model Explorer: The multiplicity lower bound has changed! mymember : MyClass [1..5] I had not touched anything in the model, the change seems to have somehow happened spontaneously. 4. In the Properties View of the member at the Multiplicity LowerBound field, click on the pencil symbol and in the "Edit LiteralUnlimitedNatural" dialog, specify 0 in the Value field and click OK. The multiplicity displayed in the Model Explorer stays at the spontaneously changed value, mymember : MyClass [1..5] In other words, even explicitly setting the lower bound to 0 via the Properties View does not update the Model Explorer to the corrected value. Interestingly, doing the similar steps on the Multiplicity UpperBound has no problem - the Model Explorer update of the property's multiplicity upper value is done is expected.
Another piece of information: If in the Model Explorer I right click on the property and select Rename, the correct lower bound value is displayed: mymember : my::path::MyClass [0..5] {unique} I also checked the UML file and the value is actually save as it should be, <lowerValue xmi:type="uml:LiteralInteger" xmi:id="_HvF3MA2rEeiqk_zlia5Beg"/> Apparently it is a display issue in the Model Explorer.
