About the Advanced Study Versioning (ASV) asynchronous job
The asynchronous job recalculates the status of forms and visits affected by an ASV change.
Moving a study version that includes an ASV change to Testing or Approved starts an asynchronous job that recalculates the status of forms and visits for that specific mode affected by the change.
What happens if I open a visit or attempt a Randomization and Trial Supply Management (RTSM) action before the job finishes?
- When you open a visit during an asynchronous job, the system updates the visit status (if applicable) after checking whether all required questions are complete or not. Updated visit statuses appear on the visit tile, but form statuses on the Forms sidebar are updated only after the job completes.
New or updated validation checks are shown as red outlines on questions but don't impact the visit status until the job is done. Queries from validation rules are also visible only after the job completes. For more information, see About validation rules. Once the job finishes, validation failures appear on the visit tile.
- If a user tries to complete an RTSM action during a running job, the system recalculates validations to confirm that the RTSM action is allowed. If not, the system blocks the action as expected.
Note:
The visit status and Oracle Clinical One Analytics datasets do not show the permitted action until the job completes.
Does the asynchronous job recalculate the form and visit status for a locked subject?
No, a user must unlock and open the visit where the ASV change was applied in order for the visit and form statuses to be recalculated; the act of unlocking a subject alone does not trigger a recalculation.
Parent topic: Update forms during a live study