@craig_rouse I think our replies may have crossed paths. Good to know we were on the same path here as you outlined. As I mentioned, the biggest reason we don't like this is that code now has to be maintained by our team in extensions (generally), and now we have this one-off tag where all the code is maintained in the tag template. Just not very clean when we have a team of 10 maintaining various implementations. A work-around that seems to do the job, but not one we feel is scalable across the enterprise. Here's our flow, I'd love to hear your feedback on our approach: Pre-Loader extension sets the window.utag_cfg_ovrd = {noview:true}; Same extension does some page setup related things, then calls utag.view(utag_data, [1]); where 1 = our tag with the global functions in the tag template. Setups custom event listener. At the end of our code in the tag template, we dispatch a custom event. Custom event listener in the pre-loader fires calling utag.view(utag_data); resuming the load of the rest of our tags.
... View more
Expand/CollapseMenu
