Your newly generated data action development environment contains these folders and files:

1    %PLUGIN_DEV_DIR%\src\customdataaction
2       company-mydataaction\
3          extensions\
4             oracle.bi.tech.plugin.dataaction\
5                company.mydataaction.json
6          nls\
7             root\
8                messages.js
9             messages.js
10          mydataaction.js
11          mydataactionstyles.css
12          plugin.xml

• Line 2: The company-mydataaction folder is the ID that you specify.
• Line 6: The nls folder contains the files for externalizing strings that enable your extension to provide Native Language Support.
• Line 7: The strings in the files under the nls\root folder are the default strings used when translations for a requested language aren't available.
• Line 8: The messages.js file contains externalized strings for your extension that you can add.
• Line 9: The messages.js file must contain an entry that you add for each additional language that you want to provide localized strings for. You must add a corresponding folder under the nls folder for each locale that you want to add translations for. Each folder must contain the same set of files, with the same file names as those added under the nls\root folder.
• Line 10: The mydataaction.js file is the newly generated JavaScript module template that provides a starting point to develop your custom data action.
• Line 11: The mydataactionstyles.css file can contain any CSS styles that you want to add, and which your data action's user interface can use.
• Line 12: The plugin.xml file registers your extension and its files with Oracle Analytics.