Skip to content

Recipe Upload Request#

recipebodyrequested.lg

This task implements Recipe Upload Requests from the MES system. When triggered, it subscribes to the configured system event subject, receives an upload request from the MES, retrieves the corresponding recipe details (name, body, and format) from the MES, and emits them as outputs for downstream processing.

Connect IoT Recipe Upload Request Task

Workflows#

Data Flow Control Flow

Inputs#

Name Data Type Description
Enable/Disable Boolean Activates or deactivates the event listener. Defaults to true (enabled).
Subject String The system event subject to subscribe to for recipe upload requests.
Reply Timeout (ms) Integer Maximum time (in milliseconds) to wait for a reply before timing out.

Outputs#

Name Data Type Description
Recipe Name String The name of the recipe requested for upload to the equipment.
Body Any The recipe body content (text or binary) to be sent to the equipment.
IsBinary Boolean Indicates whether the recipe body is in binary format.
Success Boolean Triggered when a recipe upload request is successfully received.
Error Error Triggered when the task fails for some reason.

Settings#

On the General tab, you have the usual settings and the following settings:

Name Data Type Default Description
Auto Enable Boolean true Automatically activates the event listener when the task is initialized.
Reply Timeout (ms) Integer 60000 Amount of time (in milliseconds) allowed to wait for a reply before issuing a timeout.
Recipe Upload Request String RecipeManagement.UploadRecipe Subject used to communicate with the MES for recipe upload requests. This field is read-only.

Connect IoT Recipe Upload Request Task

Behavior#

This task listens for Recipe Upload Requests from the MES and emits the Recipe details as outputs for downstream processing by an IoT Workflow to upload the recipe to the equipment.

It supports two execution modes:

  • Data Flow: Emits Recipe Name, Body, and IsBinary outputs so that a downstream Send Recipe Upload Reply task can send the result back to the MES. A timeout is enforced while waiting for the reply.
  • Control Flow: Runs a single attached branch each time a request is received, passing the recipe data as output properties. The branch has a configurable timeout.

Remarks#

This task uses a context-based data structure called a zone. For more information, see Zones page.

In Data Flow mode, pair this task with the Send Recipe Upload Reply task to complete the request/reply cycle.

In Control Flow mode, the task must have exactly one branch configured.