OperatorFabric 4.13.0.RELEASE is now available.
TL;DR: OperatorFabric 4.13.0.RELEASE adds the ability to see all versions of bundles and download a bundle through the admin screen, a card purging mechanism, and access to current user data through the frontend API opfab.users. The release also enforces the type field in custom screen definitions, includes two dashboard bug fixes, and upgrades dependencies.
Features
The release includes five new features:
- See all versions of bundles in the admin screen.
- Enforce the type field in custom screen definitions.
- Add a card purging mechanism.
- Download a bundle through the admin screen.
- Access current user data through the frontend API opfab.users.
Bug Fixes
The release addresses two dashboard issues:
- A translation issue with the dashboard.
- An issue with the dashboard’s period setting when the application loads.
Dependency Upgrades
Dependency upgrades are listed for the frontend, backend Java services, backend Node services, command line interface, and miscellaneous components. The full release notes list the dependencies and their updated versions.
Migration from 4.12.x to 4.13.0
When registering a custom screen through opfab.businessconfig.registerCustomScreen(…), the type field is now required.
If the type field is not set or contains an invalid value, the custom screen will not be loaded, and an error will be logged to the console.
Ensure every custom screen definition includes a valid type value. The supported types are:
- CARD_LIST
- DASHBOARD
Learn More
Read the full release notes and review the migration guide from 4.12.x to 4.13.0.