Description
Use this task to run a search on the Nexus GO Cards ordering API to get the status of an order which was previously launched through Nexus GO Cards production.
Configuration
To use this task, configure the following delegate expression in your service task:
${caasCardOrderStatusAction}
The following parameters can be configured in Identity Manager Admin:
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. |
When the status order is retrieved from Nexus GO Cards, the RFIDs readouts can have multiple entries for the same type.
For example:
{
"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"
}
]
}
}
For these cases, the first value of the same type is used (EM_HEX_LSB and EM_HEX_MSB are considered to be of the same type).