Feature: A work order triggers a user notification.
Use: Platform users learn how to open a work order message and enter a decision.
โ
Prerequisites
Know how to create a work order.
Viewing a notification
When a project manager creates a work order with one or more assigned users, Nektar sends each assignee an email notification. The user goes to the Message Centre and opens the message.
Viewing work order assignments
The user opens the message and clicks the Open Work Order link. The work order displays in a new browser tab.
The user reviews the work order, including the start date and line item tasks, which describe the work in detail.
If the user agrees to do the work, they click the Accept Work button at the bottom of the page. The user status changes to Accepted (on the user page and admin page), and Nektar displays a Start Work button at the bottom of the work order page.
To reject the work, the user clicks Decline Work. No further action is required.
Troubleshooting
Popup error
Line item tasks in the work order open in a popup. If the browser returns an error, the user should enable popups for the URL.
Fixing an access error
If the notification link returns an error message instead of opening the Nektar work order, the user should contact the project manager. The error is probably linked to inadequate user permissions.
To solve the problem, the project manager should confirm the user's Permissions group grants access to the asset class in the work order.
Go to the side menu and click Manage > User Manager.
On the next page, locate the user name and the assigned Permissions group.
Next, go to the side menu and click Permission Manager. In the Permissions Group column, select the name of the user's group. Make sure the Assets tab is selected.
Scroll down to the By Definition heading. Confirm the Permissions group grants user access to the asset class in the work order. In this example, the work order has an asset in the A Terminal class. Based on the settings in the screenshot below, this Permissions group does not grant users access to assets in that class.
To solve the user access problem, project managers have two options:
Change the settings in the Permissions group, which would grant access to all users with these permissions.
Assign the user to a Permissions group that already grants access to this asset class.