eWizard.js framework v4.2.0

New framework features

Actions

Now eWizard.js supports actions! Actions are used to execute common predefined functionality when user performs an action on a slide, e.g., clicks a button to open a link. Actions are implemented as custom directives and registered globally by the framework. So you can use them on the slide without additional imports.

The list of available actions:

• v-goto navigates user to another slide;

Example:

<template>
    <wiz-button v-goto:tap="navOptions"></wiz-button>
</template>
<script>
export default {
 data() {
    return {
      navOptions:{
        slide: 'Home',
        chapter: 'Main',
        animation: false,
      }
    }
  }
}
</script>

The code above configures goto action at wiz-button on tap event. When user tap on button it will be navigated to Home slide without animation of slide transition.

• v-open opens a PDF file or the URL link.

Example:

<template>
    <wiz-button v-open.pdf="amazingPdf"></wiz-button>
</template>
<script>

import amazingPdf from './media/pdfs/amazingPdfFile.pdf';
export default {
 data() {
    return {
      amazingPdf,
    }
  }
}
</script>

This code snippet shows how to use v-open action to open a PDF file. When user click on the wiz-button, the PDF file will be opened.

See the full documentation of actions with examples and explanations here.

Localization

The new Common Localization feature is added. If you want some text to be present on every slide, there is no need to copy text to <i18n> tag on every slide. You just need to create .json file in common/i18n directory and then use appropriate keypath on a slide.

Note: object with localized texts should be named the same as .json file with localization.

Here is the example:

common/i18n/localization.json file:

{
    "eng": {
        "common_text1": "String of text from common localization"
    }
}

slides/slide1/index.vue file:

    <div class="row">
      <wiz-text :text="$t('localization.common_text1')"></wiz-text>
    </div>

The detailed localization feature documentation will be added to the documentation site soon.

Navigator

Now Navigator is improved by the presentation option added to the goTo method. So that now you can define the navigation between two presentations:

gotoPresentation(){
  this.$navigator.goto({
    slide:'cobalt', // Slide ID
    presentation:'default_presentation' // Salesforce Presentation ID
  });
}

This functionality is available only in Veeva CRM. More documentation can be found here.

eWizard-cli v0.5.1

• The new wiz expand blocks command is introduced. It allows expanding block's source code and localization directly into ET markup.

• The wiz-archive command is improved. It archives only presentation's source files, ignoring the build directory.

• New content types are added for initializing (block and module).

Builders enhancements

Added prerendering feature for oce-mpa build. Previously rendering was done in runtime by JS code. The presentation had been awaiting for browser to download all additional files to render the slide. After implementation of prerendering functionality, it allowed to prepare slide files for the first rendering. As a result, it will much speed up the first slide rendering. After that, all additional scripts will be loaded to actualize slide state if required.

A new build strategy was implemented in iselling-mpa-builder. Now it supports exporting of presentation based on actual version of eWizardjs (v4.2.0).

Under-the-hood improvements

• The possibility to build modules for dev builder is added. This functionality is supposed to dynamically add modules to the template in eWizard editor.

• The localization for information massages in eWizard editor is added.