Hi all -- has anyone used

dynamic

workflows in combination with reference launchplans (and specifically, the

{{ registration.version }}

macro)? We're observing an issue where it doesn't seem like the macro is getting properly replaced, and I'm wondering if the runtime nature of the dynamic workflow is the underlying cause (i.e., a "classic" workflow gets evaluated at registration time and thus the macro gets replaced properly, but because dynamic workflows skip that step, the macro never gets evaluated)?

dynamic wont work with the macro today, but it is possible to change that

Got it. Would the only real solution for now be to just hardcode a specific

version

of the workflow we want to call from our

dynamic

?

hmm i would love an example

I am about to head out on my honeymoon next week, so I am not the best one to get this done anytime soon 😝

ohh ya, enjoy your honey

Will do, I'll describe our situation in the issue