Synapcus Developers (EN)

Document (sdoc)

This Synapcus document (sdoc) represents an uploaded file with it's meta informations from the Synapcus cloud. Typically sdocs are organized in folders (fld).

Database level

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

Name

Type

Label

Description

form *

String

Form

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

sdoc_name *

String

Name

The object name

form *

String


Represents the document number. Will always be "D-xxxx" as serial number, that automatically increments by 1 as each new record is added.

sdoc_org_unid *

String


The unique ID of the organisation document.

sdoc_created_from *

String


The parent process type under which the document has been created/uploaded and referenced.

sdoc_creation_date *

Date/Time


Date of creation. 

sdoc_receiver_name

String


The name of the receiver document composed as the  first name and the last name (empty space in between).

sdoc_receiver_unid *

String


The unique ID of the receiver document.

sdoc_sender_name *

String


The name of the sender document composed as the  first name and the last name (empty space in between).

sdoc_sender_unid *

String


The unique ID of the sender document.

sdoc_prj_name *

String


The project name if the parent process under which the document has been created/uploaded was a project.

sdoc_prj_unid

String


The unique ID of the project document.

sdoc_sop_name

String


The opportunity name if the parent process under which the document has been created/uploaded was an opportunity.

sdoc_sop_unid

String


The unique ID of the opportunity document.

sdoc_cpg_name

String


The campaign name if the parent process under which the document has been created/uploaded was a campaign.

sdoc_cpg_unid

String


The unique ID of the campaign document.

sdoc_state *

String


Represents the state of the lead as a number.

sdoc_state_text *

String


Represents the state of the lead as a text.

QEE classes level

The class representing the Document is QEESdoc

Inherits from: QEESbd and QEEObject

REST level

The endpoints dealing with Document are:

xrSdoc (GET, POST, PUT, DELETE)

xrSdocs (GET, PUT, DELETE)