Dynamically Changing a Service's Connection at Run Time
You may run a service using a connection other than the default connection that was associated with the service when the service was created. To override the default, you must code your flow to pass a value through the pipeline into a service's $connectionName field.
For example, you have a flow whose primary purpose is to update your company's North American Lotus Domino Server. However, you want the flow to have the capability to update your company's European Lotus Domino Server-with the decision of which server to update to be made programmatically at run time. The output signature of the flow's first service contains a field called Target. The flow could branch based on the value in Target. If Target contains the value "NA", the second service in the flow would ignore $connectionName-thus using its default connection to connect to (and then update) the North American server. However, if Target contains the value "E", the second service in the flow would use the value in the $connectionName from the pipeline and connect to (and then update) the European server.
Keep in mind these restrictions when using dynamic connections:
Both connections - the default and override - must have the same Lotus Domino classes and methods.
The $connectionName field is present only in services created with
Designer.