If you are not working with fixed length "command sentences" you won't know how many string indicators to have. Even if LabVIEW allowed you to programmatically create them (string indicators) you wouldn't be able to wire them to the connector pane to pass their values to other VI's. If you, as the earlier post mentions, place them into an array of string indicators, it can then easily be passed to the calling VI, where you can parse the commands, either by referencing a specific location in the array (i.e.:element 2 is the third word in the command sentence)or by other tools (search 1D array for instance). This technique of parsing a command string into an array and then looking a specific elements of the array is exactly what I have done in one of my recent projects to allow me to use a text "script" to determine what functions will occur and when in the execution of my program. If you use commas (,) or the TAB charecter as your delimiter it also allows you to easily read and edit the text file with a spreadsheet program, like Excel.
Placing them into a string array would also allow you to flexibly display them on the UI, as you can programmatically change how the array is displayed, or even wire the array into a table display.
Good luck,
Putnam Monroe
PutnamCertified LabVIEW Developer
Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5
LabVIEW Champion