Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member604434
Participant
0 Kudos
269
Connector Builder Guide – Creating Parameters

Open Connectors consists of over 170 connectors to 3rd Party Applications natively embedded in the SAP ecosystem. If the Connector you need does not exist in the catalog, you can build it quickly with Connector Builder. This instruction guide will walk you through using this tool, with concrete examples throughout. The beginning, Part 1, can be found here.

 



If creating parameters on the Setup screen, they will be global parameters and will be appended to each resource API call created on the next screen, the Resources screen.



Clicking on Add Parameter will add an empty row. Let’s run through the different types of parameters that can be created.

Example 1: A value (“123xx”) that you want passed in the header (“x-key”) for every request:

Name: 123xx  Type: value    Source: request

Vendor Name: x-key    Type: header  



Example 2: A configuration value (stored under the configuration variable called token [see creating a configuration value]) that you want passed in the header (“Authorization”) for every request. The parameter setup will look like this:


The token here represents the configuration key and its value will be substituted here.

Example 3: A query parameter with the Vendor Name “lastName”:



Note that the Name “Last Name” is arbitrary and is what the user will see as the query field name.

Example 4: A configuration value substituted in the Base URL:



Here we are assuming that we have a configuration value “siteurl” created. The user enters this when creating a Connector Instance.

The parameter setup will look like this:



Example 5: Asking the user to enter a JSON body



Example 6: Asking the user to populate a query field but sending that to the vendor as a form parameter:



Example 7: Asking the user to populate a query field but not sending it to the vendor because perhaps you will use it in the prehook instead:

Labels in this area