The configuration data for the WebDAV integration is stored in the configuration object FSCOWS@1.1001:WebServiceConfiguration. The “Web Folder” form page contains the following properties:
Reference: FSCOWS@1.1001:webfoldernewfolderclassmappings
When a user creates a new folder or imports a folder, a new compound object will be created in Fabasoft Folio. The object classes for the new compound objects are defined in this aggregate array. The aggregate consists of the following fields:
The meaning of an entry depends on the fields specified. You can define object classes for new compound objects but you can also prevent the creation of new folder objects. The following table lists the possible combinations depending on what fields are specified:
Parent class | View attribute | New folder class | Comment |
---|---|---|---|
X | Defines a default folder class for all views in all parent folder classes. | ||
X | Prevents creation of folder objects in the specified view. | ||
X | X | Defines a folder class for new folders in the specified view. | |
X | Prevents creation of folder objects in all views of the specified parent folder class. | ||
X | X | Defines a folder class for new folders in all views of the specified parent folder class. | |
X | X | Prevents creation of folder objects in the specified view of the parent folder class. | |
X | X | X | Defines a folder class for new folders in the specified view of the parent folder class. |
If there is more than one matching entry for a given case the most suitable entry will be applied.
Note: The parent class takes precedence over the view attribute.
Reference: FSCOWS@1.1001:webfoldernewcontentobjectclassmappings
When a user imports or saves a new file, a new content object will be created in the Fabasoft product. The class of the new content object will be chosen depending on the parent folder class, the current view attribute and the file extension of the new file. The aggregate consists of the following fields:
The meaning of an entry depends on the fields specified. You can define object classes for new content objects but you can also prevent the creation of new content objects. The following table lists the possible combinations depending on what fields are specified:
Parent class | View attribute | File ext | New object class | Comment |
---|---|---|---|---|
X | Default content object class for all views of all parent classes and any file extension. | |||
X | Prevents the creation of content objects with the given file extension in all views of all parent classes. | |||
X | X | Defines the content object class for all views of all parent classes for the given file extension. | ||
X | Prevents the creation of content objects in the specified view for all parent classes and any file extension. | |||
X | X | Defines the content object class for the given view in all parent classes and any file extension. | ||
X | X | Prevents the creation of content objects in the specified view for all parent classes and the specified file extension. | ||
X | X | X | Defines the content object class for the specified view for all parent classes and the specified file extension. | |
X | Prevents the creation of content objects in all views of the specified parent class for all file extensions. | |||
X | X | Defines the content object class for all views of the specified parent class and any file extension. | ||
X | X | Prevents the creation of content objects in all views for the specified parent class and file extension. | ||
X | X | X | Defines the content object class for all views in the specified parent class and given file extension. | |
X | X | Prevents the creation of content objects in the specified view and parent class for any file extension. | ||
X | X | X | Defines the content object class for the specified view and parent class and any file extension. | |
X | X | X | Prevents the creation of content objects in the specified view and parent class for the given file extension. | |
X | X | X | X | Defines the content object class for the specified view and parent class for the given file extension. |
If there is more than one matching entry for a given case, the most suitable entry will be applied.
Note: The parent class takes precedence over the view attribute and the view attribute takes precedence over the file extension.
Reference: FSCOWS@1.1001:webfolderincludedclasses
This aggregate array lists all object classes that should be displayed in web folders. You may also specify specific views of compound objects. The aggregate consists of the following fields:
Note: An empty aggregate array means that all object classes should be included in the web folder view.
Reference: FSCOWS@1.1001:webfolderexcludedclasses
This aggregate array lists all object classes that should not be displayed in web folders. You may also specify specific views of compound objects. The aggregate consists of the following fields:
Note: The exclusion list takes precedence over the inclusion list.
The file size limit for uploading is defined in the Default Import Limit (Bytes) field in the virtual application configuration.
Note: Currently the Default Import Limit (Bytes) field in the virtual application configuration is only considered when using the Fabasoft Client via “Open <product> Folder” (see screenshot option marked in green). When opening a network drive with a local WebDAV Client, always a 4 GB limit applies. This can be done like in the screenshot marked in red “Open <product> Network Drive”.
The depth limit for a PROPFIND request is determined by the Registry Key (DWORD) HKEY_LOCAL_MACHINE\SOFTWARE\Fabasoft\FSCOWS@1.1001\PROPFINDMaxDepth.
The default value is 5.