Email UML

Reference to the entity that represents account transaction.

Code of the attachment included in the email.

Balance state by the end of the period (phase).

Balance state by the end of the period (phase).

Balance state by the end of the period (phase).

Balance state by the end of the period (phase).

Code of the collector's account.

Date when the record was created.

User who created the email.

Reference to the entity that represents a customer’s account.

Due date of the email.

Reference to the entity that represents email address.

Reference to the entity that represents email codes.

The extension of the file uploaded or attached to the email (e.g: .txt, .doc, .xlsx, etc).

The first name of the user.

Identifier of the object used for references; auto-incremented integer value.

Indicates whether the email is visible outside of the system.

The last name of the user.

Code of Merchant Account to which instance of this object is attributed to. Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.

The actual text message of the email.

Reference to the entity that represents payment option.

Reference to the entity that represents a payment plan.

Date when the email was sent.

Secondary identifier, which can be used to cross-reference records between UniPay and integrated systems.

See Reference Code for additional information.

Response code of the email.

Enumerates the range of values of current email status.

Subject line of the email.

Code of the template used in email.

Email address where email is sent.