Service Apps - Oxygen - Release Notes


Note: This is a version release document.
  • Some of the screenshots may show a slight difference compared to the release version as we are constantly seeking to improve the design and usability up until the release date.
  • The pages on the wiki detailing these differences will be updated soon. For more up-to-date information, please consult: Open url.png Wiki News

Oxygen version 2.1

ReleaseNotes

What's new in templates

Web content accessibility

Web content accessibility guidelines have now been applied to Service Apps.

These guidelines aim at making Web content more usable to users in general, and making it more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations.

To apply these guidelines, several elements have been added to templates.

  • Contrast management: revamping of the colors for different page elements, buttons, popups, etc.
  • Organization of information using headings and sub-headings, etc.
  • Addition of alternative text for images when they cannot be viewed.

Modifiable fonts and colors

You can now easily modify background colors as well as font colors and sizes for all template elements using the dedicated __ROOT widget. The modifications you make can then be applied in one go, using variables, to all of the widgets in the template.

Operating principle

  • A new widget called __ROOT is now available in each template. Note: You can only modify its properties using the Properties Inspector. It cannot be moved to the Design pane.
             Widget Root - properties.png
  • You can easily modify the widget contents in the HTML editor. All of the graphic elements in the template relating to font color, font size and background color are defined within <style> tags.

example  You can modify two properties for the level 3 element:

  • Background color: ezv-background-element-3
  • Font color: ezv-font-color-element-3

Widget Root - html editor.png

  • Each widget in the template can call a property from the __ROOT widget using a variable.

example  You define the background color of the theme using the var(--ezv-background-element-3) variable.

Widget Root - variable.png

What's new in the core

PHP 7.3 supported

  • PHP 7.3 is now supported.
  • PHP 7.2 is still supported.

Improved trusted provider: profile management

You can now use the trusted provider, when required, to define the Service Apps profile of the logged-in user when you implement the PHP function called apps_trusted_provider_profile.

         Open url.png To find out more about the technical details, see the sample files shipped with the trusted provider.

Improved trusted provider: authentication

In the event of a connection error, an error message can now be returned when you implement the PHP function called apps_trusted_provider_getErrorMessage.

         Open url.png To find out more about the technical details, see the sample files shipped with the trusted provider.

Integration of user language in Service Apps

The language of the logged-in user is now accessible via the userLanguage property of the EVServiceApps JavaScript object.

Administration of team management

Teams are sorted in alphabetical order when displayed in the grid.

You can also search for a team.

Web content accessibility

Web content accessibility guidelines have now been applied to Service Apps.

These guidelines aim at making Web content more usable to users in general, and making it more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations.

Overall accessibility

Mandatory elements

  • The logged-in user's language is displayed on the page.
  • The reading order direction is visible: from left to right or from right to left.
  • The page title is displayed in the tab. This corresponds to the name of the page in Service Apps.

Contrast ratio in Service Apps

  • Default colors in Service Apps have been reviewed to meet WCAG level AA requirements.
    • Validate and Cancel buttons in popup windows.
    • Titles of popup windows.
    • Notification windows for ticket creation.

Keyboard navigation

  • Keyboard navigation is possible using the Pagelink and Pagepopup links.
  • A Title attribute is used to warn users when a popup is open.
  • The focus is visible for buttons used to open and close windows.

EZV buttons

  • Keyboard navigation is possible for EZV buttons, e.g. New Ticket, New Request, etc.

Accessibility to widgets

Search Filter

  • Addition of alternative text for the data entry field.
  • Addition of alternative text for the Validate button or for the magnifying glass icon in the search.
  • The focus is visible for the magnifying glass icon.
  • The focus is visible for the cross icon in the search.

Tab

  • Keyboard navigation is possible in tabs using the <Tabulation> key.

Filter list

  • Keyboard navigation is possible for all modes (Horizontal, Vertical, List).

Logout

  • Keyboard navigation is possible for all elements, including in the widget popup window.
  • The focus is visible for all elements.

Discussion

  • Keyboard navigation is possible for all elements.
  • The focus is visible for all elements.

