Open ntknguyen opened 11 months ago
The issue was in front API calling session, locId
has extra space. For example, if we select location/locId as 72
, it will be at 727%E2%80%8B
, this value will be checked by camdecmpswks.get_facility_locations
function and will throw a forbidden error.
Note : Currently (4/10/2024) Dev environment is bypassing the cdx, so test in test environment
Forbidden Resource error still present on test. Confirmed to happen for O2,CO2,SO2,NOX systems. (NOX tested from ORIS 298, LIM1)
Steps:
4/16/2024: Currently, it is only deployed in dev environment.
Edit: testing was done while bypass was active.
Issue appears to have been fixed on dev. Analyzer ranges in component records now display properly without delay after being selected. Confirmed for CO2, SO2, NOX systems.
Steps:
Moving to Sprint 4 because this ticket cannot be tested until the bypass gets removed.
Steps on dev:
Analyzer ranges currently not visible, confirmed for SO2 (tested on ORIS 298) and CO2 (tested on ORIS 1364) in Edit view and global view. Tester was unable to successfully create a new Analyzer Range, encountering error text "Cannot read properties of null (reading 'componentId')".
Analyzer ranges are visible as intended both on global view and when user checks out a facility, and analyzer ranges can be created without issue. Confirmed at least for for SO2, CO2, NOX using Limestone LIM1.
Steps on dev:
Verified in test and experienced no Forbidden Resource error in both the logged in and global view for two configurations: ORIS 470, Location 1 and ORIS 298, Location LIM1.
Logged in view
Global view
Logged in view
Global view
Forbidden Resource error in View/Edit on any component type code of (O2,CO2,SO2,NOX) in workspace.
Steps:
This may be caused by component types with analyzer range records.