You can define your own sources 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. However, only the category (document type) Correspondence is 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 sources in the Groupware app configuration: Purchasing correspondence and Sales correspondence.

The administrator defines two new mappings for the two sources. Most of the source and target properties in the mapping table are the same. For the Department property, the administrator provides the value PUR in the mapping for the Purchasing correspondence source. In the mapping for the Sales correspondence source, the administrator enters the value SALES for the Department property.

The administrator creates two new Store in functions. For one function, the administrator selects the newly created Purchasing correspondence source. For the other function, the administrator selects the newly created Sales correspondence source.

Two new context menus for storing e-mails 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: