Create FIDO Pre-reg shipment
In this step we will configure the custom action that will call to the YubiEnterprise Delivery API to create a new YubiKey with FIDO Pre-reg shipment.
Before you proceed ensure that you have configured the connection alias and credential used for calling the YubiEnterprise API with your API token.
Action properties
On the ServiceNow home screen, search for flow designer.
Click Flow Designer, a new window should open.
Once the Flow Designer page opens, click the Create new button, then select Action.
A menu will appear to configure the action's properties. Use the following values to initialize your action.
- Action name: YubiEnterprise create shipment (Pre-reg)
- Application: YubiEnterprise Delivery App
- Description: Place an order for a new FIDO Pre-reg YubiKey through the YubiEnterprise Delivery API
- Use the defaults for the remaining properties
Click Submit.
Action inputs
Next we are going to configure the inputs that go into the action. These inputs are the parameters that are going to be passed into our API call by our flow.
For each row in the table below, perform the following steps:
- Click the +Create Input button at the top.
- Fill in the input using the data provided below to the corresponding field (note that name will be automatically input).
Label | Type | Mandatory |
---|---|---|
Company | String | on |
Delivery Email | String | on |
First name | String | on |
Last name | String | on |
Phone number | String | on |
Street Line 1 | String | on |
Street Line 2 | String | off |
City | String | on |
Region | String | off |
Postal Code | String | on |
Country Code | String | on |
Product ID | String | on |
Inventory Product ID | String | on |
Customization ID | String | on |
Quantity | Integer | on |
PIN Request JWE | String | on |
Credential Request JWE | String | on |
Delivery Type | Integer | off |
Your actions input menu should look like the example below.
Click Save once your inputs are complete.
Input script
Next, we will pass our inputs through a script to format our data to ensure that it's ready to be consumed by our API.
On the left side, in the Action Outline, click the blue + button.
Search for scripts and select the Script option
Script inputs
We'll start by creating inputs for the script. This will utilize the same inputs that we defined in the previous step (yes, sadly this does need to be repeated).
For each of the items in the table below, do the following steps:
- Click the +Create Variable button
- Set the name using the name provided in the table below (warning: these values are case sensitive)
- Drag the corresponding data pill from the right side Data menu
Name (case sensitive) | Data pill |
---|---|
company | Company |
Delivery Email | |
first_name | First name |
last_name | Last name |
phone_number | Phone number |
street_line1 | Street Line 1 |
street_line2 | Street Line 2 |
city | City |
region | Region |
postal_code | Postal Code |
country_code | Country Code |
product_id | Product ID |
inventory_product_id | Inventory Product ID |
customization_id | Customization ID |
quantity | Quantity |
pin_jwe | PIN Request JWE |
credential_jwe | Credential Request JWE |
delivery_type | Delivery Type |
Your script inputs menu should look like the example below.
Adding the script
Next we are going to add a script to Script field. Copy the script provided below into the Script field.
(function execute(inputs, outputs) {
/*
* Below are the character constraints of the text inputs
* An example of handling this is shown in the "recipient" field
* The same pattern can be used for the other fields you wish to constrain
*
* country_code_2: 2
* recipient: 20
* recipient_firstname: 15
* recipient_lastname: 20
* street_line_1, and 2: 60
* city: 60
* region: 50
* recipient_email: 80
* recipient_telephone: 40
*
* Note, when using a substring, take a few characters off of the
* limit as special characters count for * more than 1 character
*/
outputs.shipment_exact_request = JSON.stringify({
delivery_type: parseInt(inputs.delivery_type),
recipient: {
recipient_company: inputs.company,
recipient_email: inputs.email,
recipient_firstname: inputs.first_name,
recipient_lastname: inputs.last_name,
recipient_telephone: inputs.phone_number,
},
mailing_address: {
street_line1: inputs.street_line1,
street_line2: inputs.street_line2,
city: inputs.city,
region: inputs.region,
postal_code: inputs.postal_code,
country_code_2: inputs.country_code,
},
shipment_items: [
{
product_id: parseInt(inputs.product_id),
inventory_product_id: parseInt(inputs.inventory_product_id),
product_quantity: parseInt(inputs.quantity),
customization_id: inputs.customization_id,
product_customizations: [
{
fido_pin_request: inputs.pin_jwe,
fido_credential_requests: [inputs.cred_jwe],
},
],
},
],
});
})(inputs, outputs);
Script outputs
Lastly, we will add the output variable for the script. This will pass the JSON object that we created in the previous step to the action component that will make the HTTP REST call to the YubiEnterprise Delivery API.
In the Output Variables section, click the +Create Variable button.
Set the single output using the variables below:
- Label: Shipment Exact Request
- Name: Will be auto populated based on the label
- Type: String (default)
- Mandatory: on
Your script outputs menu should look like the example below.
Click Save once your script is ready.
API REST call
Next we will configure the action step for making the REST HTTP call to the YubiEnterprise Delivery API.
On the left side, in the Action Outline, click the bottom blue + button.
Search for rest and select the REST option
If the REST option does not appear then you have not activated the IntegrationHub plugin. Follow the instructions in the prerequisites section.
Connection details
First we will add our API credentials to the REST call. We will utilize the connection alias that was created earlier in this guide.
Ensure that the Connection field is set to Use Connection Alias.
Change the Connection Alias to the one created earlier in the guide. The Base URL should be set automatically based on the connection alias.
Your connection details should look like the example below.
Request details
Next we will configure the details of the API method call. We will be utilizing the POST /fpr/shipments
API method
Configure the Request Details section with the following values:
- Build Request: Manually
- Resource Path: /fpr/shipments
- HTTP Method: POST
The Headers should include two header properties using the values below
Name | Value |
---|---|
Accept | application/json |
Content-Type | application/json |
Your request details should look like the example below.
Request content
Next we will add data to the body of our POST request. We will utilize the output of the previous script step. In the Request Content section, set the following values
- Request Type: Text
- Request Body: Drag the Shipment Exact Request data pill from the Script step section on the right side of the menu.
Your request content should look like the example below.
Click save once your API call is complete
Output script
We will now create another script to format the outputs of the action. This will ensure that we can capture data from a successful shipment, and to identify and understand potential errors.
On the left side, in the Action Outline, click the bottom blue + button.
Search for scripts and select the Script option
Script inputs
We'll start by creating the input for the script. We will only create one input, which will be the result of the previous REST step call
- Click the +Create Variable button
- Name: responseBody (case sensitive)
- Value: Drag the Response Body data pill from the REST step section on the right side of the menu
Your script inputs menu should look like the example below.
Adding the script
Next we are going to add a script to Script field. Copy the script provided below into the Script field.
(function execute(inputs, outputs) {
const response = JSON.parse(inputs.responseBody);
outputs.shipment_id = response.shipment_id;
outputs.shipment_state_id = parseInt(
response.shipment_state.shipment_state_id
);
})(inputs, outputs);
Script outputs
Lastly, we will add the output variables for the script
For each row in the table below, perform the following steps:
- Click the +Create Variable button at the bottom.
- Fill in the input using the data provided below to the corresponding field (note that name will be automatically input).
Label | Type | Mandatory |
---|---|---|
shipment_id | String | on |
shipment_state_id | Integer | on |
Your script outputs menu should look like the example below.
Click Save once your output script is complete
Action outputs
Lastly we will define the outputs of the action. These outputs will be usable by the final flow that will orchestrate the ordering experience. We want to ensure that the action outputs are able to express details about the new shipment, or any issues should they occur.
We will start by clicking the Outputs tab in the Action Outline pane.
Next we are going to configure the outputs.
For each row in the table below, perform the following steps:
- Click the +Create Output button at the top.
- Fill in the input using the data provided below to the corresponding field (Note: Unlike the previous examples, the Name field is not auto-populated).
Label | Name | Type | Mandatory |
---|---|---|---|
Status Code | status_code | String | on |
Shipment ID | shipment_id | String | off |
Shipment State ID | shipment_state_id | Integer | off |
Your actions outputs menu should look like the example below.
Once complete, press the Exit Edit Mode button on the top of the menu.
A new menu should appear showing the outputs you just defined with empty Value fields. For each output, you will add a data pill from the REST step and the second Script step sections on the right side of the menu
Use the table below to correlate the correct data pill to a label.
Label | Section > Data pill |
---|---|
Status Code | REST step > Status Code |
Shipment ID | Script step > shipment_id |
Shipment State ID | Script Step > shipment_state_id |
Your actions outputs menu should look like the example below.
Click Save once your outputs are complete
Publish the action
If everything looks good, click the Publish button at the top of the action menu to make the action available for all flows.