The following JSM Binding Script directives require you to specify the Processing Sequence variable names that will provide or receive the values for the JSM binding fields that you used in your LANSA Integrator binding solution:
Receive binding field values from processing sequence variables
Write binding field values to processing sequence variables
To do this, select the appropriate script line and click the Edit Bindings button. Depending on which type of directive you are using, a window like one of those shown will be displayed.
The implementation of the JSM_BINDSCRIPT activity provides twenty-six (26) predefined binding fields. These are the fields that you should have used in your LANSA Integrator binding solution. The pre-defined binding fields are listed in:
Binding Fields and Working Lists
The window shows these pre-defined fields (you can scroll the window to see all of them). Against each of the pre-defined binding fields that you actually used in your LANSA Integrator binding solution, you should type the name of a Processing Sequence variable that will provide or receive the binding field value.
When you enter the Processing Sequence variable names, note the following:
- LANSA Composer displays the Processing Sequence variable names with the leading ampersand (&) character, but you do not have to type it.
- Processing Sequence variable names may be up to twenty (20) characters, must begin with A through Z, and may consist of A through Z, 0 through 9, and the underscore (_) character.
- Processing Sequence variables are implicitly defined simply by using them. You need to be careful that the variable names that you use do not conflict with variables that may already be used for other purposes in the Processing Sequence containing the JSM_BINDSCRIPT activity.
It should be clear that you cannot simply assign Processing Sequence variable names to arbitrary binding fields, but instead, you must do so with reference to the binding fields' usage in the actual LANSA Integrator binding solution that you are using. You will, therefore, need to make reference to the actual LANSA Integrator binding solution while completing these bindings.
It is not mandatory that you bind every binding field used in your LANSA Integrator binding solution to a processing sequence variable. Indeed, if the value is not required in or from a processing sequence variable, then you can optimize performance by omitting the binding for that binding field.
For more information about Processing Sequence variables, refer to the following topic: