Dynamic code in the audience/triggering conditions

During evaluation of the audience/triggering conditions code defining Alias functions, Custom values is added dynamically to the evaluator.

If enabled in settings, values fetched from Bank Admin could be cached on Triggering Engine site.

 "Caching": {
    "AliasFunctions": true,
    "CustomValues" :  true 
  }

caution

AliasFunctions are currently defined through direct database modifications. Hence if caching is enabled any changes applied to Alias functions require Triggering Engine nodes restart to be resembled in the evaluation process.

Custom Values are modified through user interactions and Triggering Engine will be notified on any modification requiring Custom Values cache invalidation.