Projects
Here are some links to other sections of docs that may be helpful:
- BPF Locking
- Altus Schedule Shortcuts and Task Types
- Synchronising the Project Task List with a third part tool
- Configuring the Risk Matrix
- Status Update Configuration
- Status Summary Control
Project Percent Complete
NOTE: Percent complete has two parts:
- Status Widgets which are found on the Details tab of Project, Program and Portfolio.
- Data which is used by the Status Widgets, this is stored in the Dataverse.
Note
A fix was introduced in version 2021.01.28.3 that limited Task Completion to 100%. If you are using a version prior to that and you have tasks that are showing as higher than 100% you will see issues in the Project/Program/Portfolio rollup calculations.
How it works
The plugin calculates "Project Duration Weekdays (Days)" and "% Complete" when a task is updated or an external project is synced. This leads to the calculation of "Project Duration Completed (Days)".
The Project Widget simply displays the value set for "% Complete" in Dataverse. This usually takes 10-30 seconds to update after saving or import has completed.
Note
If the external project doesn't set the start and finish dates, the plugin can't calculate "Project Duration Weekdays (Days)" which means the project won't count towards the percent complete of the program or portfolio.
| Project No. | start | end | Project Duration Weekdays (Days) | *% Complete | Project Duration Completed (Days) |
|---|---|---|---|---|---|
| Formula | Tasks Earliest/External System | Tasks Latest/External System | Weekdays(start, end) | Tasks/External System | =Project Duration Weekdays (Days) * % Complete |
| 1 | 3/01/2022 | 8/01/2022 | 5 | 20% | 1 |
| 2 | 3/01/2022 | 10/01/2022 | 5 | 30% | 1.5 |
| 3 | 3/01/2022 | 15/01/2022 | 10 | 20% | 2 |
| 4 | 3/01/2022 | 17/01/2022 | 10 | 50% | 5 |
| 5 | 3/01/2022 | 17/01/2022 | 10 | 75% | 7.5 |
Project KPIs
Description
This feature allows users to configure the KPIs that display in the Project Status pane on the project Details tab within the project.
You can add a New KPI, edit, reorder or delete KPIs

Configuration settings
These settings are located under "Settings > Configuration Settings > Projects > Project Progress"
Display Name: Project Progress
Name: ProjectProgressConfig
You can add a New KPI, edit, reorder or delete KPIs
When you create a New KPI or edit a KPI the following window will appear, you need to set at a minimum a Label and Status Update KPI Field for it to appear on the control.
The Hide for Project Types box allows for hiding this KPI from specific Enterprise Project Types i.e. Minor Projects and Agile Projects if specified.
Duplicating status updates
Description
This feature allows the Project Manager to copy the text from the previous Status Update (based on Status Date) to a new Status Update.
Only the text Status fields in the KPI Breakdown section are copied.
The KPIs are all calculated based on the current data in the system, and the General Status needs to be keyed in and is not duplicated.
If there are no previous Status Updates in the system the user will receive a message telling them "There are no status updates to duplicate"
Configuration settings
These settings control what fields duplicate on the Status Update. This can be used to add new or remove any of the default Status fields.
Note
Kaizen version 2024.04.16.3 addressed a bug which prevented Date fields from successfully being duplicated. If you are selecting to include a Date field in the list of fields to duplicate, it will successfully set the default based on the previous status update value. Please note though that fields of type DateTime (Time zone independent) will likely display with an incorrect time component and possibly Date component (depending on time zone). The value copied as part of the duplication process is simply a default value which can then be adjusted by the user as required.
Display Name: Status Update Duplication Fields
Name: statusUpdateConfig
Documents PCF
The Documents PCF has the following known limitation. This only happens if the project is not opened in Teams. If documents are opened in Teams, the channel id is stored, and it keeps the same project folder, regardless of name change.
The Project Documents Control will attempt to connect to the associated group via two methods (sequentially)
It will attempt to locate this using the Channel Id
- This is populated when the Project is Opened in Teams via the “Open in Teams” button within the ribbon.
It will attempt to locate the group using the linked group and project name.
As a result, it has been observed that if a Project changes names without having a Channel Id populated the project documents control will create multiple folders within the associated group based on the name of the project.
ProjectFormToggles PCF
PCF
Sensei.Kaizen.PCF.FormTabToggles
Overview
The FormTabTogglePCF allows users to toggle the visibility of tabs on or off based on a configuration setting that than on the form itself. By default Altus configuration this is only set on the Project entity using the projectFormTabToggles. The data set by the PCF is stored as JSON to the Form Tabs sensei_tabtogglejson column in the Project Types table sensei_enterpriseprojecttypes. Upon loading of the Project form, this JSON is queried to set the visibility of each tab.

Process
By using the Form Tabs section within Project Types, the user can check on or off each form tab. The list of form tabs is set by default within the PCF as the following forms for Project:
- Information
- Financials
- Tracking
- Resources
- Strategy
However, this can be overridden through the projectFormTabToggles configuration settings, which defaults to being 'Inactive'. This config settings requires a FormId, and AppModuleName.
forms: [
{
formId: "efacbdc9-b08e-467e-935a-0cd34e9ad8b1",
apppModuleName: "sensei_senseiiqforproject"
},
{
formId: "59100881-fae9-4d5b-b520-44f769b21f6a",
apppModuleName: "sensei_kaizen"
},
{
formId: "803e0fab-cf15-ec11-b6e6-0022481839e6",
apppModuleName: "sensei_kaizen"
},
{
formId: "b749f9bc-cf15-ec11-b6e6-002248183efb",
apppModuleName: "sensei_kaizen"
},
{
formId: "670fffd5-cf15-ec11-b6e6-0022481839e6",
apppModuleName: "sensei_kaizen"
}
]

For each form within this configuration setting the PCF processes as follows:
- Lists each tab on the form, retrieving their internal name. Excluding any tabs that end with
ignoreftv. - Creates a fieldname variable that is
toggle_show{InternalName}tab_yn. - Checks to see if this fieldname exists already, and it's checked state. If checked is true or undefined, then Yes is returned, otherwise No is returned.
- Returns the PCF with each toggle item with Labels, and Checked state.
- Stores the tab array of settings in the Form Tabs
sensei_tabtogglejsoncolumn in the Project Types tablesensei_enterpriseprojecttypes. Example:{ "toggle_showdocumentstab_yn":true" }
Upon loading the Projects form, this JSON is queried to determine which fields should be visible or not.

Altus Explorer View
Configuring the Altus Explorer View
You can configure specific fields that have been configured in the Grid Cell Renderer to appear in Altus Explorer.
For example, the Schedule Icon and KPI Icon columns in Altus Explorer are specific fields that aren't accessible via the usual Edit columns function in the view.

Configuration of specific columns of Altus Explorer is found under Configuration Settings > General > Grid Cell Renderer.

For each Table Name, you can add a specific column for Altus Explorer.
To add the Schedule Icon in Altus Explorer:
- Select the Table Name (example: “Sensei Projects”).

- Select the Column Configuration for the column that you want to add to Altus Explorer.

- Enable the Insert as Extra Column in Explorer toggle.

- Click OK to close the Column Configuration screen.
- Click OK to close the Entity Configuration screen.
- Save your changes to the Config Setting.