I have a HTML page which has a table in it. I need to read the table data and process it. When I spied the HTML table, blue prism is not identifying it as a table element but is identifying as a HTML Element. so when I used get table action to get the table data, I am not getting the table data in rows in collection but am getting entire data as a single row which I cannot process.
To resolve the issue, I got the HTML path of first row and used a counter in the logic to increment the HTML tag which would read each row data sequentially. At the end of table, when I try to read the next element, since the logic reached end of the table, I will get a time out at which point, I know that I read all the data in the table. Once I get the timeout, I will process the read data.
This logic is working fine but I am trying to see if there is a better way to achieve this solution instead of depending on the timeout, the reason being, timeout is causing the overall bot execution time to increase. Currently, when I run the bot in debug mode, the timeout action is taking about 8 seconds to timeout. I am not sure if the bot would take the same time when executed from control room, but either way, if I can identify the end of table without timing out, it would speed up the bots execution time.
Attached the screenshots of table source and blueprism logic. Appreciate any thoughts on this.