Menu

  • You can press <Alt> to access all Menu widget icons.
  • Keyboard navigation is possible for all menu links.

Link between Service Apps and Service Manager

A new functionality enables you to switch from one Service Apps app embedded in Service Manager to a Service Manager screen via an icon or text link.

         part 1_html_686d6cc8.png

Operating principle

From the app embedded in Service Manager, data is retrieved by a widget pointing to an EasyVista data source.

  • You configure the link between Service Apps and Service Manager using the Display evSE Link property in the Header section of the widget. By default, the property is disabled.

         part 1_html_6d4da19.png

  • When the property is enabled, the part 1_html_142a66f6.png icon will appear on the Service Manager screen.

         part 1_html_3b5ff7a8.png

  • You configure the link in the Service Apps app using the Evse Link property of the widget that displays data. part 1_html_1b616220.png enables you to access the HTML editor to configure it.

         part 1_html_m671adf75.png

Note

  • The link is possible only for widgets with an EasyVista data source.
  • You can display the details of the link only for users with the appropriate display rights.
  • The Evse Link property is taken into account only if the Header > Display property is selected.

New widgets

Embedded Page widget

part 2_html_m79d01e08.png This new widget belongs to the Basic category in the widget library. It enables an app page, i.e. the parent page, to call another page in the same app, i.e. the child page. The child page will be displayed within the parent page. The aim is to group sets of child pages called directly in parent pages in order to restrict the number of duplicate elements.

Benefits

  • Using the Embedded Page widget enables you to restrict the number of elements that are recurrently created in app pages and reduce the number of pages to be maintained.
  • This helps improve performance.

Operating principle

         part 2_html_5adc9a0b.png

(1) A, B and C are three pages created in an app.

(2) Page B is made up of two child pages, A and C.

(3) Page A is made up of two child pages, D and C.

(4) Page A (with child pages D and C) is called by parent page B. It will thus become the child page of page B.

Rules

  • A parent page can be the child page of another page.

example  Page A is the parent page of pages C and D and is the child page of page B.

  • A page can be the child page of several parent pages. This facilitates the maintenance of pages.

example  Page C is a page footer. It is the child page of pages A and B.

  • Although a given child page may be called several times in a page, it will only be loaded once.

example  Page C is embedded in parent page A and called directly in page B. It will only be loaded once.

 

Note: To improve performance, child pages are not visible in the graphic editor. They are visible only in execute mode.

example

  • In the graphic editor, the child page is not visible.

         part 2_html_31e40d4b.png

  • In execute mode, the child page is displayed at the top of the app.

         part 2_html_m760a53ac.png

Widget properties

         part 2_html_m3e3fab49.png

Content: Child page to be displayed in the current page. The part 2_html_m101d0509.png icon is used to switch directly to the child page in edit mode.

Theme: Theme applied to the Embedded Page widget. The child page has its own theme.

Note

  • Properties in the Theme section are identical to those in other widgets. The Embedded Page widget does not have any specific properties.
  • The entire child page is selected. You cannot select a specific zone in it.
  • Parent pages and child pages cannot call themselves.

Sidebar widget

part 2_html_m33385fa8.png This new widget belongs to the Basic category in the widget library. It enables an app page, i.e. the parent page, to call another page in the same app, i.e. the child page. The child page will be displayed in a horizontal or vertical pane.

Benefits

  • Using the Sidebar widget enables you to restrict the number of elements that are recurrently created in app pages and reduce the number of pages to be maintained.
  • This helps improve performance.

Operating principle

         part 2_html_mb9f9340.png

(1) Page B is the current page in which a button for calling page A is located.

When users click the button, child page A will appear in the current page B. The child page will be called indirectly and will not be anchored in the parent page.

  • (2) Display in a horizontal pane.
  • (3) Display in a vertical pane.

         part 2_html_m5118f51c.png

Note: To improve performance, child pages are not visible in the graphic editor. They are visible only in execute mode.

Widget properties

         part 2_html_1259cdf5.png

