Details
-
Task
-
Resolution: Completed
-
Medium
-
None
-
None
-
AE Sprint 136
-
GxP
-
A
Description
From a process standpoint, there should be a single connection between a PCM ID and an eSponsor Number….it’s meant to be a 1to1 relation 😊
Meaning if users are trying to consolidate a esponsor reference to a PCM ID that already has an eSponsor Number recorded, we should:
- Either offer the user to overwrite it….as in replace the former ESP number by the new one they are trying to consolidate
- Or point them towards creating a distinct new PCM record
When they hit consolidate to a specific PCM number, we could imagine checking if the ESP number field has a value or not and trigger below message:
“The PCM XXXX you are trying to consolidate the ESP-YYY-YYYYYYY with, already has an active linkage to ESP-XXXX-XXXXX. What would you like to do?
- Overwrite PCM XXXX Esponsor Linkage from ESP-XXX-XXXXX to ESP-YYY-YYYYYY ?
- Leave PCM XXXX with current ESP-XXX-XXXXXX linkage and create a new PCM ID for ESP-YYY-YYYY ?”
qTest: Test Execution
Attachments
Issue Links
- clones
-
OS-18741 PCM - new validation, popup for esponsor consolidation
- Closed