Release Notes 1.9.8

Freeze Periods at Project Level 

Overview 

Ability to enable and set planning block Freeze Period at the project level.  Setting the Freeze Period on a project can be used in the baseline change control process. The History and Planning phases can also be calculated off the Freeze Period and do not need to be set on the project. 

Admin & Project Properties  

To enable the functionality the new checkbox needs to be selected under Admin | System | Project. By default, this setting is unselected. 

When enabled, 2 required dropdown fields are displayed on the Project properties page 

Gantt Updates 

A pink bar is displayed on the Gantt on the timeline graph to indicate the Freeze Period. On hover over the user will see the start and end dates of the freeze period 

Task Type is used as a Custom field in MSP and populated with relevant data. 

Cora Updates  

On using the MSP functionality, Custom Fields has been relabelled to Field Mapping to cater for the inclusion of mapping to Cora system fields. 

Mapping 

The Cora Field dropdown now has 2 sections, Systems Fields and Custom Fields. The 2 sections were split so users can easily identify system and custom fields and prevent the need for additional scrolling. 

I

Import Validation  

After clicking Import, if there are any invalid records, they will be listed in the mapping Issues section. Click the hyperlink to open 

Any records that do not have a matching value in Cora will be listed. 

These are for information only, records will be written to the Cora Schedule 

Scheduling – Free Slack Field and Calculation  

Description of Change  

A new column will be added to the Gantt view of the schedule to display the calculated Free Slack for each task. Free Slack is the amount of time a task can be delayed without affecting the start of its immediate successor or the project deadline (if no successor exists) 

Functionality  

Customer Specific Tags in Page Headers  

Description of Change  

It is now possible top include a custom tag in PPM page headers.  This option is intended for customers who use third party software to track application usage. 

To include a custom tag in the page header, go to Admin | System | General | Login/Logout and enter the tag into the ‘Include Tag in Page Headers’ field. 

In the majority of cases, this field should be left blank. 

Scheduling – Task Type Based Schedule Logic  

Overview 

Task Type definition which facilitates schedule logic rules in accordance with National Defence Industrial Association (NDIA) Planning & Scheduling Excellence Guide (PASEG). 

Admin Updates  

To enable Task Types, the Enable Task Type checkbox needs to be selected on Admin | System | Task. 

The Task Type grid is displayed under Admin | System | Task -> Task Type tab. The grid will display regardless of the setting above as customers will want to set up and validate the values before switching it on. This is a standard grid with the following columns 

The grid will be prepopulated with the following records 

Gantt Updates 

The Task Type is displayed on the Task Manager in the Detailed section displaying records that are not Archived. Task Type can be added to the task list and is also available in filtering and the restore functionality. 

Task Update Logic 

Resourcing Restrictions 

If the Task Type has Resourcing Restrictions set to Yes, on adding a resource to the Task the user gets the warning message from 'Resourcing Restriction - warning message' set on the Admin side. This covers all resource Types (Skills, Users, Teams, Materials and Facilities). Warnings are displayed on both Task Manager and Task Updates pages. 

The warning message will appear in the top right corner, sample below. 

Note: The update is still captured, these are just warning messages 

Is Milestone  

If Task Type is tagged as Is Milestone, on changing duration <>0 days, the user also gets the warning message from 'Milestone Duration - warning message' set on the Admin side. Warnings are displayed on both Task Manager and Task Updates pages. 

The warning message will appear in the top right corner, sample below. 

Note: The update is still captured, these are just warning messages 

Statusing Page 

When a Status date is set on the Gantt the Statusing page is populated. Task Type field is only displayed at the 1st level after TASK. The field is not editable but can be used in filtering. 

Copy Functionality  

Task Type is included in the existing copy functionality (excluding Import Tasks from Excel). 

In the grid of register items, multiple items can now be approved or rejected at the same time without having to open each entry and approve it individually. 

When you select several items, as above, if all of the items are awaiting your approval, the approve and reject buttons will be enabled in the command bar of the grid. This allows you to quickly approve (or reject) a number of items all in one go. If you select a group of items and one or more of those items are not awaiting your approval, the buttons will be disabled and tool tipped with the reason. 

Cascading Dropdowns Structure 

1.1 Purpose 

This document provides administrators with a comprehensive guide to configure and manage the Cascading Dropdowns feature in Cora. It includes setup instructions, feature specifications, and example use cases. 

1.2 Background 

The Cascading Dropdown feature enhances dropdown list functionalities by introducing cascading logic across selections, creating a streamlined, contextual user experience. 

2.2 Future Development 

2.3 Out of Scope  

