automatically adapt namespace in external jobs when installing a model into another namespace

Situation:

You develop a model with several integrator projects.
Those projects are linked to each other by external jobs.

Unfortunatelly the namespace of the target project is quite hardcoded within the scope definition of the external job. (see picture)

e.g. if you have the namespace "Demo":

<job modified="1742307694869" name="J_ext_Groovy_Test1" type="ExternalJob" >
<project scope="Demo_de.assetcontroller.testnamespace">Test1</project>

Problem:

Imagine you install the model into another namespace "Test" instead of "Demo".
Then the namespace in the external job will not be changed automatically from "Demo" to "Test".

So the execution will fail.

We tried to use a workaround with variables. (see screenshot 2)
But this gets problems with the Integrator UI and probably is not really supported.
Also you have to change the variable manually.

Solution:

There should be a new standard setting within the external job
where you can set the namespace of the target project to a dynamic reference.
Something like: <namespace of current model>project_xyz

-> kind of relative reference, so that all projects within the same model can see each other
without using a hardcoded namespace

Thanks for evaluating this request :)
JL