You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Changes to how variable values are set/passed in pipeline after October Release.

Received Response


Has anyone else noticed a change to how your variables are being set within existing pipelines after the October Release?

Content (required):

I was working on a pipeline in one of our lower instances to pass a sub-variable value through a sub-variable name using a Set Substitution Variable job. We needed to set this value so we could pass it to a Clear Cube rule that referenced the specific sub-variable name.

Prior to the October Release hitting this environment, I was able to include a hard coded value in front of the sub-variable value I wanted to pass (i.e., FY$YEAR ,with $YEAR referencing a variable set at the runtime prompt resulting in the value = 'FY24').

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!