Notification inbox

Omnilinker tells you about things that need someone: an alert rule that fired, stock running low, a marketplace account that needs reconnecting, a label that did not print. Every notification lands in your inbox. How loudly it reaches you (right away, in a digest, or in a daily summary) is your choice; see How I get notified. Everyone who is signed in has an inbox. You need no permission to use it.

​

The bell

The bell in the top bar shows how many notifications need action: ones you have not acknowledged, that are not snoozed and that did not clear at their source. Above 99 it shows 99+. Click the bell to open a short list:

• Needs you now: notifications that reached you right away. Each one has quick buttons: Acknowledge, 1 h and Tomorrow (snooze until tomorrow at 08:00), and Open when it links to a page.
• Bundled: notifications waiting for your next digest, with the time it goes out, for example “Bundled · next digest 14:00”.
• Earlier: notifications kept for your daily summary. They show only when you switch the list from Needs action to All.

Each section shows the latest few. Click a notification to open it in the inbox, or click Open inbox. Settings opens How I get notified. Press Escape to close the list.

​

Pop-ups

When a notification reaches you right away, a pop-up appears in the corner of the screen with its severity, title and text, and the buttons Open and Acknowledge. It closes by itself after a few seconds, or when you click ×. Notifications that go to a digest or a summary never pop up.

​

The inbox

Open Notifications > Inbox. The page has three columns: views and sources on the left, the list in the middle, and the open notification on the right. The line at the top summarises your settings, for example “Critical right away · High, Medium every 1 h · Rest at 08:00”. Click it to change them.

​

Views

Under Sources, each module that has notifications needing action is listed with its count. Click one to show only that module’s notifications; click it again to show all of them.

​

Threads

The list groups related notifications into one row, called a thread: notifications from the same rule or about the same thing, raised in the same hour. A row shows the latest title and text, the source, and tags: With Most urgent first, the default sort, the Inbox, Unread, Assigned to me and Snoozed views are split into sections: Needs you now, Bundled and For the … summary. Within a section, the highest severity comes first. Choose Newest first to see one list by time. The list shows 50 threads at a time; Show N more loads the next ones. To search, press / or click the search box and type. The search matches the title and the text of each notification.

​

Read a notification

Click a row, or move with J and K (or the arrow keys). Opening a notification marks it as read. The right column shows:

• the severity, the source, and when it was raised;
• a line saying when it escalates and to whom, for example “Goes to Anna Nowak at 14:30 unless someone acknowledges it.”, or that it cleared at its source;
• What happened: the text, and the details its source sent, such as the product, the merchant or the price;
• All N in this thread, when the thread holds more than one notification, each with its own Open link;
• Activity: when it was raised and by which module, why it reached you the way it did, whether an email went out, when you read it, who acknowledged it, who it is assigned to, and any escalation still to come.

The activity explains the delivery in words, for example “Reached you right away because it is Critical.”, “Bundled because its rule fired too often this hour.” or “Escalated to you: it was not acknowledged in time.”

​

Act on a notification

The buttons act on the open thread, or on every thread you ticked. Snoozing does not stop an escalation: an alert you snoozed still escalates when its time comes. To stop it, acknowledge it. Mark unread appears on an acknowledged notification. It makes the notification unread and open again, so it is back in Inbox.

​

Work on many at once

Tick the checkbox of each thread, or press X on the open one. The checkbox in the header ticks every thread in the list. The header then shows how many are selected and the buttons Acknowledge, Mark read and Snooze 1 h. Mark all read, shown while you have unread notifications, marks every notification you have as read. It does not acknowledge them.

​

Keyboard shortcuts

The shortcuts follow the character you type, so they work with any keyboard layout. Keys held with Ctrl, Alt or the Windows or Command key are left to the browser.

​

Repricer rules that can’t set a level

When a price level that a repricer rule writes is handed to another system (see Who sets a level’s prices), the rule stops setting it, and its people get one notice per rule: “Repricer rule “‹rule›” can’t set ‹level› any more”. It goes to the rule’s creator, the person who last changed it and the person who changed the owner; when none of them is known, to administrators. Opening it shows, in place of the usual details:

• What happened: the Rule, the Price level, who it is Now set by (for example Managed by another system) and Since when.
• Why: “A repricer rule writes only prices Omnilinker owns. Another system manages “‹level›” now, so rule “‹rule›” skips it.”
• Fix: choose one:
  1. Make Omnilinker the owner of “‹level›” again opens the level’s Who sets ‹level› dialog. Without the Change who sets price levels permission it says “Ask someone who can change who sets price levels”.
  2. Point the rule at another level opens the rule in the editor.
  3. Pause the rule asks “Pause rule “‹rule›”? It stops proposing prices until you resume it.” and then says the rule is paused.
  The last two need Edit rules; without it they say “Ask someone who can edit repricer rules”.

“This notice clears when the level is Omnilinker’s again or the rule is repointed, paused or deleted.” A cleared notice shows no fixes.

​

Prices changed in your ERP

When a price changes in your ERP on a price level Omnilinker sets, Omnilinker keeps its prices and sends one notice per connection and level while the difference lasts: “Prices at ‹level› were changed in ‹ERP›”, with “Omnilinker kept its prices. Open the notice to see which prices differ and when the change was found.” Opening it shows the level’s page on the connection, with the changed prices and the choice of one writer; a notice sent before this page existed opens the connection’s Price levels tab. It goes to the people who have the Change who sets price levels permission, or to administrators when nobody has it. It clears by itself when the prices agree again, or when the level’s owner or mapping changes. See Prices from your ERP.

​

Repeats and duplicates

When the same alert comes again shortly after the first, and the first is still open (not acknowledged and not resolved), Omnilinker does not send it twice. It counts it on the first notification instead: the row shows ×2, ×3 and so on, and the activity says “Repeated once more” or “Repeated N more times”. If you had read it, it becomes unread again. How long “shortly” is, 5 minutes by default, is set on Limits and retention.

​

Notifications that clear by themselves

Some sources tell Omnilinker when the problem is gone, for example when stock is back above its reorder point. The notification then shows Resolved and “The problem cleared at its source (…)”, moves to Done, and stops escalating. You do not need to acknowledge it. A notice that prices changed in your ERP clears this way when the prices agree again.

​

What you get notified about

Each module decides who gets its notifications and how serious each one is. The severities, from highest to lowest, are Critical, High, Medium, Low and Info. Notifications are written in your language, as set on your account.

​

How long notifications are kept

Notifications you acknowledged, and ones that cleared at their source, are deleted after 180 days by default. A notification that still needs action is kept until someone deals with it, however old it is. Your administrator sets the period on Limits and retention.

​

Troubleshooting