Bug #1387: Fix bug when it happens in the opposite way.
This fixes when you have a container task which is a scheduling point, and you unschedule it to schedule its children. This is the opposite to the original description of the bug, but the cause is the same. FEA: ItEr76S04BugFixing
This commit is contained in:
parent
a20fc0ec1f
commit
5d8860474b
1 changed files with 3 additions and 2 deletions
|
|
@ -324,8 +324,9 @@ public abstract class OrderElement extends IntegrationEntity implements
|
|||
}
|
||||
|
||||
private boolean wasASchedulingPoint() {
|
||||
return getTaskSource() != null
|
||||
&& getTaskSource().getTask() instanceof Task;
|
||||
SchedulingDataForVersion currentVersionOnDB = getCurrentVersionOnDB();
|
||||
return SchedulingState.Type.SCHEDULING_POINT == currentVersionOnDB
|
||||
.getSchedulingStateType();
|
||||
}
|
||||
|
||||
private boolean itWasntSchedulingPoint() {
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue