Question
Hong Kong Exchanges and Clearing Limited
HK
Last activity: 15 Apr 2025 6:39 EDT
JUMP condition on the Activity Loop (embedded page)
I refer to JUMP conditions with PAGE LOOP | Support Center
And we tested in v23, if we have a loop on an embedded page (say 10 items in this page) AND added a JUMP condition on the Loop step that it will always Jump to another Log Step
When running, the step only does once and then Jumps right after. We expected it should finish all 10 items then Jump.
Is this an issue or as designed?
Accepted Solution
Updated: 15 Apr 2025 6:39 EDT
HCA Healthcare
US
@Jeremie When you add a JUMP condition directly on the Loop step in an activity, Pega processes it only once and then jumps, without finishing the full loop. This means it does not iterate through all items in the embedded page as expected. Instead, as soon as the JUMP condition is true, it exits the loop and jumps to the step you mentioned. This behavior is as designed in Pega. If you want to loop through all 10 items and then perform a jump after the loop, you should move the JUMP condition outside the loop step or use a separate condition after the loop ends.
Hong Kong Exchanges and Clearing Limited
HK
@SohamM95Yes. on the Jump on the loop step. we analyzed the "View Java" and it seems it's a while loop. I can see now that the Precondition on the Loop step is better handler than the Jump.
Accepted Solution
Updated: 15 Apr 2025 6:39 EDT
HCA Healthcare
US
@Jeremie When you add a JUMP condition directly on the Loop step in an activity, Pega processes it only once and then jumps, without finishing the full loop. This means it does not iterate through all items in the embedded page as expected. Instead, as soon as the JUMP condition is true, it exits the loop and jumps to the step you mentioned. This behavior is as designed in Pega. If you want to loop through all 10 items and then perform a jump after the loop, you should move the JUMP condition outside the loop step or use a separate condition after the loop ends.
Hong Kong Exchanges and Clearing Limited
HK
@Sairohith yes, we have done this as we have discouraged the Jump on iterations due to "previous incidents", however I saw someone do it and I now am worried. From your comment, these "previous incidents" are actually the behavior of Pega as designed. Thank you all for confirming.