Hierarchy Configuration
PSknowHOW enables users to define different hierarchy levels that user may require to have to manage a project within. For example, an organization may follow below hierarchy level to manage a project:
Business Unit (Highest) → Account → Subaccount → Portfolio → Project (Lowest)
By default, PSknowHOW suggests 3 levels of hierarchy to create project. However, user has a flexibility to change the hierarchy levels based on the project hierarchy followed in respective organization with the help of database. The upper and lower limit of project hierarchy is 6 & 0 respectively.
Below are the steps to achieve the desired hierarchical level.
Step1
Go to database collection → open hierarchy_levels table
By default, user will see the following existing script
Default hierarchy_levels table
Application view
3. If user doesn’t want any level of hierarchy in respective project, user can clear the collection of above table and run the changes in database.
Good To Know
Hierarchy level label name in the application will be determined by hierarchyLevelName table in database.
It is highly recommended that user shall maintain uniform/same hierarchical level throughout one instance. In case if user opt to change existing hierarchical level, user should delete the existing projects from the application UI, follow the Step 2 above and create desired hierarchy level.
Auto suggestions - when user creates a hierarchical level, he/she has an option to provide option of certain suggestions on the dropdown and these would be fetched from hierarchy_level_suggestions table based on values stored in respective hierarchyLevelId. Please note that whenever we create new hierarchy on hierarchy_levels table the similar hierarchy shall replicate on hierarchy_level_suggestions table
hierarchy_levels table
hierarchy_level_suggestions table
Making Dashboard Dynamic
PSknowHOW allows user to create categories on Dashboard and reshuffle the KPI’s among them based on user’s convenience to use the application.
By default, user will see seven different dashboard tabs on application header. The above 7 tabs can be classified into static and dynamic categories.
Static Category → User is restricted to make any changes on these categories. The Category includes My Knowhow, Iteration, Backlog and KPI Maturity.
Dynamic Category → User have flexibility to personalize these categories based on project requirement and convenience. User also can add/remove these categories within the limit of 0 to 7. It means at maximum 7 user defined categories can be created and at minimum user can remove all dynamic categories to 0.
Below are the steps to achieve the desired dynamic dashboard categories.
Step1
Go to database collection → open kpi_category table.
By default, user will see the following existing script.
Default kpi_category table
Application view
3. If user want to modify existing dynamic category setup-
Adding a new category - In Default kpi_category table, use can insert new record with new “categoryId” & “categoryName” (refer snippet in step 1.2 above) and run the database script.
Removing existing category - User can clear the collection of above table and run the changes in database.
4. When user creates a new dashboard category, in order to setup kpi user shall replicate similar “categoryId” in kpi_category_mapping table along with desired kpiId and Kanban status (true - if user willing to add kpi in Kanban board) and run the database script.
