Update State With Remark and Reason Code

Update State With Remark and Reason Code

This functionality can be used for adding remarks and related reason codes to maintenance request lifecycle state logs. This is especially useful when you want to keep records of what the reason was for rejecting a maintenance request, which can be done in a categorized way.

Setup

The setup includes:

1. License - Make sure that the following licenses are imported to your environment:
   1. Advanced Asset Management (DynAAM).
2. Configuration keys - Enable the following:
   1. Advanced Asset Management (DynAAM).
3. Security Roles - To provide users with a more granular level of access control, assign the following to F&O system users:
   1. View permission: Maintenance clerk.
   2. Managing permission: Maintenance manager.

Adding a remark and reason code when updating a lifecycle state

To use the functionality, go to Asset management > Maintenance requests > All maintenance requests > Lifecycle state > Update maintenance request state.

Once opened, you can see the the following after selecting a new valid lifecycle state:

• A 'Remark' input field is shown.
• If the current maintenance request's lifecycle state has 'Remark mandatory' on, a value in 'Remark' input must be provided.
• If there are any pre-defined remarks for the selected lifecycle state, it's possible to select one of the pre-defined remarks from the dropdown grid:
  • The maintenance request lifecycle state remarks and reason codes can be set up by modifying the following grid:
    • Asset management > Setup > Maintenance requests > Lifecycle states > Lifecycle state remarks.
• You can select a remark and change it any way you want. The remarks setup is not fixed.
• If at least one 'Reason code' exists, the 'Reason code' read-only input field will be shown. If a remark is entered for a lifecycle state and the same remark exists for a different lifecycle state, the reason code will be updated automatically. See screenshot 01 below as an example.
• Remark and reason code can be added to the lifecycle state log only when you manually update the request lifecycle state.
• If multiple requests are marked and updated, the selected remark and reason code are used on all marked requests, similarly to Actual start/end date.

When the maintenance request lifecycle state has been updated successfully, the entered remark can be viewed in Asset management > Maintenance requests > All maintenance requests > Lifecycle state > Lifecycle state log.

01: An example of a maintenance request being updated from the 'New' state to the 'Rejected' state. In the 'Remark' field, a value can be chosen for the remark, and the 'Reason code' read-only field is shown.