Please enable JavaScript.
Coggle requires JavaScript to display documents.
Persisting mAudit record in DB (Scenarios for Template Editor (Verify…
Persisting mAudit record in DB
Template Editor
CD level
Study Level
Report Settings
Approvers
and Reviewers
MCC-398112 <TemplateEditor> mAudit Approvers & Reviewers Settings
Deadline
MCC-459676 <TemplateEditor> mAudit Deadline Settings - Persist to Database
Auto email
and restrictions
MCC-459679 <TemplateEditor> mAudit Auto Email and Restriction Settings - Persist to Database
eSignature
To be updated once story is created
To be verified in the DB
When audited
The time when the action requiring audit occurred, to the millisecond in UTC
What_uri
Report settings ID (to be verified from DB)
Why (optional)
Reason for change
Who_uri
Impersonate uuid of the user who has made the changes
Where_uri
App uuid (to be verified from medistrano)
Pre-Requsite
Should have access for Scribe DB
Scenarios for Report settings
Verify Scribe DB has the Table for mAudit
Verify Column names are matching with mAudit Acceptance Criteria
Verify upon saving Deadline settings Audit record has been inserted into DB based on the changes done in the fields
verify upon saving Auto email and restrictions settings mAudit record has been inserted into the DB based on the changes
verify upon saving eSignature settings mAudit record has been inserted into the DB based on the changes
verify Approvers and Reviewers settings mAudit record has been inserted into the DB when created the record
verify Approvers and Reviewers settings mAudit record has been inserted into the DB when updated the existing record
verify Approvers and Reviewers settings mAudit record has been inserted into the DB when deleted the record
Scenarios for Template Editor
Verify mAudit record has been created in DB, by creating Letter/Report template
Verify mAudit record has been created in DB, by updating the existing template
Verify mAudit record has been created in DB, by updating the Template name
Verify mAudit record has been created in DB,t by updating the Template Visit type
Verify mAudit record has been created in DB, by updating the Template Conduct method
Verify mAudit record has been created in DB, by updating the Template Language
Verify mAudit record has been created in DB, by updating the Template Type
Verify mAudit record has been created in DB, by updating the Template Status from Active to inactive and vice versa
Verify mAudit record has been created in DB, by updating the Template status in Study level
Verify mAudit record has been created in DB, when user updates the template at Study level and clicks on Save/ Cancel/preview button.
Click here for Epic level mAudit coggle