Jobs in Vault CDMS
In Vault CDMS, a “job” represents a batch operation that Vault performs asynchronously, which can execute on either an ad hoc or regularly recurring basis. Organizations can use Vault’s job scheduling functionality to export data, run large operations (such as amendments) asynchronously, validate data, and more.
Interacting with Jobs
Vault CDMS users can interact with jobs directly from the Review tab and from Tools > EDC Tools, depending on their Study Role.
Typically, clinical research associates (CRAs) and data managers can use a limited subset of jobs from the Review tab, while a lead data manager can run or schedule any type of job from Tools > EDC Tools, in addition to those available in the Review tab.
See the following for details:
Types of Jobs
The following jobs are available with Vault CDMS:
| Job | Description | Added When |
|---|---|---|
| Schedulable in EDC Tools > Jobs | ||
| Audit Trail Export |
Export a ZIP file containing a CSV version of the audit trail for each Casebook in the Study that you have permission to view. The ZIP file also contains a CSV list of all deleted Subjects in the study. The Audit Trail Export also includes audit information for deleted records in your Study, such as those deleted by retrospective amendments. |
An EDC Tools user initiates an Audit Trail Export job from EDC Tools > Jobs |
| Core Listing |
Export Study data in a simplified CSV file. You can choose which Forms to include and which Sites to export data from. |
An EDC Tools user initiates a Core Listing job from EDC Tools > Jobs |
| Data and Definition Export |
Export a ZIP file containing CSVs of data in your Study. |
An EDC Tools user initiates the Data and Definition Export job from EDC Tools > Jobs |
| Data Export |
Exports study execution data as a series of either CSV or SAS files, in a format determined in your study’s design, to either download or send to a configured FTP location. |
An EDC Tools user initiates a Data Export job from EDC Tools > Jobs |
| Delete Site Data |
Delete all subject Casebooks, including any collected data, all queries, and all Code Requests in that Site. |
An EDC Tools user initiates the Delete Site action from EDC Tools > Sites |
| Delete Study Data |
Delete all subject Casebooks, including any collected data, all queries, and all Code Requests in that Study. |
An EDC Tools user initiates the Delete Study Data job from the EDC Tools Study lisiting (manual deployment studies) or EDC Tools > Environments (automatic deployment studies) |
| Detail PDFs |
Export Study data in a simplified CSV file. You can choose which Forms to include and which Sites to export data from. |
An EDC Tools user initiates a Detail PDFs job from EDC Tools > Jobs |
| DMR Re-assignment |
Updates the DMR Requirement Mode of all existing Items in the Study to match the assigned Review Plan |
An EDC Tools user initiates a DMR Re-assignment job from EDC Tools > Jobs |
| Query Rules |
Use this job type to have Vault evaluate a rule against existing data, for example, if the rule logic changes or it is a new rule. Select the Run in Preview Mode checkbox to run the job without creating queries. Vault sends you an email with the results of the job. |
An EDC Tools user initiates a Query Rules job from EDC Tools > Jobs |
| SDV Re-assignment |
Updates the SDV Requirement Mode of all existing Items in the Study to match the assigned Review Plan |
An EDC Tools user initiates a SDV Re-assignment job from EDC Tools > Jobs |
| Workbench Export | An EDC Tools user initiates a Workbench Export job from EDC Tools > Jobs. |
|
| Vault Coder Jobs To schedule or run these jobs, your vault must include the Vault Coder application. |
||
| Autocoding and Suggestions |
Autocodes pending Code Requests and creates suggestions. |
An EDC Tools user initiates an Autocoding and Suggestions job from EDC Tools > Jobs. The job then runs automatically. |
| Code Request Export |
Export a CSV file of all Code Requests for a Study, including details about each Code Request and what each request was coded to. |
An EDC Tools user initiates a Code Request Export job from EDC Tools > Jobs |
| Reconstitute Code Requests |
Updates existing Code Requests to use updated form configuration, and, if applicable, recreates previously deleted Code Requests to reference the updated configuration. |
An EDC Tools user initiates a Reconstitute Code Requests job from EDC Tools > Jobs |
| Logged in Job History, Initiated Elsewhere These jobs are logged in EDC Tools > Jobs > Job History, but they originate elsewhere, either in EDC Tools or Studio. |
||
| ODM Import |
Imported an ODM XML document into vault |
A Studio user imports an ODM XML document when creating a casebook version |
| ODM Export |
Exported an ODM XML document from vault |
A Studio user exports an ODM XML document when publishing a casebook version |
| Prospective Amendment |
A retrospective amendment upgrades existing subject Casebooks to a new casebook version, applying the design changes to existing data. |
An EDC Tools user runs a retrospective amendment from EDC Tools > Casebook Versions |
| Retrospective Amendment |
A retrospective amendment upgrades existing subject Casebooks to a new casebook version, applying the design changes to existing data. |
An EDC Tools user runs a retrospective amendment from EDC Tools > Casebook Versions |
EDC Jobs vs. Vault Jobs
While jobs are a feature of the Vault Platform, jobs specific to Vault CDMS, such as Data Listing and amendment jobs, function differently and are distinct from platform jobs.
Unlike Vault Platform jobs, Vault CDMS jobs cannot be scheduled or run from the Job Scheduler. Available Vault CDMS jobs are listed in the EDC Jobs (edc_jobs__v) picklist and are tracked with the EDC Job (edc_job__v) and EDC Scheduled Job (edc_scheduled_job__v) objects. Vault Platform jobs are not tracked as object records.
Learn more about Vault Platform jobs here.
Audit Logging
Actions that occur as part of a job are included in the Object Record Audit History. They are also tracked within the related object records (such as Casebook for amendment jobs).
Job Monitoring
If any action encounters an error, Vault notifies the job owner (the user who initiated or scheduled the job) via email.
Scheduling
When there are scheduled jobs configured, Vault puts the job into a queue of tasks at the scheduled start time. If Vault is unavailable at that time because of maintenance, a system outage, or too many simultaneous jobs, the job continues trying to run for approximately five (5) hours after the scheduled time. If the job cannot start within that window, Vault skips the instance. If your jobs regularly miss their schedules, contact Veeva Support. You may need to stagger your jobs’ start times or reduce the total number of jobs.