NI TestStand Idea Exchange

Problem description:

The parameters out of the step settings window and the called subsequence are not linked. If you delete any parameter out of the middle of the parameter list and the calling sequence use the "default" flag for this parameter(s), this default flag(s) will be shifted to the next parameter in the list and the original value will be overwritten. To reproduce this issue:

1. Create a test sequence
2. Create a subsequence and add six parameters (type does not matter)
3. Insert "Sequence call" in the Mainsequence and configure it to the previous created subsequence
4. In the "StepSettings" window configure the parameters of the called sequence. Parameter 1+2 with any value. Parameter 3+4 with default checkbox. Parameter 5+6 with any value
5. Save your work
6. Open the subsequence and delete the parameter 3+4 (these two that are configured with "default" in the calling sequence")
7. Go back to the MainSequence and click on the sequence call of the subsequence (reload option is visible in the step settings window)
8. click on the blinking red reload button

You can see that the name of parameters you have deleted in the subsequence disappear, but the "default" flag(s) are shifted to the parameters 5+6 and the previous configured values were overwritten. If you delete any parameter that is configured without the default flag the deletion works fine. 

Problem: If you want to delete a parameter that is used in many subsequences by searching for it and delete it directly out of searchResult window, you cannot guarantee that your sequence is running without any problems

Idea: Add a "checkup function" on the "reload" module in the stepSettings menu that all parameters are checked by name and value before any values will be overwritten. This checkup has to be done on each change of the called subsequence

Within the Teststand workspace it would be reall useful if the "Code Modules" under the sequence could auto-populate and also if it could display the filepath of the code module. That would make it much easier to keep track of what code a sequence is calling and where from on disk.