...
Camms is pleased to announce the January Feature Release for Camms.Project.
This was released on 23rd January 2021 and includes the following new features and enhancements to improve your user experience within the system.
1. Project Register to show the project portfolio hierarchy
The Project Register has been improved to show portfolios, programs, and projects to provide you with a more user friendly and accurate view of project relationships.
How to activate the Portfolio View in the Project Register?
The portfolio view will be the new default view of the project register; hence will appear automatically. A new toggle button ‘Show Portfolio View’ is now available at the top of the window, to switch between the portfolio hierarchy view and the list view.
You will see a hierarchy with two levels (program at the topmost level, followed by projects) in your project register, when you are in the portfolio view.
If the portfolio level is activated in your environment, you will see a hierarchy with three levels in your project register. The portfolio projects will be shown at the topmost level of the hierarchy. Programs will be shown at the next level, followed by projects at the bottom level.
By default, all hierarchy levels will be expanded. You can collapse them, if required.
You can filter the portfolio view to view only your projects using the ‘Show All Projects’ toggle button (by sliding it to the left).
If you want to go inside the project workflow to view more details, you can click on the Code of the respective portfolio, program, or project.
...
| Info |
|---|
Notes:
|
Can I filter the portfolio view by different filter criteria?
Yes, you can filter the portfolio view using the simple search and advance search functionalities. The following logics will be applied when you filter the projects in the portfolio view of the register.
When the portfolio level is activated:
If a particular portfolio and the program linked to it do not satisfy the filter criteria, but the projects underneath the program satisfy the criteria, then those projects will be displayed as standalone projects in the project register. The portfolio and the program will not be shown in the project register.
If a certain portfolio does not satisfy the filter criteria, but the programs and projects underneath it satisfy the filter criteria, only then will those programs and projects be shown as a hierarchy in the project register.
If a certain portfolio satisfies the filter criteria, but the programs and projects underneath it do not satisfy the filter criteria, then that portfolio will be displayed as a standalone project in the project register.
If a certain program satisfies the filter criteria, but the portfolio above it and the projects below it do not satisfy the filter criteria, then that program will be displayed as a standalone project in the project register.
If the portfolio and project levels in the hierarchy satisfy the filter criteria, but the program level beneath the portfolio does not satisfy the filter criteria, then the portfolio and the projects will be shown as a hierarchy in the project register. Programs linked to the portfolio will not be shown in the hierarchy.
2. When the portfolio level is not activated (i.e. only programs and projects are available):
If a project satisfies the filter criteria, but not the program above that project, then that project will be displayed as a standalone project in the project register.
If a program satisfies the filter criteria, but not the projects below it, then that program will be shown as a standalone project in the project register.
How does user permission work in the portfolio view?
When the portfolio level is activated:
If you have permission to view the program and projects linked to them, but do not have the view permission to the portfolio above them, only then will that program and projects be shown as a hierarchy in the project register. The portfolio will be hidden in the project register.
If you have view permission only to a project, but do not have view permission to the programs and portfolio above that project, only then will that project you have access to, be shown in the project register as a standalone project.
If you have view permission to a portfolio, but not for the programs or projects below it, then that portfolio will be displayed as a standalone project in the project register.
If you have view permission to the program, but not for the portfolio above it or the projects below it, then that program will be displayed as a standalone project in the project register.
If you have view permission to a portfolio and the projects beneath the programs, but do not have permissions to view the programs, then the portfolio and projects will be shown as a hierarchy in the project register. The hierarchy will be of two levels; portfolio and projects underneath it.
2. When the portfolio level is not activated (i.e. only programs and projects are available):
If you have view permission only to a particular project, but do not have view permission to the program above that project, then the respective project will be displayed as a standalone project in the project register.
If you have view permission to a program, but not for the projects below it, then that program will be displayed as a standalone project in the project register.
Can I get an export of the portfolio view?
Yes, you can export the portfolio view to an Excel sheet by clicking on the ‘Export data to Excel’ icon.
2. Update Primary Strategy from Linkage object when an action is linked to the project
The ‘Mark As Primary’ feature in the Strategy Linkage tab in the Linkage object used to be disabled when an action was linked to the project. Camms has now made the primary strategy editable; allowing you to directly update the project’s primary strategy from the Linkage object when an action is linked to the project.
Once you update the primary strategy in the Linkage object, the system will automatically update the strategy of the action which is linked to the project.