Document Reports; „embedded elements“ section is not processed

[PeterHeintz]

According http://www.sparxsystems.com/enterprise_architect_user_guide/13.0/model_publishing/embedded_sections.html
ff you add field content in the “embedded elements” section, this content shall be processed, but nothing happens!

Reported!

[PeterHeintz]

Calling a template fragment is neither processed as well.
refer also to http://www.sparxsystems.com/forums/smf/index.php/topic,39592.0.html

[Uffe]

Hi Peter,

Seems the document generation took a pretty severe beating in v13. Since upgrading from 11.1, I'm seeing custom fragments fail when invoked through the API (an old bug that had been fixed), and some of my users are unable to run a document generation script that works perfectly for others (well, except for only working once per session due to the first problem).

On March 27th I provided Sparx with an MDG Technology and test project to bughunt the first one, but I haven't heard back since. Regarding the critical problem with certain users being unable to run certain scripts I haven't heard a peep since my report a week ago. In fact, right now I have eight registered bug reports from as far back as March 22nd where I've only received the automated reply.

But hey, it's only half my business analysts who are up in arms. You know, the ones with a lot of say in what tools get used enterprise-wide? Yeah, them. Turns out they don't think calling a colleague to run a script for them three or four times a day is an efficient way of working.

Who knew?


/Uffe

[PeterHeintz]

A workaround I found to get almost what I want to achieve is the following.

In the template fragment, responsible for the block/class under elements>, I call among other things two template fragments (PortFragmentPatch and PartFragmentPatch). I use two fragments, to have first under the block in my list the ports and then the parts.

This xyFragmentPatch fragments do nothing but calling in embedded elements> either a PortFragment or a PartFragment respectively (this patch trick I used already somewhere else).

Within the "real" PortFragment and PartFragments under element> I have the fields to be rendered.
If I do it this way, the call of the xyFragment is processes (what it is not on class/block level)!?!

In my PortFragment I filter to ports and in my PartFragment to parts.
I call first Ports and then Parts, but in my generated document I get first parts and then ports!?!?

[Geert Bellekens]

Good to know.

One of my customers that is using document generation pretty seriously is planning to upgrade to v14 somewhere this year.
Will need to test all my templates to make sure nothing breaks.

Geert

[Uffe]

Will need to test all my templates to make sure nothing breaks.

Here's a tip: test them twice.

When upgrading 11.1 -> 13.5 I tested mine just once and they worked, but then it turned out they only work once per session.
Also, some users can't generate documents anymore. So test using a few dozen different user accounts too.

/Uffe