Process Flows (Magic xpi 3.x)
The business process should now break down into flows, each one representing a sub-process or group of activities. A flow can include one or many steps, which are configured using Magic xpi components.
The invocation of a flow can be done using the following:
-
Magic xpi trigger, such as HTTP, Web Service, and Directory Scanner
-
Invoke Flow Service – Invoking child flows from a parent flow.
-
Auto start – A flow that will be automatically activated when the server is started.
-
Scheduled flow that either starts at a specific time or after a certain duration.
-
PSS mechanism
The basic definition of the flow should include:
-
Trigger definition
-
Step definition
-
Data flow definition:
-
Data format, including relevant transformation of data format, as part of the step
-
Data types
-
Data logic
-
Activation of logic – existing or a new one, to process information or to activate an existing procedure
-
Variable definitions – list of relevant variables that should enable you to process your data
-
Processing mode (stand alone, synchronous, parallel)
-
Error behavior definitions
-
Recovery definition (save point)
You can disable, enable, and deactivate individual flows within your Magic xpi project:
-
Active/Inactive – You can improve the Checker's performance by marking a flow inactive. The flow is then omitted from the Checker process, and also from the deployment process.
-
Enabled/Disabled – When you disable a flow, the flow is not executed when the project is deployed.
