What is new in sprint 121?
DFO
Safe Work – Incidents – Overview
Dynaway Prototype
There are two menu items available to view incidents in F&O - SafeWork > Incidents:
Here you can see all incidents created, add new ones and edit existing ones:
Details shown in the Safe Work Incident overview are:
- Incident ID
- Incident type
- Description of the incident
- Functional location (linked to the asset or location where the incident occurred)
- Worker involved in the incident
- Incident date and time
- Lifecycle state (e.g., New, In progress, Closed)
- Whether the incident is marked as Active
- Notes field (for additional context or observations)
Visibility and content:
- If a functional location is defined, it is displayed as a link for drill-down.
- If a worker is assigned, their name is shown and clickable.
- Lifecycle state controls workflow tracking and progress.
- Notes can be used for documenting follow-ups, root causes, or corrective actions.
Maintenance Outage – Calculate Capacity load and Item forecast
You can now calculate capacity load and item forecasts, supporting more precise and informed scheduling of maintenance outages:
Tasks – Checklists
You can configure checklist with instructions which could be used when working on task. To add checklist to task you should set up first maintenance checklist template (Asset management > Setup > Maintenance Checklists > Maintenance checklist templates) by setting parameter "Used for task" to "Yes":
When parameter "Used for task" is checked then only following types of checklist lines can be added to checklist: text, header, variable. When you would try to set parameter "Used for task" to "Yes" on maintenance checklist template which has already some lines, then it is possible to do that only when checklist lines are of type: text, header or variable.
When you have configured maintenance checklist template, then you can select it in required task type in the field "Checklist template" (Asset management > Setup > Tasks > Task types):
Only maintenance checklist templates with parameter "Used for task" set to "Yes" are visible in the lookup and can be selected on task type.
If you assigned some maintenance checklist template to specific task type, then after creating task with this task type, all checklist lines are automatically copied from maintenance checklist template to task checklist (attachments are also copied automatically from checklist template lines to task checklist lines).
You can preview task checklist by going to task page (Asset management > Tasks > Active tasks) and clicking in top menu the button "Checklist".
Then you can see page "Task checklist" in which there is visible task identifier, task start date, related asset with functional location and all checklist lines copied from maintenance checklist template. Please note that you cannot add or remove manually any checklist line.
In the tab page "Line details" you can see details related to selected checklist line (e.g. instructions), you can provide there your notes and check the line when instructions have been completed.
Tasks – Recurrence
You can create time bound recurring tasks based on the setup done in the setup form "Recurring tasks". The service used for automatically creating these recurring tasks is "Create recurring tasks".
In "Recurring tasks", the setup is based on Task type, Asset, Start date, Period, and Period frequency these are mandatory fields. The Active task, Next task and Next date are display fields. The active task shows the number of active tasks that got created by this recurring task setup, the next task and next date field shows the lowest dated (which is near to today) active task ID and its date. You can jump to task shown in the next task by clicking it.
The task type is primarily linked to the recurring tasks; there is a display field called "Recurring tasks" which shows the number of recurring tasks set up for the respective task type.
There is a button "Recurring tasks" which takes you to the "Recurring tasks" setup form and filters it based on the task type you had active.
The "Create recurring tasks" service has two parameters period frequency and period, which is used to calculate the end date (till which future date the task needs to be created). There it the "Records to include" section too which is used to filter recurring tasks setup for particular assets, task type, period etc.
Based on the "Recurring tasks" setup and the "Create recurring tasks" service parameters, a recurring task with a defined Period and Period Frequency, example Period - "Quarter" and Period Frequency - "2", with the "Create recurring tasks" service parameters as Period frequency - 2 and Period - Year, will a create recurring task for every two quarter for the next two years from the start date mentioned in the recurring task setup.
If there is an existing task already based on the combination of date, asset, task type it will skip the task creation of this combination and it will show the warnings if the "Verbose" in User options > Preference > Miscellaneous is turned on for the user.
The task created will have the description and assigned worker group copied from the recurring task setup.
Note
- If the recurrence setup dates are changed after the initial setup and the service is run, the task will be created based on the new dates only and it will not validate for if there is any in same quarter or month based on the setup in recurring tasks. Example - Start date in set as 01 Jan 2025 , and you want it to be created once for every quarter for next one year, after the task gets created by the service. You change the setup to 02 Jan 2025 and now run the same service, it will still create new task for each quarter for the next one year, but it will not look if there is already existing task for the quarter as the date calculation will be different.
- If you manually add a task and the task which is going to be created by the batch job is in the same combination of date, asset and task type it will skip it and throw a warning if the "Verbose" is turned on.
Tasks – Asset – Event History
You can now view tasks as part of the event history for assets:
Forms – Mobile Report
This functionality allows users to navigate to the mobile application, where they can access the specific form report(s). Multiple forms can be selected and opened at the same time. Users can print or download the documents for further use.
Mobile – Dashboards
Dynaway Prototype
You can now view and setup user relations for dashboards in F&O:
Sample Control – Merge Lots
You are now able to select multiple control lots from a sample control and merge the related assets into a new control lot. This is useful for managing control lots where the number of active assets is low.
The selected control lots will become inactive, and all active assets will be part of the new control lot. The number of active assets selected is validated against the control lot size if set up on the sample control.
DMO
Cannot update attributes without enabled module configuration for adding
We fixed an issue in which both module configurations for attributes - update and add - had to be enabled for the user to be able to update an attribute.
Now the permissions are as follows:
ADD configuration |
UPDATE configuration |
Able to Add |
Able to Update |
Able to Delete |
Enabled |
Enabled |
Yes |
Yes |
Yes |
Enabled |
Disabled |
Yes |
No |
No |
Disabled |
Disabled |
No |
No |
No |
Disabled |
Enabled |
No |
Yes |
Yes |
Additionally, if the user can only add attributes, they are allowed to update and delete attributes they have added, as long as they are on the attributes page.
Show purchase requisition info on purchase order tiles
We have concluded the first step in improving the purchase order information in relation to purchase requisitions. Now the user can go directly from a purchase order line to the purchase requisition. Purchase orders show their lines and which purchase requisition they belong to. Purchase requisition lines in turn shows which orders they belong to.
Safe Work - Improvements
We continue to improve Safe Work to provide a better User Experience.
In particular:
- Added section labels: "Default lists" and "Created lists"
- Updated "Favourite" to "Favorite"
- Renamed "Last visited" to "Previously viewed"
- Added icons for Favorite and Previously viewed lists
- Enhanced list appearance and updated the color and style of the count displayed on the list
- Improve view mode of not editable Saved Search lists. When in View List mode:
- The * (required), 'X' (clear) button and the count shown in the input field is hidden.
- The opacity (disable state) on the fields and page is removed.
- Improve sort order consistency
Incident module in progress
Incident module has been created. This includes a similar behaviour like Permit and LOTO. In particular:
- new page for incident saved search list
- new page for create/edit/view incident saved search list
- new pages for search incidents
- new pages for favourite and last visited incidents
- new page for incident details
- new page for report incident details
- new page for report incident lists
- new page for analysis of incident lists
- new page for creating incidents