Our apps produce completions data which is scattered across multiple completion records to capture different states along a single process that can otherwise not properly be captured. Aka the “Save all app data” issue.
We know look for ways to make sense of this completions data that spans multiple completions to document a single process run…
The app process in question is not a simple one step after the other. In the middle of the process, a step loop occurs which is repeated until all items are processed.
In order to capture this the “Save all data” trigger is used. With this in place, each stored app completion captures a snapshot of one particular state in the loop… So the completions log looks something similar to this:
@sebme Thank you for the details here - If I am understanding, (and correct me if I’m wrong) - you are asking to be able to filter an analysis based on an aggregation as a workaround for the fact that your completions data includes saved app data from an iterative loop in the middle of the process?
Would it be possible to instead of step looping and saving data each loop, to have a separate step for each fill instead? That time spent on each step will be captured automatically.
I do not believe it is possible to filter an analysis based on an aggregation, but will probe the Tulip team further to confirm.
That’s in fact what is happening already… based on observed machine state changes, the app loops through the steps… but there is more data to be saved than just the cycle time…