Skip to content

IQVIA MI Touch

You can export e-Detailers to prepare them for subsequent upload to IQVIA Mobile Intelligence.

SPA build structure

After you export an e-Detailer to the IQVIA MI Touch single-page application format, the resulting build has the following structure:

.
├─chunks/
├─common/
│  ├─blocks-library/
│  └─media/
├─export/
│  └─export.pdf
├─media/
│  └─images/
│     └─thumbnails/
│        └─thumbnail1.jpg
├─node_modules/
├─parameters/
│  └─parameters.xml
├─slides/
│  └─slide1/
│     └─media/
├─styles/
├─themes/
|─app.js
├─icon.png
├─icon@2x.png
├─index.html
└─settings.json
PathDescription
chunks/Contains bundled JavaScript chunks generated by Webpack to support lazy loading and reduce initial page load size.
common/blocks-library/Contains the public assets for each block.
common/media/Contains the common media resources used in the e-Detailer: fonts, images, PDF files, and videos. Each type of media resource is stored in its own directory.
export/Contains the export.pdf file with the exported PDF of the e-Detailer. The builder retrieves the file from the common/media/pdfs/export directory of the e-Detailer. If the directory is empty, the builder generates a blank PDF file with one page.
media/images/thumbnails/Contains the e-Detailer thumbnail.
node_modules/Contains the following media assets from the node modules for the e-Detailer: fonts, images, PDF files, and videos.
parameters/Includes the parameters.xml file with the e-Detailer structure.
slides/Contains the media files for each slide. For example, if the e-Detailer has two slides, slide1 and slide2, the directory includes two subdirectories: slide1 and slide2.
slides/slide1/media/Contains the following media assets for each slide: fonts, images, PDF files, and videos. Each type of media resource is stored in its own directory.
styles/Contains the CSS files with e-Detailer styles.
themes/Contains the media assets from the e-Detailer themes. Assets for each theme are stored in a separate directory.
app.jsThe JavaScript bundle that's created when you run the development build. This file is referenced in index.html.
icon.pngThe e-Detailer icon.
icon2x.pngHigh-resolution (2x DPI) e-Detailer icon for retina displays.
index.htmlThe HTML file that serves as an entry point for the e-Detailer.
settings.jsonThe settings.json file of the e-Detailer.

MPA build structure

After you export an e-Detailer to the IQVIA MI Touch multi-page application format, the resulting build has the following structure:

.
├─001_slide1.zip/
│  ├─assets/
│  │  ├─common/
│  │  │  ├─blocks-library/
│  │  │  └─media/
│  │  ├─node_modules/
│  │  └─slides/
│  │     └─slide1/
│  │     └─slide2/
│  ├─export/
│  │  └─export.pdf
│  └─index.html
│  ├─js/
│  ├─media/
│  │  └─images/
│  │     └─thumbnails/
│  │        └─thumbnail1.jpg
│  ├─parameters/
│  │  └─parameters.xml
├─info.json
└─package.json
PathDescription
slide1.zipAn archive with the files for each slide. For example, if the e-Detailer has two slides, slide1 and slide2, the build includes two archives: slide1.zip and slide2.zip.
slide1.zip/assetsContains the common assets, media, node_modules, JS, and CSS files for the slide.
slide1.zip/assets/common/blocks-libraryContains the public assets for each block.
slide1.zip/assets/common/mediaContains the common media resources used in the slide: fonts, images, PDF files, and videos. Each type of media resource is stored in its own directory.
slide1.zip/assets/node_modulesContains the following media assets from the node modules for the e-Detailer: fonts, images, PDF files, and videos.
slide1.zip/exportContains the export.pdf file with the exported PDF of the e-Detailer. The builder retrieves the file from the common/media/pdfs/export directory of the e-Detailer. If the directory is empty, the builder generates a blank PDF file with one page.
slide1.zip/index.htmlThe HTML file that serves as an entry point for the e-Detailer.
slide1.zip/jsContains the slide.js file with JavaScript for the slide.
slide1.zip/media/images/thumbnailsContains the slide thumbnail.
slide1.zip/parametersIncludes the parameters.xml file with the e-Detailer structure.
info.jsonContains general information about the e-Detailer.
package.jsonContains general information about the e-Detailer and contains the list of project npm dependencies.