The explanation of what I did was already listed above. That was the actual code. The 'actual' behavorior was also listed; but I will attempt to make clearer. The 'expected' behavior is for one action to go through the datatable row by row, THEN go on to the next action AFTER the first has completed entirely. Is there something I need to change somewhere in the properties or something perhaps?
Accodinging to the code above THIS IS the Actual:
The program comes to the 'Browser("Login").Page("My company").Link("Images")' screen
Inputs rowA from the global datatableA
Browser("Login").Page("My company").Link("Images").Click
Results are seen from that input-Browser("Login").Page("My company_4").Check CheckPoint("My company_8")
Next, a button appears on that screen to perform another lookup to use a new number (I would expect Row two from the datatable)
Browser("Login").Page("My company_4").WebButton("Back to Imaging").Click
INSTEAD, of performing the NEXT ROW in the datatable and completly ALL entries of that datatable...'Action2' is begun, steps completed in 'Action2' and then returned to 'Action1' row two of the datatable and so on.
Accodinging to the code above THIS IS the Actual:
The program comes to the 'Browser("Login").Page("My company").Link("Images")' screen
Inputs rowA from the global datatableA
Browser("Login").Page("My company").Link("Images").Click
Results are seen from that input-Browser("Login").Page("My company_4").Check CheckPoint("My company_8")
Next, a button appears on that screen to perform another lookup to use a new number (I would expect Row two from the datatable)
Browser("Login").Page("My company_4").WebButton("Back to Imaging").Click
INSTEAD, of performing the NEXT ROW in the datatable and completly ALL entries of that datatable...'Action2' is begun, steps completed in 'Action2' and then returned to 'Action1' row two of the datatable and so on.