(Sub)category configuration

Subcategory configuration screen

Name

Name as displayed

Enabled

Select whether the (sub) category is enabled

• On - Teams can select the issue from the dropdown when making new issues

• Off - Teams can select the issue from the dropdown when making new issues

Subcategory (only category changes)

Select when a category requires a subcategory

• On - One cannot save an issue without the selection of a subcategory. Subcategories must be configured

• Off - One can save an issue without the selection of a subcategory. Subcategories must not be configured

Workflow

One can select the preconfigured workflow for the issue (sub)category.

Show in logbook (only category changes)

Select whether this issue's (sub)category is shown in the logbook. Often this is restricted for operational issues. All other categories (changes, permits, approval flows, ...) are lmimited to issues

• On - This type of issues is shown in the logbook. New entries can be created from the logbook page

• Off - This type of issues is not shown in the logbook. New entries cannot be created from the logbook page and will require the issue screen (table format) to create new entries

Add instructions

When activated, a rich text editor is shown and entries will have this additional information shown when creating an issue. Examples includen written explanations, visual workflows or hyperlinks to documents, etc

Configure assignee

Configuration options

One can choose to chance the selection of assignees.

• Default - No assignee is required and both workstations and users are allowed

• Required - Choice can be made to make an assignee required when creating an issue.

• Allowed assignee type - Decide to restrict the choices and only allow users or workstations to be selected when creating an issue

• Default assignee - Selecting either user or workstation will prompt to select a user or workstation. This will be the default, but is not limitative and still can be changed manually

• Allowed user assignees - Limit options and predefine which person can be selected

• Allowed workstation assignees - Limit options and predefine which workstations can be selected

Prerequisites

Workstations - Workstations need to be configured via Settings › Organization › Workstations

Send notifications (new issues/category changes)

Selection options

Activating any of the below checkboxes, will trigger the selected audience to receive notifications for this specific (sub)category. Options include:

• Send notifications to reporter - Person submitting issue will be notified

• Send notifications to assignee - Person assigned issue will be notified. Note: E-mails will not be sent for workstations!

• Individual users - Selection of active users to receive notification

• Team members - Members of teams will be notified

• With favorite workstations - Select workstations that need to be notified Note: Notifications will only be shown to users that have the selected workstations explicitly enabled in their user menu.

• By profile - Users with the selected profiles linked to them, will be notified

• In a profile group - Users with with a profiles linked to them that's part of the selected profile group, will be notified

• By position - Users assigned to a certain position will be notified

• With required skills (skill need) - Users who are required to complete the selected skills as mandatory training will receive a notification

• With acquired skills - Users who have acquired the selected skills will receive a notification

Prerequisites

• All selections - Issue notifications activated via Settings › Communication › Notifications.

• Team members - Team members configured via Training › Teams

• Favorite workstations - Workstations configured via Setting › Organization › Workstations

• Profile - Profiles configured via Settings › Skills & Training › Profiles

• Profile groups- Profiles configured via Settings › Skills & Training › Profile groups

• Acquired/required skills - Skills configured via Settings › Skills & Training › Skills

Sensitive fields

Sensitive fields are fields that will be shown when submitting an issue, but are only visible to the selected users when opening an issue after submission.

Note: This applies to all sensitive fields in that (sub)category.

Note: Changing the sensitivity of a field will only affect new issues. Existing data in sensitive fields will remain visible in those issues. Please proceed with caution when modifying sensitive field configurations.

Selection options

Activating any of the below checkboxes, will allow the selected audience to see the data in the fields marked as sensitive. Options include:

• Hierarchical line of reporter - All persons in hierarchical line of the reporter will able to read sensitive fields

• Individual users - Selection of active users will able to read sensitive fields

• Team members - Members of teams will be notified

• With favorite workstations - Select workstations that will be able to read sensitive fields Note: Selecting workstations is a personal choice and less restrictive than other options

• By profile - Users with the selected profiles linked to them, will be able to read sensitive fields

• In a profile group - Users with with a profiles linked to them that's part of the selected profile group, will be able to read sensitive fields

• By position - Users assigned to a certain position will be able to read sensitive fields

• With required skills (skill need) - Users who are required to complete the selected skills as mandatory training will be able to read sensitive fields

• With acquired skills - Users who have acquired the selected skills will be able to read sensitive fields

Prerequisites

• Hierarchical line - When not automated from HR masterdata, reporting lines need to be configured for all employees individually via Settings › User & Access management › Users › Edit user

• Team members - Team members configured via Training › Teams

• Favorite workstations - Workstations configured via Settings › Organization › Workstations

• Profile - Profiles configured via Settings › Skills & Training › Profiles

• Profile groups- Profiles configured via Settings › Skills & Training › Profile groups

• Acquired/required skills - Skills configured via Settings › Skills & Training › Skills

SAP PM

Requires SAP-PM module to be activated. Following options can be chosen:

• Never - Issues will not be sent to SAP PM

• Optional - Choice of individual users, buy profile or by position

• Always - All issues will be sent to SAP PM

Follow-up Actions

Define actions that will come up when an issue is created

Follow-up Checklists

Define checklists to start after issue creation. Use the toggle to define whether each is launched automatically (on) or manually by the operator (off).