Force user configuration changes to get added to Global project options

[tpaige]

Hello!

My team uses a shared .xpr file (under Git version control) that contains configuration settings that we want enforced for all users. Distribution works as expected, but certain user actions trigger undesired updates to this project file (for example, selecting the checkbox to disable prompts for how .ditamap files are opened).

image.png

I have two questions:

• Is there a way to specify that these types of changes get added to the user's Global options and not the shared team project file?

• Also, is there a page that describes all of the settings that can be added to a project file? (Something similar to https://www.oxygenxml.com/doc/versions/ ... ns__d96e25)

Thank you!
--Tahesha

[Cosmin Duna]

Hi Tahesha,

The option for opening the DITA map is by default saved in Oxygen global options. It is also presented on the "DITA / Maps" preferences page. Maybe you modified the storing level of this page by checking the "Project Options" checkbox (https://www.oxygenxml.com/doc/versions/ ... oring.html). Do you have options there that you want to distribute into the project?

We have a preferences page that allows controlling whether various settings should be saved in the project configuration file or in the global settings: https://www.oxygenxml.com/doc/versions/ ... tings.html
We tried to add into these pages, settings that are not included in preferences pages and are by default saved at the project level.

We don't have a documentation page that describes settings saved by default at the project level. As I said, these that are used frequently can be found in the "Project Level Settings" preferences page.

Best regards,
Cosmin