Recent posts

[on]

#41

General Archi Discussion / Re: Custom Preferences when Ge...

Last post by Eric Vendeville - April 09, 2025, 14:42:29 PM

...
I think it has something to do with the Appearance colour preference "Save the default fill colour for elements in the model file" which I notice you have set on in your custom preferences file. With this on, any new objects created will save the "fillColor" attribute if the colour for that object is set to "Default".
...

You're right about this option enabled in my preferences file : it was not the case initially, but I must admit that I "played" a bit with it while investigating my problem, in order to better understand how all this "color stuff" works in Archi, and make my own tests...

And I can confirm you that this option works exactly as expected: after being enabled, everey NEW created view correctly uses my "custom default colors" (because, as you said in your previous message, a "fillColor" attribute is "hardly" setted in the XML files, for every element contained in the view).

BUT for all "OLD" views that have been created BEFORE this option has been ticked in my preferences, they (logically) don't embed this "forced" fillColor attribute in the XML files containing the views (i checked that by myself, by opening several XML files for different "old" views)... And then they (theorically) should use my "custom default colors". Instead, the "original default colors" are used.

If a diagram object does not have a "fillColor" attribute set (either in an *archimate file or a coArchi *.xml) then the default color as set in Preferences will be displayed. If the "fillColor" attribute is present then that colour will be displayed.

Unfortunately that's not the case in our environment : the default colors as set in Preferences right after the installation of Archi are used, instead of the default colors as set in our actual Preferences panel.

I can't diagnose this any further without a model and setup where I can reproduce the problem. I would need to have a copy of an example coArchi repo to do this.

I perfectly understand that, and I thank you again for all the time you already wasted trying to help me...
I'm actually trying to build a kind of "MVP" (for Minimal Verifiable Problem  ) and will let you know when done...

Eric

#42

Share your Models, Templates and Reports / HTML Output Customization

Last post by zkhanz - April 09, 2025, 12:30:43 PM

Hi
I need all views from my models to publish on my internal portal. The user click on the view and it goes to the respective view. I am not a Web developer, but if someone can help, I can hire a developer to develop this custom portal for EA from my work. Thanks Zubair

#43

Share your Models, Templates and Reports / Re: Archimate html publication...

Last post by zkhanz - April 09, 2025, 12:17:13 PM

Hi Paul
Can you please guide me how can we publish the HTML output to sharepoint. Thanks in advance

[on]

#44

General Archi Discussion / Re: Custom Preferences when Ge...

Last post by Phil Beauvoir - April 09, 2025, 11:17:39 AM

I don't think this has anything to do with CLI or coArchi. I think it has something to do with the Appearance colour preference "Save the default fill colour for elements in the model file" which I notice you have set on in your custom preferences file. With this on, any new objects created will save the "fillColor" attribute if the colour for that object is set to "Default".

If a diagram object does not have a "fillColor" attribute set (either in an *archimate file or a coArchi *.xml) then the default color as set in Preferences will be displayed. If the "fillColor" attribute is present then that colour will be displayed.

I've tried creating a coArchi repo with this setting on and off, and with elements containing the "fillColor" attribute and not containing it. I used a fresh install of Archi, a blank location for the "-Dosgi.instance.area" and with your custom_defaults.prefs file. Whatever I try works for me.

I can't diagnose this any further without a model and setup where I can reproduce the problem. I would need to have a copy of an example coArchi repo to do this.

#45

General Archi Discussion / Re: Custom Preferences when Ge...

Last post by Eric Vendeville - April 09, 2025, 11:10:27 AM

Thanks for your last messages Phil, still investigating on my side...

The problem occurs when you try to generate the HTML report from a repository that contains only .xml files (generated by coArchi and synced from git), without any .archimate file in it... hence my assumptions at the beggining of the post, in my 1st message

OK, I tested that too and it's also working:

Code Select Expand

Archi -application com.archimatetool.commandline.app -consoleLog -nosplash --modelrepository.loadModel "path_to_coArchi_Folder" --html.createReport "output_folder"

Are you sure the model in the coArchi repo has actually got elements in it that are set to use default colours?

This command line worked for me (when generating html site from a .archimate project file) :

Code Select Expand

--loadModel "E:\sysapp\Archi\test.archimate"
But not this one (when generating html site from a coArchi git repo... still tried this morning...) :

