kewakl (Customer) asked a question.
Well, this has been fixed.
If I knew that it was broken before today, I have forgotten until today when I was adding some capability to an existing machine.
I have used this procedure for years:
-build a set of sequence steps,
-copy that set of steps to a 'd*mmy build' task, <--- Hmmm, d*mmy is inappropriate, how foreward thinking.
-FIND/REPLACE to edit to the next series of steps,
-copy the edited series back to the original task,
-repeat.
It seems this feature was added in 3.6.0.45.
All these revs are broken in this manner -> [V3.7.1.6, V3.7.0.10, V3.6.1.2, V3.6.0.45]
I do see a fix in the 3.9.0.26 release notes. Win some, Lose some...😐
I'm not quite following, What feature? Is the feature the bug that it won't find/replacement array elements?
>Is the feature the bug that it won't find/replacement array elements?
@g.mccormick (Customer) You read it exactly as intended.
I don't understand how some of these bugs slip out the backdoor. Is there no regression testing around major code changes?
For the uninformed and new entry personnel: https://en.wikipedia.org/wiki/Regression_testing
"re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change."
I feel like I have complained about this since V1.5.x.x. At that time, I could make myself feel better by uttering the mantra: "It is a new platform."