2024.13.0 (2024-12-10)

New Features

Area Title Description Reference
Architecture Licence management

Licence management is the process of tracking, documenting and controlling how and where software is used within the organisation. This licensing process allows Pragma to track, evaluate and guarantee how software is being handled and assure that users are using licences appropriately and on the correct terms.

Currently, none of the OKP tenants have licences. To address this situation, it is essential that Pragma implements a gradual approach to introducing licences and conducting licence checks.

The phased introduction of licences will allow for a smooth transition and give tenants time to adapt to the new requirements.
By taking a measured approach to introducing licences and licence checks, Pragma can:

  • effectively manage the transition and ensure that all OKP tenants eventually become fully compliant with the necessary licensing requirements; and

  • facilitate the smooth renewal and reissuing of licences.

Phase 1:

  • Introduce current counts in OKP. Implement a base licence which allows users to use OKP without any limitations on OKP’s functionalities.

  • Add licence measures and their count with a default warning threshold and threshold limit (optional, currently defaults to 0).

  • Return warning messages when reaching warning threshold and return error message when reaching count limits.

  • Admin Portal feature toggle to enforce/activate licence measures on demand.

 OKPMARCH-98
Common Functionality Geospatial data entities UI

The enablement of geospatial data types on various entities within our system provides functionality to capture physical location information, specifically GPS coordinates. That information is stored and used within the system.

Users can now capture and the following location types:

  • Point: A single location on a map denoted by latitude and longitude.

  • Line: Multiple points on a map connected by a line, useful for mapping routes or connections.

  • Area: Multiple points that form a polygon, outlining a specific area.

Visualisation tools

An interactive map is now integrated, providing the ability to visualize and interact with the geospatial data directly. This tool is designed to offer users a robust set of capabilities for working more effectively with location-based information.

Geospatial enabled entities

This geospatial feature has been enabled on the following entities within our system:

  • Regular assets

  • In-Place Assets

  • Placeholder assets (empty)

  • Placeholder assets (filled)

  • Sites

  • Locations

  • Work request

  • Work orders

  • Resources

  • Sections

  • Monitoring point reading

  • Work order progress log

 OKPMGNE-148
Common Functionality Ad hoc running of scheduled jobs

The feature gives users visibility of all system jobs and their execution schedules and the ability to run some of these jobs on an ad hoc basis using a custom action. Every job that can be manually run using the custom action will have a unique "Can Execute xxx permission". Only users with this permission will be allowed to run the job. Only a single instance of the job can be queued for execution at any point in time. Jobs can be queued from both the Admin Portal and the On Key Jobs dashboard.

 OKPMGNE-153
Common Functionality Roll out UDFs to attributes and asset attribute entities

UDF functionality has been rolled out to the following attributes and asset attribute entities:

  • Attributes

  • Regular asset attributes

  • In-place asset attributes

  • Placeholder asset attributes

  • Regular asset component attributes

  • Placeholder asset component attributes

 OKPMGNE-154
Helpfile Create health indicators help content

System Management > System Health > Health Indicators Screen

Help content has been created for the Health Indicators dashboard.

 OKPMHPTS-38
Material Management Approval workflows of requisitions

The approval workflow of requisitions functionality allows organisations to streamline their requisition approval process by implementing a multi-level approval workflow based on predefined values and user defined criteria.

Clients can opt into this feature by enabling it per site. Approvals can be setup to be required on requisition header or requisition item level.

The feature consists of the following main process steps, with the entities indicated below:

Configure roles and link roles to users:

  • Approval Roles

  • User Site Approval Roles

Create the approval matrix

  • Approval Workflow

  • Approval Workflow Expression

  • Approval Workflow Expression Approval Role

Feature in action

  • My Requisition Approvals

  • My Requisition Items Approvals

Approvals

When a user updates the requisition status to Approved, the system checks whether approval workflows are enabled for this site and then the relevant expressions. For each matched expression, a workflow of approvals is required. Where no expressions match, the normal user approval limits will still apply.

Users are able to view approvals required on their My Requisition Approvals and My Requisition Item Approvals dashboards. All Approvals can be viewed per requisition and requisition item level.

 OKPMMTM-33
Work Management Service level agreements

The service management functionality provides the ability to measure, monitor, and manage Service Level Agreements to ensure that work is completed within the expected timeframe.

The progress of SLAs are measured by tracking the elapsed time between SLA-significant work order statuses. When a work order is placed in the status that is configured as the starting status of the SLA, then that date and time signifies the start of the process. Based on the associated SLA (response time required) and the work order details (Asset Importance, Asset Type, Type of Work, Work Order Importance, Site, etc.), the Expected Completed date can be calculated (the difference between the starting time of the SLA and the Expected Completed value indicates the Response Time). The progress of the work can then be measured based on the necessary response time for the SLA, and in turn, notifications can be sent to users in order for them to manage the process and complete it within the available time.

