#102 Loss of "uniform" and "contour" ressource assignment in XML

[Christopher Mann]

Problem :

Ressource assignment drops to 0 if the repartition method is "contour" or "uniform" when saving in XML.

Steps to reproduce the bug :

1. New project in XML with one task and one ressource

2. Set 4 days of work-load on the 10-day task in either contour or uniform.

3. Save the project as an XML file

4. Close and re-open the project file.

5. The ressource assignment is 0 when it should be 4.

[Christopher Mann]

Logged In: YES
user_id=1485833
Originator: YES

File Added: t.xml

[Christopher Mann]

The test file

[Talarian]

Logged In: YES
user_id=1969822
Originator: NO

Uniform rate not correctly loaded when saved in XML format.

OWB version : 1.1.4

Here is an estimate sample of the XML saved file whith a 10% rate affectation.

<Curve name="estimates" type="2" default="0.0">
<Segments>
<Segment start="2008-01-14T08:00:00" finish="2008-06-24T17:00:00" rate="0.1" />
</Segments>
</Curve>

When this file is loaded, the rate become 0%.
When the file is saved again then rate in XML file becomes :

rate="0"

This problem doesn't happen in rmp file format.

[Talarian]

Logged In: YES
user_id=1969822
Originator: NO

The attribute estMax of node Assignment also becomes "0.0" instead of "0.1" after loading then saving the xml file

<Assignments>
<Assignment
status="0" resourceID="Talarian" start="2008-01-14T08:00:00" unplanned="false"
estPattern="0" actualThrough="2007-12-14T08:00:00" finish="2008-06-24T17:00:00" estMax="0.0">
<Curve name="estimates" type="2" default="0.0">
<Segments>
<Segment start="2008-01-14T08:00:00" finish="2008-06-24T17:00:00" rate="0.0"/>
</Segments>
</Curve>
</Assignment>
</Assignments>

[Talarian]

Logged In: YES
user_id=1969822
Originator: NO

When the xml file is modified in notepad whith

estMax="0,1" instead of estMax="0.1"

OWB read the file correctly.
But when the file is saved again with estMax="0.1" it can't be reloaded with the correct value.

It seems there is a format problem.

My OWB 1.1.4 version is in french langage : I don't known if it's important.

[Christopher Mann]

Logged In: YES
user_id=1485833
Originator: YES

I think it is a French language problem that uses commas instead of dots to seporate decimals

[Christopher Mann]

Logged In: YES
user_id=1485833
Originator: YES

I came across this code in com.abtcorp.objectModel.pm.fr.
Is this where the problem is ? The rate is defaulting to 0.0.

public class AssignmentPercentExpended extends PMFieldRule
{
// Computes the result of dividing actuals curve sum by the EAC curve sum.
// If any property needed for the computation is uninitialized, then a default of 0.0 is returned.
protected IABTValue onGet( IABTUserSession session, IABTObject parent, IABTAttribute property, IABTValue myValue, ABTHashtable parameters )