8.3.17 Effect of changing values of step properties during debugging
During debugging you can change the values of step properties and the return values. If you change the value of a step property, the value of the service property to which the step property is mapped does not change automatically. However, changing an output property of a step might indirectly change the value of a service property (output property or variable) depending on how output property mapping is configured.
The figure below shows an example of the behavior of a service template affected by changing the values of input and output properties of a step while executing a step. This example assumes that the service template is defined as described below.
Property mapping definition
- Step A
Input property Input 1 of the service is mapped to Input A1 of Step A
Output property Output A1 of Step A is mapped to Variable 1 of the service.
- Step B
Variable 1 of the service is mapped to Input B1 of Step B.
Input 1 of the service is mapped to Input B2 of Step B.
Output B1 of Step B is mapped to Output 1 of the service.
Behavior when a property value is changed
- Behavior when changing an input property of a step
If you change the value of Input A1 of Step A before executing Plug-in A, Plug-in A uses the new value when it runs. This does not change the value of the service input property Input 1 to which the step input property Input A1 is mapped. Therefore, the step input property Input B is assigned the original value specified for the input property of the service.
- Behavior when changing an output property of a step
If you change the value of the output property Output A1 of the step after executing Plug-in A, the new value is assigned to Variable 1 to which Output A1 is mapped. The input property Input B1 of the step also takes the new value.