Code Select Expand

--modelrepository.loadModel "path_to_any_model_structure_synced_from_azure_git_repo"
And yes, I am absolutely sure my coArchi repo has actually elements in it that are set to use default colours (that's to say : elements for which no appearance properties has been manually set).

It may be that the model you are using in coArchi has the element fill colours set explicitly to the standard fill colours so that your custom colours are not used.

You could create a very simple test model with one element in it that uses your custom colour and create a repo from that to test.

Or, for a technical deep-dive:

1. Go to the location of the coArchi model and locate one of its diagram XML file named like this - model-repository\repo-name\your-model\diagrams\ArchimateDiagramModel_id-1e04b80c5c1c2152948f132149bea3b1.xml, and open it in a text editor.

2. Check each <children> XML tag and you may see an attribute like fillColor="#ff8040". If this is present then the fill colour is set explicitly for that object and your custom colour will not be used. The custom colour will only be used if the fillColor attribute is not present.

I already did that "technical deep-dive" before contacting you, and I can assure you that the XML files containing the concerned diagrams (which should render with my custom default colors) do not contain any fillColor="#xxxxxx" property 

#46

General Archi Discussion / Re: Custom Preferences when Ge...

Last post by Phil Beauvoir - April 09, 2025, 10:31:30 AM

It may be that the model you are using in coArchi has the element fill colours set explicitly to the standard fill colours so that your custom colours are not used.

You could create a very simple test model with one element in it that uses your custom colour and create a repo from that to test.

Or, for a technical deep-dive:

1. Go to the location of the coArchi model and locate one of its diagram XML file named like this - model-repository\repo-name\your-model\diagrams\ArchimateDiagramModel_id-1e04b80c5c1c2152948f132149bea3b1.xml, and open it in a text editor.

2. Check each <children> XML tag and you may see an attribute like fillColor="#ff8040". If this is present then the fill colour is set explicitly for that object and your custom colour will not be used. The custom colour will only be used if the fillColor attribute is not present. Or it will be used for newly created objects if the option "Save the default fill colour for elements in the model file" is set (you have this set in your custom prefs file).

#47

General Archi Discussion / Re: Custom Preferences when Ge...

Last post by Phil Beauvoir - April 08, 2025, 18:57:48 PM

The problem occurs when you try to generate the HTML report from a repository that contains only .xml files (generated by coArchi and synced from git), without any .archimate file in it... hence my assumptions at the beggining of the post, in my 1st message

OK, I tested that too and it's also working:

Code Select Expand

Archi -application com.archimatetool.commandline.app -consoleLog -nosplash --modelrepository.loadModel "path_to_coArchi_Folder" --html.createReport "output_folder"

Are you sure the model in the coArchi repo has actually got elements in it that are set to use default colours?

[Result]

#48

General Archi Discussion / Re: Custom Preferences when Ge...

Last post by Eric Vendeville - April 08, 2025, 18:42:09 PM

Just tested, using the following command-line :

Code Select Expand

Archi.exe -application com.archimatetool.commandline.app -consoleLog -nosplash --loadModel "E:\sysapp\Archi\test.archimate" --html.createReport "E:\test"
Result : Without any surprise (I already tested that few days ago), everything is OK, my custom default colors are correctly applied to the views !

The problem occurs when you try to generate the HTML report from a repository that contains only .xml files (generated by coArchi and synced from git), without any .archimate file in it... hence my assumptions at the beggining of the post, in my 1st message 

#49

General Archi Discussion / Re: Custom Preferences when Ge...

Last post by Phil Beauvoir - April 08, 2025, 18:18:07 PM

Try a simpler command that loads an existing *.archimate file and creates the report:

Code Select Expand

Archi.exe -application com.archimatetool.commandline.app -consoleLog -nosplash --loadModel "path_to\\model_name.archimate" --html.createReport "path_to\\folder"


#50

General Archi Discussion / Re: Custom Preferences when Ge...

Last post by Phil Beauvoir - April 08, 2025, 18:09:12 PM

Please copy and paste your command line here as text. From the screenshot in your earlier post I see "-html.createReport" with one leading hyphen instead of two, it should be "--html.createReport"

Edit: ignore that, it doesn't make any difference.