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 - Geert Bellekens

Pages: [1] 2 3 ... 517
If I were you I would start by doing a simple import, and then using automation go over each of the elements, find it's original element and merge/replace the original with the new one.

This is not a small task, but at least you would know exactly what you are doing, whereas the xmi approach would be a whole lot of trial and error.

Anyway, there is never a reason to want to change the GUID of any API object.
The only result you'll get is an inconsistent model and maybe some database errors if you are lucky (unique constraint violation)


Bugs and Issues / Re: Virtual Connectors do not execute Shape Scripts
« on: December 13, 2017, 09:59:41 pm »
OK. Let's say it is an incomplete implementation and as a result, virtual connectors are useless when MDGs are used.

I wonder what is the percentage of users that do not use MDGs?
Probably lower then the percentage of users that don't use virtualized connector ends.
I never use those (and I advice all my customers not to use it) because of the weird implementation. I'd rather stick with the old limitation of having maximum one representation of an element on a diagram.

My feeling is that, in most cases using virtualized connector ends hides a more fundamental misunderstanding of how something should be modeled. There are exceptions of course, but usually it's easier to simply forbid it's usage then to verify all of the usages to make sure they are valid.


Ah, I see.

The weird thing is that, when using regular document generation this behavior is standard.
All my diagram are shrunk to exactly the size of a page.
Could it be that the document generator behaves differently when executed from script?

I would take that up with Sparx support.

Anyway, as a workaround you could write a little macro in Word to resize the images. If you search the forum you'll find one that I posted a while ago to do just that.
We actually wanted the diagram to be a little bit smaller than a whole page so the caption would stay on the same page.


General Board / Re: Import of PlantUML Sequence Diagrams
« on: December 13, 2017, 05:39:02 pm »
I think that is going to be a difficult one.
AFAIK PlantUML is more a diagram tool then a modelling tool.
That means that you can use whatever elements on you diagrams without a reference to an underlying model.
This is especially troublesome for sequence diagrams as they usually represent only something like the behavior of a single operation.
So in other to describe the full behavior of a single element you typically need several sequence diagrams. Now if none of the instances in the sequence diagram somehow represent an underlying element, you would import nothing but garbage into your EA model, having tons of lifelines without a classifier.

I'm not sure how that problem could be solved...


I am using docGenerator.DocumentDiagram( currentDiagram.DiagramID, 0, myRtfTemplateFragment) to "print" large diagrams in an RTF document.

Hi Geert,

I am not looking for dividing diagrams.  I am looking for a method to shrink each diagram so that it fits into the A4 age.
If you leave that unchecked I think it should do just that (as in not divide over multiple pages)


General Board / Re: Opening project via SharePoint interface
« on: December 13, 2017, 03:23:09 am »
You can't.
.eap files are MS-Access databases.
Sharepoint is meant as a storage for documents, not for databases.


On the diagram properties there is
Diagram | Document Generation Options | Divide Diagram into multiple pages
I think that might be what you are looking for.


I guess this is an SQL search and not a script.
First thing to do is check the dbError.txt in the %appdata% folder for EA.

Then remove the comments. IIRC EA will strip (or it used to) everything after the first comments, so your search will be nothing more then "SELECT"

Next thing is the To_Number(t_connector.PDATA1) there's a good chance you have somewhere a text in a PDATA1
I guess you better cast both fields to string to compare them instead of trying to cast it to a number.


Automation Interface, Add-Ins and Tools / Re: GUID of a diagram
« on: December 12, 2017, 03:22:09 pm »
As a post-note: the "*" should be replaced by "%wc%" "#WC#" so it will work also on non MS Access (aka EAP) RDBMS.




I don't see any options on the templates themselves, but there is an option to set a watermark on the Document generation dialog (F8).
Any reason why you aren't using that?


General Board / Re: Show tagged value?
« on: December 11, 2017, 08:45:42 pm »

I believe you can do that using a shapescript, but I've never don't that for a connector myself, so I can't really give you any further advice.


Automation Interface, Add-Ins and Tools / Re: GUID of a diagram
« on: December 11, 2017, 08:19:02 pm »

As mentioned before the properties window does not get filled in when you select a diagram in the project browser.
You can however right click on this diagram and select Copy/Paste | Copy Node GUID to clipboard to get the GUID of the diagram.


PS. I feel uncomfortable with the passive-aggressive tone in your post. :(

Automation Interface, Add-Ins and Tools / Re: GUID of a diagram
« on: December 11, 2017, 07:01:49 pm »
Sorry Viking,

you may expore your eap-file as database and find an ea_guid column inside table t_diagram - but that's only to fool you.

Diagrams don't have their own ea_guid.

If any is shown than the one from the package they are in. Because searching for the ea_guid of t_diagrams always leads me to the packages.


That is just wrong. Diagrams have guid's just like almost anything else in the EA world.


Automation Interface, Add-Ins and Tools / Re: Template for UseCase
« on: December 08, 2017, 11:55:36 pm »
You can get that info. Check the Exception section in the Structured Scenario section.


General Board / Re: Linking a Logical data model to database builder model
« on: December 08, 2017, 08:26:02 pm »
I don't thins there is / should be an automatic linking of data models at conceptual - logical - physical (schema) level.  Going from one level to another you make a number of decisions about the model structure based on circumstances, your style and habits etc. There are many different correct ways to develop a physical schema from a logical one and vice versa.  Don't know how it could be automated to have changes propagated correctly.
This particular client has all their transformation rules defined.
The add-in transforms the logical model into a physical model following these transformation rules.
Then the DBA's review the proposed structure and overrule certain rules if needed.
The tool marks the database objects that have been overruled in order to not propose a change according to the standard transformation rules next time the logical model is being transformed.

In any case, this save a lot of mindless grunt work and helps with the standardization (naming conventions etc..)


Pages: [1] 2 3 ... 517