#Quartz scheduler full
After creating the full backlog of features, the team will meet with users/stakeholders to prioritize all features in order to figure out which ones are going to be implemented in a first release. During the design phase, we will add even features and requirements. These are some of the high level specifications and user stories that could be included in this project. This will allow us to handle more advanced scheduling requirements. This type of scheduling would be difficult to support using the JDK Timer, so we would like to add an extension point to the scheduler to allow a developer (probably myself) to create a module based on the Quartz Scheduler. For instance, an implementation might want to schedule a Task to run once every day at midnight, but also at 6pm on Saturday and Sunday. cron-like) in the very near future, where we can specify rules that will allow Tasks to run more more/less frequently based on the day/time. We want to support more complex scheduling (i.e. The data model supports this type of feature (start time and repeat interval), but we need to add some logic to the Scheduler to handle triggering these tasks to occur at exact times. However, there's no way to schedule a task to recur at a particular time every week. a task will execute every X seconds, minutes, hours, days). The OpenMRS scheduler (based on the JDK Timer) currently supports executing tasks on regular basis (i.e.
#Quartz scheduler software
To give end implementations the flexibility to define these sorts of automated conveniences, the OpenMRS community has added scheduler functionality to the core software application.
For example: daily clinic reports might need to be generated the morning before a clinic opening, decision support rules might need to be run over a patient group once every week, or healthcare data coming in from outside sources might need to be analyzed every 30 mins. There are many activities within a healthcare information system which benefit from automation.
0 kommentar(er)
