2023.11.0 (2024-01-19)
New Features
| Area | Title | Description | Reference |
|---|---|---|---|
| Asset Health | Bounds alarms: Creating alarms and managing alarm statuses | When a monitoring point bound is exceeded, an alarm is created based on the monitoring point's linked Alarm Type. This feature manages the status of the alarm in three ways: 1. No auto closing by the system. 2. When a new monitoring point reading is inserted that no longer exceeds the monitoring point bound that caused the alarm. 3. When the corresponding work order reaches a set status: Closed or Cancelled, the alarm is closed by the system. |
OKPMAHM-31 |
| Work Management | Section Trades | A new table has been added to On Key Plus called Section Trades. This is the link of what Trades work in a Section. This table will be used to guide users in selecting a Trade after the Section has been allocated. No server validations will stop users from selecting another Trade that is not linked to the selected Section. |
OKPMWMN-116 |
| Work Management | Using of FMECA setup on Work Order Failure Analysis | This is where failure analysis is captured on a work order. The introduction of the Global FMECA option governs whether the failure analysis lookup lists refer to the global failure analysis master data or whether the lookup lists are based on the specified component's preconfigured FMECA data. The Analysis Component is also implemented. User selects a generic component with a preconfigured FMECA linked to it instead of a user configuring specific FMECA on each component. Furthermore, to reduce the number of clicks while performing failure analysis on a work order, the functionality of selecting the sub-set value and then auto populating the Type value has been introduced. |
OKPMWMN-129 |
| Work Management | Task Priority Weights and Work Order Priority | This feature will allow users to calculate and set the work order task and work order priority based on the following fields: Asset Importance, Work Order Importance, Task Importance and these fields' corresponding weighting set in system options. This work order priority allows the planner to schedule higher priority work first. |
OKPMWMN-145 |
Modifications
| Area | Title | Description | Reference |
|---|---|---|---|
| Architecture | Read-After-Write consistency via API Calls | Provide mechanism to ensure read-after-write consistency via API calls to work around impact of asynchronous replication on database. Integration teams can now decide if a call should be made against the Write or Read database. |
OKPMARCH-154 |
| Asset Operation | Record site and location details in each asset consumption record for analysis purposes | Record site and location details in each asset consumption record to allow analysis and cross-referencing of cost and consumable consumption history. |
OKPMIGAOM-42 |
| Asset Types | Add standard task to component more than once | This feature allows the addition of a specific standard task more than once in the asset type- or asset tree. The user can choose whether to break the inheritance link to the master data standard link. If the link is broken, the user can choose whether a system generated code should be assigned versus keeping the original standard task code. Then if a system generated code is assigned, the same standard task can be added to the same spot in either of the trees multiple times as there will be no duplicate violations. |
OKPMATY-99 |
| Common Functionality | Enhance query language to include 'where I am' as a field | A new function has been included in the On Key Plus query language: my_id() This will allow users to see their own items in On Key. Some examples include:
This feature includes adding the Supplier field on a User. |
OKPMGNE-89 |
| Common Functionality | Alphabetise the results from the main menu filter/search | This feature orders main menu search results alphabetically. |
OKPMGNE-140 |
| Financial Management | Unique identifier for a Budget required | A new Code field has been added to Budget records in order for integrations teams to more effectively identify a budget record. |
OKPMFIN-35 |
| Generic User Interface | Grid UI - More Records Available Grid Indicator | An indicator has been added to dashboards and grids if more records are available in the database than what is currently being displayed. |
OKPMUX-144 |
| Generic User Interface | Schema/Profile migrations and validations | Additional profile validations have been added to the system in order to increase the robustness of the migration of profiles from older versions to later versions. |
OKPMUX-146 |
| Generic User Interface | Profile Exchanger | Implementation of profile ehancements including the ability to replace a custom profile. |
OKPMUX-152 |
| Helpfile | Added mention that profiles can be parameterised | On Key Tools > Profiles Added the following sentence to the primary Profiles help page: Parameters can be used in profiles. Parameters are used to easily change the behaviour of the profile without changing the profile itself. |
OKPMHPTS-27 |
| Helpfile | Stock item movement descriptions expanded | Material Management > Material Configuration > Stock Items > Stock Item Screen: Expanded the descriptions of Quantity on Hand and Average Item Cost fields to describe that these fields are populated by the Material Manager Application (On Key Action) if it is being used in conjunction with On Key Plus and an integration has been configured to synchronise these fields. Made reference to the Material Manager Application help files for more information including the calculation formulae. |
OKPMHPTS-30 |
| Helpfile | Configuration examples added | Examples of configuration have been added to the help content for the following entities to guide the user in setting these up: Conditional formatting: On Key Tools > Properties Panel > Properties Panel Functionality > Conditional Formatting Examples User defined queries: Business Intelligence > User Defined Queries > User Defined Query Examples Notification templates: General Configuration > Notifications > Notification Templates > Notification Template Examples |
OKPMHPTS-32 |
| Material Management | Requisition Item Import Service | The Requisition Item API calls are now available as part of the import services. |
OKPMMTM-55 |
| Material Management | Ability to edit requisitions and line items (cost element, Gls etc) | This feature will allow users to edit certain fields on a requisition item when the requisition is in Awaiting Approval status and no transactions have taken place. Allowed field changes: Fin Year Period, Cost Centre, General Ledger, Cost Element, Supplier, Code, Description, Unit of Meansurement, Unit Cost in Spare Currency, Spare to work order currency rate, Quantity Required, Notes, Required On, Sequence Number |
OKPMMTM-63 |
| Work Management | Addition of Analysis Component | An Analysis Component field has been added to the Work Order Failure Analysis Feedback section. This allows the user to select the Analysis Component as part of his/her failure analysis when completing feedback on a work order. |
OKPMWMN-111 |
| Work Management | Add latest status change remark to work order | The latest status remark has been added to the work order table to easily display this on the work order CRUD, dashboard and notifications. |
OKPMWMN-146 |
| Work Management | Work order status classification | The new classification on work order status will aid in the standardisation efforts of business processes and reports while allowing end users a degree of customisation. |
OKPMWMN-149 |
| Work Management | Start on date to be left blank on WO create/insert | Clients need their contractors to indicate when the work will be started. They want to make it mandatory for the contractor to specify when they plan to start so that the retailers can see when to expect the contractor. If it defaults, they can't make it mandatory for them to change. An option to System Options has been added which allows the user to select whether the Start On and Complete By dates on a work order should be auto populated or not. Furthermore, the Start On and Complete By date and time has been added to work order validations in system options. This enables the client to select in which work order status it should be mandatory, if a client requires that it should be mandatory at any point. |
OKPMWMN-155 |
Bug Fixes
| ID | Area | Title | Description | Reference |
|---|---|---|---|---|
| 107381 | Asset and Maintenance Plan Configuration | Component grouping on asset tree | Component grouping now works as expect on the asset- and asset type trees. |
H0007395 |
| 108800 | Asset and Maintenance Plan Configuration | Overlapping text on asset tree view | The issue of overlapping description text in the asset tree has been resolved. |
H0008496 |
| 108876 | Asset and Maintenance Plan Configuration | RE: Profiles with ID fields | The index database indexes have been adjusted to cater for the scenario where the same record IDs are being returned from the server when doing a query builder cross reference. This is no longer causing an exception when trying to cache the records to the index database. |
B74071 |
| 109752 | Asset and Maintenance Plan Configuration | APL Convert Error: Key parent_component_id is not present in table "asset_type_component" | There are invalid subcomponents in the OK5 database where the parent component asset type is null; the asset id is not null; the subcomponent's asset id is null and asset type is not null. A script has been created to fix the OK5 database data by updating the invalid components' development status to Deleted Confirmed and setting their asset IDs correctly. |
H0008899 |
| 109338 | General Configuration | Newly created sites not visible |
The sites that are not visible or are shown as "no rights" are sites that are linked to permissionTreeIds that have been deleted. Looking at the changelog, it seems that the permission tree entities were first manually created and then the site was created with the user setting the permission tree to the one created earlier. Then some of those permission tree entities were deleted. It should not have been possible to do since the sites were still linked to those. The reason why the delete was successful was because the Site->PermissionTreeId currently does not have a foreign key pointing to PermissionTree->Id. The user is therefore not prevented from deleting a permission tree entity if the only thing that is linked to the entity is a site. The following fixes have been implemented: 1. A script has been created that can be run on the client database. The script will fix the data and also add the missing foreign key. 2. The missing foreign key has been added as a migration to prevent this error reoccuring. |
H0008391 |
| 110858 | General Configuration | UDF field not saving change | Boolean user defined fields with Field Type "Predefined" or "Both" now render as lookup fields where the user can select one of the predefined values and save the record successfully. |
H0009055 |
| 107363 | Materials Management | Error when editing material master item | A database migration has been added to nullify empty string fields in order to prevent the validation from triggering. |
H0007458 |
| 108817 | Resource Management | Full Name in Resource screen does not auto populate | Upon saving a Resource record, a check is now performed to determine whether the First Name and/or Last Name value(s) have been updated since the record was created and if so, the Full Name field is repopulated. |
H0008059 |
| 112003 | Resource Management | Default Rate on Trade | The Default Financial Rate Description are now returned when fetching a Trade. |
H0009909 |
| 106841 | Work Management | Status change history of converted work orders (OK5->OKP) does not match with the changelog | This bug was fixed as part of a new feature where the latest status change Remark is now displayed on the work order CRUD screen below the Status field. |
H0007405 |
| 106993 | Work Management | Add latest Status Change remark to Notification | This is not a bug; it is a feature request that has been implemented in V11.0. The latest status change Remark is now displayed on the work order CRUD screen below the Status field. |
H0007449 |
| 107217 | Work Management | Data Summary on Tasks does not open when viewing the second or third Work Order Task | The data summary window that gets displayed is for all the records, regardless of the selection. The same window will be displayed for the first and second work order; and even when nothing is selected on the grid. The issue of the button being non-responsive when opening the window for a second work order has been resolved. |
H0007386 |
| 107330 | Work Management | Error in V8.0 related to a parameter on query builder | On the overview screen, the user is now able to add multiple stock items when there is a profile applied to the stock items lookup. |
B73844 |
| 108496 | Work Management | profiles lookup screen values doesnt retain once selected | When creating a new work request, profiles that have been created on the work request dashboard or via the designer and set as defaults are now being applied as expected. Also, when using the Asset lookup, and applying a profile on the lookup screen, the profile is now being applied successfully. |
H0008046 |
| 108508 | Work Management | MMC OK5 convert error - null value in column "is_inspection" of relation "work_order_task" violates not-null constraint | A script was created to fix the failing database conversion. |
H0008319 |
| 108773 | Work Management | Astron Energy: OKP Staging- Work Order Notification Link status error | It is now possible to change/set the work order status via the Work Order Details screen when accessing the screen via the notification link. |
H0008478 |
| 108906 | Work Management | Work order will not create when asset type is inactive | The asset type property on a work order has been excluded from the IsActive validation. |
H0008567 |
| 109002 | Work Management | Work order Planning tab: Complete By field name incorrect | The label of the field has been corrected to "Complete By". |
H0008673 |
| 110496 | Work Management | #219: Translations not working when using any Lookup lists (eg click to lookup Work Order Status) | Phrase translations were not added to lookup screens, so the raw values were being displayed. Lookups will now correctly show the translated values for the phrases used. |
H0008751 |
Known Issues
| ID | Area | Title | Description | Reference |
|---|---|---|---|---|
| 103455 | Asset and Maintenance Plan Configuration | Development Status changes on children not rolling out to placeholder children | Changing development status on a detail asset type entity directly (eg on regular asset type spares) does not currently roll down to the corresponding detail entities of any placeholder asset types or placeholder asset type components. If the development status on a parent entity is changed and the option to include children is selected, then the development status of corresponding detail entities is updated. This will be fixed in a later release. |
|
| 111659 | Work Management | Requisition Items - No Warning Message Triggered when updating Requisition linked to another Requisition | When updating a Requisition Item that shares the same Work Order Task Spare with another Requisition Item, a warning is not returned to the user that the related Requisition Item will also be affected. |