Hi Gracie - not sure where to start here, but will have a go. A few things stand out:
One technique you might consider for steering the logic flow according the environment is to use the GetConnection() function
- a bot that was developed in Test - why was this allowed to happen?
- all three environments have different screen resolutions - you should make every effort to align your environments. Wrestling with environmental differences is a thankless task and one that will limit your RPA growth.
- the Oracle environments are laid out slightly different between Dev, Test, and Prod - as above, you should have the same version in all environments, otherwise you have to build, test and maintain workarounds.
One technique you might consider for steering the logic flow according the environment is to use the GetConnection() function
Hi Gracie - hmm I feel your pain, sounds like an awkward situation. Ideally your line manager should try to find RPA advice from BP and/or a BP partner, and perhaps start by asking whoever sold you the BP licenses. In simple terms, setting up a solid and scalable RPA shop is not just about learning the tool, there is a whole range of topics to address.
But to your specific problem: the loop stage is the mechanism to iterate through a collection, and typically developers keep track of which row is current by incrementing a count or index value. Below you can see how the Row Counter data item is increased by 1 on each iteration of the loop. Then the process checks the value of the counter to decide whether it is working on the first row of the collection or not. So in the example below, the flow will go down the Yes path once and the No path 8 times. But if the collection had only 1 row, then the logic would go down the Yes path only. If the collection had zero rows, then the logic would straight from Loo Start1 to Loop End1, missing out the 'innards' of the loop completely. And if the flow somehow executed the whole loop again, then you'd need to be sure that Row Counter was set back to zero and not left with the previous value (which in the example below would be 9). I hope this helps.
But to your specific problem: the loop stage is the mechanism to iterate through a collection, and typically developers keep track of which row is current by incrementing a count or index value. Below you can see how the Row Counter data item is increased by 1 on each iteration of the loop. Then the process checks the value of the counter to decide whether it is working on the first row of the collection or not. So in the example below, the flow will go down the Yes path once and the No path 8 times. But if the collection had only 1 row, then the logic would go down the Yes path only. If the collection had zero rows, then the logic would straight from Loo Start1 to Loop End1, missing out the 'innards' of the loop completely. And if the flow somehow executed the whole loop again, then you'd need to be sure that Row Counter was set back to zero and not left with the previous value (which in the example below would be 9). I hope this helps.
