* Now most of the algorithms for these operations can be shared between
OrderElements and Templates.
* Disable create template button from Templates view.
FEA: ItEr74S04BugFixing
* The operations in the 'selected node' bar were not implemented
* The operation getSelectedNode() launched NullPointerException if no node
was selected
FEA: ItEr74S04BugFixing
There are transient instances when you add indirect criterion requirements ,
so after saving it must be call the method dontPoseAsTransientObjectAnymore
for each transient instance.
FEA: ItEr74S04BugFixinga
If a treeitem is selected and a new element is added, the selected item
is converted into a container (newObject) and the selected item is
promoted to a child od this new container.
The criteria of the original element is copied to new element
(container) and removed from the original element. This causes that the
child has a new IndirectCriterionRequirement, which is a new object.
The error happened when doing a reattachment of the Order being this new
IndirectCriterionRequirement a transient entity.
Finally, we have decided to change the business logic of how
criterionRequirements are copied when a treeitem is promoted to a
container. What happens now is that the original item retains its
criterionRequirement and the newObject(container) has empty
criterionRequirements.
FEA: ItEr74S04BugFixing
Added delete button in list of type of work hours. A 'type of
work hour' cannot be removed if it's being used by an 'hours cost'.
FEA: ItEr74S04BugFixing
When it changes the advance type, the previous indirect advances in its ancestors
are deleted and the new one is added if not exists any indirect or direct
advance with the same type.
ItEr73S04BugFixing
When an allocation can not be satisfied keep the old resources per day
and not update them from data. Thus when moving a task back to a place
where it's satisfied the resources per day of the last satisfied
allocation are used.
If a reassign fails, the error is catched and reported so it doesn't
prevent all the load of a project.
This allows to restore checkNoAllocationWithZeroResourcesPerDay and
thus the ignored test can be used again.
Now always overload is represented with red scale based colours and load
with green tones. In project view perspective the general load/overload
is translucid just to give the additional information.
FEA: ItEr73S04BugFixing
I refactored the code that does the checking in the business layer.
Instead of putting it directly in a method executed by
HibernateValidator I put it in a static method in the business layer.
This way it can be reused easily from the view layer.
The validation returns a ValidationException pointing to the object that
caused the error. Its corresponding component is localized in the view
and the error is shown as a WrongValidationException.
FEA: ItEr73S04BugFixing
When switching from Order WBS to MonteCarlo directly, it's necessary to
initialize all proxy objects that will be needed in MonteCarloView.
FEA: ItEr73S04BugFixing
In the confirm method, when there's an OptimisiticLockingExceptio, a
StaleObjectException happens first due to
storeAndRemoveEntitySequences(). So catch any type of Exception and
launch an OptimisticLockingException, that will be handled by the
ConcurrentModification support.
FEA: ItEr73S04BugFixing
