Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: Geert Bellekens on November 03, 2022, 12:32:03 am
-
When evaluating version 16.1 I generated a document based upon a fairly complex virtual document.
When comparing these documents, I noticed a couple of differences
- Heading levels are sometimes lost: e.g. Titles under 4.2.10 Traceability have lost their style, where they should have style Heading 4. Weirdly enough this didn't happen to the titles under 4.1.10
- Headings levels are suddenly way too high. e.g. Title 4.5 Bill is an Advance is has Heading Level 2, where it should have Heading Level 4 (as in the 15.2 example)
- SQL search based content is not generated. E.g. The Rules sections in the 16.1 document are all empty, although the search is present int he model and returns elements.
I've included the sample documents generated in the two different versions in my bug report to Sparx
Looks like where stuck at 15.2 for a while longer.
Geert
-
- SQL search based content is not generated. E.g. The Rules sections in the 16.1 document are all empty, although the search is present int he model and returns elements.
I found the cause for this one. Turns out this is only a problem is the elements resulting from the search do not appear on a diagram somewhere.
Funnily enough this rule (should appear on a diagram) is only applied for content from search results. It works perfectly find if I tell the model document to generate the document from a package that contains the exact same elements.
Geert
-
tested in the new version 16.1.1621 and it actually got a bit worse.
My numbering is now completely messed up
1. Heading 1
2. Heading 1
1.1 Heading 2
and so on...
and in other cases I have
1.1 Heading 2
1.1.1 Heading 2
1.1.2 Heading 2
1.1.2.1 Heading 2
So the numbering is correct, but the headers styles aren't
I've reported these findings to sparx support.
Geert
-
According to the release notes this should have been fixed in version 1622:https://sparxsystems.com/products/ea/history.html#1622 (https://sparxsystems.com/products/ea/history.html#1622)
Geert
-
the new bug introduced in 16.1.1621 seems to have been fixed again, but no improvement on the original problem.
Geert
-
Thank you for the note about this.
I switched to 16.1 AND changed in parallel my export template. I was going nuts - I constantly thought I made something wrong in my new template. Hope this is fixed very soon! This is very annoying.
-
Just wondering: What is at the moment the most stable version for document generation?
v15.2.1560 or v16.0.1605?
Edit:
Just "dual installed" v15.2.1560 and generated the document using the same model with the same template as I used with 16.1.1622 and the headings are OK, but I recognized that I had this ugly "no padding" issue with 15.2 (see https://sparxsystems.com/forums/smf/index.php/topic,46830.msg274729.html#msg274729 (https://sparxsystems.com/forums/smf/index.php/topic,46830.msg274729.html#msg274729)) ??? :'(
-
Definitely 15.2.1560. I'm not upgrading untill they fix this issue.
Geert
-
I am still using 15.2.1560 for document export, but I saw document generation fixes in v16.1.1626 (06/2023) change log. I have not yet tested the new version, but hopefully there is some movement in this topic.
-
I am still using 15.2.1560 for document export, but I saw document generation fixes in v16.1.1626 (06/2023) change log. I have not yet tested the new version, but hopefully there is some movement in this topic.
I did, but still no fix. The main remaining problem is the fact that the heading levels are messed up.
This ofcourse messes up the structure of the document.
So instead of
2.1 Chapter A
2.1.1 SubChapter A1
I get things like
2.1 Chapter A
2.2 SubChapter A1
Geert
-
Really annoying bug and even more annoying that no fix is available yet.
This bug is also keeping me and my clients from upgrading to 16.1. Perhaps we should skip 16 all together and wait for 17, since 16.x does not really have any must have features for the clients I have.
Henrik
-
True. Just wondering whether we could provide a small database file with some content and a document template to reproduce the issues in document generation on Sparx support side. I "only" have a large database which I cannot export (cannot show my real life content without NDA). I doubt v17 will get better without working on the issues with Sparx. Does someone have something like this we can share with Sparx?
My wishes for V17: perfect and FASTER document generation (Edit:) of large documents + ability to store centrally really ALL settings for document generation in the database (as some settings still seem to depend on settings done by the local user).
-
True. Just wondering whether we could provide a small database file with some content and a document template to reproduce the issues in document generation on Sparx support side. I "only" have a large database which I cannot export (cannot show my real life content without NDA). I doubt v17 will get better without working on the issues with Sparx. Does someone have something like this we can share with Sparx?
My wishes for V17: perfect and FASTER document generation (Edit:) of large documents + ability to store centrally really ALL settings for document generation in the database (as some settings still seem to depend on settings done by the local user).
I already did that, 4 or 5 months ago.
Geert
-
Please have a look at my earlier post:
https://sparxsystems.com/forums/smf/index.php/topic,47892.0.html (https://sparxsystems.com/forums/smf/index.php/topic,47892.0.html)
I think this might be related, as updating dynamic content seems to create extra characters, which are sometimes heading paragraph marks.
Stefan
-
Just tested with the new v17 BETA, but unfortunately still the same problem.
I'm getting really annoyed that Sparx keeps ignoring my bug reports and emails. >:(
Geert
-
At least you're enduring that situation. I'm in that game a bit longer than you but gave up a few years ago...
q.
-
I tested again with the second beta of v17 (1701) and lo and behold, they actually fixed it :)
I still have some minor differences between the documents generated in v15.2 and v17, but nothing blocking anymore
- I had a few cases where the fontsize was different for a section coming from an linked document
- The order of elements was different for a model document that uses a query to get it's data
This took 1.5 years, and numerous testing cycles, but we finally got there. :o
Now I only need to wait for a stable v17 release to upgrade my clients.
Geert
-
Sounds promising ... thank you for reporting!
-
Hm, stange. I still have the same problems with 1701.
I get Letter size instead of A4 and my hadings start with 1.1.1 rather than 1.
-
I get Letter size instead of A4
As much as I personally wish it was otherwise, to the best of my knowledge page sizes for all default documents and reports are intended to be letter. It is specified in the base documents. When running a report with the different types of templates I don't know which template the page size will come from.
my hadings start with 1.1.1 rather than 1.
We're still in the process of running more tests. I think now that Geert's issues are fixed (or mostly fixed) we've probably lost the most persistent advocate for getting this addressed. I'd encourage you to send in your templates etc so that we can test your particular scenario.
-
By fiddeling around with my templates I found a solution to get the right header numbering.
So, now I want to get rid of the "letter" format to be able to have A4.
Eve what do you mean with "base documents", the template I use to generate?
-
There is an other problem with document generation in V1701. Several diagrams look odd. Mainly connectors to connect things start and end somewhere but not at the right place at all.
-
I didn't notice that. I'll check again and report back.
Geert
-
Geert are you able to generate A4 instead of letter format and if so how?
-
Geert are you able to generate A4 instead of letter format and if so how?
I haven't tried that either.
Geert
-
I haven’t tried version 17 yet, but in version 16 it is definitely possible to create templates with some pages/sections in A4 and some in A3, we did that yesterday. Hopefully this is not a v17 backwards change.
-
I had the "letter" problem with V16 as well. When I look in my template it is configured to use A4 even the template view looks nice but in the PDF I receive A4 with its content in letter. In other words only 75% of the A4 page is used.
-
When editing a template in v16, there is an option under Edit/Edit Section that controls the paper size. This is the section we use to control the page size and orientation of each section. I am assuming that this is still available in v17.
This is only available for custom templates, it is disabled for system template, I believe this what Eve is referring to as Base documents/templates. In our setup, all template have a default page size of A4 but I think this is printer dependent.
-
Well I use this as well and it is set to A4. The strange thing is I get A4 but used as letter. I only create PDF. Maybe I try RTF and Word to figure out if this is a PDF issue.
-
Now I used my template to generate RTF and word as output and the result is different to PDF but more or less identical for RTF and Word.
The horizontal space of the page is used right but vertically contend moves still much to early to the next page. Header and footer is entirely missed.
The diagrams are corrupted for any way PDF, RTF and Word.
-
Well I use this as well and it is set to A4. The strange thing is I get A4 but used as letter. I only create PDF. Maybe I try RTF and Word to figure out if this is a PDF issue.
We always generate to Word first, and then save as PDF where needed.
Often we do change some minor details left and right (diagram sizes, table of contents, some page breaks here and there) before saving the document.
Geert
-
Geert this what I try to avoid since years with success.
My target is: generate, deliver, ready without any fiddeling around.
-
Have used a similar approach to Geert for a number of years, generate rtf or word, save locally, if rtf convert to word, modify local copy, and, nowadays upload to SharePoint. I gave up generating PDFs long time ago.
Typical changes that in my experience need to be done after converting to word:
1) grammar and spelling, Sparx EA grammar and spelling features are far behind what Word can do.
2) format adjustments, such as maximising page usage and, at the same time, reducing document size, or fixing tables; Sparx never seems to get table formatting right to a publishable standard, specifically header row shading.
3) acknowledging contributors and adding document history.
4) writing executive summaries.
Improvements I would love, conditional formatting, specifically easily and dynamically change the page size and orientation based on a diagram’s page settings.
-
Thank you Modesto Vega!
Exept your point one I managed all with my templates used directly to greate PDF and I intend to stay this way.
My final goal is to deliver in middterm future just the model to outr assessores and I whant to say “Hey if you need a document for whatever reason just go to the package and generate it yourself".
And currenly with PDF I am closer to what I need (less problems). All in common is that in V1701 digrams look odd. What is in PDF worse is that neither uses the horinzontal nor the vertical page space is used right.
-
A am still trying to find out what my PDF small page usage proble is. No I realized that I get an error when trining to open the PDF with Acrobart Reader I get an error message like:
The root object is missed or invalid.
Any idea on that?
-
A am still trying to find out what my PDF small page usage proble is. No I realized that I get an error when trining to open the PDF with Acrobart Reader I get an error message like:
The root object is missed or invalid.
Any idea on that?
I just tried it myself on v17 and got the same error message when Adobe tried to open the PDF.
The file did open in Chrome, but I did saw the same small page problem you mentioned.
The document generated perfectly (in A4) when using .docx
Looks like the PDF generator used by EA is broken.
Did you report this as a bug?
Geert
-
I belief for V16 long time ago, but not for V17. Thank you! So it is for sure not a problem of my PC.
-
Today I tested the PDF generation with build 1702.
Now the PDF report can also be opend with Acrobat Reader.
However still the usage of my A4 page seem to be "letter" or something else.
In other word only round about 75% of the page size is used for content.
Any ida on this?
-
From my perspective the heading issue is now solved within the builds 1704 and 1629.
However the problem that PDF reports do only use ~75% of the page size still exist in both builds above.
And with V17 there is an additional issue with IBD diagrams with in V17 loos very odd.
I will rise a bug report!
-
From my perspective the heading issue is now solved within the builds 1704 and 1629.
However the problem that PDF reports do only use ~75% of the page size still exist in both builds above.
And with V17 there is an additional issue with IBD diagrams with in V17 loos very odd.
I will rise a bug report!
Good to see there is progress. Keep pushing for the other open issues.
Geert
-
:-\
I generated with EA17.0.1704 (64bit) a document to test it. Database content, template, styles and document generation settings are unchanged. Document is stored as a resource, output is Word format. The EA17 generated document fails with chapter order (order is mixed up), has duplicate content (some chapters are just present twice at different locations), and some diagrams are messed up, too: Elements unexpectedly have a different size than shown in EA itself, arrows and connections are missing. Some diagrams are perfect.
As I don't want to review hundreds of pages of all generated documents, I will still stick with EA15.2.1650 for document generation. Maybe EA18 will fix it. But I start losing the hope :'(
-
After fiddling around with templates for many (>20) years, almost dealing with workarounds for unexpected rendering results.
I recently gave up moving towards v16.1, again.
Besides being restricted to letter size pages, Sparx's EA is not able to render German characters, at least on fields like {ElemTest.Notes} or {PackageGlossaryMeaning} and, perhaps others. I see them rendered escaped (ä) or escorted by curious switching of font styles and -sizes. Maybe the root cause of other effects as well.
And now again, no surprise, with v17.0.1704 Sparxs introduces new varieties: Header and Footer are not rendered any more, unless a cover page is defined.
To make it clear: Linear RTF/PDF documents are still the most important interface between me and my customers and will be. THEY ARE NOT A NICE TO HAVE!
So: Should I stay with Sparx/EA? 6 license renewals later we're still stuck with Version 15.2 and 32-Bit.
Gruß
Jens
-
Hi Jens,
Make sure to contact sparx support with your issues (if you haven't already)
They eventually fixed all the issues I reported and we are now preparing for an upgrade to v17
Geert
-
I still like EA as a tool. I use v17 for editing, but I will still stick with EA15.2.1650 for document generation. You can install both on the same PC: EA15.2 is x86, then install EA17 as 64 bit, so they do not share the same Program Files ... works for me (still a workaround!) [as long as you are not relying on x86 plugins]
-
Just wanted to post my experience with 17.1:
I started some time ago creating new content in EA 17.0, today I am using the latest available 17.1 (x64). I have no issues with document generation for the newly created content. I try to ensure that the Model is not too complicated (e.g. no elements below elements, just one level with diagrams or embedded elements), and I do not include children when parent is filtered (this caused issues in false chapter generation).
I am not sure whether document generation with old content I created the last years also works with 17.1, but for that I have the fallback of using EA 15.2 just for exporting.
-
Anyhow any newer version still uses only about 75% of the page size when generation pdf's.
-
hm. I just tried it with my template and content I created recently. I just switched from DOCX to PDF output. The generated PDF looks perfect. It seems to take over template defined page margins, etc.
-
That is interesting!
I am pretty sure it is not my template because if is fine for word and rtf and when using a system template I have the same problem for PDF’s.
Can you tell me which build and which package (32 Bit or 64 Bit) you are using?
-
I use the latest available 17.1.1712 (x64)
-
Stange! ???
This one I use among others as well, with the same problems!
So maybe it has something to do with company windows installation.
Sparx support, do you know if some kind of windows installed dll's are involved in the PDF generation process?
-
Now I generated my PDF's within Citrix running on an Windows Server, and this without the problem that only about 60% of tha pages are used.
So it has something to do with my Win11 together with V16, because with V14 it works on my Win 11 as well.
Any ideas on that?
-
I cannot reproduce the issue on my machines, but changing the printer might produce different results.
From the Sparx logo button on the far left of the ribbon, select the Print Setup menu, change the printer, and then try generating again.