...
...
...
...
...
...
...
| Info |
|---|
This article includes updates for Smart ID 23.04.2. |
| Expand | |||
|---|---|---|---|
| |||
Description Use this task to run a search on the Nexus perform "GET requests" towards the Nexus GO Cards ordering API to get the status of an order which was previously launched through Nexus GO Cards productionand extract any attributes from the response. Configuration To use this task, configure the following delegate expression in your service task:
The followingparameters in the examples below can be configured in PRIME Designer | |||
| Parameter | Mandatory | Sample value | Description | orderId |
| This is the orderId (or requestId) provided by Nexus GO Cards when a cardOrder is placed. |
| statusVariableKeyName |
|
| Defines the parameter name (for example orderStatus) which will contain the order status defined by the above orderId. | EM_rfIdType | - | This parameter determines the variable name for the rfid of type EM. | MIFARE_rfIdType | - | This parameter determines the variable name for the rfid of type MIFARE. | HITAG_rfIdType | - | This parameter determines the variable name for the rfid of type HITAG. | LEGIC_rfIdType | - | This parameter determines the variable name for the rfid of type LEGIC. |
| Code Block |
|---|
{
"foundCount": "1",
"order": {
"orderId": "3541415",
"created": "2018-08-29 13:51:02",
"orderStatus": "Valid",
"orderStatusId": "1",
"cardNumber": "BB-1808-636328",
"layoutId": "147424",
"productionDate": "2018-08-29",
"validThru": "2023-08-29",
"personName": "Demo, Dynamics",
"readouts": [
{
"type": "EM_HEX_LSB",
"uid": "9876543"
},
{
"type": "EM_HEX_MSB",
"uid": "12345678"
}
]
}
} |
Identity Manager Admin.
Nexus GO Cards Ordering API
All the attributes that you want to extract have to match the Nexus GO Cards schema exactly. See Nexus GO Cards ordering for more information.
| Info |
|---|
Important details
|
Get order info:
Parameter | Mandatory | Value | Description |
|---|---|---|---|
URL |
| /api/order/{orderId} | The endpoint to call. |
param_orderId |
(for this endpoint) | Example value:
| Will replace the {orderId} value from the URL. |
costCentre | - | Example value:
| Will add the variable with the name costCentre_Output to the process map. The value will be taken from the response body. |
orderer.email | - | Example value:
| Will add the variable with the name ordererEmail_Output to the process map. The value will be taken from the response body. |
cardIds | - | Example value:
| Will add the variable with the name cardIds_Output to the process map as a list. The value will be taken from the response body. |
accessories.articleId | - | Example value:
| Will add the variable with the name accessories_articleIds_Output to the process map as a list. The value will be taken from the response body. |
Get available accessories:
Example: /api/accessory
Parameter | Mandatory | Value | Description |
|---|---|---|---|
URL |
| /api/accessory | The endpoint to call. |
queryParam_showDetails | - | Valid values:
| You can override the default query parameters by setting them yourself, or keep the default. |
queryParam_languageId | - | Valid values:
| You can override the default query parameters by setting them yourself, or keep the default. |
articleId | - | Example value:
| Will add the variable with the name articleId_Output to the process map as a list. The value will be taken from the response body. |
price | - | Example value:
| Will add the variable with the name price to the process map as a list. The value will be taken from the response body. |
Error cases
There are three major error cases:
Wrong URL
Mandatory parameter not defined, for example {cardId}
Resource not found, for example {cardId} does not exist
For these three error cases you will find two variables in the process map that describe what happened:
HTTP_STATUS_CODE
requestErrorMessage
You can use these variables to adjust your process flow accordingly.
| Expand | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||
Description Use this task to execute card productions on the server side. The service tasks supports execution of encodings via Card SDK or the PRIME-integrated JPKIEncoderJPKIEncoder integrated in Identity Manager. Printing is currently not supported. Configuration To use this task, configure the following delegate expression in your service task:
The following parameters can be configured in PRIME DesignerIdentity Manager Admin:
|