eadocX Support

[eadocX Support]

Looks ok to me.
You choose the Word paragraph style in eaDocX, as you have done, then regenerate the document.

[eadocX Support]

Good idea. There are currently no diagram type, or diagram stereotype-specific options, but it’s something we have thought about.
We originally looked at changing the way diagrams were formatted (title, description, figure number etc) but this was too slow and complicated in word.
…but this looks like a better idea, and a good time-saver.
So how about:
– for each diagram type, and diagram stereotype
– allow a document-level, or application level :
(1) do not print (2) print diagram plus contents (3) print contents but no diagram
– also maybe suppress the diagram description, in same way
Would this be ok? We can look at it for the next minor release, which should be in a few weeks time (May/June 2014)

[eadocX Support]

No.
Not because we don’t want to let you determine the order, but where to specify that order?
In response to a previous question, to make the order predictable, we now print the items in alphabetical order of their element types, that is, Change, Decision, feature etc.
I can’t see a place in the EA diagram where you can specify the order, so it would have to be in eaDocX, but we don’t know how many or which diagrams will be in any given document until we generate it.
So it would have the be an eaDocX global setting, which would apply the sort order to all diagram contents. Is this sensible?
I’m happy to change this, as I agree that it’s annoying, so I’m open to solutions.

[eadocX Support]

Thanks for the excellent explanation.
You re quite correct: TAB characters were lost on these memo tagged value attributes. This was because EA seems to save the data in a different way from regular Notes attributes.
This will be fixed in the next maintenance release. It will be 3.4.2, so look at the website for when this will be available.

• This reply was modified 10 years, 7 months ago by eadocX Support.

[eadocX Support]

Please can you mail your eaDocX profile, and a sanitised version of your EAP, to support at EaDocX.com and I’ll take a look.

[eadocX Support]

You’re SO impatient.
I generally say in advance which release a fix will be in, but its hard to say exactly when that release will be made available.
In this case, 3.4.1.1 is now available 🙂

[eadocX Support]

I have just re-checked V3.4, and we seem to be correctly printing the Description field of elements, and meno-type tagged values.
BUT
Only where the data has been entered via the EA user interface.
It’s quite possible to put data into these fields which has been imported into EA, either via copy/paste, import via the API of other means. EA seems happy to save almost any character data in these fields, but eaDocX will only correctly print dat imported via the UI – otherwise, we’d have an open-ended requirement. I’ve had problems with this myself, and have decided that the data needs to be cleaned before inserting into EA.
For example, the ‘Tab’ character, which I don’t think can be put into these fields via the EA UI, so we don’t process it.

[eadocX Support]

Ah – that gives me MUCH more to go on…

[eadocX Support]

Quite correct!
Error on my part: I never thought that the same document might contain the same use case details, down to the Scenario Step level.
This will be fixed in v3.4.1.0 which I am just completing now, and should be available on the website on 26/3/2014.

[eadocX Support]

Taking your suggestions in order:
1. Related Element heading levels: I fixed this in 3.4

2. Extra spaces after tables. This is needed just in case the next thing to get printed is also a table, in which case Word will assume they are the same table and join them together. This is probably the longest-running eaDocX issue, and I look at it again for each release, and each time I try to remove the space, lots of other test cases fail horribly.

3. Have you tried switching Compact Document to FALSE?

4. What’s the formatting from ‘System Function’ to ‘System Element Functions’? Rel. element, or simple relationship attribute ?

[eadocX Support]

Developers out in India have tried it, and they say it works in their environment, so it looks like another of these nasty setup-specific issues. I will continue to investigate.

[eadocX Support]

Can you send me a sanitised example?

[eadocX Support]

Hi,
I have tried to reproduce this issue, but with no success.
I created a new document in v3.3, and excluded some stereotypes. Then re-loaded into 3.4, and the stereotypes showed-up correctly in the Profile.
Can you send your Profile (XML) file to support@eadocx.com, and I will investigate further.

[eadocX Support]

I confess that I haven’t tested it with Office 2013, but I will do this when I get home at the weekend.
can’t see why the Office version should be a problem: we just pick up the text of the script from EA, then run it it outside of EA (I think), then just get the resulting HTML and put it into the Word document along with the rest of the eaDocX-generated stuff.
…but I’ll have a look.

[eadocX Support]

Yes!
To use a different profile for the same element type, you need to make some of the sections into Element Reports. Element Reports get to define their own local Profiles for the element type which they print.

[Author]

Posts