Right now an extension developer can only save settings for the currently viewed item, whether that's the extension configuration page or a rule action. It'd be nice if developers could dynamically create or update data elements, rules, actions, etc. Use cases:I'm allowing multiple accounts to be added within my extension. If a user wants to disable or remove a specific account, I want to be able to update all of the rule actions and remove the account from the saved settings automatically to pr...

One of the principles behind Launch is to bundle only what you need to keep the library light and fast for the end user. While developing extensions I've made sure to keep as few items loaded and kept the settings objects as small as possible. But there are also times where I want to save settings/preferences that should not be bundled in the Launch library.The two main use cases I see here:Partially disabling a feature within an extension where we want to keep the settings for when the user wan...

Right now the minification process when building just returns if there was an error and the error itself, but no context around what code is causing it. This makes it hard to debug since there is no way to search all custom code in Launch; users instead have to go rule by rule to find the error. For example, I could have the following (valid) custom code in a rule: let myVar = "foo";return myVar; But since this is ES6, the minifier will fail, saying "There was an error minifying your custom code...

Given the number of browsers that block or don't support Flash (Firefox most recently), the number of recent 0-day exploits, and the lack of features currently enabled, I think it is time for Adobe to switch to a different method for generating graphs within the Marketing Cloud. Moving away has multiple advantages:Better cross-browser support, including browsers that don't allow Flash (e.g. mobile)Remove the requirement to reload the page just to change the graph typeEasily save or export the gr...