(3/14)

Standard date format in views
This entry ensures a consisten date format even when using differently configured client systems.
    
Specify here how dates should be formatted within views.

mm/dd/yyyy will yield a format of month, day and year, e.g. 12/28/2006.


In order to use the German date format (i.e. day, month year) you should enter dd.mm.yyyy (Example: 28.12.2006)

This setting only affects future entries. The format for existing documents can be updated by using the action

Actions - Selected documents - Update view title


Document deletions
This setting controls behaviour upon deleting documents. Three options are available:
Do not check deletions
This value will result in deleting all selected documents without further checks for response documents. When documents are deleted, all corresponding response documents will become "lost documents".

Display warning if response documents are existing
When this options is activated a warning will be issued when attempting to delete a document without deleting the corresponding response documents as well. When documents are deleted, all corresponding response documents will become "lost documents".

Deny operation if response are existing and not selected
This option will prohibit deletion of documents as long as not all corresponding response documents have been selected as well.

Info: In addition to this section the special parameter DELETIONLIMIT (see 14, Special configuration) can be used to further specify application behaviour when deleting documents.


Automatically add reader fields to profiles and activities
With this section reader fields can automatically be added to customer profiles, contacts and activites.


Configuration can be done as follows:

Into the field "Field name" an arbitrary field name can be entered, e.g. DocReader.

The field "List of roles and/or groups" can hold roles resp. groups, e.g. [ReadAllDocs]. Hereby the roles are defined over which a user must dispose in order to read the document.
   
Info: The role [ReadAllDocs] given in the example above is not part of the ACL by default. You can specify an arbitrary role name for reader fields but remember to add this role to the ACL manually afterwards!

Profiles and activities which should be provided with reader fields can be selected using the selection button. When no selection is specified all profiles and activites will be provided with reader fields.

Info: When no reader fields are added to a document (which is the default setting) the document is visible to all users. Be aware, though, that adding reader fields limits access to the corresponding documents exactly to the specified users (resp. groups or roles). Therefore you should make sure at least an administrator and the server group have access to the document.


Automatically add author fields to profiles and activities
In analogy to configuration of reader fields also author fields can be added to customers, contacts or activities. This enables users with "Author" access to edit and process documents created by

Into the field "List of roles and/or groups" roles resp. groups can be entered. Users disposing of these roles resp. groups are able to edit these documents. Profiles and activities that should be provided with author fields can be selected via the selection button. When no selection is made, all profiles and activities will be provided with author fields.

Info: Users disposing of an access type of "Editor", "Designer" or "Manager" can always edit and process documents created by other users.


Automatically add reader or author fields to templates
Template documents can also be provided with reader or author fields automatically.

Configuration of these fields is done in the same way as it is done with reader resp. author fields for profiles or activity documents.