WarningReleaseNotes

            See Adjusting graphics settings on apps built in previous versions

            List of Known Errors

What’s new in the infrastructure

System message localization

System messages (error messages, system texts) now appear in the user’s language. The user’s language is determined according to the following rule:

• The language defined in evSM is used if the application user was correctly identified at login.
• The browser language is used.
• The company default language is used.

What’s new in access management

New team: Everyone

A new team has been added. This system group contains all registered users.

• It can be used to easily assign an application to all current and future users.
• It appears automatically at the top of access management dialog boxes.
• It cannot be deleted.
          

New profile: Theme Designer

A new Theme Designer profile has been added. This profile is assigned to users (or teams) with access to the theme editor.
        

What’s new: general aspects

Standardization of the popup window system

The popup windows that appear in the applications, the Studio and the App Gallery are now managed via a centralized, standardized system. As a result, it is now much easier to amend the corresponding mechanisms.

What’s new in the App Gallery

Design of the upper zone

Several icons have been added to manage the new functions. Where the screen width is limited, the icon names now appear below the icons.
        

Application filter/search function

There is now a search box at the top of the list of applications. This search box can be used to filter the list of applications automatically by the text entered in the field, by all content, by applications only, or by shortcuts.
        

What’s new in application life cycle management

Shortcut concept

Once a new application is released, various corrective update versions of the same application are normally designed and developed. A new shortcut mechanism has been introduced, making it easier to replace a released application with a more recent version.

Each shortcut is a link to a version of an application. This link is provided to users. When the application is updated, the shortcut simply needs to be redirected to the new application. The link itself remains valid.
        

  At a given point in time (T1), users are using a shortcut that directs to version 1 of the Portal application. Portal V2 is then developed. Once development is complete at point T2, the shortcut simply has to be updated so that it directs to version 2 of the Portal application. This means users will be able to use the new application without having to amend their configuration.

Deployment of shortcuts in the interface

• To create a new shortcut, click the new icon in the main bar of the App Gallery:
          

• In the box that appears, enter the shortcuts title, a description (where necessary), the application to which the shortcut directs, and the relevant execution context (which overrides the execution context indicated in the application):
          

• The shortcuts are fully integrated into the list of applications. A specific icon is added in the lower right zone of the icon to show it is a shortcut. The icon is the same as the application icon.
          

• In Edit mode, you will notice that the lower zone of the screen contains the information normally found in the sharing dialog box (which can be accessed from the Studio) for the applications. The link is the link that should be given to users so they can execute the application.
          

• The search box at the top of the list of applications can be filtered to show only those applications with a shortcut.
          

• Once a shortcut has been created, this becomes the main access point to the application for users. Shortcut access rights are managed in exactly the same way as application access rights. The access rights defined for a shortcut override the access rights indicated for the associated application.
          

• When a new version of an application linked to a shortcut is released, a warning message appears, drawing the user’s attention to the fact that a link exists.
          

Example

In this example, the Portal V1 application has been released and the Portal V2 application is under development:
        

• Access rights are configured via the application shortcut for Portal V1, and this shortcut is provided to users.
• When version 2 of the Portal application is released, simply edit the shortcut so it redirects to the Portal V2 application. The link, access rights, and execution context for the shortcut remain unchanged and are still valid.
          

What’s new in data sources

Inner joins in composite data sources

You can now qualify the joins used in a composite data source by selecting inner joins. A new checkbox has been added to the join definition dialog box for this purpose.
        

REST connector

A new connector has been added. This connector can be used to access REST data sources and replaces (and supplements) the previous JSon Online connector. For more information about the required syntax for the selector, go to http://jsonselect.org.
        

Deploying a REST connector

• The first field in the properties inspector is used to enter the URL of the REST data source.
          

• A REST data source returns a JSON table, with non-standardized content. The required data may be buried deep in this table. A specific tool is available to help you search for the required selector. To access this tool, click the  icon next to the Selector property:
          

• The selected data may then be displayed via a data viewer.

Example

In this example, an open REST data source: http://api.open-notify.org/astros.json returns the current crew of the ISS:
        

• The resulting table begins with a response status message (success), followed by the number of astronauts currently on the ISS (6).
• To recover the composition of the crew, identified by the “people” tag, either enter .people in the Selector field, or click the people tag in the table. The changes are then reflected immediately in the display.
• If the REST data source is assigned to a data viewer, the result will be as follows:
          

Authentication management

OAuth authentication should be used wherever possible, provided this is supported by the server.

