Messages

1

Automation Interface, Add-Ins and Tools / Re: Create Learning Center

« on: April 29, 2016, 06:04:37 am »

I even tried to copy the 'Books' directory and just changed some text, but after running the addDocumentationPath script nothing is changed, so the function doesn't seems to work.

Qwerty, I think it would be great if we could create learning center pages for our project, to, for instance, teach new EA user's how get started using the tool and describe our specific processes. Any other ideas how to achieve that?

2

Automation Interface, Add-Ins and Tools / Create Learning Center

« on: April 26, 2016, 10:48:06 pm »

I am trying to create our own learning center. I managed to create a new learning center pages with the script "VBScript Create Learning Center".

Now, I'm trying to load the created learning center with a simple Jscript by calling:

Code: [Select]

Repository.AddDocumentationPath('Enterprise Architect','C:\\LearningCenter\\Books',0);
The AddDocumentationPath returns true, but the learning center does not update with my pages as I expected. Am I missing something?

Does anyone have experience from creating Learning Center pages or know why nothing happens when I call AddDocumentationPath?

3

Automation Interface, Add-Ins and Tools / Re: RTF-Report - Custom SQL - Hyperlink in Notes-f

« on: February 03, 2015, 08:18:27 pm »

I just discovered that this is only valid if #OBJECTID# is not null, that is, if your model template are linking to a custom fragment from the element. In my case I can get the element notes, but not the package notes, doing like this.

Model Template:
package>
element>
{myCustomFragment}
<element
<package

myCustomFragment:
custom >
{ElementName}      
{Element.Notes}
< custom

In your case, you will get the #PACKAGEID# and therefore can get the  Pkg.Notes

Model Template:
package>
{myCustomFragment}
<package

myCustomFragment:
custom >
{PackageName}      
{Pkg.Notes}
< custom

4

Automation Interface, Add-Ins and Tools / Re: RTF-Report - Custom SQL - Hyperlink in Notes-f

« on: February 03, 2015, 07:30:22 pm »

I think I have found a workaround for this. I filter the elements I want with my SQL query  like this:

SELECT t_object.Name AS ElementName  
FROM t_object
WHERE …

Then in the custom field I use the ElementName, but instead of a custom field for notes, I use the generic “Element.Notes” (cut from some other template) :

custom >
{ElementName}      
{Element.Notes}
< custom

I’m not sure this solves you problem, but it seems to work fine in my case.

5

Automation Interface, Add-Ins and Tools / Document glossary

« on: February 03, 2015, 06:45:01 pm »

When generating documents with the report generator, we need to have a document glossary with only the terms used in the generated document. We would like to, in some way, compare the terms in the EA glossary and only pick the ones used in the document. Do you know if this is possible to achieve in any way? I was thinking of two approaches, either recursively search all the packages included in the document to find the used terms or in some way search in the generated document for matching terms. Any ideas?

6

Automation Interface, Add-Ins and Tools / Re: Show stereotypes of child packages in package

« on: January 08, 2015, 12:36:22 am »

Thanks q!

I tried this, but I can only get it to work on elements (e.g. a class elements) but not for packages. Do you know if there is any difference between packages and other elements, when using shape scripts?

Packages already have a native compartment for the child packages (showing the type icon and the name ). I would like to modify this and show the stereotypes of the child elements in this compartment.

/Henrik

7

Automation Interface, Add-Ins and Tools / Show stereotypes of child packages in package

« on: January 07, 2015, 09:08:00 pm »

I want to show the stereotype of the child packages and the child elements in a package element in a diagram. I guess it would be possible with a shape script, but I can't figure out how to change the native compartment for sub elements in the package element.

Package element example:

--------------------
Package Name
--------------------
(icon) + ChildPackageName
(icon) + ChildElementName
-----------------------------------------------

Do you know if it possible to write a shape script that adds the stereotype of the child packages?