For every server start, censhare checks whether the definitions of the standard workspace structure have changed and updates them accordingly. Your changes to these assets will be lost. That is why there are tools such as resource replace variants for adjusting the standard workspace structure.


Update module assets

For every server start, censhare updates the standard workspace structure. censhare reads the XML definitions of the assets on the censhare server. XML definitions can be found on the server in the directory:

~/censhare/censhare-Server/install/system/required/web/workspace/


The update is triggered by the asset action "Automatically synchronize module assets" in the Admin Client. You configure the asset action there in the section "Configuration/modules/administration/module assets". You can define which directories should be synchronized in an automatic update. Typically, the directory there is defined as "required". This includes all module assets that are required for running censhare, including the standard workspace structure.

You can also run the update manually in the admin client with the asset action "Synchronize module assets". You also configure this in the section "Configuration/modules/administration/module assets". If you only want to update the standard workspace structure, you need to define the path "required/web/workspace" there and only activate this one.

If the XML definition of an asset has changed, censhare creates the asset anew based on the definition.Assets whose definitions have not changed will remained untouched. Based on the change date you can therefore tell whether the asset changed on the date of the update.

We don't recommend making changes to the workspace structure directly in the assets of the standard workspace structure. If the XML definition of the associated asset changes in an update, censhare overwrites the changes you made.You should use the tools in censhare designed for that such as resource replace variants, workspace templates and roles.

Exception

There is one exception. If you change the "Active" feature of a workspace asset, it will not be overwritten during an update. This gives you the opportunity to deactivate assets in the standard workspace structure without having to remove them from the system. Deactivated assets will then also be updated and can be put back into action if need be.

If changes are made to a workspace asset for which there is a resource replace variant (RRV), then the RRV remains unchanged.

A new asset will be created for new XML definitions.

The changes saved in the workspace template with resource events and user workspaces are not affected during a censhare server update. If a user logs in after an update, censhare applies the changes saved as resource events in the workspace templates and in the user workspace on the current standard workspace structure.Only resource events that can no longer be used after the update will be discarded.

XML workspace templates remain unchanged during an update. Users will only see the changes from an update when you manually change the XML workspace templates.

Deleted module assets

Assets in the standard workspace structure can also be removed from the system during an update. To find out which assets those are, go to this directory:

~/censhare/censhare-Server/install/system/web/workspace/deleted

You will find an XML file associated with each of the workspace assets to be deleted. The name of the file has the following structure: "tombstone. NAME.asset.xml". The NAME refers to the deleted asset. The file also contains the resource key of the corresponding asset.

Every asset referenced in the directory is marked by censhare for deletion. It is not immediate, but rather after a certain amount of ti