The Memo Entity represents a Synapcus internal message send between two or more users.

Database level

See the entity fields bellow. Mandatory fields are marked in red:

NameTypeLabelDescription
form *StringFormRepresents the entity form. Will always be "mem".
mem_sdoc_name *StringNameThe object name
mem_assoc_typeString
e.g. "sac"
mem_att_fileString
The attachment name if existing. e.g. "Scan__20_21_25-25_10_2016.pdf"
mem_att_pathString
e,g, "/tmp/"
mem_bodyHTML/String
Represents the body of the object.
mem_copytoString
The name of the person document set in copy composed from last name and first name (with an empty space in between).
mem_copyto_emailString
The e-mail of the person document set in copy. 
mem_copyto_unidString
The unique ID of the person document set in copy. 
mem_created_fromString
e.g. "sdoc"
mem_fromString
Represents the sender person name. (e.g. "JahnWain")
mem_from_emailString
Represents the sender email. (e.g. "john.wain@synapcus.com")
mem_from_unidString
Represents the unique ID of the sender person document.
mem_sdoc_nrString
The number of the parent entity type "sdoc" under which the memo has been created and referenced. Will always be "D-xxxx". (e.g. "D-0007")
mem_sdoc_unidString
The unique ID of the parent entity type "sdoc" under which the memo has been created and referenced.
mem_sendtoString
Represents the receiver person name. (e.g. "TomPain")
mem_sendto_emailString
Represents the receiver email. (e.g. "tom.pain@synapcus.com")
mem_sendto_unidString
Represents the unique ID of the receiver person document.
mem_subjectString
Represents the subject of the object. 

QEE classes level

The class representing the Memo is QEEMem

Inherits from: QEEObject

REST level

The endpoints dealing with Memo are:

xrMem (GET, POST, PUT, DELETE)

xrMems (GET, PUT, DELETE)