Not as far as I'm aware, but if the getUX() call you're interested in will always be the first one in the purepath when the saveScreen() method is also in the purepath:
1) Set up your getUX return value measure to only evaluate on the first occurrence in the purepath (look for the "Only analyze first method occurrence per PurePath" checkbox).
2) Create a measure method invocation measure which tracks the saveScreen() method call.
3) Create a BT with two filters: The saveScreen method invocation AND the return value capture of the getUX method.
This BT will only produce data for purepaths containing saveScreen and getUX and it will only pull the return value for the first getUX call in the purepath.
Does that help??
Hi Adam! That's what I though also at first, but it is not useful in this situation. The solution is great, but the scenario is too unpredictable. Sometimes is not the first, and sometimes saveScreen() is not even in the PurePath.
The main problem is that the application design is not optimal in this case.
There is no way of doing this out of the box if it isn't the first or last method call each time. You could do it with a custom plugin if you really need it. Just poll the purepath details and go from there. It would take a few hours to create and test though and depending on the number of purepaths and their size it might be a burden on the server.