Enhancements to the feature include:

  • SLAs are available on any type of work order, including scheduled work orders.

  • Multiple SLAs per work order will allow users not to have to add all measures to all SLAs. As a work order progresses and changes, it can be assigned new SLAs or old SLAs that might not be applicable anymore can be deactivated.

A work order SLA can be measured from two different points in time:

  • From the time the work order entered the applicable status range; or

  • From the time the SLA was assigned to the work order.

SLAs and their measures can be reset. This means that users can choose whether the work order SLA percentage should reset to 0 or continue from the current percentage when the work order goes out of status range and re-enters again.

SLA measures can assign values to fields either when the measure starts or ends. Users with current permissions can override these values if required. It is possible not to have any fields assigned. When a measure is reset, the fields will also be reassigned. The main measure will still assign the Required By date.

Triggers are linked to SLA measures. A trigger notification can be activated at a set percentage of the SLA measure. This trigger can then be re-triggered on an interval while the work order SLA measure is still in status range or active.

Service Level Agreements consist of the following entities as part of the Work Management module:

  • Service Level Agreement Classifications

  • Service Level Agreements

  • Service Level Agreement Measures

  • Service Level Agreement Measure Field Assignment

  • Service Level Agreement Measure Triggers

  • Service Level Agreement Measure Trigger Notification Events

  • Work Order Service Level Agreement

  • Work Order Service Level Agreement Measure

 OKPMGNC-48

Modifications

Area Title Description Reference
Document Management Document linking capability rolled out to additional entities

The document linking capability has been rolled out to the following entities: Alarms, Monitoring Points, Meters, Cost Centers, Cost Elements, General Ledgers, Locations, Sites, Suppliers, Material Masters, Requisitions, Requisition Statuses, Stock Items, Warehouses, Resources, Sections, Trades, Users and Work Requests.

 OKPMDOC-29
Helpfile Enhance failure analysis help content

Help content around failure modes, mechanisms, causes and repair types has been enhanced to better guide the user in terms of best practices and how to set it up optimally.

 OKPMHPTS-37
Helpfile Notification template example with boolean fields

The 'New work order assigned email' notification template example has been updated to include two boolean fields: HasServiceLevelAgreement and IsPermitRequired.

 OKPMHPTS-41
Material Management Quick status change on requisitions

Quick status change functionality has been implemented on the Requisitions toolbar and Requisition edit screen.

 OKPMMTM-69

Bug Fixes

ID Area Title Description Reference
113395 Asset and Maintenance Plan Configuration Asset Task conversion bug constraint violation
Asset task suppressed tasks in On Key 5 (which are self-referencing) are invalid and will no longer cause a database conversion error. Those records will now be ignored when converting to On Key Plus.
H0010568
113838 Asset and Maintenance Plan Configuration Go To Ancestor Assist action gives permission tree error
The missing Go To Ancestor Assist action has been added to the regular asset type task suppressed task assist update template.
 H0010669
117360 Asset and Maintenance Plan Configuration IsMSI tick removed when there's work orders on the asset
IsMSI can no longer be changed to false on regular- and in-place assets with linked work orders.
H0011566
112908 General Configuration Notification attachment - fails due to authentication issue
The tenant report settings configuration had a clean password in the database that resulted in the password been decrypted incorrectly. This resulted in failing authentication with Wyn. The password was changed to the encrypted value and all worked from there. This bug is a known issue. Error messages and handling of password fields in the UI and API will be improved in a future release.
Additional information has been added in the error message logs that will help in debugging issues like these in the future.
 H0010299
117187 General Configuration Email address field validations not working causing user access issues
Email validation has been extended to prevent email addresses from having any trailing white spaces.
H0011427
118429 General Configuration Duplicate permission tree dode
It is no longer possible to create duplicate permission tree codes.
B75688
117034 General UI Work order edit mismatch layout from designer
The edit screen does not match the designer screen profile. This bug is a related issue and is caused by the custom conditional attributes on the fields. It occurs when the user deletes the visible field on the designer edit screen thinking that it is a duplicate field, but in fact it is a conditional field. The fields that are left behind are then hidden based on their custom conditional attributes when the profile is applied to the edit screen.
The fix is related to the related duplicate fields bug on the designer. The user is provided with a warning indicating that if the element is deleted, its custom conditional attributes will be lost and element descriptors are visible to indicate that the fields are different.
 H0011409
