Messages

1

General Board / Re: Data Model HTML Documentation

« on: March 06, 2013, 07:48:26 pm »

Yes, and look at the 'Body - Diagram' web style.  You can comment out or delete parts of this to make it more 'user friendly'.  I only leave the dagram, a 'generated on...' datestamp and notes.  No sterotypes or GUIDs etc. which only serve to confuse business users.

However what I would like is a little more customisation under the object properties - these usually have business relevant information but the webstyle options seem to be more limited / difficult.  Then again, I'm not a web developer. You need someone familiar with style sheets to work with you.

2

General Board / Re: Inserting "Generated on:" date into html

« on: March 13, 2013, 07:39:24 pm »

Thanks Phil,
confirmed - that code works perfectly!

Added it into the 'Body - Diagram' and 'Body - Object' html templates.  This seems to cover pretty much all the web pages we use - certainly enough for support purposes - to know which version of a website people are using.

cheers,
Nick

3

General Board / Re: Inserting "Generated on:" date into html

« on: March 13, 2013, 03:23:31 am »

Ah, I had pretty much the same code, but with the line :
new Date();

instead of:
new Date(document.lastModified);

I can see what it should do - looks most promising.  Will confirm tomorrow whether it has worked.

PS I also prefer your more succint code !

Thanks Phil,
Nick

4

General Board / Inserting "Generated on:" date into html

« on: March 13, 2013, 12:23:42 am »

There's lots of great html fragments that can be substituted when generating html reports.  Things like "#CREATEDATE#, "MODDATE" etc. These are for properties of EA objects.

What I want is something that will put the date the html is generated into any page - e.g. on Diagrams, Objects, etc.

It would be great if there was simply a global #TODAYDATE# or similar.  Or perhaps a guru knows how to modify the customisable Javascript that generates html, to put the date into certain places?

I've managed to put some javascript into the 'Body - Diagram' and 'Body - Object' html, but this simply gets inserted as javascript into the html, thus is evaluated every time the pages is displayed - always returning the current date.

Any hints appreciated!
Nick

5

Automation Interface, Add-Ins and Tools / Re: Composite elements and HTML report

« on: March 13, 2013, 03:35:14 am »

No, you can't choose from the parent whether to navigate to the child diagram or properties.

However, as you've probably found out by now, once the child diagram is displayed, clicking on the same element again (assuming it is on the diagram) will show the properties.

We use this feature to good effect all the time.  I think it's quite a good solution.

Nick

6

Automation Interface, Add-Ins and Tools / Automation of "Create Document to Artifact"

« on: June 12, 2012, 10:44:42 pm »

Being able to store RTF documents within a repository is great, because hyperlinks to them stay consistent, so HTML websites do not end up with broken links if a network drive changes or is not accessible.  This is made even better using the model documents / document artifacts and "Create Document to Artifact" option.

So, we have a number (quite a lot!) of these reports stored in document artifacs and linked to from the notes sections in certain elements.

We would like to be able to automate the generation of multiple of these documents, which otherwise have to be generated manually one-by-one in a time-consuming and labourious manner.
 
I have some code that will iterate through packages to find the elements with a stereotype of "document" (ideally this would also look for a Trace dependency relationship to an element with stereotype of "model document", but I haven't got that sophisticated yet).

The problem I have is finding any information that will let me invoke / automate the interface equivalent to right clicking on the document artifact and selecting "Create Document to Artifact".  I have found the Repository.CreateDocumentGenerator() object, but I suspect what is needed is more of an 'Element.CreateDocumentGenerator()' interface.  The DocumentGenerator Class seems to be based on the repository document interface, which is saving documents to the file system rather than within the repository.

The help I am using is in the EA User Guide, and I've found the Jscript documentation example. Neither of these get close.

Has anyone tried to automate the 'create document to artifact' process using the API?  Or have ideas of how to do so?

The only way would seem to be emulating the behviour of the "Create Document to Artifact" function in code, and using a temporary file.

Seeing as the 'model document' / 'document artifact' idea seems to be all about modelling how to generate documents, it's a shame there is not way to automate it.
 
Nick