Message

Use the Message action to write custom strings (For example, custom warning messages, variable values, and comments). The message action creates custom entries in your Automation Manager log files. Automation log files contain application-generated information, warnings, and error descriptions. Use Message logs to track your message variables during configuration, troubleshooting, and debugging.

To configure Message actions, do the following:

  1. Go to All Actions and select Message from the drop-down Action menu.

  2. Rename your action and insert your description.

  3. Configure your message Content: Caption, Message, and Message Type.

    Message Types include:

    • Information

    • Error

    • Warning

  4. Expand Show execution and error handling options to set conditions for showing messages, ignoring failures, and saving Automation errors to variables.

LoftwareAutomation Manager displays colored Messages (For example, red errors and orange warnings) in your Automation Log pane.

Example 81. Example:

You print Pasta labels with Automation. Your trigger receives variable values from ERP generated CSV files. When your variable "Package" value is greater than 4, Automaton Log creates a warning.

UUID-b60ba704-43c4-1d2f-b8d0-36d2f43a8c43.png

Configuring Message actions.

Your result in Automation Manager looks like this:

UUID-0fd41f2d-25c1-6051-b2d2-86c5f744ceff.png

[Note] Note

When you set your Message severity to Error, your triggers do not go to error state. Printing is still possible.

Use Message logs for:

  • configuration troubleshooting

  • debugging your solutions

  • tracking values of your selected variables

displaying your customized warnings and error messages

Action Execution and Error Handling

Each action can be set as a conditional action. Conditional actions only run when the defined conditions allow them to be run. To define these conditions, click Show execution and error handling options.

Execution options are:

  • Enabled: specifies if the action is enabled or disabled. Only enabled actions will execute. This functionality may be used while testing a form.

  • Condition: defines one-line programming expression that must provide a Boolean value (true or false). When the result of the expression is true, the action will execute. Condition offers a way to avoid executing actions every time.

Error handling options are:

  • Ignore failure: specifies whether an error should be ignored or not. With Ignore failure option enabled, the execution of actions continues even if the current action fails.

    [Note] Note

    Nested actions that depend on the current action do not execute in case of a failure. The execution of actions continues with the next action on the same level as the current action. The error is logged but does not break the execution of the action.

Example 82. Example

At the end of printing, you might want to send the status update to an external application using HTTP Request action. If the printing action fails, action processing stops. In order to execute the reporting even after the failed print action, the Print Label action must have the option Ignore failure enabled.


  • Save error to variable: allows you to select or create a variable to save the error to. The same cause of the error is also saved to internal variables ActionLastErrorId and ActionLastErrorDesc.