3.1 Creating a Cascading Dropdown Structure 

3.2 Adding Dropdown Levels 

3.3 Importing and Exporting Cascading Dropdowns 

3.3.2 Export for Review 

3.4 Notes: 

· You can only use existing dropdown lists and dropdown list values 

· You can’t edit a Cascading dropdown list. You will need to create a new Cascading Dropdown List with the updates 

· In cascading dropdowns, each child option can only have one parent, reflecting a 1:1 relationship. For example, consider cities like Columbus, Ohio, and Columbus, Georgia. Although both share the name "Columbus," their respective parent dropdowns—states like Ohio and Georgia—uniquely define their context. This ensures that each child (Columbus) is distinctly tied to only one parent (state), preventing ambiguity and maintaining logical consistency within the dropdown hierarchy. 

Cascading Dropdowns in Smart Forms 

1.1 Admin Configuration 

1.1.1 Setup Cascading Dropdowns in Smartforms - Lowest Level as a Dropdown List  

1.1.2 Setup Cascading Dropdowns in Smartforms 

1.2 Front-End Functionality 

Cascading Dropdowns in Registers 

1.1.1 Setup Cascading Dropdowns in Register 

1.1.2 Setup Cascading Dropdowns in Register - Calculated Fields 

1.2 Cascading Dropdowns in Registers 

Cascading Dropdowns in User Custom Attributes 

7.1 User Custom Attributes Add Cascading Dropdowns - Type Selection 

7.2 Users - User Attributes 

User Custom Attributes - Future Releases 

Surface Used in Data for Custom Roles 

Description of Change  

A new column called Used In has been added to the Custom Roles administration screen to make it easier for users to understand where in the system a custom role is being used. 

Cascading Dropdowns in Custom fields  

8.1 Cascading Dropdowns in Gantt Custom Fields 

8.2 Cascading Dropdowns in Custom Fields on Gantt  

Gantt Custom Fields- Future Releases 

Registers – Displaying ID in the Modal 

Description of Change  

Addition of Cascading Dropdowns in Rate Matrix 

1.1 Cascading Dropdowns in Rate Matrix 

1.2 Project Properties - Rate Matrix 

1.3 Gantt - Select a Task - Planned Resources 

Registers Linked to Advanced Financials 

The Linked Register Aggregate field type allows the aggregation of child register record data on a parent register record based on the parent-child links.  This Linked Register Aggregate field type definition consists of six elements for field configuration within a Project Register under the Administration – Configuration in Cora PPM. 

When a field is designated as Used in Financials a green check appears in the Used in Financials column on the Project Register edit grid. 

In the example below, the Total Cost column leverages the Linked Register Aggregate field configuration with Child Items Only links and the Timephased checkbox to return the total cost related to each Parent Register Record segmented by month in a string aggregate format. 

The Timephased configuration would be most helpful when used to supplement monthly project data (such as incorporating the cost of unmitigated risk as a monthly projection) within the center Forecast panel of the Project Forecasting screen. 

On the Project Forecasting screen clicking Load from Registers pulls the register aggregate values designated as Used in Financials for a given project. The register total values and register aggregate values (upon expansion) appear under the Register Billings, Register Revenue, or Register Cost categories on the Forecasting sheet. Only the Category headings, where used in financials data exists for a project, will appear under the Cost Category section of Project Forecasting. If no data exists for a project, then a “No register data found” informational toast message will be displayed in the upper right section of your browser window. 

Financial Management Widget: Amend Display of Cumulative Graph 

Description of Change 

The Financial Management Widget has been enhanced so that users can configure how data is plotted on the cumulative graph.  

The following changes have been made to the Settings modal on the Widget: 

On the Allocate to Task modal, only that Task is listed 

Resource Demand – UX Improvements 

Overview 

A number of improvements have been made to the Resource Allocation screen making it more intuitive and user friendly. 

Display Gap Values 

On the Resource Allocation page menu bar, a new dropdown is displayed called Demand figures 

Display Hours Per Period  

On Administration | Configuration | Capacity Management, a new checkbox is displayed called Display Hours Per Period 

The checkbox in unselected by default 

When selected, hours per period is displayed on the Resource Allocation page grid 

Weeks Filtering on the Resources Widget with more than 12 Periods 

Overview 

For customer using >12 periods in the fiscal calendars, the Resources Widget filtering has been updated to reflect the Fiscal Weeks dates. 

Note: Updates are displayed when 'Use Fiscal Calendar for Periods' checkbox under Admin | Config | Financials is selected 

Widget Filtering Update  

Statusing Distribute ETC From Status Date  

