Appearance
IQVIA OCE
You can export e-Detailers to prepare them for subsequent upload to IQVIA OCE.
Build structure
After you export an e-Detailer to the IQVIA OCE multi-sequence format, the resulting build has the following structure:
.
├─001_slide1.zip/
| └─assets/
| | ├─common/
| | | ├─blocks-library/
| | | └─media/
| | ├─node_modules/
| | ├─slides/
| | | └─slide1/
| | | └─slide2/
| | └─themes/
| ├─chunks/
| ├─js/
| ├─styles/
| └─01_index.html
| ├─01_thumbnail.jpg| Path | Description |
|---|---|
001_slide1.zip | An archive with the files for each slide. The number at the beginning of the archive name determines the slide order in OCE. For example, if the e-Detailer has two slides, home and slide1, the build includes two archives: 000_home.zip and 001_slide1.zip. |
001_slide1.zip/assets | Contains the common assets and block assets for each slide. |
001_slide1.zip/assets.common/blocks-library | Contains the public assets for each block. |
001_slide1.zip/assets/common/media | Contains 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. |
001_slide1.zip/assets/node_modules | Contains the following media assets from the node modules for the e-Detailer: fonts, images, PDF files, and videos. |
001_slide1.zip/assets/slides | Contains the files for the slide. |
001_slide1.zip/assets/slides.slide1/media | Contains the media assets for the slide: fonts, images, PDF files, and videos. Each type of media resource is stored in its own directory. |
001_slide1.zip/assets/themes | Contains the media assets from the e-Detailer themes. Each theme is stored in a separate directory. |
001_slide1.zip/chunks | Contains the JS files with data chunks for the slide. |
001_slide1.zip/js | Contains the JS files with JavaScript for the slide. |
001_slide1.zip/styles | Contains the CSS files with styles for the slide. |
001_slide1.zip/01_index.html | The slide HTML file. |
001_slide1.zip/01_thumbnail.jpg | The slide thumbnail. |
Single-sequence build structure
After you export an e-Detailer to the IQVIA OCE single-sequence format, the resulting build has the following structure:
.
├─assets/
| ├─common/
| | ├─blocks-library/
| | └─media/
| ├─node_modules/
| ├─slides/
| | ├─slide1/
| | └─media/
| | └─slide2/
| └─themes/
├─common/
├─js/
├─01_thumbnail.jpg
└─01_slide1.html| Path | Description |
|---|---|
assets | Contains the common assets and block assets for each slide. |
assets/common/blocks-library | Contains the public assets for each block. |
assets/common/media | Contains 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. |
assets/node_modules | Contains the following media assets from the node modules for the e-Detailer: fonts, images, PDF files, and videos. |
assets/slides | Contains the files for each slide. For example, if the e-Detailer has two slides, slide1 and slide2, the directory includes two subdirectories: slide1 and slide2. |
assets/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. |
assets/themes | Contains the media assets from the e-Detailer themes. Each theme is stored in a separate directory. |
common | Contains the common CSS and JS files for all slides. |
js | Contains the JS files with JavaScript for each slide. Each JS file is named according to the slides' chapter ID and slide ID. For example, if slide1 belongs to chapter1, the filename is 01_chapter1_slide1.js. |
01_slide1.html | The slide HTML file. The build includes HTML files for each slide. Each HTML file is named according to the slides chapter ID and slide ID. For example, if slide1 belongs to chapter1, the filename is 01_chapter1_slide1.html. |
01_thumbnail.jpg | The slide thumbnail. The build includes thumbnails for each slide. Each thumbnail file is named according to the slides' number. For example, the first slide filename is 01_thubmnail.jpg. |
SPA build structure
After you export an e-Detailer to IQVIA OCE single-page application format, the resulting build has the following structure:
.
├─chunks/
├─common/
├─node_modules/
├─slides/
| └─slide1/
| └─media/
├─styles/
├─themes/
├─01_index.html
├─01_thumbnail.jpg
├─app.js
└─settings.json| Path | Description |
|---|---|
chunks/ | Contains bundled JavaScript chunks generated by Webpack to support lazy loading and reduce initial page load size. |
common/ | Contains the common CSS and JS files for all slides. |
node_modules/ | Contains the following media assets from the node modules for the e-Detailer: fonts, images, PDF files, and videos. |
slides/ | Contains the files for each slide. For example, if the e-Detailer has two slides, slide1 and slide2, the directory includes two subdirectories: slide1 and slide2. |
styles/ | Contains the CSS files with styles for the slide. |
themes/ | Contains the media assets from the e-Detailer themes. Each theme is stored in a separate directory. |
01_index.html | The HTML file that serves as an entry point for the e-Detailer. |
01_thumbnail.jpg | The e-Detailer thumbnail. |
app.js | The JavaScript bundle that's called when you run the development build. This file is referenced in index.html. |
settings.json | The settings.json file of the e-Detailer. |