117112 General UI Designer template - duplicate fields
The fields identified as duplicate fields are not in fact duplicate fields, but rather fields which share the same titles but contain different model values and custom conditional attributes which on the work orders update screen hides and shows the different fields based on the custom conditional attributes.
To solve this, element descriptors have been added to indicate to the user that the fields are different and a warning message lets the user know that if the element is deleted, all custom conditional attributes on the element will be lost.
H0011408
118028 General UI Work order dashboard filter (on Predefined Value) doesn't want to clear
It is now possible to apply a filter and clear the filter successfully on a column that contains a predefined value.
H0011872
113231 On Key Plus On Key 5 contact information not converting to On Key Plus
Contact information now successfully converts to from On Key 5 to On Key Plus.
H0010328
114799 On Key Plus Duplicate Allowed Values allowed on attributes
Added a migration that does a precheck for duplicate attribute values and descriptions. The Code, ID and values of the duplicates are returned to the user requesting them to remove any duplicates before migrating.
 H0010800
118580 On Key Plus Work order Status Change button not showing any options
This bug has been resolved as a related bug 117464. 
H0012038
121557 On Key Plus Profiles not working
There was a issue on the saving of the record on a profile where the Geographic Data tab was removed. This caused the saving process to stop. A fix was added to skip geographic data logic if its was removed.
H0012930
121627 On Key Plus Main menu views set up in V12 not working in V13
There is a existing bug on the menu designer where if you update the name of the menu profile without opening it first. When updating the profile name
without selecting it first, it takes the current view in the menu designer and saves that as a profile.
123803 On Key Plus Notifications and Triggers
Resolved issue where email was not sent for a NotificationTemplate with an AudienceQuery configured with multiple email fields if one of the fields returned no value.
H0013594
119207 System Management Designer: Custom profile behaving incorrectly
The incorrect list items were added when a user removed and re-added the "Requester Type" field via the designer, then saved the profile. This was resolved by introducing an alternative base template and new logic to ensure the correct data source is assigned to the field.
H0012187
111444 Work Management Unable to specify the WO Task Code when adding a Spare using the Feedback Tool
The lookup was added in later version, the field is no longer greyed out.
H0009638
113808 Work Management Different work order task movement data for split and merge
On the work order split action, the work order Code on the movement work order now references the source work order. The work order Code now correctly shows on the task movement work order.


H0010642
114251 Work Management Generate work order with duplicate monitoring point type tasks
Scheduled work orders for assets with tasks using the same monitoring point can now be successfully generated.
H0010811
114737 Work Management Generating work orders from proposed work order dashboard not finding entities
A fix has been implemented to resolve the timing issue when the application boots up.
H0010926
117464 Work Management Available allowed work order statuses not showing as it should
The status restriction logic was not being applied to individual statuses as expected and styling issue were cause by the status list being overwritten with existing styles. The status list restrictions logic has been refactored and a fix applied to the cloning process of the status list to ensure all restriction styling is applied correctly.
H0011692
118550 Work Management Cannot update coded non stock item unit price
It is now possible to update the unit price of a coded non-stock Item on a work order task spare.
H0012014
121378 Work Management Profiles error
There was an issue on the Designer when removing a field and then re-adding it again where it found the incorrect data for the dropdown.  The issue was resolved by using the base template to locate the item again.
 B76319
121384 Work Management Work order profile issue
There was an issue on the saving of a record on a profile if the Geographic Data tab was removed by the user. This caused the saving process to stop. A fix was added to skip geographic data logic if it the tab has been removed.
 B76338

How do I's

ID Area Title Description Reference
118927 General UI Unable to Save Create Regular Asset Entity
The issue seems to be a syntax error. 
The user used this kind of notation: RegularAsset->ProcessedLocationPredefined_Value.
ProcessedLocation should be used instead, meaning the UDF name.
Example:
Rule: When Processed By = Person 1, the Processed Location must be Cape Town. 
If the user uses below configuration (as reported in this bug), it will not work:
- Condition: RegularAsset->ProcessedByPredefined_Value = ‘Person 1’
- Rule: RegularAsset->ProcessedLocationPredefined_Value = ‘Cape Town’
The following configuration must be used instead:
- Condition: ProcessedBy = ‘Person 1’
- Rule: ProcessedLocation = ‘Cape Town’
Meaning: ProcessedBy instead of RegularAsset->ProcessedByPredefined_Value
H0012130
117905 Work Management Issue with follow up task
Regular asset task follow up tasks with status Deleted Confirmed are always ignored when their inspection tasks fail. This is by design.
B75541