Details
-
Task
-
Resolution: Unresolved
-
Low
-
None
-
None
-
NPL Sprint 3, NPL Sprint 4
-
GxP
-
A
Description
Problem Statement
For any new NPL record created in PCM, users are able to enter both Cur Site and New Site information. The "New Site" field is actually irrelevant in the case of NPL. Users would like to eliminate this need for double maintenance by greying out this field for NPL and making it uneditable.
Acceptance Criteria
- For NPL records, "New Site" field is greyed out
- For NPL records, "New Site" field is made uneditable
- For older existing records, data contained in the "New Site" field can be deleted
qTest: Test Execution
Attachments
Issue Links
- is cloned by
-
OS-20235 PCM - Allow Specific "Global Launch Priority" values in drop down based on GSC Sub Type selected
- Closed
- relates to
-
OS-21193 TC Prep - OS-20234 - PCM - Block the usage of the "New Site" field for GSC Type "NPL"
- Done
-
OS-21194 Testing - OS-20234 - PCM - Block the usage of the "New Site" field for GSC Type "NPL"
- Done
- links to
-
TC-4173 001_Verify that user able to validate the New Site field is grayed out for the NPL records
-
TC-4174 002_Verify that user able to validate the New Site field is non-editable for the NPL records
-
TC-4175 003_Verify that user able to validate the data in New Site field is deleted for the older existing NPL records
-
TC-4176 004_Verify that user able to validate the New Site field is still editable for the other GSC Types except NPL
-
TC-4177 005_Verify that user able to validate that data in New Site field is still available for the older existing records for other GSC Types apart from NPL