The REMOTE_CALL_DETAILS collection holds the structural details of all routines that are enabled in current design projects or have otherwise been requested.
A REMOTE_CALL_DETAILS entry always has a corresponding REMOTE_CALL_RESOURCE entry and their name, nativeIdentifier, projectId and connectorId attributes always match.
{
"_id" : "",
"name" : "",
"nativeIdentifier" : "",
"projectId" : "",
"connectorId" : "",
"inTypeResource" : {},
"outTypeResource" : {},
"streamy" : false
}
Attribute |
Value |
Note |
_id |
A unique identifier for the remote call resource. |
|
name |
The given name for the remote call resource |
By default, it is the simple name of the routine |
nativeIdentifier |
The full native name of the routine |
Generally of the form <container>.<name> e.g.: "public.calculate_impact" |
projectId |
Reference to the design project (PROJECT_WIP entry) this routine belongs to. |
|
connectorId |
Reference to the connector (CONNECTOR entry) this routine is accessed through. |
|
inTypeResource |
A descriptor for the routine's inputs (arguments) in the form of a TypeResource |
DTS models routines so that their arguments and results are wrapped in structured objects (each argument and result being an attribute in the respective wrapper). These are the TypeResources that describe those models. |
outTypeResource |
A descriptor for the routine's outputs (results) in the form of a TypeResource |
|
streamy |
A flag showing if the remote call returns a stream or not. |
|