The step that adds the sequencefile path is named “Add Sequence Name”, in the “Main” stepgroup, of the sequence “AddSequenceResultToReport”, in the sequencefile “reportgen_html.seq”. It can be found in the same folder as the default process models. Either remove the step or set its Run Mode to “Skipped”. This is the case if you are using html reporting (you should be able to find a similar step in the corresponding sequencefiles of the other two report types). Also, you must have chosen in your Report Options to use Sequence instead of DLL for the reporting.
The limits for any step should be a part of your Context container. There are many different places where they reside within that container as different properties depending on which step is currently executing. The easiest way is to change their value for their own step. Just use a pre- or post- expression to change the value of Step.Result.Limits.high (or low). If you are changing the limits of a step from another step within the same sequencefile, you might use a lookup string that looks like this: RunState.SequenceFile.Data.Seq["MainSequence"].Main["Numeric Limit Test"].Limits.Low.
I hope that you find the answers to these two questions helpful. You should have all of the information that you need to accomplish these two tasks. Take care and good luck!
Regards,
Aaron B.
National Instruments
