Skip to content

Settings and activity

1 result found

  1. 43 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Product Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Charles McCabe commented  · 

    I have another alternative approach: Step alias names.

    Imagine:
    StepA sets a variable "MyVariable".
    StepA also gets assigned an arbitrary alias name, say "AliasMyVariable".
    For some reason StepA gets renamed to StepB. Since it still has the AliasMyVariable alias, references to it are still valid.
    For some reason we have to set MyVariable on StepC instead of StepA. We just remove the AliasMyVariable alias from StepA and assign it to StepC. (The use of a GUID for the step doesn't address this situation.)
    A step template has to reference MyVariable no matter where it's used. Just assign the AliasMyVariable to the appropriate step and the step template works.