I work around this by writing a "Custom Code" Data element, and use that
data element as a condition. This creates a condition that can be
reused. But yes, I think a "Conditions" feature could be nice so
Conditions could be written in a simpler way.
Hi Thomas, The base Adobe Launch Library script can be formatted, but
the custom rules applied to the page can't be. See this exampleNotice
that even formatted, the code is inside a JSONSo I found a manual way to
work on each file.I used the new overrides feature in Chrome and add //#
sourceURL=rule1.js to the end of the stringAnd now you can see the
script as a file in the debuggerIf Adobe Launch could add the option to
add these to Dev builds, that would be so awesome! //#
One challenge I have found with Adobe Launch is debugging custom rules.
The custom code in Adobe Launch is put into JSON strings and evaluated
resulting in the code not being available in Developer Tools for
debugging.I found a feature in Chrome Dev Tools that allows a local
override and a “SourceURL” to be set.If I modify the script file by
adding something like this to the end. “//#
sourceURL=someUniqueName.js”Then I can find “someUniqueName.js” in
sources and browse the code and set breakpoin...