Configuration Monitor should not set parameter for the name of configuration file that is used

At the moment the configuration monitor sets the name of the configuration file as a parameter in the order. As a result, this name will be used for all nodes this order will execute.

This is not intended for example in these both scenarions:

1. When a new order is cloned from the order and will be put into another job chain, the configuration file of the first job chain will be used.
2. In a nested job chain the configuration file of the first job chain will be used for all involved job chains.

The resolution is to disable the setting of the order parameter to avoid these unintended side effects.

There are some workarounds for this issue:

1. You can use the jobchain_node_state/parameter syntax. This works, if you have different states in the involved job chains and if you not need the substitution ${par}
2. You can use one configuration file for all involved job chains. This works, if you have different states in the involved job chains. You can not edit the file with JOE because JOE only uses the default file name for the configuration file.
3. You can add a postprocessing to each job that is used in the involved job chains.

The monitor is like this

 

    <monitor  name="process1" ordering="1">
        <script  language="javax.script:rhino">
            <![CDATA[
function spooler_process_after(spooler_process_result){
    spooler_task.order().params().set_var("ConfigurationBaseMonitor.configuration_file","");
    return true;
}
            ]]>
        </script>
    </monitor>