Camms.Project | December 2021
- amani imtiyas (Unlicensed)
Camms is pleased to bring you the Quarterly Product Release Note for Camms.Project.
This quarter we've got a number of exciting new features and enhancements to improve your user experience within the system, which will be available in your Test environment on 4th December 2021 and will be available in your Live instance on 18th December 2021.
1. Introducing additional single-select dropdown lists in the Details object |
More flexibility has now been provided to you when configuring fields in the Details object with the introduction of five (5) new single-select dropdown lists.
How do you configure this?
As an Administrator, you can make the new custom dropdown list fields visible in the end user view and configure its properties (label name, help text, etc.) from the Object Configuration area of the Details Object.
The fields which have been made visible via the Object Configuration area will be shown in the end user view of the Details Object as shown in the figure below.
Figure 1.2: End-user view of the Project Details objectYou can further activate these new fields as columns or filters within the Project Register page by configuring these via the Project Settings > Project Register View page.
Note: There will be updates to the Insights datasets corresponding to the Details Object to include the new Custom fields. Please refer the Camms.Insights Release Note item #5 for further details.
How does this work?
You can customise the options that will be displayed in single-select dropdown lists via the Framework > Project Settings > IPM Lists page.
The IPM List area will show all single-select dropdown lists which have been made visible in the Details Object (through the Object Configuration area) in the project workflows.
You can select the required single-select dropdown list in the left panel and add items (dropdown options) to the selected single-select dropdown by clicking on the Add New List Item icon in the right panel.
Note: Only the items which have the ‘Active’ tick box selected will be shown as options in the respective dropdown list in the end user view.
2. Permitting any staff member to be the primary responsible person for project risks |
You will now have the option to set any staff member in your organisation to be the Primary Risk Owner for project risks. Previously, the primary risk owner was limited to the project board and team members.
How do you configure this?
As an Administrator, you can now navigate to the Project Settings > System Settings page and switch OFF the 'Restrict the primary responsible person of project risks to the project board and team' to let any staff member (who is not a part of the project board and team) to be the Primary Risk Owner for project risks.
How does this work?
When the above setting is turned OFF, the Responsible Person dropdown in the Risk Assessment object will show all staff members in the organisation, allowing users to select a person outside the project board as the Primary Risk Owner, if required.
How can a person outside the project board view the risk(s) which they are responsible for?
If a person outside the project board is selected as the primary responsible person for a particular risk, they will be able to access the details of that risk through the Risk Assessment object or Project Hub > Risks tab only if they have the required permissions to the Risk Assessment object. However, they will now be able to access and update the risk via the My Quick Update > My Risks area regardless of their object permissions.
3. Viewing additional budget details within the project register |
With this feature, we have now introduced the ability to view budget fields such as, Budget YTD, Actual YTD, Variance, Variance %, and Current Year Budget Performance, which are currently available in the Implementation Budget object as columns in the Project Register.
How do you configure this?
The following fields have been introduced to the Framework > Project Settings > Project Register View, allowing the admin to configure them in the register.
Net Budget YTD
Net Actual YTD
Variance
Variance %
Current Year Budget Performance
If you wish to have any of the fields mentioned above as a column to be displayed in the Project Register, then you can navigate to the Project Register View page, and select the ‘Column Visibility’ tick box next to it.
If you wish to have any of the fields mentioned above to be displayed as a filter in the Advanced Search area of the Project Register, then you can select the ‘Search Visibility’ tick box next to it.
You can change the label of the fields to appear in the project register if required. You can further change the order of the new fields by dragging and dropping it onto the desired location.
Note: There will be updates to the Insights datasets corresponding to the Project Register to include the new Budget fields. Please refer the Camms.Insights Release Note item #6 for further details.
How will this work?
When the new fields are activated as columns in the project register, these columns will refer data from the following fields in the current Implementation Budget object.
Field Name | Field which the data is referred from |
Net Budget YTD | Net Budget YTD in Implementation Budget object |
Net Actual YTD | Net Actual YTD in Implementation Budget object |
Budget Variance | Net Variance in Implementation Budget object |
Budget Variance % | Net Variance% in Implementation Budget object |
Current Year Budget Status | Budget performance RAG against the current financial year |
4. Assigning another staff member as the project owner when a project is duplicated |
You can now set another staff member as the Project Owner when a project is duplicated. Previously, when a project was duplicated, the Project Owner of the duplicated project was the same as the Project Owner of the original project; while you had to manually update the Project Owner through the Details object once the project was duplicated.
How will this work?
A dropdown list ‘Select the project owner for the duplicated project’ is introduced underneath the ‘Select Objects’ section in the ‘Object Selection’ step of the Duplicate Project screen. This dropdown list will display the Name and Position (defined through the Project settings > Staff page) of all active staff members in your organisation. The existing Project Owner of the source project will be selected by default.
If you prefer to select another staff member as the Project Owner of the duplicated project, then you can select that member from the dropdown list. In this scenario, two new radio buttons will be displayed as mentioned below:
Create a general position for the existing project owner with the linkages: When this option is selected, a new general position will be created for the existing Project Owner with all their responsibilities such as tasks, risks, issues, etc. in the Board and Team of the duplicated project. The new project owner will not have any of the responsibilities which the previous Project Owner had.
Assign linkages to the new project owner and remove the existing project owner from the project board: When this option is selected, the existing Project Owner will be removed from the Board and Team of the duplicated project, and their responsibilities such as tasks, risks, issues, etc. will be reassigned to the new Project Owner (i.e., the staff member selected from the dropdown list mentioned above). This option will be ticked by default.
You can select the relevant option and proceed to duplicate the project by clicking on the Create button. The system will assign positions and responsibilities based on the radio button option you selected.
Note: The radio buttons mentioned above will only be shown if you select a staff member other than the project owner of the original project from the dropdown list.
When you navigate to the duplicated project, you will be able to view the name which you selected, auto populated in the Project Owner dropdown list in the Details object.
5. Having a two-way link between referenced projects |
With this feature, we have introduced a two-way linkage to link projects to each other. Previously, the Referenced Projects functionality in the Reference object was a surface-level linkage between two projects.
How will this work?
When a referenced project is linked to a particular project from the Reference Object > Referenced Projects tab, that linkage will be created in the Reference object of that referenced project.
For example, if you link Project A to Project B as a reference project (via the Reference Object > Referenced Projects tab of Project B), then Project B will appear in the Reference Object of Project A.
When a referenced project linkage is removed from a particular project, that linkage between the two projects will be removed from that referenced project too.
E.g. Project A and B are linked to each other as referenced projects.
When you delete Project A from the Reference Object > Referenced Projects tab of Project B, then Project B will also be removed from the Reference Object > Referenced Projects tab of Project A.
