Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Nick Webb

Pages: [1] 2
1
General Board / Re: EAUML::trace and Relationship Matrix
« on: January 04, 2017, 12:04:11 am »
Fantastic, thank you Mr Savage  :)

2
General Board / EAUML::trace and Relationship Matrix
« on: December 17, 2016, 01:08:17 am »
Slightly confused - in a relationship matrix I select the trace relationship type and link 2 elements.  However on clicking refresh the relationship vanishes.  On checking the link type I see an abstraction link with stereotype EAUML::trace is created so it's thrown me a bit.

- What am I missing please?!

3
Thanks v much for the replies - I can confirm that BPMN2.0 was enabled at the time the script was run.
The only conclusion I can come to is that some modelling had previously been done in BPMN1.0 (I found a stray element) so I'm guessing that this stereotype is embedded somewhere in the database which may have caused EA to need to differentiate it.  If I can come up with anything more sensible then I'll report back...
I haven't done any automation for yonks either  :)

4
Thanks but I've checked that BPMN2.0 is checked in Extensions>MDG Technologies and went as far as unchecking BPMN1.0 and 1.1 - any idea whether setting StereotypeEx should achieve the expected result?

Cheers, Nick

5
I have written some VBA to change diagrams imported from Visio using the Visio Importer add-in to BPMN2.0.
I have used FQ Names to change the imported elements, e.g. anElement.StereotypeEx = "BPMN2.0::Activity".
This appeared to work fine in an empty project used to test the VBA but the behaviour seems different when running it against our project model!
i.e. in the empty project the element stereotype appears in the Project Browser as <<Activity>> but in the project model appears as <<BPMN2.0::Activity>>  and I'm wondering if I've done something wrong!
Checking the database, in the empty project t_object.stereotype = "Activity", but in our project model appears as "BPMN2.0::Activity".
Any idea why the FQ stereotype name appears in one case but not the other?!
I should add that this behaviour is happening only for Activity elements - Gateways, StartEvents, EndEvents seem fine/consistent.
Seems weird - any help much appreciated. 

6
Quote
You'll be pleased to hear that EA 7 will introduce individual tool tips.


Can anyone confirm whether this feature is currently available?

Unfortunately it looks like it didn't make the cut.

ah well, at least i didnt spend shed loads of time looking for it ;)

7
Quote
You'll be pleased to hear that EA 7 will introduce individual tool tips.

Can anyone confirm whether this feature is currently available?

8
General Board / Re: Inheritance within profiles
« on: October 30, 2009, 02:59:12 am »
Have just run into this one myself - it appears to work if I:

1. Add a new metaclass
2. Set _defaultDiagramType in new metaclass
3. Add extends connectors between stereotypes and new metaclass

...  I wonder if metaclass supported attributed are only inherited by extending stereotypes?

HTH

Nick

9
General Board / Re: ask for help to create customized template
« on: October 25, 2009, 10:19:29 pm »
For the variables bit, have a look at Project Constants...

10
General Board / Re: Initial tips please
« on: October 25, 2009, 11:21:05 pm »
Paulo, Graham, many thanks. Nick

11
General Board / Re: Initial tips please
« on: October 22, 2009, 07:35:23 am »
I'm just starting to dip into the idea of using elements to capture glossary terms (for reporting flexibility mostly) - will use InformationItem as suggested.  I'd anticipated that it wouldnt be convenient to capture all my glossary terms in an entity model - any ideas?

12
General Board / Re: Grouping pre-conditions in a single section
« on: October 22, 2009, 06:46:15 am »
I struggled with this one too and ended up adding tags named "preconditions" and postconditions" (memo) to my UCs. Maybe crude, but the output looks as intended.  

13
General Board / Extending built in stereotypes in a profile?
« on: October 22, 2009, 12:08:17 am »
Hi all,

Apologies if this is covered elsewhere but i'm not having much luck with the search results...

I've a little experience in creating profiles and MDG Technologies, but wish to create a new profile, adding some tagged values to the existing BPMN BusinessProcess stereotype.  

I can select an Activity for a metaclass, but not BusinessProcess (which I kind of expected to see if "Include extended" is checked).  Currently, my options appear to be:

1. Create a stereotype named "BusinessProcess" and synch tagged values to update elements created from BPMN toolbox
2. Create a stereotype with a different name and change the stereotype for an existing BPMN element then synch.

I have yet to find a method of defining a stereotype to inherit the existing tags available with BusinessProcess and drag and drop elements from the resources pane

Can anyone confirm whether the above is correct and if stereotypes can be defined to extend existing stereotypes in this way?  The profile should be as easy to use as possible for new EA users, when developed.

Cheers

Nick

14
General Board / Re: Stereotype in actor
« on: December 12, 2008, 10:33:19 pm »
Playing with the above script a bit more, I see the stereotype overlays the namespace when visible.  Can anyone advise whether there is a simple way to avoid this when the inbuilt glyph is used?

Cheers, Nick

15
General Board / Re: Stereotype in actor
« on: December 11, 2008, 08:46:53 am »
(Greetings all)

For actor with stereotype i use...

shape main {
      addsubshape("inbuiltglyph", 100, 100);
      addsubshape("labels", 100, 100);

      shape inbuiltglyph {
            h_align = "center";
            drawnativeshape();            
      }
      
      shape labels {
            h_align = "center";
            println("<<#stereotype#>>");
      }      
}

Hope this helps

Nick

Pages: [1] 2