Hi BigRoux.

Thank you for your reply. I'll go through each point:

1. I was looking for a way to update the job tag dynamically and this solution doesn't do that as you pointed out.
2. "Manual" means it's not dynamically and programmatically set at runtime, so this is not applicable in my scenario.
3. I'm using DAB but I din't find a way to make it "really" dynamic, based on the job execution. I can do similar stuff during DAB deployment only, but once it is deployed it remains static all the time. So, I think there is no way to do what I wanted to do through DAB right now.
4. I've thought about an "external solution" using REST APIs, however that's not our use case since the job will run with the incorrect tag and than the workflow will be updated with a new tag once it is finished with its run.
   Let's do an example. We have "tag_1" and "tag_2". The initial setup will set the job with a generic "tag_x" tag. The workflow is triggered with parameter's value "1", so I'd like to tag that execution with "tag_1", instead it will be tagged as "tag_x" with this point 4. solution. Finally, the external service will update the workflow tag through the REST APIs and set it to "tag_1". Then, a new job triggering happens with parameter's value "2". The updated setup for the job will tag this second execution with the previous set tag of "tag_1", which is incorrect.
   Long story short, we needed a way to set the tag before executing the job run to mark correctly the execution, the resources and so on.

So, I deduce there is no way for the moment to set a job tag based on a job parameter. I hope in the next releases this feature will be available, along with some other similar "dynamic functionalities".

Thank you again. Best regards.