AnsweredAssumed Answered

Behavior of Export Variables from Fragment Assertion

Question asked by StefanKlotz on Feb 15, 2019
Latest reply on Mar 18, 2019 by StefanKlotz

Hi all,

we put some of our functions into fragments to use them easier in different policies and to be more flexible in case of updates are required (then only the fragment needs to be updated and it will inherit into all involved policies). But some of these fragments are using variables, which will be used later in the policy (outside of this fragment) or maybe in another fragment, which will be executed at a later stage. As of now we are NOT using the "Export Variables from Fragment"-Assertion and everything is working fine.

But how does this maybe affect overall performance? In that regards, what's the technical difference between using this assertion or not? CA documentation does not really say much about it. It mentions the words "For maximum performance", but doesn't explain what happend when not using it.

And what about the other way round, means we define variables in the policy itself, which will then later be used within an included fragment. I assume this direction is not critical, isn't it?

Who can provide some more technical details about this behavior and how this maybe Impacts overall Gateway performance.

Thank you!


Ciao Stefan