The Request of Absence entity defines the information required for a request to leave the office followed by an approval or declined workflow.

Database level

The entity's attributes are shown below. Mandatory fields are marked with a red star:

NameTypeLabelDescription
form *StringFormRepresents the entity form. Will always be "rqa".
xxx_name *StringNameThe object name
rqa_approverprj_name *String
Represents the name of the project manager who must aprouve the request.
rqa_approverprj_unid *String
Represent the unique ID of the person document. 
rqa_approver_name *String
Represents the name of the superior who must aprouve the request.
rqa_approver_unid *String
Represent the unique ID of the person document. 
rqa_body HTML/String
Dscriprion of the reason.
rqa_start *Date/Time
Start date and time of the leave.
rqa_end *Date/Time
End date and time of the leave.
rqa_nr *Number
Represents the request of absence's number. Will always be "RQA-YYxxxx" as serial number, that automatically increments by 1 as each new record is added.
rqa_per_name *String
Represents the name of the person who makes the request composed from firts name and last name.
rqa_per_unid *String
Represent the unique ID of the person document. 
rqa_state *Number
Represents the state of the document as code. (e.g. "100", "200" )
rqa_state_text *String
Represents the state of the document as text. (e.g. "requested", "aproved" )
rqa_type *String
Represents the type of the document as code. (e.g. "lev", "trv").
rqa_type_text *String
Represents the type of the document as text. (e.g. "lev", "trv").

QEE classes level

The class representing the Request of Absence is QEERqa

Inherits from: QEEObject

REST level

The endpoints dealing with Request of Absence are:

xrRqa (GET, POST, PUT, DELETE)

xrRqas (GET, PUT, DELETE)