Hi,
We have a question regarding the industrialisation process from one environment to another:

We have two environments (production and test). The jobs are simply constructed in test and then passed onto production when validated.
The naming convention in place, requires that the job's name should have the environment within it. Therefore, when we pass the job in production we should modify the job's name afterward, either in the client or the xml when exported. Both solution are not great, is there a better solution, what is the recommended solution for this use case?

Maybe you can use User Variables that are different on the two servrers (and do not export these Variables). So, for example you could create a User Variable called Environment which contains PROD or TEST. You could then use this Variable in the Job name.

---

Hi,
This is what I thought at first, but it doesn't work. The variable is not resolved in the job name and it displays the variable at least on the 8.2.1 version I tested this.
Has this beaviour changed?

In which places do you use it now?

---

I tried in the job name field and the task name field but no success.

Yes, I see now that this is the case. The reason behind this performance. We do not want to have to resolve name through Variable resolving on each place the name is being used.

---

Ok I understand this.
In my case it will be a great feature. Can you see another alternative?

Actually I export the jobs configuration, edit le job.xml file and import it on the other server. it work but I think it is a little error prone

We do not recommend editing it manually. We do recommend using Variables but maybe you can use the Variable in Notifications instead of the interface.

---