Can we break out of if-else conditions and will tagui step works with repositories or datatables?

[kensoh]

Raising this from an user email for sharing, as other users might benefit from this question.

---

An additional query – we noticed that when scripting in TagUI and where we have multiple if-else conditions, we are unable to skip/break those codes which are not applicable based on the business process flow (e.g. if a file exists, we want to move directly to step 15 instead of going through to step 2 to 14) – is there a specific command in TagUI that we can use to get out of certain if-else condition?

We also understand that we can code the functions by blocks (i.e. calling script within script – your Github issue #80 refers) so would you say this functionality can help (to a certain extent) with the above issue? But we also note that the object repository functionality in sub-scripts is disabled so if we start grouping the codes based on certain functions, they may not work as intended?

[kensoh]

You can't break out of an if statement, but you can try something like this -

if condition 
{
step 2
...
step 14
}

step 15...

or if you call sub-scripts using tagui step -

if condition
{
tagui crm_app.login
}

step 15..

What tagui step does is simply retrieve the contents of the sub-script crm_app.login (or some other filename) and insert the steps in that sub-subscript into the tagui step location where it is used. So the repository definitions or datatable definitions should still work just like in the rest of the automation flow.

Also within a sub-script you can call other sub-scripts to go really deep into the modularization. But I generally don't recommend going too deep, because it can backfire and become harder to maintain or troubleshoot (you gotta open multiple files just to get an idea of the complete automation flow).