Content: Used to configure the child page.

  • Page: Child page called by the current page. The part 2_html_m101d0509.png icon is used to switch directly to the child page in edit mode.
  • Direction: Direction and opening of the pane, i.e. horizontal, from left to right or from right to left, or vertical, from top to bottom or from bottom to top.
  • Open Button: Text button or icon button for opening the pane. part 2_html_1b616220.png enables you to access the HTML editor to configure it.
  • Close Button: Text button or icon button for closing the pane.   part 2_html_1b616220.png enables you to access the HTML editor to configure it.
  • Width: Size of the pane displaying the child page, in pixels or as a percentage.
  • Active Shadow: Used to indicate if a background color is applied to the parent page to highlight the child page. You can select the color and its opacity.

Theme: Theme applied to the Sidebar widget.

Note

  • Properties in the Theme section are identical to those in other widgets. The Sidebar widget does not have any specific properties.
  • The entire child page is selected. You cannot select a specific zone in it.
  • Parent pages and child pages cannot call themselves.

New page property: Page Header

This new property is used to call a child page and anchor it at the top of the current parent page in the foreground.

  • The property is available in the global properties of each page.
  • A new child page can replace the current child page when users scroll down using the mouse.

Benefits

  • The Page Header property is used to display elements in a fixed position.
  • Using the Page Header property enables you to restrict the number of elements that are recurrently created in app pages and reduce the number of pages to be maintained.
  • This helps improve performance.

Operating principle

         part 3_html_36dfd611.png

(1) The Page Header property is enabled in parent page B and it displays child page A at the top.

(2) Another child page C is called by page B. Although the structure of the app indicates that it is positioned at the top, page C will always be found below page A because page A was called using the Page Header property in parent page B.

(3) A new child page D is displayed when users scroll down using the mouse. After a specified scroll distance, child page D will replace child page A at the top of the screen.

example

  • Display the first child page at the top of the screen.

         part 3_html_m4a87385f.png

  • Display the second child page at the top of the screen when users scroll down using the mouse.

         part 3_html_56eb5bc3.png

Note: To improve performance, child pages are not visible in the graphic editor. They are visible only in execute mode.

Page Header properties

         part 3_html_b8a8e3f.png

  • Page: Child page called by the parent page to be positionned at the top of the parent page.
  • Change State On Scroll: Second child page to be displayed when users scroll down using the mouse. It will replace the first child page.
  • Distance of Scroll: When a second child page is selected, you can specify the scroll distance after which this child page will replace the first page.

Note

  • The child page called using the Change State On Scroll property must be different from the first child page defined in the Page Header property.
  • The entire child page is selected. You cannot select a specific zone in it.
  • Parent pages and child pages cannot call themselves.

Service Bots and Self Help

Customer-specific information (name of the domain, server address, etc.) is now extracted from Service Apps apps and placed in connectors. In addition:

  • Self Help connectors can now be used to specify the Self Help project ID.
  • A new Service Bots connector has been created to define the virtual agent reference to be used in apps.

Benefits

  • Defining customer-specific information in connectors enables you to modify it in a single spot. You no longer need to do this in each page of the app.
  • This also makes it easier to move from a production environment to a preproduction environment using aliases.

Properties of new Service Bots connectors

The EasyVista Virtual Agent data source no longer points to a Self Help connector. Instead, it now points to a Service Bots connector.

(1) Create a new Service Bots connector.

(2) Enter the virtual agent reference previously found in the Virtual Agent widget.

(3) Specify the Public Account field. This is the Self Help connection account previously found in the EasyVista Self Help data source.

         part 3_html_m42b3edc3.png

Properties of Self Help connectors

Two properties have been moved from the EasyVista Self Help data source to the connector.

(1) Project ID or Alias: ID of the Self Help project or procedure to be run.

(2) Connection Account: Self Help connection account.

         part 3_html_6dc80462.png

New properties of the Virtual Agent widget

Properties are now grouped in two sections to facilitate access and configuration.

         part 3_html_6a849c25.png

  • (1) Configuration of the conversation panel.

         part 3_html_m744bd95e.png

  • (2) Configuration of the call button.

         part 3_html_m23572935.png

