I would like to define a "load rules" section with a parameter in a template project.
The parameter value would be defined in another 'concrete' job refering the template project scm configuration.

I tried the following:

I have a job named "my-template"
It is a parameterized build, defining parameter named "paramter1".
It defines a scm configuration whose load rules is :
/vob/myvob/${paramter1}

I have a job named "my-instance-0"
It defines "parameter1" value in section "Inject environment variables to the build process"
It defines the use of SCM from another project : my-template

When I look at "Base Clearcase Polling log", I see the parameter is not evaluated.

In EnvInject known limitations, i found in 'known limitations' section:
Only previous environment variables are available for polling
Some plugins provide polling mechanisms (such as SCM plugins, XTrigger plugins, ...) and you want to use injected environment variables in form fields of these plugins. Unfortunately, injected environment variables are processed only at build time therefore after the build is scheduled. Therefore, we can't access environment variables configured within the job. However, previous injected environment variables (from the previous build) are retrievable (implemented for example in the XTtrigger plugins). For the otehr plugins, authors are free to add the envinject-lib library dependency in their plugins in order to provide the ability to use environment variables given the EnvInject plugin.

Is there another to reach my needs ?
Is-it possible to take my needs into account in the next releases of clearcase plugin ?

Thanks