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 - Paolo F Cantoni

Pages: 1 2 [3] 4 5 ... 409
31
Because I have users, quite a few of them, who understand the long form better.

Perhaps there are other ways for your users to understand directionality?
I think it's more about helping reduce semantic impedance (is that correct Uffe?).  A long time ago, I understood that some (many?) people have difficulty abstracting.  It is clearer for them to see the concrete form proposed by Uffe as opposed to having to concretise the (more) abstract form proposed by Simon.  It's all about reducing friction for the user.

In fact, we distinguish between the name of the relationship (the most abstract - and noun form) and the caption which describes the (more concrete - and verb form) action of the relationship.  Uffe's version is justs the extension of the action.  We name the metatype after the name, but the Quicklinker after the caption.

Paolo

32
Presumably, you do that by having some of your people using the technology at one location and the rest using the technology at a different location? Unfortunately, for imported technologies I don't think you can switch off the internal location, so yes that's the version that everybody will get.
Yes, although by location I mean different URLs.  I "improve" the MDG on my local hard drive.  Power users get the stable development as UAT at one URL.  The masses get the "approved" version at a third URL.

Paolo

33
I'm not importing into the repository as a resource (I thought this was deprecated - may be wrong).

The old version of importing to resources was deprecated. That used to break out all the parts of the technology and import them into their respective tables (e.g. profiles imported into the t_stereotypes table). The new version of importing to resources imports the whole technology file undigested and then uses it as just another place to read technologies from at start-up. (I have no idea if what I just said makes sense)
It does make sense, Neil,

But presumably, if we do that then EVERYBODY has to use the same version of the MDG at the same time yes?  We allow multiple versions of the MDG to be "Live" at the same time. Can that still be done under the imported scenario?

Paolo

34
Automation Interface, Add-Ins and Tools / Oracle Reverse Engineer
« on: May 28, 2018, 02:55:51 pm »
One of our users is trying to reverse engineer an Oracle DB.

We're usually a SQL Server shop, so I haven't done one of these for ages.  Using b1351, he seems to be doing all the right things on the Import from ODBC dialog.  Are there any "gotchas", "secret sauces" that we should be using?

The result is that after asking it to reverse engineer everything, for the tables, we get the table objects, no features or relationships - just empty boxes...

TIA,
Paolo

35
But it doesn't help Alain. I think you still have to unload/reload the MDG to re-read the entries.  We found it quicker, easier and more reliable to do it from the XML files.
Paolo

BTW: Our repository doesn't have any t_documents marked "TECHNOLOGY".

If i choose to import the MDG to the local Database , it writes it as an entry in the t_document table.
The unload / reload was a issue, when we used to add MDGs  by specifying the path in 'MDG Technologies - Advanced' window. however after we started adding it in the resource (to the repository) a restart of EA usually fixes the Quick linker.

May be i'm missing something.
We're both missing something.  I'm not importing into the repository as a resource (I thought this was deprecated - may be wrong).  We find it faster to unload/reload than an exit of EA and restart.

36
General Board / Re: System Resource Exceeded on Large Deletes
« on: May 28, 2018, 01:12:53 pm »
Hi Rich,

if it's only on .EAP files, you might try changing the Access Locks count in the registry.

HTH,
Paolo

37
An MDG added in the DB is stored in the t_document table (ElementID = TECHNOLOGY)

I believe the contents are stored as zipbin, you must be able to write some code to replace the <QuickLink /> content, and update the MDG dynamically.

Not sure if this is what you are after.
But it doesn't help Alain. I think you still have to unload/reload the MDG to re-read the entries.  We found it quicker, easier and more reliable to do it from the XML files.

Paolo

BTW: Our repository doesn't have any t_documents marked "TECHNOLOGY".

38
Hi Alain,

Unfortunately, they're NOT stored in the DB!

We have a related issue.  We generate the Quicklinker entries from an Excel Spreadsheet (similar to the ArchiMate relationship matrix).  We have some automation to embed the new QuickLinker definitions into the MDG and then we unload/reload the MDG.

Works for us.

Paolo

