Unfortunately, Sharing properties (and a few other "structural" ones) seem to be elaborated before Substitution Variables are populated, so that strategy will not work. I have a feeling this came up before, and that there are technical reasons for this situation.
An alternative could be to generate artifacts via code, either directly in OS or by exporting and processing xml, in order to hardcode the necessary values in those properties.
Hey Jack: Thanks for confirming and the alternative suggestions. Those are certainly options, and ones I'll think on, but probably not as clean as the method I was hoping for. That said, this was a only concept being toyed with (and one that might fall into the 'pass the salt' category), so its acceptable if this is not possible.
Thanks, -db
Or in the automation category 😅
Ha! That's a good one as well.