BASIC Authentication

This was the first form of authentication available. Simply enter the login and password, which are then encrypted via http(s) and submitted to the source.

Once BASIC Authentication has been selected, the login and password are entered by clicking  next to the Authentication Parameters property:
        

OAuth (versions 1 and 2)

Under this authentication type, an application can access a user’s information without the need for a login or password. In this case, the data are managed by the target system/service.

• The login boxes relate to the called system, which returns the encrypted tokens to the application.
• Note: Under OAuth 2 authentication, there is no need to enter the URL of the REST service, since the OAuth system enters the value automatically.

  Displaying a Twitter feed in a data viewer:

• Create a new ‘Twitter’ REST data source, with OAuth 2 authentication selected from the drop-down list (1):
          

• Display the REST service via OAuth selection dialog box by clicking (2):
          

  (1)	Select the REST service from the list of available services. Note: The list will be extended gradually as new services are approved.           Twitter
  (2)	Select the REST resource you wish to use, from the list of available resources. Note: New resources may be added.            Home timeline: this is used to input tweets from the timeline of the selected account
  (3)	Click + to add the account authentication details. The following dialog box appears:          Notes: The authentication dialog box depends on the selected service (the dialog box comes directly from the service concerned). Your login information will never appear within the application itself.
  (4)	Indicate whether you wish to save the authentication details with the application: Checkbox selected: when the application is executed, the authentication details entered by the creator will be re-used. This feature can be used, for example, to store the user account for Twitter feeds. Checkbox not selected: users executing the application will need to log in the first time. Note: Technically speaking, the authentication details (access tokens) are not actually “stored” in the application, but in a dedicated, encrypted table.

• The new account is then displayed, and the JSon selector can be used to control access to Twitter:
          

• Create a data viewer to display the corresponding Twitter feed, via the following configuration:
          

Saving authentication details

The Use these credentials checkbox (4) indicates whether the authentication details are stored with the application:

• Checkbox selected: when the application is executed, the authentication details entered by the creator will be re-used. This feature can be used, for example, to store the user account for Twitter feeds.
• Checkbox not selected: users executing the application will need to log in the first time.

Resource management

When you have entered multiple authentication details for several REST data sources, it is useful to have a list of these resources, so you can delete any not required.

• A dedicated dialog box is available in the user profile window:
          

• All stored authentication details for each service are displayed. You can delete one or all of the items in the list.
  Note: If you wish to delete authentication details saved in an application, a warning message will appear. If you delete the details, users will then need to log in again, as if they had never been stored.
          

Adding new resources for a REST service

A list of resources is provided for each supported REST service, along with predefined access. The user does not need to worry about the corresponding technical information.

New resources can be added:

• Click ‘Manage’ in the service’s OAuth configuration dialog box. The list of defined resources is then displayed.
• Click Add Resource and enter details of the resource you wish to add (in particular the URL). Note: A resource may be private (accessible only to the application creator who created it).
          

MSSQL connector

The memo fields (VARCHAR(MAX)) can now be displayed.

What’s new in the Studio

Changes to the main creation window

Viewing widgets for a row or column

The right-hand application design pane has changed, and is now more flexible and user-friendly.

• Rows and columns can now be viewed more easily, with a green dotted line around the widgets they contain.
• Rows can now be viewed more easily with the addition of a dark gray color to distinguish between rows more clearly.

  When you mouse over a column, a dotted green line appears around the two widgets contained in the column.
        

Simpler widget resizing process

When you resize a widget, the height in pixels is now displayed:
        

Addition of a local menu on columns and grids

The display has been improved, with a new menu to the right of each row or column containing all functions that can be executed on that particular row or column. The menu icon  appears when you mouse over the row or column concerned:
        

Click the icon to display the menu:
        

Simpler Drag & Drop process

The Drag & Drop function has been changed.

• The display of fields to which an element can be dropped has been reduced.
• The field expands when you mouse over the area concerned, to make the drop process easier.
          

• The mouse cursor display has been changed in the working space, to make it easier to identify fields into which the element can be dropped.

    The cursor changes appearance when placed over a row to initiate the Drag & Drop process
        

    The cursor changes appearance when placed over a widget
        

General change to the local menu

The Custom Widgets interface was too cluttered, due to the presence of the  icon next to each widget.
        

There is now a cleaner interface, with a local menu to the right of each widget. This menu, accessed via the  icon, appears when you mouse over each widget:
        

Addition of a text-entry field to the sliders

