Messages

1

Automation Interface, Add-Ins and Tools / Re: Classifier's tag values being overridden by shapescript default

« on: August 01, 2020, 12:52:57 pm »

Thank you Uffe and qwerty for following up. The explanations were helpful.

I doubt the shapescript would let me accommodate this, will keep looking. Thanks for your time.

2

Automation Interface, Add-Ins and Tools / Re: Classifier's tag values being overridden by shapescript default

« on: July 29, 2020, 03:26:39 am »

Thank you for your responses,Qwerty and Uffe. Follow up questions..

Qwerty - Not sure how I can get the stereotype to extend the instance. In the MDG, the stereotype does extend the base object class. In that stereotype ,I have defined the custom attributes and the associated shapescript.

Uffe - I am unsure about what you mean. The classifier:instance combination is in MDG, and then when I import the MDG, I have elements with my custom stereotype and they show the related custom tag attributes. When I try to drop this element as an instance, the shapescript takes over. The tag values are created as if it is creating a new MDG defined element. I hope I have provided some more information instead of reiterating what you already gathered Not sure if you meant the instance that I create in MDG, or when I am using the element.

Thanks again!
SparxUser19

3

Automation Interface, Add-Ins and Tools / Classifier's tag values being overridden by shapescript default

« on: July 28, 2020, 03:40:58 am »

Hello,

I am working with an MDG element that contains a shapescript to set the fill color depending on a custom tag's value. When I drag and drop the element from the Project Browser as an instance, the tag values are resetting as per the shapescript, instead of bringing over the value set on the classifier element. Is there a way to prevent this?
I am hoping not to use script to update these values.

Thanks!

4

Automation Interface, Add-Ins and Tools / Importing more than one Alternate Path on a Use Case

« on: February 21, 2019, 02:36:17 am »

Hello,

I am using MS Office Addin to import use cases and I see that Sparx only allows one value for each property (i.e, there can be only one Name or Notes or Alternate Path in my case). Is there a workaround to supply more than on Alternate Path.

It makes sense to not have more than one Element Name, but Alternate Path is a different story

Thank you in advance for your inputs.

5

Automation Interface, Add-Ins and Tools / Re: Use Alias if available

« on: April 27, 2018, 10:59:38 pm »

Thanks all. Will look into  Project Template. Not sure where to look, but EA Help to rescue I hope

I have the Auto naming turned on for Requirements, right now it is populating it for my Packages, that’s the issue.

6

Automation Interface, Add-Ins and Tools / Re: Use Alias if available

« on: April 26, 2018, 11:35:49 pm »

I looked under the Configuration setting for it but I don’t see anything configured for “package”. I will keep looking to see if it is applying a different basic type to the package and then auto populating it?

If there are any other setting you think I should check, please let me know.

Thanks for your help!

7

Automation Interface, Add-Ins and Tools / Re: Use Alias if available

« on: April 26, 2018, 10:14:07 am »

You are right, I do. So the auto naming populates the alias?

8

Automation Interface, Add-Ins and Tools / Use Alias if available

« on: April 26, 2018, 07:54:13 am »

Hello,

In my MDG technology, I have a diagram where I have enabled “Use Alias if available”. In my MDG toolbox, I have a package element, and every time I add this onto the above mentioned diagram, it populates the alias and then displays it on the diagram, but I don’t want it to do that.

Before I turned on this flag, it was not prepopulating the Alias field on the package. Not sure why it is doing it now. Any pointers?

TIA

9

Automation Interface, Add-Ins and Tools / Re: MDG- Updated stereotypes

« on: April 19, 2018, 04:43:06 am »

I ended up using the Configure|UML Types screen to get rid of some and that seemed to help.
 
What is FQN btw?

10

Automation Interface, Add-Ins and Tools / MDG- Updated stereotypes

« on: April 19, 2018, 02:07:13 am »

Hello,

How do I get rid of the leftover stereotypes that continue to exist as part of the various versions I went through, before finalizing my MDG technology. The old stereotypes are conflicting with similarly named stereotypes that are part of my final MDG technology.

Thank you in advance!

11

Bugs and Issues / Re: Auto numbering doesn’t work for imported requirements

« on: April 19, 2018, 02:03:02 am »

Thanks. That is what I ended up doing! 

12

Bugs and Issues / Re: Auto numbering doesn’t work for imported requirements

« on: April 12, 2018, 11:05:06 pm »

Makes sense, although I wouldn’t mind a configuration option for this

Thanks a bunch!

13

Bugs and Issues / Re: Auto numbering doesn’t work for imported requirements

« on: April 12, 2018, 02:08:30 am »

CSV import

14

Bugs and Issues / Auto numbering doesn’t work for imported requirements

« on: April 11, 2018, 11:50:16 pm »

Hello,
I have auto numbering turned on for Requirements and while EA auto numbers any requirements that I manually create, it doesn’t auto number the ones I imported. Anyone else faced this? How did you get around?

TIA

15

Automation Interface, Add-Ins and Tools / Propagating MDG updates to the existing elements

« on: April 03, 2018, 01:28:54 am »

Hello,

I have a set of requirements that are using MDG technology version 0.9. In my next version, I have removed the groups that I had created for my tagged values. My question is - for the existing elements, how can I apply these MDG updates so that the grouping doesn’t show any longer? Appreciate any input you all might have.

TIA!