The E-Mail Document Type

enaio® editor 10.10 »

If you are managing e-mails and e-mail objects in enaio®, configure an e-mail document type for every cabinet which will contain e-mail messages.

E-mail document types are automatically set up with the following fields:

Field

Internal name

From:

MAIL_FROM

To:

MAIL_TO

Cc:

MAIL_CC

Subject:

MAIL_SUBJECT

Date:

MAIL_SUBMIT_TIME

Message:

MAIL_BODY

Mail Digest

MAIL_DIGEST

When transferring an e-mail in enaio® client, the identification data of the e-mail can be assigned automatically to the index data fields via the internal name. When creating an e-mail, the fields are then automatically indexed with the corresponding data.

To create e-mails you will need the microservice 'mailstorage'. The microservice is preconfigured so that the configuration file ems-prod.yml does not need to be customized if all e-mail document types have fields with the internal names specified above.

The 'Mail Digest' field is required to store location information. Without this field no e-mails can be transferred. It is arranged on the form such that it is not visible.

Additionally, you can set up a field for the addressee of a blind copy with the internal name 'MAIL_BCC'. This field will also be automatically indexed with data from the e-mail.

The 'Date' field has the database field type 'Date/Time'.

Up to version 8.50, the date field was created with the database type 'Date'. For such e-mail document types, migration can only be carried out via data migration in the project.

You can edit the dialog elements in any way; for example, you can change the name, the field length, the length of the database fields, or you can delete fields which you do not need anymore. Only the field 'MAIL_DIGEST' is necessary.

The 'Message:' field has a default length of 248 characters. If the database allows more characters you should extend the permitted number of characters.
If the text of an e-mail which is transferred to the field 'Message' is longer than the maximum allowed length of the text field, the text that exceeds the maximum length will not be transferred to the data sheet in the 'Message' index data field, even though it is shown in the e-mail application and in the content preview. Embedded objects will not be fitted to the database field.

A document type can have any number of dialog elements added.

The index data form is not opened in enaio® client when you are creating e-mails. This action can be changed in the configuration file of the microservice.

If the index data form is opened, then the e-mail's identification data is auto-populated in the appropriate fields and can be edited by default by the user. The microservice's configuration file can be used to specify that changes made to fields by users are not applied. Those fields are not identified for users and should be marked on the form or be read-only.