All sliders now have a text-entry field in which numerical values can be entered directly. These values can be copied from other fields to harmonize the values.
  Setting identical margins on all four sides of the widget
        

Improved display of inherited fields

The properties inspector has been modified so inherited fields are now displayed more prominently (i.e. those fields with a pre-populated value). A blue border has been added to the upper section.
        

Improved display of inherited data sources

You can mouse over the Inherit option in the properties Inspector to see the value and source of an inherited value. The tooltip shows the value and the source of the value (theme, page, etc.).
        

What’s new in Custom Widgets

Editing Custom Widgets

You can now use the Edit function in the local menu for each Custom Widget to edit an existing Custom Widget (e.g. to change its name, associated icon, color, access rights, and settings).
        

Resource integration

Each Custom Widget now includes the local resources it requires. In particular, all images and data source files are automatically copied when the Custom Widget is reused.

Custom Widgets consisting of multiple widgets – Custom pages

The Custom Widgets mechanism has been enriched, and multiple Custom Widgets can now be grouped together to create a single Custom Widget. It is now also possible to create custom pages, comprising all widgets present on a page.

This means applications can now be created more easily, by reusing and then customizing custom pages.

Reminder about columns

The layout system can be used to separate windows into separate fields, so the application can be divided up as required.

Under the new system, all widgets contained in one of these fields can be saved in a single operation.

• (1): two widgets located one under the other in the same column.
• (2): two widgets positioned in a layout (which has been divided into two).
          

Creating composite Custom Widgets

Composite Custom Widgets are created using a similar process to the existing single-widget module (which is still present). The only difference is the location of the icon used to access this function.

• At present, the icon is located in the upper section of the Studio properties inspector, next to the widget icon:
          

• In the new version, the Create custom widget function is used. This is located in the local menu for the selected widgets:
          

• The dotted green line gives a clear indication of the widgets that will be included in the future Custom Widget.
    The Service Availability and Find Wifi & Printer widgets will be used to create the new Custom Widget.

Custom theme management

The previous piecemeal theme management mechanism has been completely overhauled and is now more flexible and powerful. Most importantly, it is now possible to create new themes directly in Studio.

Theme concept

Each application consists of content and a container. The content relates to all elements displayed on-screen, while the container is the manner in which these elements are displayed on-screen.

In order to ensure all applications have a standardized appearance, it is advisable to separate content and container. This means these two separate components can now be produced by different individuals with the necessary skill sets. For example, a graphic designer may handle the graphic elements, while another person handles the content of the application.

In order to manage themes effectively, the application must be as neutral as possible.
  A neutral application may change significantly, when governed by three different themes
        

Reminder: the inherited design principle

Each widget has a Theme section, which contains all of the visual elements comprising the widget. The inherited design principle is as follows:
        

Themes and their impact on the appearance of a widget

Editing a theme is a completely separate task from editing an application, which is done using a specific version of Studio. The editor features a toolbar and a range of dedicated functions.

Each theme consists of several parts:

• The default graphic elements for each page
• The default graphic elements for all widgets
• The default graphic elements for all widgets of a specific type

Under the new system, the appearance of a widget is defined as follows:
        

Theme editor

• The theme editor is accessed via the new button in the App Gallery. This button is only available to those users with the new Theme Editor profile.
          

• The main window consists of four panes:
          

• The theme creation/modification workflow is as follows:
  • Click  then  to create the theme, define the theme, then save by clicking
  • Click  then  to select the theme, update the theme, then save by clicking

Toolbar

The function bar

	Switch the current theme to Edit mode.
	Access the list of current themes:          From this list, you can switch a new theme to Edit mode (via the properties inspector or by clicking on the theme), or delete an existing theme via the local properties inspector:
	Create a new theme

Properties inspector

Application pane

Menu section

• In this section, you can adjust the style settings for the application’s main menu (upper zone showing the list of accessible pages).
          

• You can also change the font of the application title and the active and inactive menu items.
          

Page section

Here, you can define the default settings for all application pages.

• The Inside Color and Outside Color properties are applied to the central section and outer sections of the applications.

• Note: The Outside color will only be visible if the site has a maximum width defined.
          
   

Widgets section

Here, you can define the default settings for all widgets.

• Use the Element drop-down list to indicate the section concerned. Use the Widget option to change the background and text colors for all widgets:
          

• Any change to the active color only affects Tab and Accordion widgets. This is the color of the selected element.

• Similarly, the secondary color only affects the inactive tabs of Tab and Accordion widgets.
          