Oxygen version 2.0

ReleaseNotes

New widgets

Funnel Chart widget

part 1_html_209bd76a.png This new widget, in the Dashboards category of the library, shows bottlenecks in chart form. 

  • All of the elements are compared from bottom to top according to values, indicating the so-called blockage zone.
  • There are various features that allow you to amend how the chart is displayed: colors, width of the 3 sections of the funnel (top, main body, bottom), descriptor appearance and positions, etc.
     

                   part 1_html_5e8729c4.png

Operating principle

The Funnel Chart widget requires a data source from a report, view or file in .csv format, containing two columns (breaks): Descriptor and Value.
         part 1_html_dbaf8d2.png

Some of the chart layout properties

part 1_html_4164b80c.png

Charts

  • Base Width: Width of the base of the chart
  • Neck Width: Width of the central section
  • Neck Height: Height of the lower section

Connector

  • Dash Size: Thickness of the dashes linking the descriptors and values
  • Gaps Size: Space between dashes
  • Thickness: Width of the dashes
  • Color: Color of the dashes

Important information

  • The .csv report, view or file linked to the data source must contain only 2 columns.
  • Colors can be selected from a predefined palette. You cannot define custom colors.

Tag Cloud widget

part 1_html_4091ee3e.png This new widget, in the Dashboards category of the library, shows text data in chart form and is primarily intended for keyword frequency analysis. 

  • The size of each word depends on its value (the higher the value, the bigger the word).
  • There are various features that allow you to amend how the chart is displayed: overall color of keywords, angle of words, font, etc.
     

                   part 1_html_m5d2f6617.png

Operating principle

The Tag Cloud widget requires a data source from a report, view or file in .csv format, containing two columns (breaks): Descriptor and Value.
         part 1_html_dbaf8d2.png

Some of the chart layout properties

part 1_html_451b94c1.png

Charts

  • Position: Display tags as a sphere or rectangle
  • Color Range: Show legend
  • Series Angle: Tag rotation angle
  • Text Spacing: Space between tags

Important information

  • The .csv report, view or file linked to the data source must contain only 2 columns.

Virtual Agent widget

part 1_html_5de53385.png This new widget, in the EasyVista category of the library, allows you to add a virtual agent call button in Service Apps. A chat window opens, where the user can talk to a chatbot via a text-based conversation (chat).

  • The widget allows you to customize the call button and the agent chat interface.
  • The virtual agent interface is laid out according to a Self Help theme.
  • There are various features that allow you to amend how the virtual agent is displayed: chat interface font, call button and chat header and text-entry zone configuration, list of keywords displayed when the chat interface opens, etc.
     

                   part 1_html_m2b4936a7.png    part 1_html_1c9f41b6.png

Operating principle

The Virtual Agent widget requires an EasyVista Virtual Agent data source (new data source type).

Some of the virtual agent layout properties

part 1_html_44733764.png

Content: EasyVista Virtual Agent data source used by the virtual agent, and Self Help theme applied to the chat interface


Panel: Font settings in the chat interface


Panel Top: Characteristics of the top of the chat panel (icon, text, background color)

part 1_html_2bbfe199.png


User Area: Characteristics of the text-entry zone (text entry color, background color, keywords displayed when the chat interface opens)

part 1_html_6262440a.png


Virtual Agent: Name of the virtual agent, and primary and alternative colors

part 1_html_m7c440868.png


Panel Bottom: Characteristics of the bottom of the chat panel (icon, text, background color)

part 1_html_289cb406.png

part 1_html_m5beb5103.png

Theme

part 1_html_m2d797f91.png

  • Button Style: Characteristics of the virtual agent call button (1)
  • Search Label: Properties for display of a text zone before the text-entry zone (2)
  • Search Style: Properties for display of a text-entry zone before the call button (3)

Changes to widgets

Self Help widget

part 2_html_m10b9f947.png New properties have been added to the Self Help widget.

  • It is now possible to choose the data source that the widget uses directly from the widget itself.
  • New properties allow you to choose which buttons are displayed in the Self Help portal.

