Please enable JavaScript.
Coggle requires JavaScript to display documents.
Payments Regression based on Quartz Job changes (Core CTMS related jobs …
Payments Regression based on Quartz Job changes
Core CTMS related jobs
(29)
Amend IN Letter Site Templates
completedActivityDoneFlagProcessing
Country Planning - Site Actual Date
Country Planning - Subject Actual Dates
Country Planning - Upgrade - Set Planned values
Enrollment Rollup Batch
eTMF Export Batch
Generate Milestones
generateActivities
generateCRFs
generateDocuments
generateLostMargins
Import Controller
IN Letter Study Mailbox Alerts
IN-Letter Resource Notifications Generation
MileStone Rollup Batch
MileStone Rollup Batch - Expected
milestone_alert_1
Regulatory Documents State Processing
Resource Notifications Alert
Set Identifiers For Countries in Dropdown
Site Contact IN Letter IRB Acknowledgment
Site Contact Management
Status Rolldown Batch
Status Rollup Batch
survey_alert_1
survey_alert_2
Update Institution Name
Visit Date Fill
Resources
Katarzyna Czaplicka (KC)
Galina Koleva (GK)
Ranjeeta Adusumilli (RA)
Micah Stapleton (MS)
Shubhra Singh (SS)
Sweta Chhetri (SSC)
Functionality:
CTMS Performance & Scalability Enhancement: Workflow Scheduler Improvements
MCC-447789
[TECH] Create configuration tables for Quartz scheduler
MCC-447790
[TECH] Populate Quartz tables with the Quartz configuration data
MCC-440925
[TECH] Implement custom batch job for workflow rules
Payments related jobs
(12 jobs / 2 triggers)
event_cost_deletion
Disbursement Study Site and PI ID export
generateEventCosts
new_drugtrial_billable_tmpl_object_alert
Payments iiPay Status Extract
payments_awaiting_approval_alert
payment_approved_requests_alert
payment_rejected_requests_alert
Set Billing Event Flag For Rave Imported Visits And CRFs
Payments Auto Assemble And Approve
generateEventCosts / CostGenThread1-4 (INC)
Payments Auto Assemble And Approve
General Triggers
CRF Page Reviewed Billing
CRF Page Source Data Verified Billing
Questions
a) Does it have impact on other tables such as relationship/FK constraint etc
No, these are specific to quartz or batch scheduling…
b) Testing area to be focussed?
Verify batch jobs/work flow rules specific to payments and should continue to behave as before
c) How to evidence areas tested?
Capture when job/WFR started, when its completed, is it completing as expected, execution time was as before, its triggering as expected etc
d) Is it going to improve performance?
Main consideration from testing perspective is to focus and verify jobs/WFRs are consistent and working as before
INFO
All batch jobs (such as background jobs, cron jobs, work flow rules etc) which we run using quartz API was using RAM store i.e in memory store but now we moved in memory store to JDBC store i.e all quartz job trigger details (such as when its triggered, completed, next trigger time etc) will be maintained in quartz specific tables i.e new tables again these tables were used from official quartz API documentations