Overview 

When Statusing is turned on in an environment all effort prior to the Status Date is removed from Planned Effort. Only the effort from the day after the Status Date remains. 

Task Updates  

Prior to this development when the Status was set on a project and the effort or cost was subsequently updated on a task, Cora automatically updates the Distribution Curve to Custom. 

With this development Cora no longer updates the Distribution Curve to Custom. 

Modify Rate Matrix so that a baseline can be taken 

Description of Change  

This feature extends the baseline functionality. When a baseline is taken Cora now includes details of the Rate Matric values in use on the project at the time the baseline was taken. 

This supports audit requirements 

Alternative Hierarchy Pivot 

Description of Change: 

This feature introduces expanded functionality for Cora Register reporting and dashboards, enabling the utilization of new Alternative Hierarchy type. This enhancement provides greater complexity and flexibility in reporting and visualization across multiple levels of project data. 

Key updates include the ability to visualize and filter attributes within Alternative Hierarchy registers based on their relationships to tasks at the project level. 

Notes: 

Use Cases: 

Please, find below a WBS Dictionary (Alternative Hierarchy type) register and a Project Schedule selected as the Second Hierarchy: 

EVM1 EV Technique and Task Activity Groups 

Description of Change  

This Feature introduces additional functionality required to support EV Techniques. This particular functionality validates that when EV technique on a task is set to ‘Incremental Weighted Milestone’ that the associated tasks have sufficient detail to support the EV % complete calculation.  

Note: This calculation is aligned to the requirements within the Earned Value Management System Interpretation Guide (EVMSIG) 

EVM1 Baseline Cost Fields 

Description of Change  

This Feature introduces BCWS and BCWP calculations into Cora.  

A field for each of these Metrics is available to include in Cora’s Gantt. 

These calculations are aligned to the requirements within the Earned Value Management System Interpretation Guide (EVMSIG) 

EVM1 Percent Complete Calculaion by EV Technique 

Description of Change  

This Feature introduces following EV Techniques into Cora. These techniques are aligned to the requirements within the Earned Value Management System Interpretation Guide (EVMSIG) 

Techniques 

Cora Integrations 

Dropdown List Values Import 

Description of Change  

Administrators can now import the values for a dropdown list.  To import values, click the import button on the change drop down list items modal. 

This will prompt you for a file.  On successful import, close the modal and the values will be added to the list of values for the dropdown. 

Notes: 

Freeze Period Fields in API  

Overview 

As a user of the API for extracting and updating data from/to the system the Freeze Period data points is now available. 

API End Points 

The Freeze Period data points are available in the following API end points 

Examples 

GET/Projects and GET/Project{id}  

For PUT and POST the API accepts enum values or enum named 

PM Technique = No EV 

Freeze Period = Time Now +3 

{ 

   "description": "IT 104762", 

   "startDate": "2024-09-02T11:18:11.294Z", 

   "pmTechnique": "NoEV", 

   "freezePeriod": "3" 

} 

Scheduling - Task Type in API 

Overview 

As a user of the API for extracting and updating data from/to the system the Task Type data point is now available. 

API End Points 

The Task Type data point is available in the following API end points 

API Cora Hub Staging – Admin User Credentials  

Restrict the ability to create, update and delete data based on the authenticating user as an Admin user type within the CORA Hub Staging POST and PUT methods. 

Endpoint: CoraHubStaging  

If the authenticating user is not an administrator, an error code of 403 Forbidden and error message will respond with "User does not have administrator permissions". 

API Enterprise Financials – Admin User Credentials  

Restrict the ability to create and update data based on the authenticating user as an Admin user type within the Enterprise Financials endpoint: Global Sites, Account Groups, Account Sub Groups, Accounts and Financials  

Endpoint: EnterpriseFinancials  

If the user is not authenticated as an administrator, an error code of 403 Forbidden and error message will respond with "User does not have administrator permissions". 

API Facilities – Admin User Credentials 

Restrict the ability to create and update data based on the authenticating user as an Admin user type. 

Endpoint: Facilities 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and error message will respond with "User does not have administrator permissions". 

API Files – Admin User Credentials 

Restrict the ability to create data based on the authenticating user as an Admin user type within the Files endpoint. 

Endpoint:  /Files/Create 

If the authenticating user is not authenticated as an administrator, an error code of 403 Forbidden and error message will respond with "User does not have administrator permissions". 

API Forecasting – Admin User Credentials 

Restrict the ability to create and delete data based on the authenticating user as an Admin user type within the Forecasting endpoint.  

