Create Label Variant

This action allows you to create a review-ready variant of an existing label. Label objects in such variants have locked data source values. Their content is defined by the current value of the applicable data source.

The purpose of creating a review-ready variant of a label with “locked” data sources is to make the label suitable for approval process in which data and template need to be approved together. Instead of viewing a label without defined content for its objects, the approver reviews a variant with defined values. This allows him to quickly see and approve the final label layout with actual values that are going to be used for printing.

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.

Settings group defines the label file to be converted and the output file (label variant).

• Label name: the name of the label file to be converted into a review-ready variant with locked data source values. Data source dynamically defines the Label name using an existing or newly created variable.

• Print time data sources: this option allows you to define the data sources whose values are going to be provided at the actual print time. If a data source is listed in this field, its value is not locked and can be provided at print time. Typical examples are data sources for production values like LOT number, expiry date, etc.

  Tip

  Insert only data source names without square brackets, separated by commas or listed in a column using Enter key.

• Output file name: the name of the label variant file that is going to be ready for review. Data source dynamically defines the Label name using an existing or newly created variable.

There are several rules that apply to the review-ready label variant:

1. Data source values are locked by default. To exclude the data sources from being locked, list them in Print time data sources field to keep them active on the review-ready label. You can define their values at print time.
2. Counter variables, functions, database fields and global variables are converted to non-prompted variables.
3. Graphics are embedded.
4. The destination label variant stored in Loftware Control Center Document Storage is automatically checked in. Original Label name and Print time data sources are used as check-in comment.
5. Label variants can be opened in Loftware Designer in locked state.
6. Label files generated with this action cannot be imported.
7. If label variants are stored in printer memory, the recall command can only provide values for print time data sources.
8. If using Loftware Control Center, label preview in Document Storage allows editing of print time data sources.
9. Current time and current date variables cannot be set as Print time data sources on the review-ready label variant.

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

At the end of printing, you might want to send the status update to an external application using the 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.