Learning DeadCL DeadCL Tutorials DeadCL Syntax DeadCL MBS

Walk throughs

Author Keys Conversations Libraries Arrays

  Network Status Community Hub Contact Us



(Parcel Specific)

(deadCL Syntax)


deadCL uses Parcel Specific syntax to ensure potential code conflicts are easier

You'll only need to use Parcel specific syntax if you've setup or are using either CHAD or Arnold - if you have any questions best to visit our Community hub.





PARCEL-

Used to inform when PARCEL endpoint(s), Object(s) or parameter(s) are present

Examples



Within deadCL we use PARCEL- to inform when the following commands are for Parcel interruption.



For example we use PARCEL- before setting an endpoint.

?DRP PARCEL- G C #Do-ID+OWZbS-NR5B6-vAX3N



G

Generate a Parcel object

Examples



Within deadCL we use G to Generate a Parcel object for use in another action or object string.



For example we use G to inform deadCL that we'd like to create a new header parameter within an Author Key.

PARCEL- G H VAL_{'vAX3N'}



C

Indicates CHAD is Parcel mode in use

Examples



Within deadCL we use C to inform the Parcel mode in use is 'CHAD'



For example we use C to inform deadCL that we're creating a Parcel endpoint for use with CHAD.


?DRP PARCEL- G C #Do-ID+OWZbS-NR5B6-vAX3N -- VAL_LR5p6



A

Indicates Arnold is Parcel mode in use

Examples



Within deadCL we use A to inform the Parcel mode in use is 'Arnold'



For example we use A to inform deadCL that we're creating a Parcel endpoint for use with Arnold.


?DRP PARCEL- G A #Do-ID+VkD2s-NR5B6-vAX3N -- VAL_vAX3N



H

Header parameters comes next

Examples



Within deadCL we use H when setting header object values.



For example we use H to set header parameters for external endpoints.

PARCEL- H Save-Data : OFF



P

Path parameters comes next

Examples



Within deadCL we use P when setting path parameter values.



For example we use P to inform deadCL when an endpoint can be used with path parameter (object) values.

PARCEL- P GET https://query.uk-london-1.oraclecloud.com/country/ PV_england /region/ PV_wessex



Q

Query string parameters comes next

Examples



Within deadCL we use Q when setting Query String parameter values.



For example we use Q to inform deadCL when an endpoint can be used with Query String parameter (object) values.

PARCEL- Q GET https://telemetry.uk-london-1.oraclecloud.com? QV_locations=300 & QV_time=13



B

Body parameters comes next

Examples



Within deadCL we use B when setting body parameter values.



For example we use B to inform deadCL when an endpoint can be used with body parameter (object) values.

PARCEL- B POST https://telemetry.uk-london-1.oraclecloud.com RV_locations RV_time



QV_

Parcel Query string parameter object Value

Examples



Within deadCL we use QV_ to inform deadCL that a PARCEL value may be substituted for another, this is similar to $_word



For example we use QV_ to set parameter object values.

QV_time=13; PARCEL- timeVAL_$13



PV_

Parcel Path parameter object Value

Examples



Within deadCL we use PV_ to inform deadCL that a PARCEL value may be substituted for another.



For example we use PV_ to set the value of a path parameter to a substitutional value, in this example $england

PPV_englandVAL_$england



RV_

Parcel Request body parameters object Value

Examples



Within deadCL we use RV_ to inform deadCL that a PARCEL value may be substituted for another, this is similar to $_word



For example we use RV_ to set parameter object values.

PARCEL- B XML RV_user B XML RV_remove