Phil Chudley – Dunstan Thomas

[Phil Chudley – Dunstan Thomas]

Or, you can use EA’s suppress Line Segment feature to “split” lines across page breaks on your big diagram.

Copy the big diagram (using Project Browser right-click menu)

Paste as Shallow copies n copies (preferably to a new package) of the big diagram

On each Shallow copy, delete elements (Delete key on the diagram) so that you are left with just the elements on a page … work at a high zoom level

Move all elements to “page 1”

use eaDocX to print all these individual diagrams in page order

Wow, its a lot easier to do than to describe and a fair amount of work

Of course only attempt the above when the big diagram is in a steady state!!

The above works, sure, but in the end I agree with eaDocX Support, keep diagrams small and focused, link diagrams together using abstraction (Composite elements or call actions)

All the best

Phil

[Phil Chudley – Dunstan Thomas]

For complex tables I use the new scripting feature in eaDocX version 3.4

Works a treat

[Phil Chudley – Dunstan Thomas]

Thanks for your reply

I have some digging, and discovered a bug in EA and eaDocX works fine as you have said

Just for information the bug is

Create a Requirement in EA with tagged values of type Memo
Populate with data
Export to CSV using EA and its CSV specification
Open in Excel and add some more requirements including the Memo tagged value
Import back in EA and all looks fine, the memo is populated and shows the familiar * and all data is there.

BUT when put in eaDocX no data for the memo field!

What happens is the Value of the tagged value is null string instead of , I fixed this with a simple Script in EA. The only other way is open the memo note and resave it.

Using eaDocX only works fine of course

All the best

[Phil Chudley – Dunstan Thomas]

As a follow up I have tried the scripting with Full Tracing and the error is

System.IO.FileNotFoundException: Could not find file or assembly ….

File name: Interop.MSSCriptControl, Version 1.0.0.0 …

at eaDocXAddin.EAScript.runUsing(…

Does this help track down the issue and offer a solution?

All the best

[Phil Chudley – Dunstan Thomas]

Thanks for the update, is there any specific areas in the setup that I should look for? Is the likely cause due to the script call being blocked or something else.

The error message received does not really many clues as where to look.

I have tried running EA as Administrator, but that had no effect

I have tried the basic APITest script, but alas the same cannot generate document error.

All the best

Phil

[Phil Chudley – Dunstan Thomas]

Any update on this apparent incompatibility between the new scripting feature and Word 2013?

[Phil Chudley – Dunstan Thomas]

I am having a play with the new scripting feature and I have noticed the following

In the profiles section I change the formatting of a element type (and its available stereotype) to use a script (I have written one, and I have also tried the sample Table2 script), and when I return to the preview section, the element is marked as “Excluded from Section”

In addition, if I select a package in the project browser and then add this as a section to the document, ALL the elements are not shown in the preview

In addition I get the error “Cannot generate document” whenever I have attached a script to a profile, (both my script and yours).

Are the two connected? Should attaching a script to a profile mark the element(s) as “Excluded from Section”?

Just as a follow up, I believe the element may not actually be marked as excluded, but it does show in the preview with a X in front of it. But certainly, no elements are included when a package in inserted as a section.[/quote]

I am attaching the eap file and the docs file hope this helps

[Phil Chudley – Dunstan Thomas]

I am having a play with the new scripting feature and I have noticed the following

In the profiles section I change the formatting of a element type (and its available stereotype) to use a script (I have written one, and I have also tried the sample Table2 script), and when I return to the preview section, the element is marked as “Excluded from Section”

In addition, if I select a package in the project browser and then add this as a section to the document, ALL the elements are not shown in the preview

In addition I get the error “Cannot generate document” whenever I have attached a script to a profile, (both my script and yours).

Are the two connected? Should attaching a script to a profile mark the element(s) as “Excluded from Section”?

Just as a follow up, I believe the element may not actually be marked as excluded, but it does show in the preview with a X in front of it. But certainly, no elements are included when a package in inserted as a section.

[Phil Chudley – Dunstan Thomas]

The Compact Document option certainly removes the empty constraints etc, nothing appears at all for empty constraints etc.

However what I was after is an indication that a set of data is missing from the model. So rather than output

(none)

I would like to output

No Constraints Defined!

similarly for other empty sub element collections

Hmm, maybe a change to try the new scripting option in the new beta?

[Phil Chudley – Dunstan Thomas]

Thanks for the reply. This is what I get in a table cell for the Description field of a set of related elements

All enquiries from staff, e.g. specialists, must go through the archives team, which has a limited number of staff.,
The process involved in providing an electronic copy of the required paper artefact is lengthy and time-consuming (see P5).,
Given that the current artefacts are either in paper or microfilm format, these need to be converted to an electronic format before the query can be responded to. This is achieved via standard office photocopier hardware, which is not ideally suited to, for example, scanning microfilm to a PDF file.

These are the descriptions of three related elements.

There indeed is a newline between each description, but there also appears to be an extra comma at the end of each description.

What I hoped to be able to output in a table cell is the following

All enquiries from staff, e.g. specialists, must go through the archives team, which has a limited number of staff.

The process involved in providing an electronic copy of the required paper artefact is lengthy and time-consuming (see P5).

Given that the current artefacts are either in paper or microfilm format, these need to be converted to an electronic format before the query can be responded to. This is achieved via standard office photocopier hardware, which is not ideally suited to, for example, scanning microfilm to a PDF file.

Which is a lot easier to read in the document.

Hope this clarifies my question

Thanks a lot

[Phil Chudley – Dunstan Thomas]

We are all smiles again!! 🙂 🙂

I uninstalled the 64bit version Office 2013 and installed the 32bit version of Office 2013 and it all works as expected.

Problem solved!

[Phil Chudley – Dunstan Thomas]

Thanks you for your reply, and I have installed a complete version of Office 2013, not the Click-to-Run installation.

However, eaDocX does not appear to work 🙁

I can open an existing Word document (in Word 2007 format) and as usual eaDocX identifies no profile and request one to be created. This I do (I have tried both the Full Details profile and generating a profile from the model), and all is fine

I add sections and all features work perfectly as expected 🙂

I perform a full generation and the document is generated and saved correctly 🙂

After closing eaDocX and restarting and re-opening the document just generated, it appears to eaDocX that there is no profile and no sections 🙁 🙁 possibly implying that the profile / sections were not saved after document generation.

The dialog for the profile selection is displayed

This happens every time, I have tried saving in Word 2003 format, to no avail, I have tried different profiles, same result. I have tried creating a brand new document in eaDocX, again same result.

I attach the Word document that has been generated from eaDocX using Office 2014 and upon re-opening appears to have no profile

The only installation difference between my previous version of Office and the new Office 2014 installation, is that Office 2014 has been installed as 64bit, whereas my previous version was 32bit.

That cannot be the cause of the problem, or can it?

Any advice more than appreciated.

Best regards

Phil

[Phil Chudley – Dunstan Thomas]

Thanks for your response, I will send you what I am seeking to achieve, I will prepare an example to illustrate this.

The pre-condition and post-condition summary do output pretty much what I want so thanks for that, like EA eaDocX is just full of hidden gems 🙂

[Phil Chudley – Dunstan Thomas]

Correction to above post in my profiles I am using in-line VERTICAL tables not horizontal as stated in the post

[Author]

Posts