The JSON-controlled Remote Commands feature requires a JSON file for each Remote Command, in place of a TiQ tag. Previously, a Remote Command tag needed to be configured in TiQ in order to use a Remote Command, but now there is the choice to use a JSON file instead. This does away with the need for TiQ/webview, which may improve the overall performance and memory footprint of the app.
Currently, there is no UI support for JSON-controlled Remote Commands, so the JSON files must be built manually. To make this process easier, and to make it simpler for existing users of Remote Commands to migrate, the mobile team has built a Tealium Tool that can export the config of existing Remote Command tags.
Add a new custom tool, and enter this URL in the "Add By URL" field: https://solutions.tealium.net/hosted/tealiumTools/remotecommands_exporter/tool.json
Navigate to the profile in TiQ containing the existing Remote Command tags. Once loaded, open the tool, and press the "Export Remote Commands" button. A JSON file will be generated and automatically downloaded for each Remote Command tag discovered in the profile.
If configuring Remote Commands for the first time and you don't currently have any TiQ-based Remote Commands, the tool may still be used as a convenient way to generate the JSON files for the Remote Commands you wish to use. Simply add the tags to use in TiQ, configure the mappings as usual, and then run the export tool. The tags don't need to be published.
The mobile team will endeavor to keep the tool updated, but there may occasionally be delays where the marketplace tags are updated before the tool is updated. Please reach out to Tealium Support if you need an urgent update.