You can define your own categories to create specific mappings for your organization.

Example

An employee receives a variety of different e-mails. One part of these e-mails is correspondence for purchasing. The other part of these e-mails is correspondence for sales. The categories (document types) CorrPurchase and CorrSales are available in the d.3 repository.

The Department property must be defined based on the e-mail type (purchasing or sales). However, only the employee can decide which type of e-mail it is. Nevertheless, when storing e-mails, the employee should only have to change the storage form in a small number of exceptional cases. In the ideal scenario, the employee stores the e-mails directly in the repository so that the relevant processes can be started within the organization.

The administrator for the organization defines two new categories in the Groupware app configuration: Purchasing correspondence and Sales correspondence.

The administrator uses one of the default sources as the source.

The administrator creates two new Store in functions in the Groupware app configuration. For one function, the administrator selects the newly created category for the correspondence for purchasing. For the other function, the administrator selects the newly created category for the correspondence for sales.

Two new context menus for storing items in the d.3 repository are then available to the employee. With the aid of the context menus, the employee can directly decide whether an e-mail is to be stored for Sales or Purchasing.

See also: