Suggestion for Extension Point in PCS
We are using PCS Pega Foundation for Healthcare 24.2 (pega_foundation_for_healthcare_24_2_2024-11-12).
While processing plans, we encounter an error in PegaPCS-Data-Plan during the FetchFlattenedRecordsStatus validation of flattened records. This error is displayed in the Flattening Process Summary as a mismatch: Flattened Expected <> Flattened Actual records.
Currently, the flattened record ID is placed in the Queue Processor for Customer synchronization. However, customers might prefer not to process records they consider erroneous. To address this, I suggest the following enhancement for the current or a future release of PCS:
- In PegaHC-Data-CreateFlattenedStructure, add a line (e.g., line 20) to call the VerifyFlattenedRecordsStatusExtn activity. This will allow for additional qualification of flattened records before processing.
We are using PCS Pega Foundation for Healthcare 24.2 (pega_foundation_for_healthcare_24_2_2024-11-12).
While processing plans, we encounter an error in PegaPCS-Data-Plan during the FetchFlattenedRecordsStatus validation of flattened records. This error is displayed in the Flattening Process Summary as a mismatch: Flattened Expected <> Flattened Actual records.
Currently, the flattened record ID is placed in the Queue Processor for Customer synchronization. However, customers might prefer not to process records they consider erroneous. To address this, I suggest the following enhancement for the current or a future release of PCS:
- In PegaHC-Data-CreateFlattenedStructure, add a line (e.g., line 20) to call the VerifyFlattenedRecordsStatusExtn activity. This will allow for additional qualification of flattened records before processing.
- In PegaPCS-Data-Plan FetchFlattenedRecordsStatus, save the .Status of mismatched Flattened Expected <> Flattened Actual records in the Parameter page. Since all other pages are removed after processing, retaining the .Status would provide a mechanism for further evaluation if required.
These adjustments would offer greater flexibility and control for customers when handling erroneous flattened records.
Thank you, Art