Author Topic: Extending built in stereotypes in a profile (BPMN)  (Read 2675 times)

rmartinezb

  • EA User
  • **
  • Posts: 44
  • Karma: +1/-0
    • View Profile
Extending built in stereotypes in a profile (BPMN)
« on: April 04, 2017, 12:49:08 am »
Hi!

I'm working with BPMN and I have to create some new elements. I know how to do this thanks to this guide http://sparxsystems.com/enterprise_architect_user_guide/12.1/building_models/non-uml_metatypes.html

For example:

But some of the new elements have to extend form some built in stereotypes, like a subProcess Task. For that I have to extend form BPMN2.0::Activity and indicate that this activity have the subProcess type. How can I do that?

Greetings

Dermot

  • EA Administrator
  • EA User
  • *****
  • Posts: 589
  • Karma: +7/-0
    • View Profile
Re: Extending built in stereotypes in a profile (BPMN)
« Reply #1 on: April 04, 2017, 11:44:57 am »

rmartinezb

  • EA User
  • **
  • Posts: 44
  • Karma: +1/-0
    • View Profile
Re: Extending built in stereotypes in a profile (BPMN)
« Reply #2 on: April 04, 2017, 04:44:13 pm »
This is the same that I posted before but the v13 guide instead the v12.1  :-[

But how can I redefine my new activity to be a subProcess Activity?

rmartinezb

  • EA User
  • **
  • Posts: 44
  • Karma: +1/-0
    • View Profile
Re: Extending built in stereotypes in a profile (BPMN)
« Reply #3 on: April 28, 2017, 10:44:51 pm »
Hi!, I'm here again and I still have the problem. I'll try to give more information about it:

I need to create a custom BPMN 2.0 Sub-Process element, but EA define this elements changing the "activityType" Tagged Value on a Activity element.

I tried to include the "activityType" property on my new elements, but instead overwrite the property, the elements get 2 activityType properties one of the of the task type and the other with Sub-Process type. This later gives problems in other processes.

So, is there any way to assign a value to an inherited property an the in the MDG file? I really need that the custom elements that extend from BPMN 2.0 Activity be Sub-Process type.




Geert Bellekens

  • EA Guru
  • *****
  • Posts: 8470
  • Karma: +207/-26
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Extending built in stereotypes in a profile (BPMN)
« Reply #4 on: April 30, 2017, 02:10:16 am »
I think you have to set a default value for the tagged value, but I'm not sure if you have access from your profile to that tagged value.
In that case I guess you'll have to use some kind of add-in, or EA-Matic script to fill in the default value for that particular tagged value.

Geert

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2529
  • Karma: +33/-2
    • View Profile
Re: Extending built in stereotypes in a profile (BPMN)
« Reply #5 on: May 01, 2017, 09:23:26 am »
There is the following in the release notes for build 1305:
Quote
Redefine stereotypes from external profiles using a <<redefines>> stereotyped generalization
   . Add new tagged values to stereotype group for parent stereotype - Define distinct tags on the child stereotype
   . Replace the type of tagged values from parent stereotype - Define tagged values with the same name on the child stereotype
   . Remove tagged values from the parent sterotype - Define tagged values with the same name and the stereotype <<remove>> on the child stereotype
   . Automatically replace parent stereotype with child - Use same name for stereotype, and user selects technology containing child stereotype as active ( Configure | Technology | Manage | Set Active )

I think something in there will help you.
The Sparx Team
support@sparxsystems.com

rmartinezb

  • EA User
  • **
  • Posts: 44
  • Karma: +1/-0
    • View Profile
Re: Extending built in stereotypes in a profile (BPMN)
« Reply #6 on: May 02, 2017, 06:00:32 pm »
Hi! Thanks for your suggestions.

Unfortunately, the company I work for only use EAv12, so we resolved this problem doing an addin and using the EA_OnPostNewElement event to edit the activityType for the elements we want.

Greetings  ;D