These are the bugs that have been recently resolved in MetaModelAgent. Any remaining open bugs can be found in the list of open bugs.
These are the bugs that have been recently resolved in MetaModelAgent. Any remaining open bugs can be found in the list of open bugs.
|4.5.1||MMA-2459||General UML guidelines, Papyrus||
Incorrect association end labels in General UML Guidelines for Papyrus
|The labels for several association ends are swaped in the diagrams in the General UML Guidelines metamodel for Papyrus. The underlying model is correct, but the display of association end labels, e.g. multiplicity and name have been swaped. Users of the model will be confused.|
|4.5.1||MMA-2457||General UML guidelines, Papyrus||
Profile diagrams do not allow profiles when using General Modeling Guidelines
|If a profile diagram display the profile element, an error is reported as invalid diagram content.|
|4.5.1||MMA-2455||UI Chart View||
Tooltip on horizontal labels in bar chart does not respect diagonal labels
|Wrong tooltips are displayed due to diagonal labels.|
|4.5.1||MMA-2454||General UML guidelines, Papyrus||
Redefinition context should be removed from General UML Guidelines for Papyrus
|Redefinition context is not available in the advanced tab of the standard property view in Papyrus and should therefore not be available in the General UML Guidelines for Papyrus|
|4.5.1||MMA-2453||RSA, UI Wizards||
Closed metamodels in workspace could not be retrieved in the New Model Wizard when using RSAD and RSARTE
| If a closed metamodel from the workspace is selected in the New Model Wizard. That metamodel will not be opened and cannot therefor be used for the new model.
The workaround is to open the metamodel in workspace prior to invoking the New Model wizard.
Incorrect diagram section on guidelines web pages if referrered metaclasses has mixed submetaclass categories
|If a diagram metaclass has a shared aggregation to a metaclass that have sub-metaclasses of mixed categories (e.g. elements, relations). None of the metaclasses in the inheritance hierarchy will be listed as potential diagram content.|
|4.5.1||MMA-2447||General UML guidelines, Papyrus, UI Diagram & Palette||
Metamodels based on General UML Guidelines do not allow all kind of elements in static diagrams
| All elements should be allowed as nodes on static diagrams.
But only packagable elements should be available in the palette.
|4.5.1||MMA-2443||Guideline Reporting, RSA, UI Wizards||
Some registered but unloaded UML profiles cannot be found by MetaModelAgent
| Profiles registered using pathmaps defined by extensionpoint "org.eclipse.gmf.runtime.emf.core.Pathmaps" cannot be load because the pathmap definition is not resolved correctly.
This holds for some built-in profiles in RSAD.
The effect is the creation of new models using those profiles fails and publishing guidelines only using those profile failes, as long those profile has not unready have been loaded caused by reference from some other model.
Html-encoding is visible in some tooltips if the metamodel elements contains special characters
|4.5.1||MMA-2428||Model Reporting, RSA, UI Property View, UI Summary View||
Comments are not regarded as documentation if model lacks application of "Default" profile
|4.5.1||MMA-2426||General UML guidelines||
General UML Guidelines does not support stereotype, keyword and documentation property for some relationships
|The elements that not have stereotype, keyword and documentation properties defined are; Generalizations, Element Import, Package Import, Package Merge, Protocol Conformance, Template Binding,|
User defined stereotype "Standard" conflicts with built-in reserved word
| The word "Standard" is used internally in MMA to dentotes a standard property for a UML element.
That leads to a conflict resulting in a reported error when the word "Standard" is used for a stereotype containing user-defined properties.
|4.5.1||MMA-2421||UI Property View||
Accessing defining feature of a slot may cause a runtime exception
| This bug was introduced in v4.5.0 build 005.
Resolved in v4.5.0 build 007.
|4.5.1||MMA-2418||Model Reporting, UI Summary View||
Consecutive spaces in element documentation are displayed with visible encoding
|Resolved in v4.5.0 build 007.|
|4.5.1||MMA-2417||Model Reporting, RSA, UI Common, UI Summary View||
User-defined element icons not defined in profile will not be displayed in UI views or generated web
|Some profiles extended deployed in a plugin will have their icons defined programmatically instead of in the profile. These icons will not be displayed in MMA UI.|
|4.5.1||MMA-2415||UI Property Table View, UI Property View||
User-defined properties with element as type cannot be set if the property type is an inherited stereotype
|Resolved in v4.5.0 build 007.|
|4.5.1||MMA-2413||UI Property View||
User-defined properties with element as type cannot be unset
| Pressing the delete bottom \[X] has only temporary effect in the view but the reference to the element is not removed in the model.
Resolved in v4.5.0 build 007.
The most specific metaclass is not selected when there are several that matches an element
| The most specialized metaclass in an generalization hierarchy should be selected.
When a contrete (super)metaclass is referred that has overlapping submetaclasses. The supermetaclass is incorrectly selected. This bug was introduced in 4.5.0 build 005.
Resolved in v4.5.0 build 007.
|4.5.1||MMA-2394||General UML guidelines, Papyrus||
Papyrus freezes when a diagram in General UML Guidelines metamodel is enlarged
| This might be problematic when the metamodel is used as a template for a new metamodel
The reason might be that the diagram originally was created for Papyrus 2.x
|4.5.1||MMA-2388||UI Property Table View||
Exception thrown when bringing up context menu from Property Table View containing unidentified items
|This occur when initiating Property Table View from Chart View with a bar that represents unidentified items|
|4.5.1||MMA-2372||UI Trace Matrix View||
Some none-circular connections remains when circular filter is applied in Trace Matrix View
|4.5.1||MMA-2371||UI Trace Matrix View||
Legend is not updated when circular filter is activated
|The legend shows number of relations prior to the filter is activated.|
Web publishing not available with FREE license
|When trying to publish a model being activated using a FREE license, the insufficient license dialog pops up and indicates that you already have an activated model|
|4.5.0||MMA-2369||UI Property View||
Renaming elements using standard UI when MMA Property View is opened causes rollback
|Changing element names using standard property view, diagram editor or model explorer causes the previous name to be set again. It appears like a rollback.|
|4.5.0||MMA-2367||Linux, UI Trace Matrix View||
Matrix table not aligned with target headings in some Linux environments
|The difference in font size in different environments has led to the matrix not being aligned to the vertical target labels.|
|4.5.0||MMA-2366||Linux, UI Property View||
Check boxes for boolean property values are not visible in some Linux environments
|In Ubuntu Linux, the checkbox is not visible, however it shows the check-icon when checked.|
|4.5.0||MMA-2365||UI Trace Tree View||
Trace Tree View shows incorrect content when initated from derived content in Trace Matrix View
|4.5.0||MMA-2364||UI Trace Tree View||
Icons are missing and execption is thrown for multiple relations in Trace Tree View
|This issue occurs when the Trace Tree View is initated from the Trace Matrix View in transitive mode.|
|4.5.0||MMA-2363||Linux, UI Guidance View, UI Summary View||
Incorrect formatting in some embedded web browsers
|If the text to be displayed contain special characters, the formatting provided by CSS will not be applied. This has been detected in OpenSUSE 15.0|
|4.5.0||MMA-2351||UI Problem View||
Same metamodel problem occurs multiple times in Problem View
|4.5.0||MMA-2344||Papyrus, UI Property Table View||
Elements deleted using property table view context menu will still remain as incorrect nodes in diagrams
Nested unidentified element is still registered as activated even when root element has been inactivated
| Steps to reproduce:
# Activate a model that contains an unclassified element.
# Inactivate the model
# Select the unclassified element
# Open MetaModelAget->Acivate and you will see that the unclassified element is still checked as activated
Web publish hyperlinks that populate both frames in one click does not work in some browsers
| This holds at least for Firefox when the published web site is accessed locally.
The solution is to redesign so that only one frame at a time is updated
|4.5.0||MMA-2332||UI Guidance View||
Explorer navigation from Guidance View fails in several situations
| The navigation (by pressing the explorer button) do not works for metaclasses that have been displayed by following a hyperlink or the back button in the Guidance View.
The navigation do not work for pages displaying the metamodel either.
|4.5.0||MMA-2330||UI Property View||
Dependency target could not be cleared using MMA Property View
Adding an association or one of its subclasses using General UML Guidelines opens the Change Wizard
| When drag & drop of Association, Extension or Communication path fom palette to diagram. If preference automatic change is set, the change wizard is shown where you once again have to select the correct metaclass.
This should not be needed.
Connectors within a behavior classifier web page has same source and target
There is an incorrect built-in rule that the name of Property-elements must be non-empty
|The UI wizards indicates an error if the name is left empty.|
Directed relationship with multiple sources are not identified
Exception thrown in web publisher if there are references to unloaded/unsolved enumeration literals
|4.5.0||MMA-2308||UI Trace Matrix View, UI Trace Tree View||
Populating Matrix View or Trace Tree View with potential activity flows for activities lacking a start node throws exception
|4.5.0||MMA-2302||UI Property Table View, UI Property View||
Control Flow & Object Flows guards and weight properties have an obsolete item selection button
|The guard and weight property should only have editable text fields.|
|4.5.0||MMA-2299||UI Diagram & Palette||
Exception thrown in Diagram palette
|Error message: java.lang.IllegalStateException: IWorkbenchSite.getShell() was called after part disposal:|
|4.5.0||MMA-2298||UI Property View||
Signature could not be cleared from Message when using MMA Property View
MMA-Add wizard does not support adding Combined Fragments, Gates & InteractionUse to an Interaction
|4.5.0||MMA-2293||UI Trace Matrix View||
Trace Matrix View columns do not support icon width other than 16 pixels
| If the icon has a different width than 16. The width of the columns in the first header row will not match the column width in the other rows
This is the case when populating the Matrix View with control flows from an BPMN activity diagram.
Each column width should be adjusted to the actual width of the icon or the icon should be cropped to fit 16px
|4.5.0||MMA-2292||UI Trace Tree View||
Object nodes in activities are invalidly reported in outgoing trace tree view starting from the activity
|When populating the Trace Tree View from an activity containg object nodes, the object nodes are reported as being relationships/references and the element column displays "non-existing element".|
|4.5.0||MMA-2291||UI Trace Tree View||
Exceptions thrown when populating tree view with Potential flow paths if the activity contains activity partitions
| If MetaModelAgent->Show in Trace Tree View -> Outgoing Relations -> Potential flow paths is selected on an initial node within a partition then an com.adocus.mma.ui.views.common.ViewSourceException is thrown
API-method com.adocus.mma.api.getUmlMetaClass() throws exception if the element has not been classified
|4.5.0||MMA-2266||UI Chart View||
Incorrect result in scatter chart and related elements bar chart when relation distance are set to limited
|This occur when the distance is set to 3 or more but still limited and there are different relationship paths that shares the same node on different distances from the start element.|
|4.5.0||MMA-2254||UI Property View||
"No more handles" exception thrown when both standard Property View and MMA Property View is opened
|Exception is thrown the selecting a widget in MetaModelAgent tab of standard Property View when the MMA property view is open as well.|
Wizards have not scrolling capabilities when there are many properties to display
|The scrolling capabilities in wizrads that existed in MMA 4.3.x does not work any more,|
|4.5.0||MMA-2241||UI Property Table View||
The cell color in Property Table View is not always automatically updated when property value is changed in a cell text field
|The background color should change automatically to indicate a invalid property value or that a problem is solved by the new proeprty value. Currently you will have to refresh the view to update the colors|
Exception is thrown if a metamodel refers to a stereotype that does not exist in the referred profile
|4.5.0||MMA-2237||UI Trace Matrix View||
Matrix View could not be invoked from metaclass packages or metamodel root
|Show in Matrix View is always disabled in the context menu when a metaclass package or a metamodel root is selected|
|4.5.0||MMA-2211||Guideline Reporting, Model Reporting||
Invalid thread access when looking up workspace profile during model and metamodel reporting
|This occur when publishing is done directly after loading+activation|
Metaclass classification remains after ongoing activation has been cancelled
|If an activation is being cancelled in the progress monitor dialog, ome allready validated elements remain their classifications and exceptions will occur in some situations.|
|4.4.1||MMA-2231||UI Diagram & Palette||
Instance specifications does not occur on the diagram palette
|Even thus a metamodel says that a diagram can contain an instance specificatíon. New corresponding tool occur in the MMA palette.|
Relationships cannot be drawn between elements using different metamodels
|This bug was introduced in version 4.4.0|
|4.4.1||MMA-2225||UI Property Table View||
Stereotype on singular elements could not be changed using the cell editor in Property Table View
|Bulk editing works fine as a work around, if more than one element are selected.|
Some kind of elements in diagrams will not be considered when validating diagram content
| If a metamodel ruls explicitly requires specific item kinds in a diagram, the rule will never match elements that occurs in top-level nodes such as properties, operations, actions.
All kind of elements, except relations, diagrams, connectors and constraint should be considered.
|4.4.1||MMA-2220||Model Validation, Papyrus||
Manual loading of nested submodels are incorrectly handled as new activations
| If a nested submodel within an already activated model is loaded manually. The submodel is treated as a separate model and will result in a new activation.
The correct behavior would be that the loaded submodel are included in the activation of its parent element.
Methods in the IMetaModelProvider interface are obfuscated
|Some methods are obfuscated, making it harder to provide metamodel lookup|
|4.4.1||MMA-2204||UI Chart View||
Incorrect bar chart when elements from several different metaclasses with the same metaclass name should be displayed
| This occur in Relations Bar Chart when elements from different metamodels are displayed and in Nested Element Bar Chart when there are nested models.
It will also occur in Problem Bar Charts where stereotypes are displayed.
One common case is when a metamodel is inherited from another and both are applicable for the elements to be displayed.
The effect is that there is a missmatch of bar segments and the segment legend labels
Removal of elements may result in other elements can be unclassified during revalidation
| This occur if there only are other elements of the metaclass at the same model level as the element being deleted.
If there are other elements of the same metaclass in other positions in the model, the bug does not occur.
|4.4.1||MMA-2202||UI Chart View||
A bar element can incorrectly be included in bar segment in Related Elements Bar Chart
|This occur in reflexive associations or circular relationship chains|
Exception in Add Wizard when adding an association by selecting an element
| This occur when selecting an element and bring up the Add Wizard for adding association end, association and opposite end.
The problem does not occur when adding an assoication by selecting two elements in a diagram.
Activating a parent to an already activated item throws exception
|Trying to activate an element that already have an activation on a nested element throws an exception|
|4.4.1||MMA-2186||UI Trace Matrix View||
Incorrect result in Trace Matrix's 'Transitive (Start-End)' mode
|Source elements with no incomming relationships connected to target elements participating in a loop are incorrectly displayed in Trace Matrix View's 'Transitive (start.end)' mode,|
|4.4.1||MMA-2184||UI Trace Matrix View||
Invoking the matrix view when several models using same metamodel are activated may give incorrect result
|If Trace Matrix View is invoked from the context menu in the explorer view by selecting a root item of an activation and a metaclass representing a relation, then the resulting view will be populated will all instances of the metaclass in all activated models using the same metamodel.|
|4.4.1||MMA-2181||Linux, UI Trace Matrix View||
Invisible target labels in Trace Matrix View in some Linux environments
| Invisible vertical target labels have been reported in RedHat linux environment.
|4.4.1||MMA-2180||UI Problem View||
Quick fix of multi value properties opens wrong popup-dialog
|When fixing an invalid property where multiple values are allowed. The value list dialog should be opened.|
|4.4.1||MMA-2176||UI Trace Matrix View||
Incomplete scope in Trace Matrix Labels when context button is pressed
|This issue occurs for some selections, but not all.|
|4.4.1||MMA-2175||Papyrus, UI Activation View||
Same model sometimes occurs twice in Activation View
|In some situations, for example when a new model is created, or when library models are loaded, the same model occurs twice in the Activation View.|
|4.4.1||MMA-2173||Linux, UI Property Table View||
Incorrect multi-line table layout in Property Table View on some Linux environment
| Multi-line documentation will be displayed over several rows in the Property Table View.
Expected behavior is that only first line som be displayed.
|4.4.1||MMA-2172||Linux, UI Chart View, UI Common||
Invisible styled tooltips in some Linux-environments
| The default tooltip front & background color is both black in some Linux environments. That makes the styled tooltips invisible.
The styled tooltips must respect any default tooltip color settings.
Source property should be hidden in Add Wizard for relationships
|If source property for a relationship is explicitly defined in ametamodel, it should not be editable in the Add Wizard for the relationship. The source property should be hidden or readonly|
|4.4.1||MMA-2168||UI Property Table View||
Don´show automatic Source property if the current metaclass has a defined source property.
|4.4.1||MMA-2164||UI Trace Tree View||
Obsolete context menu entry in Trace Tree View
|In the context menu in the Trace Tree View, the menu entry "Navigate to Unhandled Item in Project Explorer" is obsolete and has no visible effect.|
|4.4.1||MMA-2163||UI Guidance View, UI Wizards||
Cryptical characters in Guidance View fall-back mode
|Strange characters occurs on first and last line of the guidance view when it is in fallback mode due to lack of embedded web browser.|
|4.4.1||MMA-2150||Papyrus, UI Activation View||
Activations remains after activated model has been closed
| This occurs if one of the activated models are closed, The Activation view then shows activations from the closed model.
Activated library models will also be listed as activated twice.
|4.4.0||MMA-2143||UI Chart View||
Problem Distribution Chart Item kind/Problem kind groups mixed up when bars display Severity
|When letting bars display Severity, the group is mixed up Item Kinds displays Problem Kind and vice versa|
|4.4.0||MMA-2108||UI Property View||
Interactions could not be selected as "target" within an Interaction Use
|Interactions are not displayed in item selection dialog|
|4.4.0||MMA-2105||RSA, UI Wizards||
An extra empty section is displayed in Add Wizard when using RSA RTE 10.3 on some Linux environments
|An extra empty section is displayed between the properties section and the guidance section|
|4.4.0||MMA-2099||UI Guidance View||
Show in table view selection is not updated when moving to new metaclass in Guidance View
|THe Guidance View context menu that displays all occurences of the current metaclass in the Property Table View is not updated when a new metaclass is present to the hyperlink navigation.|
|4.4.0||MMA-2088||UI Property View||
HTML-control characters in element names are exposed with their HTML-encoding in hyperlink labels in MMA Property View
| For example, the name <FOO> are exposed as & lt;FOO& gt;
This also holds for metaclass names in MMA Property View heading.
|4.4.0||MMA-2082||Linux, UI Guidance View||
Eclipse crashes when clicking on a hyperlink in Guidance View in some Linux environments
| The whole aaplication crashes without a stack trace when clicking on a hyperlink that leads to a metamodel item in the Guidance View.
This behavior has so far only been detected in some Linux environment (SUSE Linux Enterprise Server 11 SP4).
|4.4.0||MMA-2046||RSA, UI Perspective||
Reset MMA perspective in RSA RTE 10.x opens a second project explorer view
|When resetting the MMA perspective with the project explorer already open, opens a second project explorer view|
|4.4.0||MMA-2042||UI Trace Matrix View, UI Trace Tree View||
Exception is thrown when clicking on an empty cell in Trace Tree View or Trace Matrix View
|4.4.0||MMA-2029||UI Chart View||
Error message is displayed when refreshing the Chart View using the refresh button
|4.4.0||MMA-2027||UI Property Table View, UI Trace Matrix View||
Population of MMA Property Table View and Trace Matrix View makes the model editor "dirty"
|When populating MMA Property Table View and Trace Matrix View the model editor is incorrectly marked as "dirty" indicating that a model change has been made. But nothing has changed in the model and saving the model does not save any changes.|
|4.4.0||MMA-2024||Guideline Reporting, Model Reporting||
Impossible to select folder for web publish output on certain OS when using Eclipse Photon or newer
|\[Resolved in 4.3.1.009]|
|4.4.0||MMA-2019||UI Trace Tree View||
Relations where the target is null is not displayed in Trace Tree View
|4.4.0||MMA-2018||UI Trace Matrix View||
Relations where the target is null results in an error message in the Trace Matrix View
| The Trace Matrix View indicates an error when there is a relationship without a target within the selected context.
\[Resolved in v4.3.1.009]
|4.4.0||MMA-2013||RSA, UI Property View||
Exceptions are thrown randomly when setting focus on MMA Property View after metamodel changes being applied
| Sometimes a popup-dialog indicating exception when setting the MMA Property View in focus.
The problem have only been observed in RSA RTE environment running on Eclipse Neon.1.
\[Resolved in 4.3.1.009]
|4.4.0||MMA-2008||Model Validation, Papyrus||
Diagrams in fragments are not recognized
| Diagrams contained in a model element which belong to a fragmented part of the overall model and stored in its own metamodel, will not be recognized in MetaModelAgent. This bug was introduced in v4.3.1.
\[Resolved in 4.3.1.009]
|4.4.0||MMA-1999||UI Chart View||
Several Bar Chart displays incorrect content when the scope includes several nested models using the same metamodel in different activations
| In all charts that groups the result around metaclasses.
The bars presented and the tooltips are not correct if the selection includes content from several nested models using different activations of the same metamodel.
\[Resolved in 4.3.1.009]
Connection to metamodel in closed projects fails
|Metamodels in closed projects should not be available for connection|
The bugs in the list are all reported and confirmed. Any major bug will be resolved in the next upcoming release.
|MMA-2412||Model Reporting, Papyrus||
Papyrus diagrams created in older versions are published with invalid views
| Papyrus diagrams created in older versions of Payrus and not currently open in diagram editor is published with invalid views.
The workaround is to “touch” each diagram, save and reopen the model.
|MMA-2386||Model Validation, UI Activation View||
Referring JRE System Library elements in RSAD is very slow
| Trying to activate an open instance of "JRE System Library", takes very long time.Trying to open an item selection dialog where the current value is a JRE System Library element is slow.
The problem is not related to MMA. It is the access of model elements that takes time.
It seems that the JRE-jar - library is reversed incrementally when accessing some of its content.
Models generated upon model openingen will be duplicated in the Activation View's Activation popup-dialog
| This holds for "JRE System Library" in RSAD where that model is created based on JAR-files when a model referring it will be opened.
It may be impossible to control this as there actually might be double models internally with different object id:s
Property values get lost in Change Wizard when drag & drop from explorer view to diagram node
Adding a nested model does not automatically activate this nested model and it will be unclassified
|This will hold both if the nested model is created by MMA Add wizard or by using the build in add UML submenu.|
|MMA-2274||UI Property View||
Entered property values remains after rollback caused by rejecting set a model as writeable
|When a property is edited for an element in a read-only model, a confirmation dialog occurs that let you switch to writeable mode. If you cancel that option, the old property value should replace the new one.|
|MMA-2228||Papyrus, UI Problem View||
Concurrent modification exception when switching between activated models in different editing domains
Unloaded submodels may give warnings of overlapping IDs in web publish
|MMA-2156||UI Trace Matrix View||
Eclipse session ends when there is too many relationship targets to be displayed in the Trace Matrix View
|The vertical target labels are currently generated images. The exception says "no more handles" indicating run out of UI resources. Limit the max number of targets to be display or redesign the target labels|
|MMA-2140||UI Problem View||
Problem view filter "item+childs" gives incomplete result when applied to a package containg nested models
FREE License insufficient when moving a block of elements within an activated model
|Workaround is to temporary inactivate MetaModelAGent during moving of several elements.|
|MMA-1910||General UML guidelines||
Metaclass Structured Activity Node occurs twice in metamodel General UML Modeling guidelines
|MMA-1897||Imposer, Model Validation, Papyrus||
MMA does not react on model changes in a model managed by CDO initiated by another CDO session
|Running two simultaneous CDO sessions and changing the model in one of the session, does not initate a revalidation of the model in the other session. Any added model element will be unclassified by MMA|
|MMA-1803||Model Validation, UI Property View||
Lower limit of multi-valued user defined properties are not validated
|A lower limit of 1 for example is not reported as invalid, not by color in the MMA Property view or by an entry in the MMA Problem View|
|MMA-1793||Model Reporting, PapyrusRT||
Fallback filenames are used for some RT-elements when publishing an PapyrusRT model using PapyrusRT RCP
| The standard way to retrieve the UUID, Resource.getURIFragment(element) does not work for all RT-specifik element types when running the RCP-installation of Papyrus.
If so, files with encryptic file names are generated instead of UUID-based file names.
An invalid thread access exception occurs first time an unloaded profile is refered
|This exception does not affect the resulting guideline web.|
|MMA-1748||Model Reporting, Papyrus||
Invalid thread access exception sometimes in web publish
| Invalid thread access occurs sometimes when executing web publisher. This seems to occur randomly. A temporary fix has been made by catching the exception, but this bug is still open waiting for a permanent fix.
Work around that have proven successful is to restart the tool and redo the model pubslishing.
Publish documentation failure sometimes when reusing output folder
| Exceptions has been detected a few times when publishing once more into an existing folder. This have not been reproducable in test environments.
Work around may be to clean the target folder or use another target folder.
The order of ordered nested elements are not preserved in web publish
| The order of parameters are semantically significant and must be preserved. The same is for Pins and for nested properties (e.g. qualifiers)
These elements should therefor always be listed in original order as stored in the model.
Inherited elements from other activations are presented with the other activation´s metaclass
| If an element inherit another element, for example a property, the other element has a metaclass from the metamodel from the other activation.
In such a case the element should be presented in some special way
If both the activations uses the same metamodel, the elements shoould be grouped under the same heading in the nested element section.
The preference setting "Show only editable pages in wizards" is not respected for the first Add wizard page
|Add wizard should not be showned when adding an element or relationships by selecting two elements, if there are no editable properties and the preference setting is set to hide non-editable pages.|
|MMA-1539||Model Validation, Papyrus||
Associations are reported as invalid elements if there are permitAll operations allowing any association ends
| To remove the invalid reported problem, a manual refresh (reactivation) must be made.
Even afterwards and also in RSA when selecting such an association, a message in the GuidanceView says that the element could not be identified
Metaclass comparison reports invalid errors when constant default values are used in combination with enumeration types in metaclass attributes
| When two metaclass attributes are compared and they have different fixed default values but the same enumeration as types. They are invalidly reported as overlapping as the default values are not respected.
The bug is related to the compareEnumTypes() method in class MetaClassComparison.
Adding a Capsule using RSA RTE UI when Change Wizard is enabled causing an "Invalid model modification" dialog to appear
| Adding a Capsule using RSA RTE UI automatically add some nested elements as well.
This is very difficult to fix because the EMF Transaction framework reports the added elements in a reverse order, making it impossible for MMA to identify the added elements correctly.
One solution would be to detect that there is nested elements to a capsule being created and disable the change wizard upon this fact.
This behavior may occur in other situations as well where several elements are added using a single operation.
|MMA-1255||General UML guidelines, Metametamodel||
ExpansionRegion, LoopNode, ConditionNode and SequenceNode are handled as StructureActivityNodes
| Their stereotypes are already defined in the MMA profile, but they are not suppported in the code, Metametamodel and General UML Guidelines metamodel.
There are a lot of properties for these elements to be added also. Those are supported by Papyrus property view but not RSA
ConditionNode: Is_Determninate, Is_Assured, (Clause), Result
Expansion Region: Mode - Expansion Kind, input, output
|MMA-1241||UI Property View||
Item selection dialog button for Slot value property need sometimes to be pressed twice before the dialog appear
| If the defining feature has been changed the item selection dialog for slot value has to be pushed twice
The problem occur because the widgets are redrawn when the defining feature lost focus. At that point the push button listener is not yet registered.
Automation is not always automatically enabled on a model that have been created
| When a model is created and MMA has the preference setting "Always activation". MMA tries to do the activation Before the editing domain is available. Automation is therefore not initialized. Activation must therefore be made manually.
The stereotype 'templatebinding' in the MMA-profile used in metamodels is misspelt
|The correct name should be 'templateBinding' with an uppercase B.|
|MMA-976||UI Property View||
MMA Property View is not automatically updated when a property value is changed in some other view or editor
|An automatic update would be the expected behavior But that may make the MMA Property View obsolete if it affects key-properties. In such a case the classification might change forcing a complete switch of the view content or that the view should be empty (base on that the element could not be classified). This bug needs more investigation and consequence analysis.|
Circular <<key>> references in a metamodel leads to an inifinte loop upon activation
|This might be detected if a test model can be automatically genererated from a metamodel|
|MMA-564||General UML guidelines||
UML Connectors could not be created using the General UML Guidelines
| The current UML General Guidelines does not have 2 as a lower number of Connector Ends to a connector, that means that a connector will be created by the Add-wizard without the option to create any connector ends. That results in an thrown RSA exception.
The lower number of Connector Ends should be set to 2 in the General UML Guidelines.
The Add-wizard should respect that number and make it possible to create 2 Connector Ends.
|MMA-542||General UML guidelines||
General UML Modeling Guidelines: Associations can contain other classifiers besides use-cases
| The "Association" meta class can invalidly contains "Class Item"
This is a necessary exemption until association classes are supported. Currently association classes are identified as associations by MMA, and association classes are allowed to have other nested elements
The location of a referenced element is not considered when matching meta-classes representing external elements
| An element must be in another model to be able to be matched with a meta-class representing an external-element
A fix of this bug may reveal new (unknown) problems in customer models.
All bugs applies to all environments, any exemption is indicated in the Component column:
|RSA||Only present when using IBM RSAD/RSARTE or HCL RTist.|
|Papyrus||Only present when using Eclipse Papyrus.|
|Windows||Only present when running on a Windows platform.|
|Linux||Only present when running on a Linux platform.|
|IOS||Only present when running on an Apple IOS platform.|
To use the hyperlinks in the tables, you must have authorized access to Adocus JIRA issue tracking repository.