The basics

Path Parameters are set using substitutions within a dedicated endpoint Library. They're used by CHAD to access resources at remote (external) endpoints.

Assigning a parameter is done using PV_.

In this example we've got two path parameters;

PV_england
PV_wessex

NOTE: Path parameters can only be set on endpoint calls made by Parcel not to it.

     
  

 *lib - oracle_API_endpoints
 *// COPYRIGHT 2018 ZERO //*
       
oracle-query-uk;
	PARCEL-GEThttps://query.uk-london-1.oraclecloud.com/  
	PARCEL- PGEThttps://query.uk-london-1.oraclecloud.com/country/PV_england/region/PV_wessex  
		
oracle-telemetry-uk;
	PARCEL-PUThttps://telemetry.uk-london-1.oraclecloud.com   
		
 /recall -- Oxford University Press

 *END*

You may review the syntax here.

Assigning path parameters

Okay, now lets explore how to set the values for the path parameters discussed.

PV_england
PV_wessex

Assign a value

Here we're using the Endpoint Library itself this works just fine when you've only a handful of parameters. Generally speaking we'd recommend using two seperate Library for both the endpoints & parameters.

What we've done is change the values to something easily manipulatable within a your Conversation (deadCL programme).

PV_england	becomes$_england
PV_wessex	becomes$_wessex

You may also set permanent path parameters as shown below the two variable values.

     
  

 *lib - oracle_API_endpoints
 *// COPYRIGHT 2018 ZERO //*
       
oracle-query-uk;
	PARCEL-GEThttps://query.uk-london-1.oraclecloud.com/  
	PARCEL- PGEThttps://query.uk-london-1.oraclecloud.com/country/PV_england/region/PV_wessex  
	
		PPV_englandVAL_$_england
		PPV_wessexVAL_$_wessex
		
		PPV_fixed-valueVAL_fixed
	
	
 /recall -- Oxford University Press

 *END*