Backlog

Partial default config.xml = merge

0 vote

avatar

Due to a particular configuration element no longer being supported in our default.xml, we needed to update it the default.cfg to no longer have that element. This led to confusion on our end-users' who didn't know if they should click accept or ignore when opening RDM. We have since set the GPO to not prompt and to just import the default.cfg when it changes. This also caused confusion because a lot of their particular settings/themes get changed back to the way it was when they opened RDM for the first time. We tried editing the default.cfg and removed all of the settings we did not need control over, hoping that what would happen is the default.cfg would only overwrite those settings explicitly within the default.cfg. Instead, anything not in the default.cfg was reset back to application defaults. The ask is that a partial default.cfg will only overwrite those explicit settings and leave the rest alone.

For example. Let's say I launch RDM for the first time, which will import the default.cfg so my datastores are preset for me. I go into options and change my theme to dark. Sometime later, the admin needs to change a particular setting in RDM (for example. <NoInternetConnection>true</NoInternetConnection>). Currently, there is no way for the admin to change that setting without resetting my theme back to default white and causing confusion.

All Comments (1)

avatar

Hello,

Thank you for the request. I will open a ticket.

Regards,

Hubert Mireault