Missing stereotype on connector in properties

[ntm]

Hello,

We are seeing another issue in Enterprise 10 where users with limited permission do not see stereotype property when they double click and open properties window for a connector. Here is a list of permissions that a user has who has this issue:

• Check Password
• Check data integrity
• Export XMI]
• Generate Documents
• Import XMI
• Manage Diagrams
• Spell Check
• Update Diagrams
• Update Elements
• Use Version Control

Here are the steps to reproduce the issue.
1. Crete a project and setup a user which has only the above set of permissions.
2. On a diagram, create two application components (Archimate 2 stencil)
3. Using the connector tool, create a 'used by' relationship from one application component to the other. It is represented as a solid line with an arrow at the end.
4. Double click the connector to see its properties and notice that the stereotype prperty is blank. when the user clicks 'OK' on this screen, the connector now changes from a 'used by ' relationship to 'dependancy', from a solid line to a dashed line on the diagram. The stereotype property says 'Archimate Used By' if an admistrator who has all permissions does the same steps and the relationship stays intact.
This was not an issue inversion 9.3.

Is there a new security permission that is governing this behavior or is this a bug in version 10?

Thanks,
NM  

[ntm]

Adding 'Configure Stereotypes' fixed the issue for non-admin user. However, still feel it is a bug because 'Configure Stereotypes' should control adding and deleting custom stereotypes and not effect the stereotype in Properties window. Thoughts?

Thanks,
NM

[qwerty]

Once I came across this I had the same feeling (it must have been with 9.3?). However, it does not help much to report bugs on that level. Feel free to convince me it helps.

q.

[ntm]

Hello,

Not sure if I usderstand your response correctly. Do you mean it is not a bug?

We were not seeing this issue in version 9.3.

Thanks,
NM

[qwerty]

Well, I think it's a design flaw which is not necessarily a bug. So you might request a new feature here. However (like in the other thread), chances are low to see it realized in a near future.

q.

[Eve]

Please do report it.

I would consider it a bug, and it could easily be corrected for a future version.