Configuration Studio Server-Side Data Storage
Until now, Socotra Configuration Studio has operated in a “client side” storage mode. This is fine for many purposes, but there are two key limitations to client-side data in configuration tasks:
The amount of configuration data is limited to the browser limits for the amount of stored data. Typically this is 5 megabytes which may be inadequate for some configurations; and
When more than one browser is used, it is cumbersome to export and import the configuration data from the original browser to the next.
Storing configuration data on the server addresses these limitations.
Enabling Server-Side Storage
To use the server for storing configuration data, within Configuration Studio select the User drop down menu at the top right of the window. You will see an option to
Turn Server Storage ON (Beta). You will be presented with a confirmation dialog. Click
Confirm to enable.
After enablement, you will need to log into Studio again.
The client-side and server-side configurations are different. If you switch between modes, the data will not be available in the alternative mode. For example, if you add an exposure to a product in the normal (client-side) mode, and then turn server-side storage on, that exposure will not be in the configuration data you are now working with. (If you switch back to client-side, you will again see the newly-added exposure).
The configuration information is stored with the user account, not the overall tenant, so different configuration users will have separate configuration data stores. Future Socotra releases will have provisions for multi-user collaboration.
Working with Server-Side Storage
Configuration Studio should behave identically after you enable server-side storage, other than your changes being reflected if you switch browsers.