Customization Tool to manage stereotypes for objects and links

[#1]

Please provide a customization tool that will allow for the stereotypes that apply to an object to be set as part of the modelling language.

Currently on the details tab for most object and links in ProVision there is a stereotype field.  In some cases this field has pre-defined (by Metastorm) drop down values, in others there are none, but a modeler can enter any value in this field.  As we don't use the same stereotypes at predefined by Metastorm this means the modeler has to remeber the valid stereotypes, and manually enter these every time, with the associated risk if mis-entered stereotypes, or incorrect stereotypes.

We need to be able to:

• set the valid stereotypes for an object or link
• turn off the ability for a modeler to enter a stereotype not in the drop down list

[#2]

iOctane has previously submitted an enhancement request to make stereotypes a customizable field based on both our Provision clients feedback in various and our own modeling experience, when undertaking consultancy roles with our clients..

In respect Jims need to turn off the ability of a modeled entering a stereotype not in the drop down list, this is a perfectly valid approach, and supports best practice methodologies being implemented... 

This wasn't part of our original iOctane enhancement request, but I believe that it should be an option when creating a custom modeling language but not the default position.

Not all Provision users are part of a large community of users with a defined custom modeling language and therefore there will always be a need for manually entered stereotypes.

[#3]

I think this is  a no brainer.  We seldom find stereotype values that fit our business context and are forced to manually type in values. The problem is with typos and other editing mishaps.  When using reporting or filters we notice that some values may be missed and on later investigation can see a typo.  The other issue is that we have to continually educate users to use the correct stereotype i.e. the one we want not an inbuilt one. 

I fully support this idea. 

[#4]

+

Stereotypes management is highly appreciated also here. We have also submitted such enhancement request (case#: 18640 - 7/2009).

[#5]

I have posted a similar issue with one possible resolution option already:  manage them in the .pvp like a custom property.

[#6]

Same idea raised before

if added a link to the last time i raised this idea here when i worked at Telecom.  I also raised this idea via the Provision product advisory board when I was a member 2009/2010.

[#7]

Hi Jim, That has been discussed in the past and we currently have an item on the backlog specially for it. I don't have a release date for this, but it will definitely be added. This take our initial concept a step further though. What we've discussed is the ability to add custom stereotypes, but the management of those has not been discussed. I'll take this back to development.