You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Known Issue Status
| Occurrence |
KNOWN ISSUE OCCURRING FROM RELEASE 1.3
| |
|---|
| Change Management Issue |
JS-1281
-
Getting issue details...
STATUS
| |
|---|
Behavior
- 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 holiday.xml
- Jobscheduler suppress the job execution for dates defined as "non working days" in the holiday.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.
Requirement
- The order should consider a newly added job node at the top of the job chain and should execute accordingly
Workaround
- Solution 1: Update the order configuration
- An updated order configuration file will force JobScheduler to reload the order configuration and to adjust the assignment of the initial state.
- Solution 2: Use start and end nodes
- We recommend that you use our /sos/jitl/JobChainStart start job as the first node in every job chain and our /sos/jitl/JobChainEnd end job as the last full node. These are dummy jobs without any function of their own. However, they are helpful for fixing orders or pre-/post-processing rules: changes to the names and/or order of states within a job chain do not require a change to the order.