Release 9.0

Assessment Management

Assessment Builder

A completely new version of the Assessment Builder has been added in this release. Completely rebuild in the new front-end, the new Assessment Builder consists of three parts:

  1. The index on the left where categories and questions can be added and re-ordered
  2. The canvas in the middle where a preview is shown of how the assessment will look like on desktop and mobile
  3. The editor on the right where you can add the following information per question:
    1. Name and values
    2. Calculation options
    3. Conditions (see below)
    4. Setting target values for 'right' and 'wrong' answers
    5. Options such as allowing images, comments or setting of not applicable

You can find the new Assessment Builder by going to the Knowledge Base > clicking NEW and then Assessment.

Question conditions

When filling in an Assessment, it can be that not every question type is relevant for the current situation or that you sometimes do want to make a question mandatory, but sometimes don't. The Question Conditions allows you to easily set this up per question.

The Condition Builder consists out of two sections:

  1. The 'If' part where you can select a question and compare the answer. The following options are available:
    1. (Does not) contain
    2. (Does not) equal
    3. Bigger / Smaller than
  2. The 'then' part that sets the action that has to be taken when the 'If' part is true. The following options are available:
    1. Show/hide questions or categories
    2. Show/hide related questions (see below)
    3. Make questions (not) mandatory
    4. Make questions (not) read only

NB: Please note that currently no 'nested' conditions are support, only direct conditions from one question to another are expected to work.

Related questions

Related questions (or 'child' questions) are questions that are connected to another question. Functionally they can do everything a normal question can do, but they are connected to another question to show that they are related. Through the Condition Builder (see above) these can be shown or hidden based on (for example) the answer of the top question.

Choice (image) button

Sometimes a picture says more than a thousand words. To leverage this, we've added a question type where you can add images as answer options as well as set whether the chosen option is 'positive', 'negative' or 'neutral'. 

When you don't add an images, you just visualize the answer options as buttons. This prevents opening dropdown menu's when configuring multiple choice questions.

Setting columns

By default, Assessments are shown with two columns of categories next to each other. Now, you can select in the Details tab, whether you would like to have one or two columns. 

Note that on mobile we will always show one column for a better user experience.

Target Questions 

In R8.0 we've introduced target questions: a setting for the Numeric Scale, Boolean and Choice question to be able to set whether an answer is positive, negative or neutral. In R9.0 we've expanded the functionality also to Yes/No questions on desktop.

Signature question

Sometimes you want to have an extra confirmation that an Assessment has been filled in accurately and correctly. On mobile it has been possible to add a Signature question to Assessments for a while. In R9.0 we are expanding this functionality to the desktop application as well.

Form support (Info tab)

It is now possible to show or hide a form by checking the 'Enable Form View' for the Assessment Instance table. This allows for easily assigning the assessement to someone else, changing the due date, equipment or work area or any other field. Don't forget the create a mobile form view configuration for this to work!

For the techies: we've added support for Assessment in the Task API. This means that every functionality that we from now on develop for tasks, will also work for Assessments!

Add assessment to any task

For many processes a step is required to complete an assessment to move through the steps. Before you would first open the task and then separately open the assessment to complete it. By adding the Assessment to the 'Related Assessment' field, the Assessment will show in a separate tab (both on mobile and on the desktop).

Setting values in the back-end

To make sure that filling in an Assesssment takes as little time as possible, it can help to have some answers pre-filled. Through configuration with the Flow Designer, question answers can be pre-filled and shared with the user that is going to fill in the Assessment.


Mobile

New top and side bar

Since space on a mobile device can be scarce, it is important to determine what will (not) be shown. From now on, you can find the following information in the sidebar:

  • Detailed description
  • Equipment
  • Work area
  • Document type
  • Process line
  • Line status
  • LOTO(TO) level

We've added the side bar for all task types, to give an uniform experience across the whole mobile application.

New theme colors

Aligning the look and feel of the mobile application can help with the adoption. To allow for easing configuration, we've added the following colors:

  • Activated: Used for selected elements like active icons
  • Neutral: Unclickable objects.
  • Affirmative: Green color for affirmative buttons.
  • Warning: Yellow color for warning buttons

This configuration can still be found under 'Application theme' in the back-end.

Expansion of related work functionality

For all tasks in mobile we were already showing a 'Related Work' that shows records that have the current task either as their source or parent. This tab now also shows the records that are added to the Task Relation table (x_ap4_scm_core_m2m_scm_tasks_scm_tasks). 

This makes it possible to build more complex logic by automatically adding records to that table through (for example) machine learning.

Auto lock out & auto log out

Security is an important aspect of the 4Industry application. Though the default functionality of the mobile devices already add an important security protection, we've added two additional security implementations:

  • Auto lock out: by setting the 'Lock out duration' system property, you can determine after how many seconds the user is locked out and thus redirected to the user overview screen. After selecting their user and filling in the PIN, the application can be used again.
  • Auto log out: In the 'Application Registry' module you can configure after how many seconds the user should log in again by setting the refresh token. Next to that, it is possible to check if the user is still allowed to have acces after a set period (by setting the access token). For more information, check out the technical documentation.

Other notable improvements

  • Mandatory fields now become red when you forget to fill them, to provide better feedback to the end-user
  • We've improved the typograhpy of the Assessment Executor to have a more natural visual hierarchy
  • Information such as safety measures, detailed description, the related knowledge article and assessment are now added in the API itself, instead of combined in the mobile devices, allowing for easier configuration

Breaking Changes

Two changes have taken place this release that require your attention:

  • When setting a question to 'not applicable' in mobile, we now use a separate 'Boolean' field 'not_applicable', where this before was done by setting the answer to '-1'. Please update any logic you have created for this to take into account the new field.
  • In order to allow for easier reporting in analysis management, some data model changes have taken place. Since these changes have also been released as a hotfix in R7.0 and R8.0, this change should already been applied on your environment if you have updated to the latest hotfix pack. 
    • Countermeasure records now link to Task and Why records directly
    • The link between countermeasure records and RCA records has been removed
    • Why records are now directly linked with Why records
    • The link between Why records and RCA records has been removed
  • Support for Android 9.0 devices have been removed. Please make sure that your Android device is running Android 10.0 or higher.