FLOW-319: Manual.to – Machine message
Description: Added platform messages to Manual.to mapping.
Benefit: User can create a mapping in order to show a manual based on a platform event (eg machine message).
- FLOW-222: Manual.to integration
Description: Manual.to is a solution for digital work instructions. Within 24Flow, a Manual.to mapping component was created, in this way the user can easily link certain context / scenarios in 24Flow to Manual.to. The Manual.to component can be added to a page, the component will take into account the Manual.to mapping and show a relevant manual if required.
Benefit: A user can easily create extensive work instructions. Reduce waiting times by showing in context manuals to the user.
- FLOW-194: integrate components Operator page in Teamviewer & FLOW-248: Teamviewer Settings: Configure which components should be shown in Teamviewer for an operation & FLOW-270: Extend Teamviewer: Component integration
Description: The user can now add components (component picker, checklist, time registration, Manua.lto, …) to the teamviewer page in order to create his own personal cockpit. This is necessary for operators to do all required actions to finish an operation on one screen, so no need to navigate between different pages. With this new feature, the operator can simply select the operation he will be working on and he will be guided with all relevant, in-context, information in order to finish his work. We expect that this reduces waiting times significantly as all information is available to the operator
Settings: Add components to a page where there is a team viewer component.
Benefit: This is necessary for operators to do all required actions to finish an operation on one screen, so no need to navigate between different pages.
- FLOW-204 Teamviewer: UX improvements
Consistent letter type
Remove grid lines from workload graph.
Remove background colors from workload graph: rule by exception, only have part of the bar chart that is above certain capacity threshold in red.
Benefit: Better / easier UX experience
- FLOW-292: Sorting Parameter on 24Flow: Release Lateness component
Description: User can now define his own sequence rule logic. By applying sequencing rules, we can accomplish better delivery reliability and throughput times.
Settings: Go to edit page, and insert the field on which sorting logic should be applied.
Benefit: Better sorting of priorities. User can define his own, or can apply academic, sequence rules in order to maximize delivery reliability and optimize throughput times.