Messages

1

Bugs and Issues / Re: Document Publishing: Heading Numbering in Custom Script Fragments

« on: September 14, 2022, 11:56:20 pm »

Hello Geert,

thanks for your suggestions, much appreciated. I tried to "Adjust Heading Levels" but this seems to limit the maximum heading level only. Also I created all templates as new (it is actually only one master template) and created the fragment  as a copy from the master, but it didn't help much.
It seems that as soon as I use a template fragment with a numbered heading, it is assigned the wrong level. Unfortunately the heading contains data from the custom script used in the fragment, so I need the heading inside the fragment...
Oh well, it seems I'm stuck here. Time to contact support... 

Kind regards,
Martin

2

Bugs and Issues / Document Publishing: Heading Numbering in Custom Script Fragments

« on: September 13, 2022, 10:23:30 pm »

Hi everyone,

I am publishing a model as a custom document, where I currently have a main template, that is using a template fragment to output each element. The fragment uses a custom script to gather some data for each element.
My issue is with the numbering of the section headings. It seems as soon as I enable the custom section in the template, the heading level is fixed to the one used in the fragment, when it should be incremented according to the actual position in the output document.
So for example an element XYZ is a child of package "ABC", and in the final document the package is output as "1.2. ABC", I would expect the element heading to be numbered as "1.2.1. XYZ" for example. But it is numbered "1.3. XYZ" for example, so it seems it is always put to the same level as the parent. When I remove the custom section from the fragment and put some standard field as a heading in the element section, the numbering is as expected.
Is this a bug or am I missing something here?

Best regards,
Martin

3

Automation Interface, Add-Ins and Tools / Scripted report generation, language selection

« on: April 20, 2022, 11:49:48 pm »

Hello everyone,

in the "Generate Documentation" dialog there is a selection for the language/translation to be used for the report generation.
Is there any way to access the selected value through the object model, in scripts that are executed during the report generation process? I need to provide the language code for calls to the GetTX... Element member functions, for example.

Thanks in advance
Martin

4

General Board / Re: EA 15.2 Native XML Import requires credentials

« on: August 05, 2021, 09:50:33 pm »

It was a good hint though  Instead of disabling security in the model after import, I changed the t_secpolicies.xml backup file accordingly, prior to import. Thanks guys!

5

General Board / Re: EA 15.2 Native XML Import requires credentials

« on: August 05, 2021, 09:35:13 pm »

I don't think security is enabled, because if I go to CONFIGURE -> Administer, it shows me the option to enable security. Unfortunately I don't have MS Access at the moment, to check it directly in the eapx...

6

General Board / EA 15.2 Native XML Import requires credentials

« on: August 04, 2021, 10:46:48 pm »

Hi everyone!

We created a XML export/backup of our main (cloud-based) project and I wanted to create a local copy of the project based on this backup, for testing some automation stuff.
So first of all I created an empty local project, performed the native XML import, and directly afterwards I can open the project as expected, content seems OK. Only after I reopen the project, EA requires login/password credentials.
I am not sure what to enter here, because I created the local project and it should not require any authorization. Does anyone know how to handle this, bug or feature? I tried the cloud login credentials, but that doesn't help...

Thanks in advance and kind regards,
Martin

7

General Board / HTML report filter

« on: May 27, 2021, 06:53:18 pm »

Hello everyone,

I would like to filter the model elements to put only certain element types into our HTML report. For example, "only gateways with non-empty notes" My first idea was to create a report package with one model document, and reference a model search in the SearchName.
As model search I created a custom SQL search, like this (only for testing without any WHERE clause):

Select
   ea_guid AS CLASSGUID, Object_Type AS CLASSTYPE, name as Name, Object_Type as Type
from t_object

When I try this search in the Find dialog, it returns results (obviously .
When I generate the HTML report on the report package, it is empty. I also tried with Common Searches to just search for an existing package name, report is empty too.
Now I read in the HTML reports PDF documentation on sparx website, that you would create a model document by adding elements to the model document, but explicitly not by adding a model search.
So is the model search approach not possible with HTML reports? Is there any other way to achieve this, maybe by modifying the javascript templates?

Thanks in advance,
Martin

8

General Board / Translation for HTML

« on: May 25, 2021, 10:58:34 pm »

Hi everyone,

we want to publish our model both as HTML and DOC format. Also we have manual translations for our model elements/notes. While you can select the output language in the report builder dialog, we are missing this feature for the HTML report. Is translation possible for HTML? (we are using EA 15.2.1559)

Kind regards,
Martin