Job Request Action

A Job Request action allows you to submit a print request or a preview request for a job What is submitted for processing. A job is separated into print jobs and print job details based on the processing rules. A job defines which processes to use. to the Loftware Application Server. You can specify the process An object in Loftware that binds together all of the components to be used when responding to a print request. Among other items, those components may include a label template, layout, device, and a business rule to be used when processing a print request. Processes are created in the Process Design page. to use for the job request and whether the request is only for a preview. You can specify whether a Print button is displayed in a preview to a Data Provider Person or process that enters data into a form or other data entry view for a label that was configured by a Designer. A user acting as a Data Provider requires the DOCUMENT_PRINTER role or equivalent permissions..

Note: This type of action is available only in applications.

Note: Each action must have a name by which it is identified, and this name must be unique within the form in which it appears. This name can be modified in the Name field of the action and is displayed in View > Actions after the action has been created.

The following are the properties for a Job Request action.

Important! Content in an action or rule is case sensitive.

Value	Description
Name	The name for the action or rule.
Trigger source	The field that is used in conjunction with a trigger event to interactively run the rule. For example, a button that runs a query when clicked, a prompt that runs a query when submitted, or a form that runs a query when loaded.
Trigger event	The event that is used in conjunction with the trigger source to run the rule. For example, clicking a button, entering text at a prompt, loading a form, or submitting a job.
Priority	The order in which the rules that have otherwise identical triggers are run. Trigger values are compared only if the triggers have the same trigger source, trigger event, and trigger key (if any). The type of trigger source is irrelevant. The trigger source with the lowest value for priority is run first.
Conditional	Determine whether to perform an action based on the result of a comparison of values or the result of a logical operation. Name Operator Equals Not Equal Equals Ignore Case Not Equal Ignore Case Less Than Greater Than Is Missing Is Not Missing Is Empty Is Not Empty Value
Job request options	Whether to allow preview requests, print requests, or both.
Process	The name of the process An object in Loftware that binds together all of the components to be used when responding to a print request. Among other items, those components may include a label template, layout, device, and a business rule to be used when processing a print request. Processes are created in the Process Design page. to use for a job request. Tip: You can use the Relative Path check box to control whether the path is represented as an absolute path or a relative path. Using a relative path may be helpful if an object is likely to be transferred to a different Loftware Enterprise SP instance A Loftware Application Server and a Loftware Database Server that are associated with each other by a Loftware Enterprise - SP License.. The check box is available to select after the object has been saved for the first time. For more information, see Relative Paths.
Target folder data ref	The name of the job target folder to add to the data map A repository for the data for use when responding to a print request. Each data map entry is composed of a name (key) and a value.. If a target folder is not specified, the default job target folder is added.
Job ID data ref	The name of the job ID to add to the data map.