Interface - Process Model: The 'On Success' variable is not displaying the final value of the variable

Question

Hi everyone! 
 I am facing the following issue: I have a toggle button that activates a startProcess!, which is a Process Model designed to update the dates of a list of tasks. This list can contain more than 100 tasks which should be analyzed one by one in an iterative loop in the process model. However, I have noticed that the onSuccess variable, which should be displayed in a grid is not correct . This problem might be due to exceeding the 50-node limit. I have checked the process, and everything appears to be correct including the onSucess variable. Can you advise me on any way to retrieve this variable with the correct values?

Mike Schmitt · Answer

Echoing Dan's reply - this feature isn't really meant for situations where massive chaining / looping is happening. Any chaining effect will break after the 50th flow connector, so the best approach would be to design around this in such a way that it isn't critical to get the final value passed back into your interface, if you have to perform hundreds of loops in-process. Can you share a bit more detail around your use case / what you're trying to accomplish in general, that this is required?

Dan Lluhi · Answer

It looks like those are two script tasks to update the tasks/dependents, and then an XOR to iterate through your list. Are you able to redesign this to be a single script task that uses a!forEach instead? That is generally preferred over looping in a process model when possible, and in your case will avoid hitting the node chaining limit.

Mike Schmitt · Answer

yahairat said: Just to confirm, is there any way to obtain the final variable from the process model 
 If you were able to refactor the process model to avoid that loop (i.e. do the looping internally in a script task in a single epxression rule, if possible), then you'd probably get the final PV value returned at your calling interface. 
 Can you share anything more about what's happening inside the two looping nodes? Often (though maybe not always) a loop like this can potentially be replaced with an expression rule that handles necessary looping via an a!forEach() call, etc.

Mike Schmitt · Answer

Instead of looping back over the two script tasks over and over, and each time using the "append to list" function, I posit that you could perform the looping in each script task (there would still be 2 script tasks but each of them would do all loops in one step). The only way this wouldn't work very well is if each loop relies on the reult of the previous loop somehow, which you aren't very clear about (this isn't a very common constraint).

Interface - Process Model: The 'On Success' variable is not displaying the final value of the variable

Top Replies