EFS Release Fall 2017

Ā 

Survey


Responsive Layout 3

Our new standard layout for surveys named ā€œResponsive Layout 3ā€ is now available.

The preselected layout button for creating a new project was replaced respectively, so ā€œResponsive Layout 2ā€ is no longer selectable directly. Via the button ā€œMy layoutsā€, individualized templates based on ā€œResponsive Layout 2ā€ will remain selectable though.

Old layouts which were created individually for ā€œResponsive Layout 2ā€ are not applicable to ā€œResponsive Layout 3ā€ and are therefore not selectable per default.

If you would like to keep on working with ā€œResponsive Layout 2ā€ as standard layout, your Tivian contact person will reset your layout configuration to the previous version and deactivate ā€œResponsive Layout 3ā€.

Surveys created with the layout template of ā€œResponsive Layout 3ā€ adapt themselves dynamically to different display sizes:

  • Wide Screen - Desktop

  • Tablet

  • Mobile

All question types implemented so far are supported by ā€œResponsive Layout 3ā€.

page3image62015008

Accessibility

The new standard layout for Survey ā€œResponsive Layout 3ā€ contains major improvements in the area of accessibility.

All standard question types are created barrier-free, meaning that each page can be captured, structured and read by a screen reader software and be completely controlled by keyboard (via tab and arrow keys).

Complex question types (Hotspot, Images) are not necessarily created barrier- free, since these rely on further descriptions of the visible image by the survey creator for example.

Prequalification Trigger

With theĀ Prequalification Trigger, new panelists can be generated from anonymous surveys.

These panelists are generated through survey variables. Entering the e-mail address is mandatory.

To use this feature, the panel module must be active.

page4image62560048

Additional disposition codes

New disposition codes are available enabling a more precise classification of survey participants. These additional codes for classification can be assigned on final pages or through customizing.

The new disposition codes behave like existing disposition codes:

  • Screenouts ā€“ codes 38, 39 and 40 behave like code 37. Classification example: Quality screenout. Labels: Custom Screenout 1, Custom Screenout 2, Custom Screenout 3.

  • Completes ā€“ codes 33 and 34 behave like codes 31 and 32. Classification example: Complete, high quality. Labels: Custom completed 1, Custom completed 2.

  • Final-not-participated ā€“ codes 18 and 19 behave like code 15. Classification example: blacklisted. Labels: Custom unavailable 1, Custom unavailable 2.

  • Non-final-not-participated ā€“ codes 16 and 17 behave like codes 11 and 12. Classification example: Has opened e-mail. Labels: Reserved 1, Reserved 2.

Ā 

Portals


Feedback Assistant

The moduleĀ Feedback AssistantĀ (formerly namedĀ On-Demand Guided)Ā for creating template-based ad hoc surveys was completely revised and is now available in an extended scope.

Template configuration in personalized project

The new template configuration forĀ Feedback AssistantĀ can be found in the respective project under ā€œProject propertiesā€ and is divided into different areas.

The access to each template configuration is controlled via the rights and role system of EFS. EFS administrators with respective rights can extensively configurate each personalized project as templates for use and choice within the moduleĀ Feedback Assistant.

Basic information

Here, administrators define a title as well as a description and a background image to make your template in the moduleĀ Feedback AssistantĀ visible.

Synchronizing panelist data

Via the new functionality ā€œSynchronize panelist dataā€, you have the possibility to keep the data of panelists as participants ofĀ Feedback AssistantĀ surveys up- to-date at all times.

Selecting and creating context variables

Select or create variables you want to offer to the survey manager within the moduleĀ Feedback AssistantĀ for free definition. Accordingly selected and filled variables will be available for evaluation in the dashboard afterwards.

Selecting panelist variables

If panelists take part in your survey, here you can select the panelist specific variables you want to be available for evaluation in the dashboard of the respectiveĀ Feedback AssistantĀ survey for further use.

Selecting manager variables

Master data variables which are solely allocated to the respective survey manager initiating theĀ Feedback AssistantĀ survey via the respective module in Portals can be selected in this section and appended to the template for later evaluation in the dashboard.

Allocating the template to certain portals

By selecting certain portals, you have the possibility to control in which portals your template will be available within the moduleĀ Feedback Assistant.

Defining mail templates for invitations and reminders

You have the possibility to allocate mail templates of type ā€œProjectsā€ to the template to be configured, for invitation mails as well as reminder mails for participants of theĀ Feedback AssistantĀ survey.

Portals moduleĀ Feedback AssistantĀ Overview ā€“ filtering, searching, sorting

On the overview page of the moduleĀ Feedback Assistant, you can now search for createdĀ Feedback AssistantĀ surveys, filter the status of the surveys and sort the view by creation date.

List of participants

By clicking on the banderole in the middle of the tile or optionally on the list icon, you get to the list of participants displaying the invitation status of survey participants in an overview. Also, you can export participants from here.

Copying and editing

In the context menu of each tile, the menu items ā€œCopyā€ and ā€œEditā€ can now be found to edit createdĀ Feedback AssistantĀ surveys subsequently or to make a copy of the tile.

Adding participants

From now on, you can additionally invite single panelists from yourĀ PeopleĀ module toĀ Feedback AssistantĀ surveys.

HTML preview for invitations and reminders

