Requirements diagram not available after restricting perspective

[Geert Bellekens]

Details:
We us a model based perspective to limit the number of diagrams people see.
This seems to work just fine, until we use the "restrict" button on the perpective to further restrict the possible diagrams. When we actually uncheck any of the diagrams, certain diagrams such as the requirements diagram are no longer available.
This might be related to the built-in technologies as you cannot select those diagrams when restricting.


Steps to Reproduce:
- Create a perspective with BPMN 2.0, Core Extenstions, EA Requirements
- Select this new perspective in EA
- use Add Diagram and notice that you can choose the Requirements diagram from the Extended header
- Go back to the perspectives window and set it to strict.
- Click on the "Restrict" button and uncheck any of the BPMN diagrams
- Save the perspective
- Try to add a diagram and notice that the Requirements diagram is no longer available.

Reported.

This has been noticed on both v15.2 as v16

Geert

[Guillaume]

Hi,

I have a similar issue with Model-Based perspectives:
- it shows my MDG + SysML 1.5
- for SysML, I don't want users to see all diagram types so I set it as String and used the Restrict button
As a result, "silent uml patterns" available from one of my MDG Toolbox are no longer visible (it works fine without the perspective).

[Geert Bellekens]

I think they fixed it in the latest v16 RC

Geert

[Guillaume]

Hi Geert,

Thanks, I confirm that it's been fixed in EA 16 RC.
If Sparx plans to release an additional EA 15.2 build, it would be nice if it could integrate this fix since the team won't update to EA 16 in the short term.