|
|
|
|
 General
|
|
Step/Trigger Name
|
The component name. You can enter a different name to describe what the step or trigger does. The step/trigger name can contain up to 30 characters.
|
|
Description
|
Enter a description of what the step does in the integration flow.
|
|
Step/Trigger ID
|
A read-only field displaying the ID of the step or trigger in the flow.
|
|
Component ID
|
An internal identifier number generated automatically.
|
|
Component Type
|
A read-only field displaying the name of the step type.
|
|
Condition
|
Enter a condition to specify the flow's execution behavior. You can either click  to open the Expression Editor, or you can right-click on the component and select Condition from the context menu.
|
|
Processing mode
|
The synchronization capability of the step depends on the Processing mode property.
A linear step will run in its parent context while a non-linear step will run in a new thread.
The options are:
-
Linear: Linear steps run in a sequential order one after the other depending on the order and levels defined in the flow.
-
Parallel: Parallel steps run at the same time as other steps defined on the same level.
-
Stand Alone: A component with the stand-alone processing mode is executed at the same time as another step in the flow (in the same way as a Parallel step), however it is executed independently of the flow. A Linear step with Wait for Completion = Yes will not wait for this type of component.
|
|
Wait for completion
|
In Wait for Completion mode, a linear step will wait until all the parallel steps on the same level are completed. This option is valid only for the Linear Processing mode.
The options are No or Yes.
|
|
Interface
|
Select the interface to be used with the component. You can select one of the following standard interfaces:
|
|
Advanced
|
|
Save point
|
Select Yes to indicate that the step is a Save Point in your flow. This is available only if the flow's Recovery Policy is set to Save Point.
|
|
Call logic flow
|
Use this option if you want to call generic logic after the execution of a specific step. Once this step has been executed, the logic flow that you defined in the flow properties is called before the Server continues to the following steps.
The options are Yes or No (default).
|
|
Logging
|
|
Step Logging
|
|
Logging Scope
|
Using the Logging Scope property, you can specify when the information is to be sent to the Magic xpi Activity Log view in the Magic xpi Monitor. The possible options are:
-
No (default): Nothing will be written to the Magic xpi Activity Log view.
-
Method: Magic xpi will write information to the log for each method in the step. This will be carried out after the method was executed. The XML interface does not allow Method level logging.
-
Step: Magic xpi will write information to the log for the entire step.
-
Full: Magic xpi will write information for both the Step and the Method options.
|
|
Step Logging Options
|
This property is only available if either Step or Full are selected in the Logging Scope property (above). The property defines when the information will be logged to the Monitor.
The available options are:
-
Before: Information will be logged before starting the step.
-
After: Information will be logged after the step has finished its execution.
-
Full: Information will be logged before and after execution of the step.
|
|
Message
|
This is the message that is saved in the log. You can either type the message, or click to open the Expression Editor and create a message.
|
|
BLOB
|
The BLOB file contains the message that is sent to the log. You can use the Expression Editor to select a BLOB file by clicking to the right of the BLOB field.
|
|
File Extension
|
Specify the file extension that you want to use. The available options are:
|
|
Trigger Logging
|
|
Logging Scope
|
Using the Logging Scope property, you can specify when the information is to be sent to the Magic xpi Activity Log view in the Magic xpi Monitor. The possible options are:
|
|
Message
|
This is the message that is saved in the log. You can either type the message, or click to open the Expression Editor and create a message.
|
|
BLOB
|
The BLOB file contains the message that is sent to the log. You can use the Expression Editor to select a BLOB file by clicking to the right of the BLOB field.
|
|
File Extension
|
Specify the file extension that you want to use. The available options are:
|
|
Setting
|
|
Step
|
|
Resource Name
|
Select a resource from the drop-down list, according to the component type. If you want to add another resource to this list, click the Project menu and select Settings. This opens the Settings dialog box, where you can then add resources as necessary. Alternatively, in the drop-down list, select New to open the Settings dialog box. A new resource is automatically created for you. You only need to name the resource, and enter its values.
At the end of the drop-down list, you will find an entry called Dynamic. When you select the Dynamic option, you can expand the Resource Name field and then click to insert an expression.
If a resource matching the Dynamic resource is not found:
-
In the Studio, the default resource is used for the configuration.
-
During runtime, an error will appear.
|
|
Resource Description
|
This read-only field displays the description of the resource that you entered in the Settings dialog box's Resources section.
|
|
Trigger
|
|
Service Name
|
Select a service from the drop-down list. If you want to add another service to this list, click Setting. This opens the Settings dialog box, where you can then add services as necessary. Alternatively, in the drop-down list, select New to open the Settings dialog box. A new service is automatically created for you. You only need to name the service, and enter its values.
|
|
Service Description
|
This read-only field displays the description of the service that you entered in the Settings dialog box's Services section.
|
