Page History

...

• Passed Test Case
  • Starting Situation
    • A holidays.xml file is being included into a order for "non working days"
    •  order.xml and holiday.xml  are deploy in to the Jobscheduler
    • Jobscheduler read the order.xml and included file holidayholidays.xml 
    • Jobscheduler suppress the job execution for dates defined as "non working days" in the holidayholidays.xml
  • Action
    • Check JOC and right click on the order --> show start times --> submit
  • Behavior
    • Jobscheduler will show all dates jobs will be executed. Jobscheduler will supress execution for "non working days"
• Failed Test Case
  • Starting Situation
    • A holidays.xml file is being included into a order for "non working days"
    • User apply changes into the holiday.xml and deploy it in to Jobscheduler.
    • Jobscheduler does not read CHANGES from the  holiday.xml file.
  • Action
    • Check JOC and right click on the order --> show start times --> submit
  • Behavior
    • The Jobscheduler will ignore the changes from holiday.xml file and will execute jobs on "not working days".
• Explanation
  • When stating that an order is associated to a job chain then technically this means that it is assigned the first job node of the job chain.
  • Adding a new job node to the top of the job chain does not modify the order's assignment to the job node that was the first node at the time when the order was updated the last time.Jobscheduler read new or changed job, job chain, order and schedule files as soon as they are deployed in the Jobscheduler live folder. Jobscheduler does not reload chnages done in the  included  files i.e. holidays.xml

Requirement

• The order should consider a newly added job node at the top of the job chain and should execute accordingly 

...