JobchainNodeSubstituteMonitor does not work correct when used with Universal Agent

Current Situation

This issues affects the new implementation of the configuration monitor
com.sos.jitl.jobchainnodeparameter.monitor.JobchainNodeSubstituteMonitor

When having a job chain with more then one node running on a Universal Agent and the nodes do have node parameters then for the first node everything works ok but for the second node the node parameters are not available.

Desired Behaviour

All node parameters in a job chain should be available even when running on a Universal Agent or having more than one node in the job chain.

Workaround

Use the old implementation sos.scheduler.managed.configuration.ConfigurationOrderMonitor

Please note the old implementation will be removed with release 1.12. Then both implementations wll be the same.