RoadMap

About 3 min

Road map

Some task for planned feature are skipped to meet the dead-line of Project Portal

CompleteMinimum viable productActive - Currently working onPlanned - not started on

Authentication Q1 2022

Core of the Fusion Framework is to provide tooling for executing authenticated service requests.

Developers of the Fusion platform should with minimal effort consume Fusion Services and provide their own.

Developers should be able to configure named clients for services. When using the client it should acquire scoped user identity token for the requested endpoint.

The client should also internally expose requests and responses, which can be managed from the portal (example telemetry, custom headers)

initial modules for moving from ADAL to MSAL

configure and create http clients
MSAL authentication
documentation

Foundation Q2 2022

Fusion Framework is buildt on a modular design.

Functionality for apps and portals composed together by small building block called modules
The framework provides essential modules, but developers can pick or create additional modules needed.

Fusion Framework provides scoped functionality.

Each collection module instances has their own sandbox to not pollute other applications.
When a applications is ejected, all facilitated functionality is disposed.

Fusion Framework Modules are independent and should be interchangeable.

Example: if the technology for authentication changes,
only the authentication module should be replaced.

Fusion Framework is ecosystem independent.

Written in plain TypeScript for future upgrade of libraries or platforms
Tooling for easy development on React

Fusion Framework is the foundation of applications

build once, run anywhere, Fusion Apps should run on any host(portal).
developers can focus more on UI, framework handles complexity

create functionality for adding, configuring and initializing modules.
create interface with collection of essential modules (app and portal)
add type-hinting for working with framework in IDE
tooling for React
documentation
guide

Service Discovery Q2/Q3 2022

Applications consumes data from Fusion services.
The Framework should dynamically resolve services from the host portal.

Developers should easily configure which services the application needs and maintainers see which one are used.

developers should only name the service, then the framework resolves the endpoint and authentication requirements

Ag Grid Q3 2022

Allow application to register AgGrid license for removing watermark.

documentation
guide
cookbook

Events Q3 2022

Since modules are decoupled, the Framework needs a bus to communicate on.

Application can interact with events and prevent default behaviors

Context Q3 2022

Fusion context is scoped data with user-friendly name and follows users throughout session.

Applications present the user with a interface related the to selected context.

The framework needs to facilitate query, filtering and selecting scoped data.

The framework maintains the cache of context, aborts dangling request and throttles queries

Fusion provides metadata about registered applications and configuration for runtime environment.
When loading an application the Framework resolves and provides this information,
which the application uses to dynamically configure before rending.

The framework also keeps track of selected application and notifies when when current application changes.

Bookmarks Q4 2022

Bookmarks are snapshots of application states which users can navigate to and share with other Fusion users.
The framework should facilitate functionality for storing and restoring bookmark.

configurable interface for storing and restoring bookmarks
tooling for React
Cookbook for developing bookmarks
Developer documentation

Widgets Q4 2022

Widgets are small applications which are uploaded to an global storage and consumed by portals and applications.
The framework should manage loading metadata and configuration for the widget.