EFS Release Spring 2017

Portals

New page module Reports

The new Reports page module enables the display of reports which are released or requested for a certain user. The source of these reports are corresponding ES projects on the installation. The user will be informed about the availability of new reports in the notification center of Portals.

Open

Import / export of portal languages

User-defined translations for standard phrases of a portal can now be exported and imported. This way, you’ll be able to export your data, send them to a translation agency for example and import the translated data into the system later.

Layout limitation for page modules

When configuring pages in the admin area of a portal, certain modules will only be available for specifically adapted layouts.

This way, misconfigurations can be avoided. Furthermore, modules are always being displayed in the optimal view.

New indication of changes to pages in Portals admin area

To prevent admins from forgetting to publish changes after editing pages, we built an eye-catching header, which suggests the publication of a changed page.

Open

New user icon for moderator

A crown at the user icon now marks portal users as moderator. A corresponding quick info additionally indicates a user as moderator by mouseover.

Rearrangement of tab Contents

The tabulation of the discussion board of the tab Contents within the Portals admin area has been optimized and adapted to the design of the other tabs. Besides, the content of the tab Classifications can be found on the tab Contents from now on.

Action Planner enhancements

MyTasks Action Planner module for Portals

In Portals you can add the MyTasks page module. With this new page module, you can create, view and edit actions. Heading, the target ES project and the number of actions can be defined in the Portals admin area. You can restrict all users from creating actions on their own by unchecking the provided option.

Based on a new filtering area with several new filters, the list of alerts can now also be sorted by name, date of creation, due date and status.

When creating a new action, the unit and responsible person picker are dependent. Select a unit first to load a list of responsible persons for that unit. If more than 10 units or responsible persons are visible, the select box becomes a filtering list. Saving is not available until all required fields are filled.

In detail view, commenting and a history log are now available. Comments can contain text, images or videos. The history log shows all modifications to the action.

All Action Planner variables can now be shown in the MyTasks page module of Portals.

To hide variables in the Portals module, go to the variable editor and change the property “Show the content of this variable” to “no”.

The Portals module requests the order of manually created variables in the variable editor.

Changes to actions

All actions now have a history log. The history log stores all modifications to the action. The information stored in the history log is only viewable through the Portals MyTasks module.

All actions now have a created date (ac_created) and an internal variable (ac_source), which stores information on which functionality created the action. When creating a custom action planner variable, the ending ac_ is used.

An action can now be assigned to a specific Org-Processor user of a unit in new ES projects. The variable ac_response_id will be used to contain the user’s id, and ac_response will be filled with the name of that user for backward-compatibility.

In existing projects the functionality remains as is.

Action Planner variable editor

The variables storing information on an action are user-manageable now. The action planner variable editor is available in Org Processor > Configuration > Action Planner Configuration > Action Planner variables. This menu is available to users with the access right ac_variable_editor.

Action Trigger

This trigger creates a new action in the target ES project. A range of conditions and settings defines if an action is created and what content is stored in the action.

The target unit for an action needs to be provided in a variable of the originating survey. If a unit cannot be found, a survey runtime error is thrown and the surveys error notification recipients will be notified.

The surveys wildcards can be used to dynamically fill action planner variables. Conditions can be defined to provide different content based on pre-defined rules. Default fields cannot be removed and must have a value.

Action Planner data in MySight

Action planner data can be synchronized with MySight. All selected variables will be available as dimensions. The fields date of creation, put in progress at and closed at are always available.

Import of org-structure users to People

In Panelist administration, functionality Panelist import from Employee project has been extended
to also support org-structure users. Users can be added to an existing panel group.

Hierarchy question types

New question types Hierarchy and Hierarchy search are available on installations with the Employee module enabled. They allow browsing and selection of a unit in non-Employee projects. The meta name of the selected unit is stored in a variable. An ES project with an org-structure needs to be selected as source in the question editor.

Change Requests

New question type: Blacklist email

You can use this new question type to build unsubscribe surveys with user-defined layout, text and questions. This question type extends the existing black list feature introduced in the EFS Winter 2016 release.

You can select the variable in the question editor, which stores the email address of current participant. Furthermore, you can define the question type’s behavior. Users can either be added to the global or the project based blacklist or be removed from all lists.

This new question type is only available on final pages.

Update of master data in LUA question type

By using the function setMasterDataValue (varName, var Value) you can update master data of a panelist directly from the survey.

This function is only available in PA and MD project types. The function returns “true” on success and “false” on error.

X-Frame-Options: HTTP header settings in Panel and Survey

This setting controls the behavior of EFS, when embedding the Panel website or a survey in a different website. Possible choices are “Do not send”, “Deny”, “Same origin”. The default “Do not send” does not change the existing behavior.

Panel: Website > Global configuration: “Select whether a header with X-Frame- Options should be sent to the client”.

Survey: Project properties > General options: “Select whether a header with X- Frame-Options should be sent to the client”.

SMS-Report

On installations with the SMS module enabled, in Options > SMS admin, there is a new functionality called SMS report.

This detailed list shows all SMS that were sent by EFS to the provider along with the initial response received from the SMS provider.

New service layer methods

employee.reports.getDefinitions: Returns all existing report definitions of employee download-platform for given project-id

employee.reports.addReport: Uploads a new report file into download-platform of a given project-id and assigns the report to the unit.

MySight field report

Aggregated field report data, grouped by days, is now available in MySight. You can use them to rebuilt the field report diagram of EFS in MySight. Filtering based on survey data is currently not possible.