19. Record locking and E-signatures

[MintooXavier]

Brief description: This feature is used to lock/unlock records; and add e-signature during locking if required.

User spec: https://github.com/CCTC-team/redcap_cypress/blob/redcap_val/user_requirement_specification/core/19_record_locking_and_e_signatures.spec

Feature link: https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/C/Record%20Locking%20%26%20E-Signatures_19/C.2.19.100%20-%20Lock%20status.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/C/Record%20Locking%20%26%20E-Signatures_19/C.2.19.200%20-%20Lock%20form%20display.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/C/Record%20Locking%20%26%20E-Signatures_19/C.2.19.300%20-%20Locking%20record%20filter.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/C/Record%20Locking%20%26%20E-Signatures_19/C.2.19.400%20-%20Lock%20status%20display.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/C/Record%20Locking%20%26%20E-Signatures_19/C.2.19.500%20-%20eSign%20display.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/C/Record%20Locking%20%26%20E-Signatures_19/C.2.19.600%20-%20Locking%20module%20navigation.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/C/Record%20Locking%20%26%20E-Signatures_19/C.2.19.700%20-%20eSign%20customization.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/C/Record%20Locking%20%26%20E-Signatures_19/C.2.19.800%20-%20REDUNDANT.feature https://github.com/CCTC-team/redcap_rsvc/blob/redcap_val/Feature%20Tests/C/Record%20Locking%20%26%20E-Signatures_19/C.2.19.900%20-%20eSign%20and%20Lock%20access.feature

Pre review:

• [x] Script(s) targets the correct feature sufficiently
• [x] The user requirements are met

Post review:

• [ ] Script(s) targets the correct feature sufficiently
• [ ] Script(s) appropriately tests the feature

[MintooXavier]

Scripts pre- reviewed:

1. C.2.19.100 - Lock status

[MintooXavier]

Scripts Pre-reviewed:

1. C.2.19.100 - Lock status
2. C.2.19.200 - REDUNDANT
3. C.2.19.300 - Locking record filter
4. C.2.19.400 - Lock status display
5. C.2.19.500 - eSign display
6. C.2.19.600 - Locking module navigation
7. C.2.19.700 - eSign customization
8. C.2.19.800 - REDUNDANT
9. C.2.19.900 - eSign and Lock access

[MintooXavier]

1. C.2.19.100 - Lock status

   • Modified this script completely to meet URS

2. C.2.19.200 - REDUNDANT

   • Incorporated this into C.2.19.100 and made it REDUNDANT

3. C.2.19.300 - Locking record filter

   • Script doesn't test filtering
   • Modified the script to test the different filtering options

4. C.2.19.400 - Lock status display

   • Added steps to verify logging

5. C.2.19.500 - eSign display

   • Added steps to unlock instrument which negate e-signature and then verify logging and E-Signature and Lock Management Tool

6. C.2.19.600 - Locking module navigation

   • Added steps to verify event name and Record ID
   • Deleted steps to Add User and verify logging

7. C.2.19.900 - eSign and Lock access

   • Not sure why we are testing in Dev and Production separately
   • Modified the URS to include validating User Rights for locking/unlocking instruments, locking/unlocking with e-signature authority and LOCK/INLOCK Entire Records (record level) through user rights.
   • Modified the script to validate the new URS

All 7 scripts modified and pushed to MX_v13.8.1 an MX_v13.1.37

[MintooXavier]

Modified Timezone in php.ini for C.2.19.300 - Locking record filter.feature to work