ProjectHub Overview

Overview

The new ProjectHub introduces a revamped framework and interface for easy navigation and creation of Projects within the platform. This experience involves changes to building applications, interacting with designer entities, and updating folder tree organization and navigation. ProjectHub includes a new experience of configuring, creating, viewing, and deploying a project.

Projects are logical groups of entities used to create an application. They must be set up as the first step in developing an application.

Purpose Definition

ProjectHub in version 9 is designed to maintain its integrity while allowing designer users to manage their projects independently of administrators. It provides easy access to the information they need to manage their projects and simplifies the folder tree structure to reduce confusion. With version 9, designers can easily locate and track their projects' status, eliminating issues with finding projects, understanding their contents and dependencies, and tracking project versions across multiple servers. Additionally, this feature enables designers to compare the status of their projects with the deployment server.

Projects in Older Versions vs. Version 9

Designer Folders vs Projects:

In previous versions, Designer folders were used to define projects. However, in version 9, Projects define independent applications, and Designer folders are items that exist within Projects.

Project Configuration/Settings:

In the older versions, only Admin users were allowed to configure all the configurations at system level. With the Projects in version 9, designer users have full access to control project configurations, whereas, in older versions Designer users could only design the application. Users can manage Jobs and Events, configure all the integrations, and monitor project health and activity from the new Settings folder added to the project's folder structure.

Project Permission:

In older versions, all the designer users had access to all projects. But in v9, projects are permission specific. Admin users must give appropriate permission to designer users to access the projects.

Project Dependency:

In the older version, all the entities were allowed to be used within all the projects, but now users have to declare a project dependency to use entities from other projects. Similarly, installed modules are not automatically available in any projects. Users must create a module dependency to use the module.

See Next:

• Project Conversion: This article explains how to convert the projects from an older Decisions version to a version 9 compatible project.

• Create a Project: A starting guide to create your first project.

FAQ

• Can users choose to opt out of the Projects to operate the platform like the prior versions?

  • No, opting out of the Projects View is not possible.
    

• What impact will this have on existing projects?

  • Existing projects will require manual conversion to align with the new projects.
    

• Is transitioning to the new ProjectHub design straightforward?

  • The transition process depends on the organization of folders in legacy projects. Highly organized projects will have the most seamless transitioning process to the new ProjectHub.
    

• How will we manage currently disorganized projects?

  • To address 'messy' projects, refer to the Project Conversion documentation for guidance on streamlining and structuring projects.
    

• What limitations does the new ProjectHub impose on designer users?

  • The new system restricts designers from selecting elements exclusively from the current project or its dependencies. Enabling modules at the project level is necessary post-installation within the environment. For further details, refer to the Dependency Documentation.
    

• Will there be any loss of capabilities with the transition?

  • Unlike earlier versions of Decisions, the ProjectHub prohibits the establishment of circular dependencies, where this was allowed. Projects with circular dependencies will require reconfiguration before migration.
    

• How can users differentiate between items from different projects referencing each other?

  • When utilized within a Flow, the step icon will be modified to display the dependent project icon, indicating the element's association with a different project.
    

• Will there still be regular designer folders or folders not attached to projects?

  • No, designer folders or folders will not operate independently without attachment to projects.