Run Command File

This action executes commands that are included in a selected command file. All File type options provide commands that Loftware executes in top-to-bottom order.

Command files usually provide data for a single label, but you can define files of any level of complexity. For more information, see section Command File Types.

About group identifies the selected action.

Name: allows you to define a custom action name. This makes actions easily recognizable on the solution's list of actions. By default, the action name is taken from its type.
Description: custom information about the action. Enter a description to explain the purpose and role of action in a solution.
Action type: read-only information about the selected action type.

File group defines the type and name of the command file that is going to be executed (JOB, XML or CSV).

File type. Specifies the type of the command file to be executed.
File name. Specifies the command file name.

File name can be hard-coded, and the same command file will execute every time. The option Variable enables a variable file name. Select or create a variable that contains the path and/or file name if a trigger is executed or an event takes place. Usually, the value to the variable is assigned by a filter.

Use UNC syntax for network resources. For more information, see section Access to Network Shared Resources in Loftware Automation user guide.

	Product level info
	Requires Automation Builder.

How to receive a command file in a trigger and execute it

After a trigger receives the command file and you wish to execute it, complete the following steps:

In Automation Builder module, on Variables tab, click the Internal Variable button in the ribbon.
In the drop down list, enable the internal variable named DataFileName. This internal variable provides path and file name of the file that contains the data received by the trigger. In this case, its contents is command file. For more information, see section Internal Variables in the Loftware Automation user guide.
In Actions tab, add the action to execute the command file, such as Run Command File, Run Oracle XML Command File, or Run SAP AII XML Command File.

For the action Run Command File, select the type of the command file in File type.
Enable the option Variable.
Select the variable named DataFileName from the list of available variables.

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
	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 39. 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.