Recent Posts

11

General Board / Document Generation - how to get elements on a diagram to nest

« Last post by andrew.francis on December 17, 2025, 12:12:59 am »

I am generating a virtual document using 'Model Documents' and custom templates, and I want the diagram elements in the published document to be nested in the same way as they are in the Project Browser, but they just export as a flat list. Is there a way to get the generated document to follow the package browsers structure?

I could drop the package containing the elements onto a separate Model Document, but this would mean lots of model documents and lots of templates...

The elements are of the same type, so I don't think I could apply a filter, and again this would need another template.

Thanks in advance

12

Automation Interface, Add-Ins and Tools / Re: Diagrams not fully rendered in reports

« Last post by Geert Bellekens on December 16, 2025, 11:20:37 pm »

Check the document generation options.
Some of them are related to the diagram. If you play with them, it might get solved.

Also, don't generate directly to PDF. In my experience it works better if you first generate to .docx, and then save to .pdf.

Geert

13

Automation Interface, Add-Ins and Tools / Diagrams not fully rendered in reports

« Last post by Tarzan on December 16, 2025, 07:50:05 pm »

I am experiencing an issue in Sparx Enterprise Architect 16.1 when generating diagram reports that include diagrams as images. When generating a report, some diagrams (e.g. BPMN process diagrams with swimlanes and multiple activities) are not fully rendered in the resulting Word document. It appears that the diagram image is being scaled down or cropped, causing parts of the diagram (lanes and activities) to be missing. In the report, the diagram seems to be rendered at approximately 75% size, while the full diagram is displayed correctly within EA itself.

Notably:

• Generating the report at a higher package level (including all elements) does not change the result.
• The issue occurs with multiple document templates, not just a single specific template.

My questions:

• What determines how EA scales or crops diagrams during report generation?
• Which diagram, page setup, or document template settings influence this behavior?
• Is this a known limitation or bug in EA 16.1?
• What is the best practice to ensure diagrams are always fully visible in Word reports?

Any insights or suggestions are appreciated.

14

Suggestions and Requests / Journal for Connector

« Last post by A_Marsh on December 16, 2025, 03:04:07 am »

It seems that I'm not able to create a Journal entry for a connector.   I would quite like this as a feature.

15

PCS General Board / Service Now mapping and synchronization questions

« Last post by Guillaume on December 12, 2025, 10:02:20 pm »

Hi,

I have a client's ServiceNow integration configured in their PCS.
In EA, when I open ServiceNow configuration, I can select one of its types as the external type e.g. Application and map it with an EA type or stereotype.
The issue is that I have several ServiceNow items of the same type from different views that I need to map with different EA stereotypes (maintained within an MDG).
If I want to create Local Elements from a ServiceNow view e.g. only with "Type A" components, I have no way of telling EA to create "Type A" stereotypes elements since the ServiceNow External type is common to Type A, Type B...
Would a change be required in this integration to either add views on a mapping, or define multiple mappings for the same ServiceNow external type and select the appropriate one when importing new elements from a view ? Is there a workaround e.g. I noticed there a way to create a Data Miner connection but I can't test it yet since the current EA license doesn't support it.

Other question: Once elements are created in EA, I need to manually run a synchronize linked elements from EA. Is there a way via a script or else to run this synchronization e.g. on a nightly basis? The PCS automatic updates only applies to the diagram/images sync on a repository.

16

General Board / Re: Keep on getting the login dialog on sparxsystems.com

« Last post by IsaiahMorris on December 11, 2025, 06:37:08 pm »

Thank you, I am on the same boat.

17

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

« Last post by Geert Bellekens on December 09, 2025, 08:51:27 pm »

You don't use the template to point to a single element, but the model document.

And yes, if you have 50 use cases in a single package, you would have 100 model documents (one for each use case, and one for each interaction)
That's why I usually automate the creation of the virtual document with a script.

I have an article on my website that explains this in more detail: https://bellekens.com/2015/11/12/tutorial-generate-complex-documents-from-enterprise-architect-with-a-two-step-semi-automated-approach/

Geert

18

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

« Last post by andrew.francis on December 09, 2025, 08:40:47 pm »

With different model documents however you can use one model document that points to the use case, and the next that points to the Interaction.

Hi Geert, thanks for the reply again, I appreciate that I could do this if all the Use Cases are in individual packages, but how could I do this when the Use Cases are in a single package? I'd be pointing the Model Document at the Package and using a template that is specifically pointing at the single use case? Via a GUID or something like that?

If that's the case I would need 100+ individual templates to point at each use case...

19

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

« Last post by Geert Bellekens on December 06, 2025, 01:49:11 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.

The fragment will always point to the package/element is was called upon.
With different model documents however you can use one model document that points to the use case, and the next that points to the Interaction.
Or you can put them in different packages and let the model document point to the package by dragging the package onto the model document.

Geert

20

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

« Last post by andrew.francis 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.