Some of the widget properties

part 2_html_6d3ed409.png

Datasource: Data source linked to the widget; must be an EasyVista Self Help data source (new data source type)


Theme: Theme applied to the Self Help widget


Select which buttons are displayed in the Self Help portal

  • Allow Log: Report button
  • Allow Postit: Comment button
  • Allow Map: Overview button
  • Allow Pause: Pause button

Data sources linked to widget headers/footers

A new feature, common to all widgets, allows you to link the header/footer to a different data source than the one used by the widget. Various types of information from different sources can therefore be displayed in the same widget, such as the total number of records displayed by the widget.

Example documentation icon EN.png  Display the breakdown of incidents by life cycle status via a Funnel widget (1), and show the total number of late incidents in the widget header (2)
         part 2_html_494731a7.png

Explanatory diagram

The same widget can use 3 separate data sources: one for the Header, one for the Footer, and one for the widget itself.
         part 2_html_m71bdec2f.png

What are the benefits?

  • Using 3 data sources for the same widget allows you to reduce the number of widgets that the app uses.
  • Reducing the number of widgets allows you to:
    • reduce loading time for the elements of each widget
    • improve overall app loading performance.

Important information

  • To show the number of records displayed by the widget in the header/footer, the data sources will need to be linked to the same filter but to different views (List view for the widget, view by grouping level for the header/footer, for counting purposes).

Operating principle

1. Go to the following property: Theme > Header (widget header) or Footer (widget footer).
         part 2_html_2f47d99b.png  part 2_html_38222887.png

2. Select the data source for the Header (widget header) or Footer (widget footer).
         part 2_html_25e01579.png

3. Click on part 2_html_7f40205f.png to open the text editor.
         part 2_html_m1334bff4.png

4. Enter the widget header/footer text.

5. Use the Data Picker part 2_html_m764634a4.png to select the data source values you want to insert in the widget header/footer.

         part 2_html_2c38bc81.png

6. Save and close the text editor. The HTML code is updated in the widget Header/Footer field.
         part 2_html_m68cf71f5.png

New data sources

EasyVista Virtual Agent data source

part 2_html_m7cc519c.png This new data source, in the Apps category of the library, allows you to link a data source to a Virtual Agent widget (the virtual agent opens a chat window where the user can talk to a chatbot - new widget type).

Some of the data source properties

part 2_html_6d3ed410.png

Virtual Agent Id: The unique ID of the virtual agent


Locale: Virtual agent language


Public Account: Self Help ID (for disabling user authentication)

EasyVista Self Help data source

part 2_html_408c802b.png This new data source, in the Apps category of the library, includes the options that were previously present in the Self Help widget. It should be linked to the new Self Help connector.

Some of the data source properties

part 2_html_27b49ae0.png

Alias/connector Self Help: Connector used by the Self Help widget linked to the data source


Locale: Language used by the Self Help widget linked to the data source


Connection Account: Account used to connect to Self Help

New Self Help connector

This connector allows you to define the Self Help domain.
         part 2_html_6a137977.png

Oxygen version 1.6

Responsive mode

This new functionality is used to define exactly how an app will run depending on the device hosting it. You can specify the behavior and properties of each widget for each device, e.g. smartphone, tablet, PC screen, etc.

There are five modes available, each corresponding to a type of device: S = Smartphone, M = Tablet, L = PC screen, XL = High definition PC screen, XXL = High-end flat-screen TV.

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_4c7f07c6.png

Note:

  • By default, an app is designed for mode L = PC screen.
  • In versions prior to Oxygen, properties enabled users to show or hide certain widgets on smartphones using the options below. These remain available to ensure backward compatibility.

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m16526b2a.png

Operational overview

  • Click wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_441538f5.png in the toolbar to access responsive mode.

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m34bfba7c.png

  • A new workspace will appear.

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_466df5e7.png

  • Click wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_4f97fccc.png to select the widget you want to configure.
  • Click the option you want in wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m2600bfad.png to select the mode.