39
General Board / Re: Default to not show connectors in other diagra
« on: May 25, 2018, 06:07:36 pm »
The tool offers support for this, via automation. We use scripts to 'tidy-up' context diagrams, so they show only the associations of the system of focus. I admit, it's something you have to build yourself but it is possible and not difficult!
Maybe a decade ago, I suggested that when a relationship is added, EA could pop up a dialog (similar to set visible relations) that determined which diagrams the new relationship might appear on, and you could deselect those that you didn't want it on.

It might be time to resurrect this concept.

Paolo

40
Bugs and Issues / Re: EA 14 Import DB fails
« on: May 24, 2018, 06:58:12 pm »
Hi,

I try to run an Import DB Schema in EA from an existing DB via an ODBC data source.
Once the Import starts, I get an 'Error retrieving table list' message when using EA 14 build 1420.

Running the same test in EA13.5 works fine.
Bu**er!  I was going to import a DB tomorrow.  Anyone else seeing this?  What is the DB Technology involved?

Paolo

41
I think you would render an event of Tiggers as having a top made out of rubber and a bottom made out of springs...

(And pay due reverence to the combined work of A A Milne and Walt Disney.)
and it's not yet Friday!  8)

Paolo

PS you can also use them for ArchiMate Zebedees...

42
Bugs and Issues / Re: Synchronise Stereotype via API odd behaviour
« on: May 24, 2018, 04:10:59 pm »
Thanks.

it all seems to be in order. there is no duplicate stereotype in the UML Types options, I am somehow thinking this might be "Wild" - I see that MDG TV's are also added to the t_xref table. Also that the t_xref record includes the tag details in the description
[myTag]D4F0310E-E861-2fe8-B98D[/myTag]-E17A6212FB46}  -- does anyone know what the Client and this embedded tag relate to in the database, I could not find anything?

Cheers
What's the Name and Type of these t_xref entries?

Paolo

43
Hi All,  First let me say THANKS for all the great help and advice.  I think I need a bit of time to go through all of this and make a call.  The reason I prefer VB.net is that I have at TON of EA automation "helpers" written VB.NET as separate executables to do all kinds of stuff and have gotten to know the EA API quite well. That includes this crazy thing (https://www.youtube.com/watch?v=tpvqeNLQnxQ) that I wrote about 2 years ago that I use all the time in my work.  Much of what I do involves interchanging data with MS Excel (both reading from Excel and writing to it).  In that world, it helps a lot to use a language similar to Excel VBA, so VB.Net works better for me for that reason, too.  Plus, I'm just old, and I don't want to change my ways!   8)

I can do C# if I need to and maybe I just need to eat my spinach in this case and get on with it (or maybe I don't).    I'll let you all know how I get on, but thanks again for all the help!
I hear you.  When interacting with MS office, we tend to use VBA - we have some libraries that we build on top of and so it makes it relatively easy.
We have our diagrammer Add-In in C#
We started to use JScript for scripts but found VBScript allowed us to leverage our investments in VBA.  There was also the issue of how to specify ByRef parameters in JScript (which we couldn't).

I, too, am old.  But fortunately, people tell me I look 10 years younger.

PAolo

44
And it is MUCH easier to hide a connector that you can see than show a connector that you can't see. If you open a diagram and see that a new connector has suddenly appeared, that means that there is new information in the model that the person who created the diagram wasn't aware of. If it belongs in the diagram, great; if it doesn't, hide it. Better that than opening a diagram and not knowing if there is new information that may need to be shown.

That's certainly pragmatic.  The ArchiMate shapescript is probably the second or third worst in the base product, but the most worked on by your more knowledgeable customer base.  It would equally be as pragmatic to ask for their improvements and fold them into the product.
One thing we've toyed with is a "widget" to indicate that there are hidden relationships on the diagram. It's easy enough to run a query (behind the scenes ) to determine if there are hidden relationships on a diagram and add/remove the widget as appropriate.  Obviously, it would be better if it was automagical.

"Information: This diagram has hidden relationships.  You may be missing some information.  To see which relationships are hidden, use the "Set Visible Relationships" dialog [Ctrl+Shift+I]"

Paolo

45
Sounds reasonable. 

Can you give examples of how the macros would be used?  Your QuickLinker line and the resultant text on the QuickLinker menu?

What other objects might get placeholders (besides origin/destination element name)?

Paolo

Pages: 1 2 [3] 4 5 ... 409