EA V8.0 - Doc Generation

[Sunshine]

Version 8.0 is now out and so I've just tried it on a copy of a production model. An EAP file.

Is there anyone out there who is experiencing doc generation issues with EA V8.0?
From the same EA model I've generated two RTF documents using V7.5 with V8.0 and then comparing them. I've generated these documents using the master/model document method and I'm experiencing the following issues;

• diagrams missing
• sections missing
• Inconsistent indentation
• Inconsistent justification

I'm in the process of investigating further but I'd be interested to know whether its just me. :'(

[WorkerBee]

We are facing the same problems.
If lazy loading is turned off the situation improves a little bit.
But ... in our docs for example only the name of the FIRST element gets rendered, other fields (status etc) work as expected. Weird.
I already have sent a bug report.

[AndyJ]

I'm not sure that you're seeing the same bug/feature as me...

...in Project Explorer, are your diagrams "inside" the use cases?

I've just noticed that if diagrams are contained in a use case, they don't appear in generated documentation.

If you lift them out to the same level as the use case they do appear...

Is this the same issue?

Please note I'm using 7.5.848

[Michael Proske]

I started doc generation today with EA 8.0 with an 7.5 file and template and stopped it immediately. For me it seems that EA will return 2 packages instead of one when child packages exists even if child packages are not included. That causes a lot of trouble. I did not send a bug report. Also the document doesn't look like in EA 7.5. I will wait if the bugs are closed before i upgrade to 8.0

[bnils]

We had a minor problem in the Document Template Editor. For some reason, at some workstations, the template code was messed up (field names were really strange), the generated documents were however ok. the messy template code could be solved by enabling "View|Field Names", then the code returned to a nice readable form. Im not sure wheter this is a bug or not, have not reported it as such anyway.

[Keith Ralphs]

I too have this issue. My version is, despite checking the 'Include all diagram elements in report' option, from a diagram containing 13 linked elements I now get a report that contains 2 elements with Version 8. In Version 7.5 I get the full set of elements as expected. Not impressed  .

Hey Mr Sparx, please fix this and issue an update.

[Graham_Moir]

We had a minor problem in the Document Template Editor. For some reason, at some workstations, the template code was messed up (field names were really strange), the generated documents were however ok. the messy template code could be solved by enabling "View|Field Names", then the code returned to a nice readable form. Im not sure wheter this is a bug or not, have not reported it as such anyway.

Just for clarification this "messy template code" issue can arise purely in 7.5, I don't believe it's related to the v8 upgrade.   I think it happens on certain machines because it's a local setting to each machine.   We've seen it a number of times way before 8 was available even in beta.

[Graham_Moir]

I too have this issue. My version is, despite checking the 'Include all diagram elements in report' option, from a diagram containing 13 linked elements I now get a report that contains 2 elements with Version 8. In Version 7.5 I get the full set of elements as expected. Not impressed  .

Hey Mr Sparx, please fix this and issue an update.

Everyone who's having this problem should submit a formal bug report to make it clear to Sparx that this is a widespread problem.

[meierch]

I have also the effect that for diagrams the elements are no longer reliably reported. In some cases all are shown - in others a few - in others none. Nested elements are more often affected than others.

If I switch back to EA 7.5 everything works as expected.

[suki]

We have probably similar problem. We use Oracle 11 database and generation with old version 7.5.850 is ok.

I've generated the same document using new EA version 8.0.855 and many part of document were missing.
During generation the document were shown many errors while application went trough "problematic parts".

Messages are:
1. ORA-01795: maximum number of expressions in a list is 1000
2. ADODB.Recordset [-2146824584] Operation is not allowed when object is closed

[Graham_Moir]

Just checking - have all you guys formally reported this issue?
And if so have you had any acknowledgement/confirmation from Sparx that it's a problem and they're working on it ?

[Sunshine]

I've been snowed under with work since I posted this originally so haven't investigated this further yet nor have I reported it to Sparx. I wanted to verify whether it was a real issue or just one of those things that happens to only me.

[WorkerBee]

Actually I have sent two bug reports.
Both were confirmed as follows:

I have verified that the full data is not rendered for Virtual Document generation.
This has been lodged for correction as issue: 100454

... and ...

I have run this through builds 850 & 855, and yes this does drop the top
table row in build 855.
I have lodged this as issue: 10045479

Well, build 855 is nice to work with. But, for document generation, we are still using build 850, which was the best release so far.

[meierch]

I have submitted a priority bug together with a small model consisting of three classes and two diagrams which demonstrates the bug that in case of nested elements only the root element is reported along with diagrams.

I hope this gets fixed as we are setting up a large modeling effort at work where we would like to use the added use case modeling functions but where we also need to be able to run the already defined reports.

[Sunshine]

Okay so since I first posted issue I've been too busy to look into this issue any further until now. What I have found is that the sections that were missing in my RTF document seemed to be caused by an integrity error. When I ran EA tool to fix these errors  the problem of missing elements disapeared. The weird part was that V7.5 didn't seem to mind and created the document in full but V8.0 didn't until the errors were fixed.
The differences between V7.5 and V8.0B856  generated RTF documents now seem to be minor with a few extra blank paragraphs and the odd centre justfied text that was originally left justified. I found when I created a new template it seems to work okay.