Document generation broken in v16.1

[Geert Bellekens]

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

[Geert Bellekens]

- 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

[Geert Bellekens]

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

[Geert Bellekens]

According to the release notes this should have been fixed in version 1622:https://sparxsystems.com/products/ea/history.html#1622

Geert

[Geert Bellekens]

the new bug introduced in 16.1.1621 seems to have been fixed again, but no improvement on the original problem.

Geert

[chrislro]

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.

[chrislro]

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)

[Geert Bellekens]

Definitely 15.2.1560. I'm not upgrading untill they fix this issue.

Geert

[chrislro]

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.

[Geert Bellekens]

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

[wivel]

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

[chrislro]

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).

[Geert Bellekens]

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

[StefanFS]

Please have a look at my earlier post:
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

[Geert Bellekens]

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