Description of the responsive mode toolbar

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m6c5c795f.png

(1) Used to return to the standard workspace of default mode L
(2) List of app pages
(3) Used to save the app
(4) List of devices available for each mode

wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_4e8ffa44.png

(5) Resolution in pixels
(6) Used to switch between Portrait and Landscape orientation
(7) Minimized or maximized display, automatically adapted to contents
(8) List of all app objects

Click wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_3b560f7.png to show or hide the object in each mode.

wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_47358da1.png

(9) Used to run the app

Principles of inheritance and context-specific properties

  • By default, each mode will inherit the properties of mode L. Any modifications made to a widget in another mode will be context-specific and will replace the default properties.
  • Each property is managed individually. Properties are inherited in a hierarchy with mode L at its highest level.
    • Default properties in mode L apply to all modes unless context-specific properties are defined in one of the other modes.
    • A property defined in mode M also applies to mode S unless it is specifically modified in mode S.
    • A property defined in mode XL also applies to mode XXL unless it is specifically modified in mode XXL.

                   wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m1062d4bf.png

  • When the cursor hovers over wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_mcdb886e.png found to the right of each property, the behavior for each mode and the inherited and context-specific properties will be displayed.

Example documentation icon FR.png  Device Native Style property

  • The option is checked in mode L (true value) and applies to all modes.

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_571897fc.png

  • The option is unchecked in mode M (false value). Mode S will therefore inherit the false value of this property from mode M. Modes XL and XXL will inherit the true value from mode L, i.e. the option will be checked.

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m22208861.png

  • If you defined a context-specific property in a given mode, you can click wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m302f8160.png to return to the value inherited from mode L.

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_41d7e7e8.png

Monitoring screen

This new screen enables you to view the most commonly run apps in the App Gallery, the last user activity date and the widgets used in the App Gallery, etc.

Only the platform administrator is authorized to access the screen.

Access

  • Click Admin panel in the toolbar to display the monitoring screen.
             wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_232048d1.png
  • Click Back to Store to return to the App Gallery.
             wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_66774821.png

Description

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m70699a5d.png

(1) List of apps in the App Gallery
  • By default, apps will appear from most commonly run to least commonly run
(2) List of users with access to the platform
  • By default, user activity on the platform will appear from most recent to least recent
(3) List of widget types used by all apps in the App Gallery
  • By default, widgets appear from most frequently used to least frequently used
  • There are two views available:
    • Grid: Information is displayed in a table       wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_2f685534.png
    • Matrix: Information is displayed in a chart       wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m2283611c.png
(4) Statistical indicators:
  • Number of apps available in the App Gallery
  • Number of custom widgets
  • Number of shortcuts
  • Number of themes
  • Number of users

Sorting data

  • Click in the column header of the table to modify the sort order.
  • wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_a63a558.png displays data sorted in ascending order. wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m466ab1b.png displays data sorted in descending order.

Example documentation icon FR.png  Click wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m181349c8.png to display apps from least recently run to most recently run.

New Dashboards widgets

Presentation

New graphic widgets with advanced properties have been added.

Note: Previous widgets will remain available to ensure backward compatibility.

wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m5dabe6a8.png wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m2bc45c0c.png

New functionalities

  • 3D display

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_43179b3c.png

  • Display of x-axis and y-axis scales in color

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_14bf5235.png

  • Display of lines on the chart to facilitate identification of x-axis and y-axis scales

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m46fe5bb3.png

  • Possibility of displaying the Save and Print icons in the app: Enables users to save or print an image of the chart

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m762314db.png

  • Possibility of applying a background color to the chart

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_m3708d30c.png

  • Possibility of displaying formatted values in the chart, e.g. color, font, position, etc.

         wiki - Sortie de version evApps - Version Oxygen Q2-2018_html_md927768.png

Tags:
Last modified by Christine Daussac on 2019/12/16 11:52
Created by Administrator XWiki on 2019/01/10 13:26

Shortcuts

Recent changes
•  Service Engine
•  Service Apps
•  Self Help

Glossary

Powered by XWiki ©, EasyVista 2019