Improvements
Update User Department Setting for Mapal OS Source Companies
We’ve updated the User department setting for Training Managers in Mapal OS Source companies. User departments will now be set upon creation of the user.
Why this Matters
Previously, department details for Training Managers in Mapal OS Source companies weren’t automatically passed through to Flow MS, leading to delays, extra admin, and potential data inconsistencies. With this improvement, department settings are now applied automatically when the user is created—saving time, reducing manual steps, and ensuring data is accurate and up to date from the start.
Benefits
- Reduced Admin Work: No need to manually update users after creation for department info to sync.
- Faster Setup: Training Managers can get started right away without waiting for data corrections.
Improved Data Accuracy: Department settings are correctly applied from the start, reducing errors.
Learner Merges for OS Source Companies
We’ve made an update in the logic of merging learners in Flow for OS source companies. Previously, leaver records were overwritten with new learner data when a merge was actioned in Flow, leading to data discrepancies in Mapal OS.
Why this Matters
This update improves how learner records are merged in Flow for OS Source companies, ensuring the correct record is retained and kept in sync with Mapal OS. It helps prevent duplicate records and keeps learner data accurate across both systems.
Benefits
- Improved Data Accuracy: Ensures the correct learner record is kept in Flow and matches Mapal OS.
- Prevents Duplicates: Reduces the risk of duplicate user records being created.
Less Manual Cleanup: Minimises the need for admin teams to fix record mismatches.
Bug fixes
- Unable to export Module Builder content
- Our users reported that the export function in Module Builder was no longer working. This has now been resolved, and Module Builder content can be exported as a Word document.