RoadMap

Dependency Graph​

🎉 Application Assets​

The application currently cannot load external assets due to the absence of asset loading support on our web server.

• Help Page assets proxy
• Handle cookie authentication

Work Assigned​

The task feature within the portal is currently lacking in sufficiency, and its implementation remains incomplete. This is primarily due to roadblocks encountered in data structure and por layout decisions. The business has expressed a high level of interest in this feature, with expectations for an improved experience compared to what is currently implemented in ProCoSys. Additionally, it should encompass all the various task types offered by Fusion, including PIMS, Fusion Task, NCR/Query, and more. We should also accompany this with an enhancement proposal to further develop and enhance this feature.

User Feedback​

The Project Portal should serve as a platform that actively encourages and facilitates user feedback and the initiation of feature requests, with the goal of seamlessly integrating their valuable input and suggestions into ongoing developments. In pursuit of this objective, the Fusion Core Team has proactively introduced a dedicated service that seamlessly integrates with "ServiceNow."

• Add link to service now

Service message enhancements​

The Service Message feature is nearing completion, with just a few enhancements left to be implemented. Specifically, if a user has hidden the Service Message icon in the top bar, it should reappear when a new message is received. Additionally, refining the scoping of messages is crucial to prevent user confusion.

• Show Notification icon and System messages if item is present
• Scope Service Messages to project-portal
• Scope service messages to applications available in context

Portal Administration​

The application will appear under app category Portal utilities alongside Service message application and the context explorer

As our project portal continues to expand with more contexts, the demand for an administration tool has become apparent. This tool primarily serves developers and portal administrators, empowering them to effectively manage the project portal.

To ensure secure and controlled access, this administration tool should be developed as a Fusion application and made accessible exclusively to users possessing the Fusion.ProjectPortal.Admin role.

This approach embraces role-based service applications, where access is contingent upon specific roles. The administration tool will be categorized under "Portal Utilities," alongside other applications such as the Service Message application and the Context Explorer.

The Portal Administration Tool must fulfill the following acceptance criteria:

1. Administrative Work Surface: The tool should enable administrative users to effectively work with and view project facilities and contracts.
2. Context Onboarding: Administrators should have the capability to onboard new contexts, making it a seamless process.
3. Application Onboarding: Users should be able to onboard new applications, simplifying the application integration process.
4. Connect Applications and Contexts: The tool should facilitate the connection of applications with specific contexts, ensuring that they operate harmoniously within the portal environment.

Notifications Update​

Several enhancements are required for the notification section in the portal, encompassing both user interface (UI) improvements and critical core enhancements. Some of these enhancements are dependent on the Fusion Core team, while others are closely tied to the URL handling feature.

• Adaptive card style of Notifications
• Ensure that clicking an action does not navigate the user away from the portal.

Fusion Context Enhancements​

Currently, the "Fusion Project Portal" operates on a context-driven basis, requiring users to specify their intended context before gaining access to any of its applications. While this approach enhances user experience by tailoring functionality to specific needs, it's imperative to recognize that certain shortcuts have been implemented behind the scenes to initially meet the portal's objectives. However, these shortcuts may prove inadequate as we consider the portal's scalability in the future.

This milestone signifies our commitment to addressing system shortcomings through strategic solutions, enhancing functionality, and ensuring long-term sustainability.

• Add IsHidden column to Onboarded App
• The x in the context selector should clear search text not context ?
• Add context type to worksurface
• API endpoints should require ContexId instead of ExternalId
• Menu has items when context is lost
• Add title to onboarded contexts
• If the context is not activated, no applications should be displayed in the menu

Project Portal Landing Page Update​

The portal's landing page appears somewhat sparse today, and it's currently limited to using only the "project master" context type. However, it's important to note that the UX enhancements are still in the proposal stage and have not yet been implemented. These proposed changes aim to enhance the portal's functionality by enabling the utilization of multiple context types across various workSurface / views.

Project Homepage​

Facility Homepage​

Url handling​

User Information and Settings​

The top bar should feature an avatar or icon that, when clicked, opens the user's account and settings. Clicking on it should trigger a flyout or side sheet, providing the user with essential information, including their name, online status, position details, and contact information. Additionally, this menu should offer quick access to "My Allocations," "My Roles," and the "Delve" feature, along with "Portal Settings."

Bookmarks​

This component / module is a element of the fusion core, and given that the CC applications only utilize this functionality, the responsibility for its improvement naturally falls upon the team. The team has been involved in its initial development, which reinforces their accountability for enhancements.

These enhancements encompass:

• Offering comprehensive user information in cases where no bookmarks have been created.
• Ensuring proper error messaging for situations where issues arise during usage.

It's important to note that this feature has yet to be integrated into the workspace applications, making it less pressing in terms of prioritization.

Project Portal Configuration​

As we move forward, we need to improve our configuration and add new GitHub actions. This will make our processes more flexible, efficient, and secure while also automating tasks and streamlining our workflows. These changes will help us adapt to new requirements and work more effectively.

• CI: Set up Github action for automatic test runs on PR (backend)
• Add Dynatrace to applications

Project Portal Branding​

The Project portal has adopted the Fusion branding, potentially causing confusion. Should the portal maintain a distinct branding identity, complete with its own logo and related elements? While the portal is indeed fueled by Fusion services and integrated within the Fusion environment, the question remains: should it possess a unique and prominent identity?

Global Portal Search​

The Global Portal Search empowers you to search across any dataset consumed by the application. The application should have the capability to register datasets or search endpoints for this global search. Additionally, the search functionality can extend to include context and other applications. Search results can be presented within a dedicated search application, a side sheet, or a dropdown menu. The action triggered upon clicking a search result should be determined by the developer responsible for supplying the current search item.