Delete File

This action deletes a selected file from a drive.

Loftware Automation module runs as service under a defined Windows user account. Make sure that account has the permissions to delete the file in a specified folder.

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 sets the file related details.

File name: the name of the file to be deleted. File name can be hard-coded. Data source dynamically defines the File name using an existing or newly created variable.

Path and file name can be hard-coded, and the same file is going to be used every time. If only a file name without path is defined, the folder with Loftware Automation configuration file (.MISX) is used. You can use a relative reference to the file name, in which the folder with .MISX file is used as the root folder.

Data source option enables variable file name. Select or create a variable that contains the path and/or file name or combine several variables that create the file name. For more information see section Using Compound Values in Loftware Automation User Guide.

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

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