CM MES DEE Actions#
Estimated time to read: 4 minutes
CM MES integrates default DEE Actions for the external printing systems BarTender and NiceLabel:
What follows is more detailed information regarding those out-of-the-box CM MES DEE Actions.
For more information, see DEE Actions.
BarTender#
BarTender is a printing system that allows you to design layouts and configure/deploy integrations.
Printing Integration BarTender Web Service Input#
The DEE Action sends the data via query parameters on the GET HTTP method and via a body on the POST HTTP method.
Note
If you use the POST HTTP method, the content-type can be JSON, XML or another type and some changes may be required for adequate integration.
Printing Integration BarTender Web Service Output#
The DEE Action assumes that the response is a JSON string with this format:
{
"Version": "1.0",
"Status": "RanToComplete",
"WaitStatus": "Completed",
"Validated": true,
"Messages": [
{
"ActionName": "Print Document",
"Level": 2,
"Text": "BarTender successfully sent the print job to the spooler.\r\n\r\nJob Name: LabelMaterialNameAndId.btw\r\nDocument: LabelMaterialNameAndId.btw\r\nPrinter: PDF"
}
]
}
And it returns the Text line as in the example above.
Note
If you configure another output, you may need to adjust your data structure.
Printing Integration BarTender File Input#
The DEE Action is prepared to send data in CSV or XML format:
- CSV - the Text Delimiter and Text Qualifier are set using the Printing Integration metadata, so you need to make sure that it is compatible with the BarTender configuration.
- XML - assume the following structure (Content as root node):
Note
If you use another structure, you must alter the DEE Action.
NiceLabel#
NiceLabel is a printing system that allows you to design, print, and manage labels for various industries.
Printing Integration NiceLabel Web Service Input#
The DEE Action sends the data via query parameters on the GET HTTP method and via a body on the POST HTTP method.
Note
If you use the POST HTTP method, the content-type can be JSON, XML or another type and some changes may be required for adequate integration.
Printing Integration NiceLabel Web Service Output#
The DEE Action assumes that the response is a JSON string with this format:
{
"AsyncState": null,
"CancellationPending": false,
"CreationOptions": "None",
"Exception": null,
"Id": 250,
"Result": "NiceLabel printed file to material name: Cookie-01",
"Status": "RanToCompletion"
}
And it returns the Result line as in the example above.
Note
If you configure another output, you may need to adjust your data structure.
Printing Integration NiceLabel File Input#
The DEE Action is prepared to send data in CSV or XML format:
- CSV - the Text Delimiter and Text Qualifier are set using the Printing Integration metadata, so you need to make sure that it is compatible with the BarTender configuration.
- XML - assume the following structure (Content as root node):
Note
If you use another structure, you must alter the DEE Action.
Hints and Tips#
For both file formats, variables like NumberOfCopies and Layout are sent with the Context Data, and the BarTender and NiceLabel configuration must be prepared. If this is the case, to capture those variables, you should use actions like:
-
BarTender
- Transform Text To Record Set
- For Each Database Record
-
NiceLabel
- Use Data Filter
- For Each Line
Note
If you are setting up the FTP server locally, you can follow this post: How To Setup FTP Server on Windows 11 - Microsoft Community ⧉.

