Changes

 The content browser's tabs (children, properties and documents) are only shown if necessary (and if they aren't are not empty).For some types of objects (e.g., tasks), specific tabs are always shown though - , especially if a tab is considered the main view for that object.<br/><br/>It is possible to configure this feature in order to behave more precisely as desired.<br/>By default, the children tab is shown if no other view should be shown explicitely and if the client has no information whether there are children or not.<br/>This means that for objects where (by customizing) the properties tab or the documents tab should be shown when entering the browser, the children view is only shown if it is not empty.<br/> However, if nothing is configured, the children tab will be shown by default, because there could be children on the server and it would be annoying for the user to not see the children tab at all until something is loaded.<br/> This is the other way round for the properties tab, because properties are always known as soon as the object itself is available on the client.<br/> 

There are basically two ways to configure the dynamic tabs feature.<br/>:First, one * Oone can configure the [[SYSCLS_CHILDINFOOWNER|Children Information Classification, ]] (former: Document Owner Classification]].This ): this will lead to a precise behaviour of the dynamic tabs, because the client has more detailed knowledge about the children of respectively classified objects.<br/>* Another possibility is the configuration of the [[SYSCLS_SHOWPROPERTIES]] or [[SYSCLS_SHOWDOCUMENTS]] classifications. This : this will lead to the displaying of the properties/documents tab as initial view, even if it is empty.