Ian Mitchell

[Ian Mitchell]

It sounds like there is either (a) an issue with the EA content, or (b) eaDocX has found something in the model it doesn’t understand.
If (a) then run the EA Integrity Check (in V15: Configure / Model / Integrity check) which can find errors. If this does not work, then export a large part of your model to an XMI, delete that part of the model, then re-import. This removes all kinds of errors.
if (b) then I can only look into it if I have some sample data to work with.
Thanks
Ian

[Ian Mitchell]

If you can send me a small XMI with the data which makes eaDocX fail, I will have a look at it. The data probably just has a state which I have not seen before.

[Ian Mitchell]

Does this happen for every kind of Quick Document? Or just on one part of your model?

[Ian Mitchell]

Hi JD,
I have run Model Expert with EA16. The only outstanding issues I have with it are stability (occasional, un-characteristic crashes) and with accessing the new QEAX database, which seems to have a few funnies (MX has A LOT of SQL…).
I have also only run it with the 32-bit version.

[Ian Mitchell]

You are quite correct!
Issue has now been fixed in v5.0.5.9, now on the website. Sorry about that.
You might like to know that we plan to retire some the document management functions of eaDocX in V6, specifically:
– assigning people to document roles
– definition of those roles.
– ideas about approval and sign-off of documents.
Our research indicates that organisations who need this kind of function use dedicated document management systems, and use eaDocX to just create the documents, not managem them.
If you want to know more, please contact me..
Ian

[Ian Mitchell]

Noteice that it has to be a Named Range. That’s something you do in Excel: i think you just select the area you want, then right-click and choose ‘DEfine Name’, or something like that. Then eaDocX will use that name to fetch the data and put it into the report.

[Ian Mitchell]

Hi Mike,
I’ve reproduced the diagram you posted above, and re-created the same document you see, so we’re both on the same page.
Albeit not the page you want to be on…
To re-create your example, I told eaDocX to print each of the TVs by name, for any InterfaceBlock element. Whic is all that eaDocX allows us to do.
There is no way to say ‘only print non-inherited TVs’, or, ‘only print the TV with where an element has it’s own value for it.
I think that maybe what you are asking for is a more generic feature, which says ‘print all my Tagged Values’, with a further option to ‘print TVs specific to this elemnt’ or the opposite ‘print TVs INCLUDING those I inherit’.
Is this what you need ? Or am I missing something?

[Ian Mitchell]

I thought that Start- and End-events are just stereotypes of Event (or, as it’s BPMN, maybe stereotypes of Class..) To get their constraints and internal requirements, just add those from the ‘subelement’ tab.

[Ian Mitchell]

Hi Marie,
Thanks for the test file. Good idea to send it as a Zipped .txt file – I just renamed it to .XML, and it loaded fine into my PostgreSQL test database.
Just like when you loaded it into a new repository, it seems to create the dashboard OK. I tried to create a meta-model diagram from the dashboard, and there was a temporary error, but then it displayed OK.
BUT
…your test data didn’t touch quite a lot of the function Model Expert, as there are no connectors.

When a package creates errors like this, but then they go away when the package is exported and re-imported into a new repository, this shows that there are low-level inconsistencies in the source data. Lots of these are easily removed using the Ea built-in EA integrity check (Configure / Model / Integrity / Project Integrity), but it doesn’t find everything.
Taking a backup, exporting the package to XMI, deleting the package, then re-importing it works well, though beware if the package is heavily liked to other parts of the model.
Less dangerous way is to try Model Expert on sub-packages, and see which one creates the error, then repeat the steps above on a much smaller scale.
I hope this helps
Ian

[Ian Mitchell]

All users of EA must install Model Expert on their own machines.
Sorry if this was not clear in the help.

[Ian Mitchell]

where does this appear? At install time ?

[Ian Mitchell]

Thanks Marie – is it possible for you to post an XMI of one of your packages which shows this error? I tried it on a few test cases, but your data is clearly a bit different from all of them! Please remove any confidential data from the XMI – I just need the structure.
Thanks

[Ian Mitchell]

OK – found the problem. Seems like postgreSQL does casting of variables slightly diffrently to SQlServer and the other DBMSs.
I THINK I have fixed this, but I haven’t tested every bit of SQL, so please re-post here is you find any more issues.
Sorry for the problem – issue is resolved in v2.2.3.0, now available for you to download.
Ian

[Ian Mitchell]

Hi Marie
This looks like an incompatibility between DBMS types – it always seems to be postgrSQL which causes the problems!
I am investigating….

[Ian Mitchell]

see reply to this latest post in another thread.

[Author]

Posts