Clarity: XOG ActCurve Segments seem to erase ETC segments

Document ID : KB000049527
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

We are performing a simple XOG write action to update the Actual Hours on a Task. After the Time Slicing job completes, the ETC values are erased.

Steps to Reproduce:

  1. Administration > Project Management > Settings > Default Loading Pattern = Fixed

  2. Create a project (myProject100)

  3. Set 'Track Mode' = None, 'Open for Time Entry' = unchecked

    Figure 1

  4. Add more than 2 or 3 Team Staff Members to the project

  5. Be sure each of the resources have Track Mode = None and Open for Time Entry = unchecked

  6. Create a task and assign the resources to the task (myTask100)

  7. Be sure the Task 'Open for Time Entry' = unchecked, Loading Pattern = 'Fixed'


    Figure 2

  8. Open the Project in Open Workbench (OWB)

  9. Highlight the task (myTask100) > right-click > choose 'Modify...' > Go to Resources Tab

  10. Add Actual hours to all resources assigned > Set the 'Act Thru Date'

    Figure 3

  11. Save the OWB Changes back to Clarity

  12. Executed 'Time Slicing' job

  13. View the Actuals, ETCs and Sliced ETCs on the Project Task Properties List View have been updated - ETCs show beginning in June 2012 because the 'Act Thru' Date was updated to 5/31/2012

    Figure 4

  14. Open the Project in OWB again > Modify Resource01 to remove actual hours

    Figure 5

  15. Save the project back into Clarity

  16. Execute 'Time Slicing' job

  17. View the Actuals, ETCs and Sliced ETCs on the Project Task Properties List - Actuals are updated to zero and ETC Slices remain as expected (Resource01 new start date 6/1/12)

    Figure 6

  18. Create a simple XOG write file for updating the 'ActCurve' data for 'Resource02' and 'Resource03'
    <?xml version="1.0" encoding="UTF-8"?> <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_project.xsd"> <Header action="write" externalSource="NIKU" objectType="project" version="13.0.0.7032"/> <Projects> <Project name="myProject100" projectID="myProject100" > <Tasks> <Task name="myTask100" taskID="myTask100" outlineLevel="1"> <Assignments> <TaskLabor resourceID="resource02"> <ActCurve> <Segment start="2012-01-03T00:00:00" finish="2012-12-31T00:00:00" sum="0"/> </ActCurve> </TaskLabor> <TaskLabor resourceID="resource03"> <ActCurve> <Segment start="2012-01-03T00:00:00" finish="2012-05-31T00:00:00" sum="0"/> </ActCurve> </TaskLabor> </Assignments> </Task> </Tasks> </Project> </Projects> </NikuDataBus>
  19. Peform a XOG Write action using the file

  20. Execute 'Time Slicing' job

  21. View the Actuals, ETCs and Sliced ETCs on the Project Task Properties List

    *** See how the ETCs for Resource02 are removed through 12/30/2012 ; this is NOT what we expected ***

    Figure 7

Solution:

ETC values can only appear on a Task Assignment as 'future' segments showing remaining ETC values after the 'Actuals Thru Date'.

When performing a XOG write action for the Task Labor ActCurve Segments, the 'finish' date should be set to a date that you want to effectively use as the 'Actuals Thru Date' (Act Thru).

In the example described above, the XOG write file contained ActCurve Segments with a future 'finish' date for 'Resource02'. This effectively set the 'Act Thru' date to be the same and therefore 'appeared' to erase the ETC values. What happened is that the future 'finish' date was for the end of the year (12/31/2012) and the view for the ETCs where shown only up to the end of the year. Upon scrolling forward or changing the TSV view to show more periods, the ETC values were seen after this effective 'Act Thru' date. NOTE: XOG dates take timestamps into consideration. In this example using 12/31/2012 midnight -- sets the curve data to end of day for 12/30. This is why we see 8 hours in December.

When Actual Units are updated on a Task Assignment, the 'Act Thru' date should reflect appropriately so that the remaining ETC values can be distributed as expected.

The XOG write file also had an ActCurve Segment finish date of 5/31/2012 for this example. After the XOG write action was performed, he remaining ETC values appeared as expected as illustrated for 'Resource03' in the last picture shown above.

Keywords: CLARITYKB, how-to, configuration.