How Do I Access the Configuration Settings through XMDesigner without Connecting to a Site?

I understand the reasoning behind encrypting the site.config files, but I have recently encountered some situations with 5.1 where this causes issues.

The current situation causes issues if:

– You make a typing mistake within XMDesignerIs used to configure XMPro BPM solutions. for the XMPro Database connection

– A client changes their Database server and does not update through XMDesigner before hand

– A client changes an SQL user account and does not update XMDesigner before hand

– In a Disaster Recover or Test refresh type situation and the client wishes to use a new SQL password

In all these situations, I am locked out of my site.config, as I cannot connect to XMDesigner as my XMPro site can no longer connect.

Is there a way to access the configuration settings through XMDesigner without connecting to a site?

In my opinion site management needs to be removed from the XMDesigner requirement to connect to a site.

An option I thought of could be to create a site.config admin user during installation stored in the site.config (obviously as it is encrypted) and that could be used for validation when you just want to open XMDesigner to edit the site.config.

This would allow for all the situations above and also for situations where you may want IT to be able to maintain the site.config but also not have access to XMDesigner, for example, where a client wishes to regularly change their SQL passwords.

Answer

Currently, as you have outlined, this is not possible within the XMDesigner, it is possible however from the XMWorkspace using the web services.

In my opinion site management needs to be removed from the XMDesigner requirement to connect to a site.

An option I thought of could be to create a site.config admin user during installation stored in the site.config (obviously as it is encrypted) and that could be used for validation when you just want to open XMDesigner to edit the site.config.

This would allow for all the situations above and also for situations where you may want IT to be able to maintain the site.config but also not have access to XMDesigner, for example, where a client wishes to regularly change their SQL passwords.

This is a very good idea and will be added into our request list.