Endpoint:  Forecasting 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and error message will respond with "User does not have administrator permissions". 

API IDP Config – Admin User Credentials 

Restrict the ability to get data based on the authenticating user as an Admin user type. 

Endpoint: IDPConfiguration 
 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and error message will respond with "User does not have administrator permissions". 

API Organisation – Admin User Credentials 

Restrict the ability to create and update data based on the authenticating user as an Admin user type. 

Endpoint: Organizations 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and error message will respond with "User does not have administrator permissions". 

API ProjectStatus – Admin User Credentials 

Restrict the ability to get, create and update data based on the authenticating user as an Admin user type within the endpoint: 

Add Is admin restrictions to the following endpoints: 

If the user is not authenticated as an administrator, an error code of403 Forbidden and message will respond with "User does not have administrator permissions". 

API ProjectTypes – Admin User Credentials 

Restrict the ability to get data based on the authenicating user as an ADMIN user type within the ProjectTypes endpoint. 

Endpoint: ProjectTypes 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and message will respond with "User does not have administrator permissions". 
 

API ResourceActualsWithRateSegments – Admin User Credentials 

Restrict the ability to create, update and delete data based on the authenticating user as an Admin user type within the ResourceActualswithRateSegments API group. 
 

Endpoints: ResourceActualswithRateSegments 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and message will respond with "User does not have administrator permissions". 

API ResourcePlannedWithRateSegments – Admin User Credentials 

Restrict the ability to get, create and update data based on the authenticating user as an Admin user type within the endpoints. 

Add Is_admin restrictions to the following endpoints: 

ResourcePlannedwithRateSegments 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and message will respond with "User does not have administrator permissions". 

API ResourceTypes – Admin User Credentials 

Restrict the ability to get, create and update data based on the authenticating user as an Admin user type within the endpoints. 

Add Is_admin restrictions to the following endpoints: 

ResourceTypes 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and message will respond with "User does not have administrator permissions". 

API Skills – Admin User Credentials 

Restrict the ability to create and update data based on the authenticating user as an Admin user type within the endpoint. 

Add Is_admin restrictions to the following endpoints: 
 

Skills 
 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and message will respond with "User does not have administrator permissions" 

API Strategies – Admin User Credentials 

Restrict the ability to create and update data based on the authenticating user as an admin user type with the Strategies API group. 

Endpoint:  Strategies 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and message will respond with "User does not have administrator permissions". 

API TimesheetEntriesWithRateSegment – Admin User Credentials 

Restrict the ability to create, update and delete data based on the authenticating user as an admin user type with the TimesheetentrieswithRateSegment API group. 

Endpoints: TimesheetEntrieswithRateSegment  

If the user is not authenticated as an administrator, an error code of 403 and message will respond with "User does not have administrator permissions". 

API Users – Admin User Credentials 

Restrict the ability to update data based on the authenticating user as an Admin user type within the User group. 

Endpoint: Users 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and message will respond with "User does not have administrator permissions". 

API WorkOrders – Admin User Credentials 

Restrict the ability to create and update data based on the authenticating user as an Admin user type within the WorkOrders API group. 

Endpoint: WorkOrders 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and message will respond with "User does not have administrator permissions". 

API Get Rate Matrix – Config Endpoint 

Rate Matrix Configuration API need to be updated to match CORA PPM Rate Matrix Configuration Functionality 

Create new RateMatrixConfiguration Group (Route) 

Move/Add the following endpoints under this group:  

GET /BurdenCosts 

GET /BurdenCosts/{id} 

GET /BurdenRuleMatrix 

GET /BurdenRuleMatrix/{id} 

GET /Options (formally Configuration) 

GET /RateAdjustment 

Rate Matrix Configuration/Options 

Rate Matrix Configuration/Rate Adjustments 

API Get /BenefitsTracker 

Currently the Benefit Management data is only available via the CORA PPM Benefits Management Module  

Add API endpoint for Benefit Tracker: GET /Benefits/BenefitTracke 

Add API endpoint for Benefit Profile Data:  GET /Benefits/BenefitProfile 

API – Forecasting Actuals – GLVoucherNum 

Add an optional query parameter to the Get /Forecasting/Actuals to filter on GL Voucher Number as datatype string. 

This will result in the response body only containing results with GL Voucher Number. 

API TimesheetSubmissionEntries – Admin User Credentials 

Restrict the ability to get, create and update data based on the authenticating user as an Admin user type within the endpoints. 

TimesheetSubmissionEntries 

If the user is not authenticated as an administrator, an error code of 403 Forbidden and message will respond with "User does not have administrator permissions". 

Bug Fixes