Fonts section

  
In this section, you can define the default fonts for the HTML tags used for various texts within widgets.

• Use the Title 1 (H1) drop-down list to select the tag you wish to modify.
          

Widgets pane

• Select the widget you wish to configure either by choosing the widget in the corresponding pane, or by clicking the widget in the application Design tab.
          

• The number of style elements you can configure will depend on the chosen widget. All widgets include at least one Theme section, and the corresponding section is reflected when the widget is positioned on a page:
          

Managing theme access rights

• By default, themes created by a Theme Designer can only be modified by this user or by an App Center Manager.
• The Theme Designer may allow other Theme Designers to access his/her own themes.
• The access interface is located in the lower zone of the properties dialog box for the current theme. The list contains the other Theme Designers. The Theme Designer selects the checkbox next to the user’s email address to allow the corresponding user to access his/her themes.
          

Other improvements to Studio

What’s new in page configuration

The settings that can be modified on each page are the settings in the Application tab of the Theme Editor.
        

What’s new in sliders

You can now enter numerical values for all slider components.
        

Updated style guide

The general style guide has been standardized and simplified (HTML/CSS structure).

What’s new in widgets

Menu widget

Visual change to the menu entry management function

Menu entries are now managed via a popup window, thereby avoiding excessive scrolling for menus containing multiple entries.
        

(1)	: Display the menu entry pane
(2)	: Duplicate the menu entry
(3)	: Delete the menu entry

The menu entry pane is divided into two tabs: General and Indicator.
        

New menu functions

• Color On Hover: Select the color of the menu entry when the cursor is placed over the entry.
• Logout link: Used to log the user out from a menu entry in Execution mode.
• Inactive links: A new option, which can be used to deactivate the link for a menu item.
          

• Improved link input process for the service catalog: Where the purpose of a menu item is to create a new service or a new incident, the item is now selected from a list of services, rather than by entering the GUID.
          

• Optional display of the right arrow : Where the menu is laid out in a single column, display of the arrow is now optional.
          

Custom icon for menus and search mode

• The icon gallery now contains a search box (1), making it easier to select icons.
• A similar option to the option available for Custom Widgets has been added. This option allows the user to add a custom icon to a menu item by entering a URL in the corresponding field (2).
          

Adding an indicator

An indicator is a marker containing a value, which is displayed on the menu item. You can customize the appearance and position of the indicator:

• The value is retrieved from a database.
• The position of the indicator can be fine-tuned using the new options available.
• The color may be fixed or dependent on the value shown.
          

The indicator is customized via the dialog box:
        

Data viewer widget

• The data viewer has been corrected and extended to make it more flexible and more user-friendly. In particular, you can now use the Grid Style section to define the fonts used for the content in precise detail. Note: These settings can also be accessed via the Theme Editor.
          

• The Element property is used to define the fonts used for the headers, even rows, and odd rows.
  

• Grid mode is now the default display mode for the data viewer.
• The data viewer settings now include a new Embedded Form property in the Form section of the data viewer, which can be used to include the Detail view in the list of entries.
          

  Service catalog

• Currently, when you click on a service, the Detail pane is displayed instead of the list of services. The  button can be used to return to the list.
          
          

• Under the new version, if the Embedded Form property is selected in the Form section of the data viewer, the Detail pane appears below the selected service. The list of services also remains displayed, and the other entries are shifted downward.
          

Filter widget

The Filter widget can now be displayed horizontally or in a compressed format, via the Display Type property:
        

Vertical display	If the field is too small to display all items, an arrow appears on the right. Clicking this arrow shows the non-displayed items.
Horizontal display
Combined display	Designed for displaying filters on smartphones.

Tab widget

In the previous version, two widgets were used to show dialog boxes with tabs:
        

These two widgets have now been combined into a single widget, which also includes new options.

Note: The previous Horiz Tab and Vert Tab widgets are no longer displayed in the widget list. However, they are still present in the system. All applications that use these widgets will continue to work normally.
        

The properties inspector for the new widget is displayed as follows:
        

Dashboard widgets

Dashboard widgets have been extended, and it is now possible to define the fonts used in greater detail.
        

What’s new: miscellaneous

• The widget background color now applies to the header and the footer.
• You can now choose to display certain widgets in mobile mode only, using the new property available in the Theme section:
          

Interaction with evSM

New style guide for questionnaires

The questionnaire creation procedure has been overhauled to handle responsive application design (the questionnaire is now displayed more effectively on mobile devices), to provide better multi-browser support, and to manage the new features in the latest version of evSM.