Messages

1

General Board / Re: Document Generation - Connector target is a diagram

« on: December 06, 2025, 01:22:47 am »

I think this would give me the same issue whereby I would struggle to get the document to generate with a Use Case followed by it's diagrams. I don't think there is a way to point fragments at diagrams ?? as they are just called within a template which is associated to a Model Document element.

If I can point a fragment at a package that would fix my issue.

2

General Board / Re: Document Generation - Connector target is a diagram

« on: December 04, 2025, 01:12:36 am »

Hi Geert, thanks for the reply.

I am currently using a virtual document (document artifact) and a number of model document elements with different templates for heading levels etc. - I think this is what you are recommending.

Currently I am pointing the model document at each individual Use Case (which is in it's own package), and then at the Diagram (which is also in it's own package).
- I would like to be able to move the use cases into a single package.
- I don't mind whether I keep the diagrams in their own packages.

I wasn't sure whether I would be able to use a fragment, as I don't know if I can point fragments at packages while the main template loops through the Elements?
and I wasn't sure how to point the template at the Interaction/State Machine - how would you go about this?

Thanks again!

3

General Board / Document Generation - Connector target is a diagram

« on: December 03, 2025, 09:35:07 pm »

Hi, I'm hoping I have missed an easy option and there is a quick solution to this problem.

I have a package full of Use Cases, and each Use Case has an associated Sequence Diagram or State Diagram in another package. I want to generate a document where I show a Use Case followed by it's associated (linked via Trace) Diagram, but I cannot work out how to do it as the Element >> Connector >> Target doesn't have an option to include a diagram.

Temporarily I have just put the Use Cases in individual Packages, so that I can drop the Use Case package on followed by the Diagram package, but this is not ideal.

Any help greatly appreciated!

4

Bugs and Issues / Doc gen IDBs generating properties

« on: November 28, 2025, 02:22:21 am »

I have an issue where disabled 'Show Compartments' settings fail to apply consistently during Doc Gen.

When I generate a document with multiple Internal Block Diagrams (IBDs), the 'properties' compartment is being wrongly added to about half of them in the outputted document, corrupting the diagram layouts.

I'm hoping there's a simple configuration fix I've overlooked.

Edit:
1. I have created a Test document, with just the misfiring diagrams on it (added the 'Model Document' elements and used the same template), and they export correctly to the generated document - which makes me think the problem is configuration of the 'Model Document' block rather than the Diagram - wrong.
2. I have deleted and re-added the misfiring 'Model Document' elements, and the problem persists.
3. I have checked all the configuration settings I can find for the firing diagrams against the misfiring diagrams and can find no differences.
4. I have tried enabling and disabling all available Compartments from the 'Show Compartments' option on the diagram - interestingly the 'Properties' compartment was not an option

Edit 2 - and fix:
1. I wanted to recreate the diagram to see if that helped, and when I created another IBD in the same package as the misfiring IBD, the misfiring IBD suddenly updated itself to show the compartments that I had disabled (including in the options). I was then able to disable the compartments and save, and the subsequent doc gen did not include the misfire. Shame I have about 50 IBDs to recreate and save.
2. The fix works by just creating another IBD and then dropping the Elements onto it, this updates the bad diagrams.