With mail templates of the formats ā€œtext + HTMLā€ or ā€œHTMLā€, you now have the possibility to show the rendered HTML e-mail in a preview.

Configuring and sending reminder mails

The new menu item ā€œRemindā€ enables you to select a mail template defined via template configuration as well as to set the time of dispatch of reminder mails (manually or controlled by a timer). After the dispatch of invitation mails, the manual dispatch is triggered by clicking on the envelope symbol of the respective tile in the overview.

Limiting the creation ofĀ Feedback AssistantĀ surveys

To avoid over-surveying for example, you now have the possibility to limit thenumber of permitted surveys within a certain period of time.

Ā 

Report Manager


Requirement profiles

TheĀ Report ManagerĀ is the new product of the Employee portfolio. Rather unpretentious in the appearance, its advantages are on the side of the report generation, which can be carried out in a very large amount. But its qualities are not limited to such a scenario.Ā 

By the means of this new module, you evaluate the results of an employee survey that covers the many different departments of a company and you assemble those in reports instructively.

The Report Definition

The Report Definition that underlies each report of an order is the basis for the report generation. So you are working at a very abstract level. Finally, an order can contain thousands of reports and each of these reports is addressed to a different department. Nevertheless, you depict the individual shade of each department. To show how this works, you can emphasize two stations on the way to the completed reports: the mapping and the report order.

The mapping

The mapping is conducive to create a path for the data space query (DSQ). You define for which departments values are determined without first having to specify which departments are involved. The paradigmatic use case can serve as an illustration: If you want to generate reports for all departments that show the comparison of the regarding unit with the next higher one in relation to any value, it is sufficient to use the two units elements focus unit and level-up comparison unit and define the properties or result types that you want to query.

The report order

In the first step of the report order process, you determine the unit that is to function as the focus unit. As a consequence, the abstract relation to the next higher unit is automatically transformed into a concrete one. Besides, the report type ā€œStandard Reportā€ allows you an easier workload. You are able to hook ā€œInclude subunitsā€ and order reports for all units that are located in the organizational structure below the unit you selected. They will be functioned as the focus unit of these reports.

According to this, the relation to the next higher unit is respectively transferred differently. But you donā€™t have to adjust it manually.

Ā 

Updates for the Report Manager


Page conditions

To guarantee a higher standard of anonymity and to present the reports in a scope that is tailored to the addressed unit, you define the page conditions for each page of the report.

You can use a page condition to determine the conditions under which the respective page is included in the report or not. To define a page condition, you pick a DSQ (Data Space Query), select the desired set operator from the six available set operators (=, !=, >,>=, <,<=) and enter the reference value. Words and numbers can be used as a reference value. If you select ā€œMetanameā€ or ā€œLabelā€ as unit property or ā€œLabelā€ as a scale property, you use the set operators = or != to be able to enter in the reference value field the label or the metaname. You are able to deactivate a page pointedly because you deactivate the page for a specific unit.

Rights and roles management

In the role management of the Data Voyager, you hook the right to create, edit and delete page conditions for the roles ā€œAdminā€ and ā€œAnalystā€.

You hook the access right to the elements of the page conditions for the roles ā€œAdminā€, ā€œAnalystā€ and ā€œReaderā€. These three roles are then given the right to view defined page conditions.

The following use cases are worth mentioning:

  • The user can view, create, edit and delete page conditions in the role of ā€œAdminā€ or ā€œAnalystā€ if the following rights have been activated or deactivated in the role management of theĀ Data Voyager:

    • Access to elements of the conditions is disabled or enabled.

    • Report management is activated.

  • The user cannot see, create or edit the page conditions in the roles

    ā€œAdminā€, ā€œAnalystā€ and ā€œReaderā€ if the following rights have been deactivated in the role management of theĀ Data Voyager:

    • Access to elements of the conditions is disabled.

    • Report management is deactivated.

  • The user can view the page conditions in the roles ā€œAdminā€, ā€œAnalystā€

    and ā€œReaderā€ but cannot create, edit and delete them if the following rights have been activated or deactivated in the role management of theĀ Data Voyager:

    • Access to elements of the conditions is enabled.Ā oĀ Report management is deactivated.

A new column in the report order table

The report order table (under the tab report orders) obtains the new column ā€œOrder Stateā€. By the means of this update, it is possible to depict the four different order statuses clearly:

  1. Created

  2. In Progress

  3. Done

  4. Cancelled

Each order is initially set to the status ā€œCreatedā€.

Report order management and control

The report order management gives you direct access to the processing of an order. This saves you time, especially in the case of orders that contain large quantities of reports to be generated. If a report definition turns to be in need of correction, the report order management allows you to cancel and to delete the corresponding order. Of course, you are able to pause an order and check any possible changes before placing it. You continue the processing with ā€œResumeā€.

By mouse over, the icon available in the respective order status appear in the row of the report order table. Not all actions are available in each status. Accordingly, the icons of the non-executable actions are not displayed. All in all, you have the following actions:

  • Pause

  • Resume

  • Cancel

  • Delete

Improvements for the tables: refresh button and fixed header

The report table, the report order table and the report distribution table obtain a refresh button.

A scrolling header provides a better overview of the report order table and the report distribution table: the header of the table remains in screen when you scroll.

Ā© 2024 Tivian XI GmbH