Appearance
PharmaTouch
You can export e-Detailers to prepare them for subsequent upload to PharmaTouch.
Build structure
The exported e-Detailer for PharmaTouch has the following build structure:
.
├─assets/
| ├─common/
| | └─media/
| | ├─fonts/
| | ├─images/
| | └─videos
| ├─node_modules/
| └─slides/
├─common/
| ├─common.css
| ├─common.js
| ├─slide.css
| ├─common.js.LICENSE.txt
| └─slide.js
├─js/
| └─slide_name.js
├─settings.json
├─slide1.html
├─slide1.jpg
├─slides.json
└─structure.json| Path | Description |
|---|---|
assets | Contains the common assets and block assets of each slide. |
assets/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. |
assets/node_modules | Contains the following media assets from the node modules of the e-Detailer: fonts, images, PDF files, and videos. |
assets/slides | Contains the following media resources used in the slide: fonts, images, PDF files, and videos. Each slide has its own directory with media assets. Each type of media resource is stored in its own directory. The structure of the media resource directories is copied from the original e-Detailer. |
common | Contains the common CSS and JS files of the e-Detailer. |
js | Contains the JavaScript files of each slide. |
settings.json | The settings.json file of the e-Detailer. |
slide1.html | The HTML file of each slide. |
slide1.jpg | The thumbnail of each slide. |
slides.json | The JSON file with the e-Detailer structure mapped for PharmaTouch. |
structure.json | The structure.json file of the e-Detailer. |
Slide display order
In the PharmaTouch CLM, you can add an alternative slide display order. Use the mapname field in the structure.json file to specify which slides must appear in the specified display order. When you export your e-Detailer for the PharmaTouch target system, the eWizard.js builder adds the slides.json file to the build.
For example, to add the alternative slide display order named Alternative scenario:
In the
structure.jsonfile, add themapnamefield to the slides you want to display in theAlternative scenario.json// ./structure.json { "slides": { "slider1": { "name": "Interactive input", "template": "slides/slider1/index.vue" }, "slider2": { "name": "Interactive input. Correlation", "template": "slides/slider2/index.vue", "mapname": "Alternative scenario" }, "roundSlider1": { "name": "Curve Chart Template", "template": "slides/roundSlider1/index.vue" } } }Zip the e-Detailer project.
shwiz archiveUpload the zipped project to the eWizard Library.
Export the project for the PharmaTouch target system.
Download the exported zipped project and unzip it.
Open the
./slides.jsonfile.json// ./slides.json { "slides": [ { "mapname": "All slides", "name": "Interactive input", "filename": "slider1.html", "preview": "slider1.jpg", "ishidden": 0, "position": 1 }, { "mapname": "Alternative scenario", "name": "Interactive input. Correlation", "filename": "slider2.html", "preview": "slider2.jpg", "ishidden": 0, "position": 2 }, { "mapname": "All slides", "name": "Curve Chart Template", "filename": "roundSlider1.html", "preview": "roundSlider1.jpg", "ishidden": 0, "position": 3 } ] }The PharmaTouch CLM displays the slide with the
mapnamefield in theAlternative scenariodisplay order while other slides have the defaultAll slidesdisplay order.