eadocX Support

[eadocX Support]

Strange. I didn’t make any changes to this for v4, and I’ve just re-checked the test cases, and they seem ok.

[eadocX Support]

Hi Daniel,
We had a long discussion about whether, for a new workbook, it’s better to include children of elements, or make it a user-selectable option.
In the end, we decided to make it the default. You can go back to NOT including children of elements in the settings for a Worksheet.
What decided it in the end was that during testing, I kept being surprised when the list of elements was smaller than I expected, then remembered I had to click the ‘children’ option, and this happened so many times we decided that exporting children should be the default.

[eadocX Support]

Also, please can you submit each issue as a separate thread. Makes it easier to see which answers belong to which questions.

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

[eadocX Support]

I’ll have a look at this. I didn’t test this

[eadocX Support]

I think I understand the requirement, but the challenge we have is that a table could come from lots of sources. It’s just a list of “things” which might be from a package, but also from a report. Anything which adds a caption to tables needs to work in all those cases. We did add the option for a title above each table, but that’s a fixed string.
So my question is, how would you specify what the table caption would say, so that it covers all types of table? And make it backwards compatible?

[eadocX Support]

Oh, that’s very odd. What OS and screen resolution are you using?

[eadocX Support]

Sorry, never used it.

[eadocX Support]

webview?

[eadocX Support]

Ah – I love this one….I have spent many (un) happy hours trying to find out why it does this.
What I KNOW is that eaDocX sends some HTML to Word for each table, and that usually includes the column width.
Word then looks at this and thinks “I know that’s what they ASKED for, but what would look nice?”
So that move stuff around.
Where there are long strings with no spaces in between, like this_is_a_long_variable_name, then it won’t break the string, but make columns wider. It sometime just tries to make stuff “neat” by just changing widths for no obvious (to me) reason.
It’s just part of the adventure of gluing two very complex bits of software together – Word and EA – each of which are full of strange behaviors.

[eadocX Support]

Or, if you REALLY have to keep modelling things this way, then you can create an eaDocX script. That lets you do pretty much anything.

[eadocX Support]

Is there a relationship in EA to associate BR010701 with My-Rule.001? Other than the description of one has the same string as the name of the other? If so, eaDocX will now print the notes: we don’t match on strings: what to do where there are multiple matches?
BUT
If the description field of the BR has an EA link to the MyRule, then you can print a hyperlink to the Rule.
Better still, link the BR and rule by a connector, then you can do what you want easily.

[eadocX Support]

Firstly, all BPMN elements can have eaDocX Profiles. You just have to find out which ‘true’ meta-type they are stereotypes of. Most BPMN things are stereotypes of ‘Class’, but there are also other meta-types. To find out, just create ‘Quick Document’ from the package, and eaDocX will figure out all this for you.
AS for the rest of your question, I’m not sure which bit is an EA problem, a problem with your model structure, or and eaDocX problem.
I suspect a bit of all of them.
When I’m teaching people about modelling, I usually tell them to avoid the structure you have: a package, with lots of different important things in it. You have Use Cases, and Processes, plus I guess other stuff related to these two. I always say to create sub-packages: one for the use cases, one for the processes. Tidier, and easier to manipulate.

[eadocX Support]

OK – I’ll change it for V4 to use …AppData/.. instead. That should work better for you.

[eadocX Support]

For each Linked document, eaDocX has to write it out to a file called temp.rtf in the same directory that the document is located. Looks like this has gone wrong. Maybe temp.rtf is locked, so can’t be overwritten?
I have updated the error message in V4 to be a bit more helpful.

[eadocX Support]

Quite right. No idea how long this error has been in the code – years!
Anyway, thanks to you, it will be fixed in V4, which is coming soon.

[Author]

Posts