.NET Service - Configuration (Magic xpi 3.x)
Enter the parameters in the following table in the .NET Configuration dialog box:
|
|
|
|
|
|
Name
|
Type a name that describes the service in the flow.
|
|
Description
|
Type a description of the service in your flow (optional).
|
|
Processing mode
|
Select whether the step should be executed linear, parallel or stand-alone. This is only available if the .NET Service is not the first step in the flow.
|
|
Wait for completion
|
Select whether the step should be run in Wait for Completion mode. The options are Yes or No.
|
Note:
|
Wait for completion is only available when the .NET service is a Linear step, and if it is not the first step in the flow.
|
|
|
|
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.
|
|
Magic xpi Server
|
Select the Magic xpi Server where the .NET service is executed.
Click  to the right of the Magic xpi Server field to open the Servers List. Select a server from the list and then click Select.
|
|
Call logic flow
|
You can use this option if you want to call generic logic after the execution of a specific step. Once this step has been executed, the flow logic that you defined in the flow properties is called before the Server continues to the following steps.
The options are Yes or No (default).
|
|
|
|
Component Name
|
The name you give to your .NET service.
|
|
Language Code
|
Select the language that you will use to create the .NET Framework component. You can select C# or VB.NET.
|
The .NET Configuration dialog box also has the following additional buttons:
|
|
|
|
Generate
|
Generates a .NET class with the name supplied by the user.
|
|
Configuration
|
Calls the .NET Class Config method. You can use this to call existing .NET services, including ones created in V2.5. To do this, you have to save the component folder under the project folder, drag a .NET service into the Flow Editor and configure the service with the .NET class name and language. The .NET class will be located by the component name. When you click the Configuration button, the Class Config method will be called.
|
|
Edit
|
Lets you edit an existing .NET service.
|
|
Note:
|
-
.NET SDK components from V2.5 will be automatically migrated to the current Magic xpi version's .NET service. The component name is taken from the migrated project and used in the appropriate fields of the .NET service.
-
The way in which Magic xpi transfers BLOBs (binary large objects) to and from .NET is different when using Magic xpi’s predefined context BLOB variables than when working with user-defined BLOB variables. Because of this, it is recommended to utilize user-defined variables (for example, F.Blb) to send and receive BLOB content when using the .NET service.
|
|
Since version: V3.2 SP2
Magic xpi allows you to customize the .NET service icon. This confers several advantages. For example, you can ensure that a specific .NET service stands out in a flow, or you can easily differentiate between multiple .NET service instances in the same flow.
|
Note:
|
-
Only icons in .gif format are supported.
-
Your new icon will also be visible in the Magic xpi Monitor.
-
If you print your project, the new icon will be used.
|
|
To customize a .NET service icon, follow these steps:
-
Configure and generate a .NET service. A folder named after the new .NET service is automatically created in the <Magic xpi installation>/projects/<project name> folder. The new <.NET service> folder contains a default icon in .gif format, which is also named after the .NET service.
-
To use your own icon image instead of the default icon, rename your icon with the same name as the default icon.
-
In the <.NET service> folder, replace the default icon .gif with your new icon .gif.
-
Repeat this process for other .NET service steps, as required.
-
The next time you open the flow, your new icons will be visible.
