Zebra Datawedge Intent configuration
You could also export the config (Will be named as datawedge.db as default) and copy this to the othe devices.
Then a script has to be run (We use Android 7/8 TC51, so could be different for you):
copy /sdcard/Android/data/com.symbol.datawedge/files/datawedge.db /enterprise/device/settings/datawedge/autoimport/datawedge.db
execute_shell chmod 777 /enterprise/device/settings/datawedge/autoimport/datawedge.db
Generally speaking, it is recommended that you create a new DataWedge Profile and associate it to your particular application. You can then modify that specific profile with the Intent output configuration so that DataWedge activates that configuration while your app is in the foreground. If you modify the Profile0 profile then you could potentially impact the default scanner behavior across the rest of the device.
Once you have a working DataWedge configuration on a sample device you can export either the Profile or the entire DataWedge config into a .db file and then can distribute that as a Package or File Sync Rule to the devices. More specific instructions are available below:
Here is an article covering the process that you need to follow:
DataWedge does technically support configuration Intent "APIs" so you could theorhetically build something with SOTI scripting instead of using the .db export and deploy concept but I honestly have never heard of any one taking that approach. The DataWedge config APIs are more for individual apps to be able to configure DataWedge on the fly rather than leveraging the EMDK for scanning integration.