Customize the event types

The diary’s Events element picks from a list of types (HSE, Technical fault, Material release…). You can fit that list to your organization: rename, colour, reorder, enable/disable them, and with multiple plants decide which plant’s diary offers which type.

“The diary’s Events element picks from these. Rename, color, reorder, enable/disable; with multiple plants, set which plant’s diary offers which type. (The built-in key and the EBK logic stay.)”

Before you start

• Permission: the diary-structure right — layout:manage or full admin.
• Where to find it: Master data → Diary elements → expand the Events element → the Event types box. (Not a separate tab: it lives where the element itself lives.)

The type set belongs to the organization, not to a site

Event types live at company level: a rename or a colour applies to every site. What is site/plant specific is availability — which plant’s diary offers a given type (see step 5).

Steps

One row per type. On the left a live preview: the badge looks exactly as it will in the diary.

1. Open Master data → Diary elements and expand the Events element.
2. Open the Event types box (its header shows how many types there are).
3. Rename it if your site uses a different wording: type your own name into the field. Left empty, the default name stays (the field’s placeholder shows what that is).
4. Pick a colour from the dropdown (Amber · Blue · Red …). The badge on the left shows the result immediately. Press Save on that row.
5. With multiple plants: in the “Available plants (none = all)” row, tick which plants’ diaries offer this type, then Save plants. If you tick none, the type is available in every plant.
6. Order: use the up/down arrows on the right to set the order the diary offers them in.
7. Disabling: clear the Enabled checkbox and save. The type disappears from the picker.

Disabling does not erase the past

A disabled type cannot be picked for new events, but events already recorded stay — in the diary, in the PDF and in the reports. That is deliberate: an event must not vanish from an audit trail just because you no longer use its type.

If it worked

In the diary’s Events element the type picker appears in your order, with your names and colours — filtered to that plant. Events recorded earlier also show the new name/colour, because the badge resolves from the type key, not from stored text.

Common problems

What you see	Why	What to do
No “Diary elements” tab	You do not have layout:manage (or full admin).	Ask your admin.
I cannot find the Event types box	It is embedded in the Events element’s editor — there is no separate tab.	Expand the Events element; the box is there.
A type does not show up in one plant’s diary	That plant is not ticked in “Available plants”.	Tick it, or clear every tick (that means all plants).
I renamed it but an old name is still somewhere	The name changes in the badge; the event title typed by the user stays as it was.	That is correct: the title is the reporter’s own text, not the type’s name.
HSE still forces a severity	The HSE logic is bound to the key, not to the name — it survives renaming.	Nothing to do; this is deliberate safety behaviour.

Worth knowing

• The key stays, the label changes. Every type has a built-in machine key, and the system binds special behaviour to that — for example that an HSE event requires a severity. Renaming swaps the label only, not the logic: a label cannot switch off a rule.
• Colour is not decoration. Alert economy: red should be the rarest. If every type is red, the important one disappears into the noise.
• Reports filter on the type. In event review the type is a filter value — which is why it pays to keep the set narrow and consistent.
• You cannot add a new type. The set is the seven built-in types; those you can tailor. If you need a category that is missing, tell us — that is a product decision, not a setting.

Related

Edit the diary elementsThe Events element this editor is embedded in.

Log an event in the diaryWhat you set here is what the operator sees there.

Review and export eventsThe type comes back here as a filter value.