2024.12.0 (2024-10-22)
New Features
| Area | Title | Description | Reference |
|---|---|---|---|
| General Configuration | Geospatial data types | The geospatial data type is now available on selected entities via the API. This will allow users to convert to On Key Plus without losing On Key 5 geospatial data. This information is not available on the UI yet. Geospatial data is available on the following entities:
|
OKPMGNC-85 |
| Generic User Interface | Legend added for work order timeline | Work Management > Work Orders > Work Order Timeline A legend has been added for the work order timeline bars. This is available from the Help sidebar. |
OKPMUX-123 |
| Generic User Interface | Legends added for work order base status indicators | Work Management > Work Orders; Work Management > Work Requests Legends have been added for work order- and work request base statuses. |
OKPMHPTS-28 |
| Helpfile | Clarified profile functionality ito operational role vs user operational role | User Access Management > Operational Roles New content has been created to clarify the difference in functionality between operational roles and user operational roles in terms of profiles and the inheritance thereof. The difference between a profile linked to an operational role and a profile linked to a user operational role has been clarified. Also, the different methods of adding profiles (ie via the profile manager, the operational role itself and the profile picker sidebar) has been detailed. |
OKPMHPTS-29 |
| Helpfile | New notification template example | General Configuration > Notifications > Notification Templates > Notification Template Examples A new notification template example has been added to the help content. |
OKPMHPTS-36 |
| Work Management | Work Progress Log | The work order progress log feature facilitates effectively keeping track of user activities in the field while executing a specific work order, without altering the work order status unless specified. Users can provide notes per action performed. This feature enhances the accuracy and reliability of activity tracking. Geospatial information can also be tracked per event. The feature consists of the following entities:
|
OKPMWMN-138 |
| Work Management | Parity: Linking attributes to work order status | The addition of attributes on the work order status entity allows users to better classify and track the progress of work orders. The purpose of this feature is to broaden the functionality and flexibility of the existing work order management system. |
OKPMWMN-159 |
Modifications
| Area | Title | Description | Reference |
|---|---|---|---|
| Asset Health | Monitoring Point Trigger Expression Evaluation Dashboards | This feature is designed to provide users with detailed information about monitoring point trigger expression events in order to analyse their impact, diagnose issues, and facilitate resolution. This feature enhances the user's ability to understand and troubleshoot these type of events within the system. The following dashboard were introduced as part of this feature:
|
OKPMAHM-34 |
| Document Management | Bulk deleting attachments | Ability to bulk delete attachments through multiselecting or select all file attachments. |
OKPMDOC-20 |
| Generic User Interface | Report icon on toolbar | A report button has been introduced as a more efficient way of accessing an entity's default report(s). This addition will serve as a convenient shortcut, easily accessible from the entity's toolbar. The primary aim of incorporating this report button is to streamline the process of launching default reports, with just a single click. |
OKPMUX-84 |
| Generic User Interface | Hide Asset Tree in Asset Work Order screen | Quick action to show or hide the Asset Tree panel on the Asset Work Orders Screen. |
OKPMUX-143 |
| Generic User Interface | Enhance Subtask Visibility and Subtask Feedback | Asset task subtasks can now be viewed on work order level:
Also, subtasks are now included in the Complete All Tasks custom action, when completing work order tasks. |
OKPMUX-165 |
| Helpfile | Updated workflow diagram for Configure Asset Type Models | The workflow diagram for configuring asset type models has been improved. |
OKPMHPTS-33 |
| Helpfile | Added better special resource examples to Competency page | Resource Management > Resources Configuration > Competencies The Competencies page has been expanded to not only focus on staff resources, but also describe non-human special resources. Examples have been added of non-human special resources. |
OKPMHPTS-34 |
| Helpfile | Updated asset tree screenshot | Asset and Maintenance Plan Configuration > Assets > Asset Tree > Asset Tree Screen Updated the asset tree screenshot to include the MSI icon. |
OKPMHPTS-35 |
| Work Management | Ability to specify a historic status changed on date | The historic status change time stamp feature provides users with the ability to specify the time of a work order status change and view when the change was synced to On Key Plus. This feature has been implemented within the work order progress log and is represented by two additional fields: Executed On and Created On. |
OKPMWMN-136 |
Bug Fixes
| ID | Area | Title | Description | Reference |
|---|---|---|---|---|
| 106657 | Asset and Maintenance Plan Configuration | Classifications not available in Preprod Database | Default classifications were added to the empty database. Classification allowed values must be added by the user/client. |
H0007307 |
| 109394 | Asset and Maintenance Plan Configuration | Regular Asset Type Component Import Error | Client confirmed this is no longer an issue, so ticket has been closed. |
H0007956 |
| 111157 | Asset and Maintenance Plan Configuration | Standard Task Component Lookup Not Filtering on Asset | The standard task component lookup now correctly filters by Asset as expected. |
H0009092 |
| 111900 | Asset and Maintenance Plan Configuration | Problem with Columns in Task resources usage dashboards | The issue was related to a custom profile that was being applied. The affected profile was manually recreated. This resolved the issue. |
B74487 |
| 111905 | Asset and Maintenance Plan Configuration | String with containing only numbers displayed as numeric value | When setting the values for the attribute, the attribute type was being ignored in the case of it being a string. The internal binding system then converted it to a number. This issue has been resolved by now passing in the attribute type when setting these values. |
H0009582 |
| 112029 | Asset and Maintenance Plan Configuration | Regular asset tasks error | The processes that are supposed to be executed from the task screens when performing actions from the Assist menu, did not execute the batch actions correctly. New processes have been defined to call the correct batch actions. |
H0009482 |
| 115250 | Asset Health Managment | Monitoring Point Trigger Parameters : Unable to add/edit parameters | Resolved the error, users can now add and edit parameters on the Monitoring Point Triggers |
H0011110 |
| 115168 | General Configuration | Follow up work orders - System Options | The control showed the wrong items. It should be 'Closed' or 'Completed'. We fixed the dropdown to show the correct values. |
H0011104 |
| 117237 | General Configuration | Notification Audience Issues | Fixed an issue with loading the Notification Template Audience Query that contained UDF predefined value fields. |
H0011600 |
| 118449 | General Configuration | Duplicate key value violates unique constraint "geographic_data_pkey" | In some cases the same Geographic Data Id was used by multiple records in On Key 5. This is most likely caused by merging/splitting/cloning operations. This caused problems during the convert to On Key Plus. The convert logic has now been reworked to detect these duplicates and make a copy of the Geographic Data for the duplicate scenarios, rather than pointing to the same instances. |
H0011974 |
| 114248 | General UI | Conditional formatting using utcnow() does not work | Conditional formatting involving formulas containing the utcnow() function now works as expected on all columns and rows. |
|
| 114635 | General UI | Filter view after v11 update | This bug was resolved as part of the fix for bug 113415. The CSS properties failed to apply to the context menu following a recent modification in the CSS file. The issue was resolved by introducing supplementary CSS properties to accommodate the scenario responsible for the bug. The count is now visible and is no longer cut off by the scrollbar. |
B75051 |
| 112086 | Materials Management | Problem with ORACLE Interface | Requisitions are now always closed automatically when two issues are processed in parallel for the same requisition. Code copied to domain event which will catch any scenarios where the requisition is not closed because two issues are done in parallel for the same requisition. |
B74501 |
| 114729 | On Key Plus | Another case Asset Number 3237 Like the assets 2890 , 3111, 1433 and 1835 | We’ve done an in-depth investigation and have not yet found exactly why this happens. We can however confirm that for one of the WO it resolved itself when we re-open it and cancel it again. We did this test with WO S145620. It is interesting though that it’s only WO that are cancelled that we see this on. |
B75065 |
| 119213 | On Key Plus | Attribute Value not updating on Work Request | The reported issue has been resolved by replacing the existing single quotations. |
H0012343 |
| 119363 | On Key Plus | OKP Work Request Attributes Dashboard | The correct id is now assigned to the perspective property on the grid. The user can now group by column fields. |
H0012408 |
| 114931 | User Access Management | OKP V11 Security Role Permission dashboard | Fixed a regression bug that was introduced with the over-fetching API performance improvements. |
H0010895 |
| 108748 | Work Management | Duplicate Scheduled Work Orders | After generating WOs there is a delayed side effect to update the relating asset task and their corresponding due tasks. This ensures that On Key's performance is not affected by the work order generation, so users can seamlessly continue, and the necessary updates to asset tasks will happen over time. Thus when you want to run PWOs a second time you need to ensure all delayed side effects are completed, this can be checked by looking at the Delayed Side Effects dashboard. There is also a System Option that you can enable to ensure people do not by accident generate duplicate work orders called "Verify Outstanding Delayed Side Effects" When this system option is enabled users will be stopped by the system if there are outstanding delayed side effects. |
H0008481 |
| 111972 | Work Management | Complete all Task in Preventive Work Order | This bug is no longer reproduceable. It was resolved in version V9.0. |
B74486 |
| 113285 | Work Management | Estimated Duration not pulling through. | Work order Estimated Duration is calculated as follows: - Work order Estimate Duration equals the sum of all work order task Duration values (this is recalculated every time a work order ask is added or removed) - Work order task Total Duration equals the asset task or standard task Total Duration. - Asset task Total Duration is calculated as Duration Per Unit multiplied by Component Quantity. Duration per Unit is based on the asset task's required resource usage if set to auto calculate. Bottomline, Estimated Duration is not calculated from the resource total usage, but from the asset task Total Duration. Refer to the help file for more information. |
H0010448 |
| 115153 | Work Management | WO: Requester Field is removed when opening a Edit: Work Order window | The condition responsible for setting the requester field value to null passed due to a complex issue regarding the isDirty property on the model. We resolved the issue by modifying the condition to determine whether the requester type had actually change which resolved the issue. |
H0011093 |
| 115212 | Work Management | Follow up work order bug | Fixed bug by checking if the follow up work order is being created and then not to return the error for this scenario. |
H0011118 |
How do I's
| ID | Area | Title | Description | Reference |
|---|---|---|---|---|
| 112989 | Asset and Maintenance Plan Configuration | Cumulative meter reading not updating | A new Help topic (Manual Reset Meter) has been created to clarify the behaviour of the meter reset functionality and the relevant fields involved. |
H0010200 |
| 114481 | Asset and Maintenance Plan Configuration | Error when adding regular asset type components | There is a validation on creating a regular asset type component that checks its direct parent and all of its descendants. In this case there is a regular asset type descendant that is marked Deleted - Awaiting Confirmation and also IsActive = FALSE. If you go to the asset type tree properties and select the options to show Deleted - Confirmed and Inactive Objects and click Apply. The specific item is listed under ROOT->D->D-Frame Pump. When attempting to add a new component under the D-Frame Pump, rollout see the descendant with the Deleted - Awaiting Confirmation regular asset type and tries to add the component there, but the validation is more strict and the action is not allowed. The fix is to either confirm the Deleted - Awaiting Confirmation item so that it can go Deleted - Confirmed OR to bring the item back to Confirmed state. It looks like the intent was to actually make this item Deleted - Confirmed, but instead it was marked as IsActive = FALSE. |
H0010814 |
| 119788 | On Key Plus | Error: No Spares found to Generate Requisitions | The message: "No Spares found to Generate Requisitions" is for information purposes only, the work order is still generated. |
H0012373 |