Rate Matrix allows Overlapping Rates
search cancel

Rate Matrix allows Overlapping Rates

book

Article ID: 241745

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

Overlapping dates for matching columns in the Rate Matrix. This issue is reproducible only on Postgres Database environment. 

The Rate Matrix is allowing rows to be updated with overlapping dates, thereby causing incorrect rates to be extracted. This issue happens only on a PostgreSQL environment. This occurs when updating an existing matrix row, not when creating a new row. 

Steps to Reproduce: 

  1. Login to a 16.0.0 Clarity environment using a Postgres Database 
  2. Classic, Navigate to Administration - Manage Matrix
  3. Create a new Matrix and add the below columns for the matrix under Assigned Columns
    • Resource
    • Resource Role
    • Resource Class 
  4. Create 2 records as below 
    • Record 1:
      • From Date: 1/1/2021
      • To Date: 31/12/2021
      • Resource: abc
      • Resource Role: *
      • Resource Class: *
      • Rate,Std Cost, Actual Cost: $100
    • Record 2:
      • From Date: 1/1/2022
      • To Date: 31/12/2022
      • Resource: abc
      • Resource Role: * 
      • Resource Class: * 
      • Rate,Std Cost, Actual Cost: $100 
  5. Open the second record created above and make the below changes to the From Date
    • From Date: 1/10/2021 (this was earlier 1/1/2022)

Expected Results: The system would throw an error because Record 1 and Record 2 dates are overlapping: ERROR REVMGR-20219:A row with this information already exists. 

Actual Results: The system does not throw the error and the record is saved with the overlapping dates.  

Environment

Release : 16.0.0, 16.0.1, 16.0.2 

Postgres Database 

Cause

DE64880 - The system is allowing overlapping dates when modifying existing records. It does not happen on new records. If a new row is created and the Administrator enters dates that overlap, an error is presented and the new record is prevented from getting created. 

Resolution

Targeted Fix in Release 16.0.3