Workflow
AMF is a workflow driven framework that invokes workflow definitions defined in the workflow rule for a combination of Sender, Receiver & Message Type.
Last updated
AMF is a workflow driven framework that invokes workflow definitions defined in the workflow rule for a combination of Sender, Receiver & Message Type.
Last updated
Workflow Actions rely on "Action types", which are the smallest units of work that are used in workflow definitions to form a sequence of steps. Default action types made available in OpenMFT are:
Deliver -> If used without any changes to Receiver, Message Type, or File Format, messages are put in Delivery Queue for scheduled pickup. Typical AMF messages use this as the default action inside a workflow definition.
EOL Conversion -> End Of Line conversion from one OS to another
Call Web Service -> Web service action in the workflow
Gunzip -> De-compress a .gz file
Gzip -> Compress a file to a .gz format
Mailbox -> Mailbox in /Inbox
Run Script -> Allows one to invoke a Python module
Route -> Route the message to an alternate receiver with a new message type so the workflow that corresponds to that combination of Sender, Receiver and Message Type could be invoked.
Most often used action types is: Deliver
Workflow definitions contain one or more Actions as a sequence of steps. Workflow definitions are like an itinerary that executes a sequence of steps or Actions that are defined. Here is an example of a Workflow Definition with Transform , Compress with Gzip & Queue for delivery using Call Web Service, Gzip & Deliver action types respectively:
Workflow Rules invoke a defined Workflow Definition for a given combination of Sender, Receiver & Message Type. Here are a few examples of Workflow Rules:
