GetProgramName Request#
Overview#
The system must process POST requests sent to the /getprogramname endpoint to retrieve the DEFPRODFILENAME and QUANTITY values. The system processes POST requests received at the /getprogramname endpoint and validates the lot. If validation succeeds, the resource recipe name and quantity are returned to the laser.
How To Configure#
Relevant Artifacts#
The following table lists the entities relevant to the implementation of this requirement:
| Name | Type | Is Mandatory | Description |
|---|---|---|---|
| IoTMetaDataDefinition | SmartTable | Yes | Smart Table used to configure REST server addresses and ports. |
| SMTLaserMarkerRequestOrder | DEE | Yes | DEE used to retrieve the Resource Recipe Name and quantity of the requested lot (WORKORDER), if defined, or the lot currently in process. |
How It Works#
- The host receives a POST request at the
/getprogramnameendpoint. - By default, the system invokes the
SMTLaserMarkerRequestOrderDEE, or another DEE configured in IoTMetaDataDefinition underGetProgramNameDEE. - The DEE returns the
RecipeNameandQuantityvalues. - After receiving the DEE response, the response payload is created using the original request data, adding
DEFPRODFILENAMEwith the value ofRecipeandQUANTITYwith the value ofQuantity. - The system returns an HTTP 200 response containing the generated payload.
- In case of an error, a dedicated error payload is generated and returned.
Assumptions#
- The
/getprogramnameendpoint is accessible and correctly configured.
Example Payload#
Request#
```json{ "MESSAGEID": 21, "MACHINEID": "LASER01", "USERNAME": "OPERATOR01", "WORKORDER": "123456" }