I have a webpage table that can have results in 2 locations. Using some logic I've created 2 possible paths for the logic flow. Once it determines which path to take, there is a loop (Location1 Loop, and a Location2 Loop). It will always end up in one or the other successfully.
The problem I am having is that the Index key property will show up correctly and let me wire it for only one loop line. As soon as I connect the second loop, the Index disappears from the first loop. I can repeatedly disconnect and reconnect, but cannot get both to stay in the automation. This is preventing me from looping through the data to find the portion I need when the logic takes the 2nd path, since the Index will not stay.
In the attached image, I've highlighted where the Index I am trying to use needs to be located in both lines.
Oddly, we had the index working in the automation prior to making a minor update in another part of the page. The Indexing disappeared during the unrelated changes and doesn't want to come back.
Any help you can give is greatly appreciated!
***Edited by Moderator: Pooja Gadige to move from Pega Academy to Product, add platform capability tag***
@AlphrettaE have continue playing with this and was able to get the Index back on both paths by connecting BOTH the StartLoop and Yielded to the next box in the execution. Is this going to cause me problems later down the line?
@AlphrettaEIf you are using any key fittings, they will re-calculate when you connect them within the execution path. This is because they try to determine based on the execution path if they are necessary. As this re-calculation is not always desired, what I suggest is that you perform your work with the keyed controls in a separate automation. This ensures you don't disturb those fittings once you have them setup as intended.