Skip to main content
Skip table of contents

Memo (mem)

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:

Name

Type

Label

Description

form *

String

Form

Represents the entity form. Will always be "mem".

mem_sdoc_name *

String

Name

The object name

mem_assoc_type

String

e.g. "sac"

mem_att_file

String

The attachment name if existing. e.g. "Scan__20_21_25-25_10_2016.pdf"

mem_att_path

String

e,g, "/tmp/"

mem_body

HTML/String

Represents the body of the object.

mem_copyto

String

The name of the person document set in copy composed from last name and first name (with an empty space in between).

mem_copyto_email

String

The e-mail of the person document set in copy. 

mem_copyto_unid

String

The unique ID of the person document set in copy. 

mem_created_from

String

e.g. "sdoc"

mem_from

String

Represents the sender person name. (e.g. "JahnWain")

mem_from_email

String

Represents the sender email. (e.g. "john.wain@synapcus.com")

mem_from_unid

String

Represents the unique ID of the sender person document.

mem_sdoc_nr

String

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_unid

String

The unique ID of the parent entity type "sdoc" under which the memo has been created and referenced.

mem_sendto

String

Represents the receiver person name. (e.g. "TomPain")

mem_sendto_email

String

Represents the receiver email. (e.g. "tom.pain@synapcus.com")

mem_sendto_unid

String

Represents the unique ID of the receiver person document.

mem_subject

String

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)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.