search cancel

Clarity: XOG OBS complete='true' flag fails to replace unit changes


Article ID: 51904


Updated On:


Clarity PPM SaaS Clarity PPM On Premise



When the complete='true' flag is used in Organizational Breakdown Structure (OBS) XML Open Gateway (XOG) the results will show the original unit is removed and new entry is not written even though the XOG log states that it was updated correctly.


The use of the 'complete' tag in the OBS XOG cannot be used for structures associated with an Entity due to the business rules preventing the deletion of OBS Units in order to create replacement units.

Steps to Recreate:

  1. Create an OBS via XOG using the following XML replacing names in your system for the placeholders below:
    <NikuDataBus xmlns:xsi="" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_obs.xsd">       <Header action="write" externalSource="NIKU" objectType="obs" version=""/>       <obsTypes>           <obs code="test001" name="Test 001" isSecurity="true" complete="true" description="Test OBS">               <level depth="1" name="Level 3"/>               <level depth="2" name="Level 4"/>               <level depth="3" name="Level 5"/>               <level depth="4" name="Level 6"/>               <level depth="5" name="Level 7"/>               <level depth="6" name="Level 8"/>               <objectAssociation associationType="Any Unit" object="resource"/>               <unit code="user1ID" name="lastname, firstname">                   <unit code="user2ID" name="lastname, firstname">                       <unit code="user3ID" name="lastname, firstname">                           <unit code="user4ID" name="lastname, firstname">                               <unit code="user5ID" name="lastname, firstname">                                   <unit code="user6IDi" name="lastname, firstname"/>                                   <unit code="user7ID" name="lastname, firstname"/>                               </unit>                           </unit>                       </unit>                   </unit>               </unit>           </obs>       </obsTypes>  </NikuDataBus> 
  2. Verify that your OBS exists the way it is written above.

  3. Use the above XML again to modify your last resource in the list (user7ID) and replace them with someone else from your test system.

  4. XOG in this XML and observe that it writes successfully.

  5. Navigate to the UI and check your OBS - you will see that the user7ID whom you replaced with a new resource is now gone and your replacement is missing.

Expected Results: Complete='true" flag to make changes as in XML.

Actual Results: Change does not occur - original unit is removed and new entry is not written even though the XOG log states that it was.


Update the OBS Units through the application UI.

Resolved in Clarity 12.0.6 Generic Patch. Reference TEC522707
Resolved in Clarity 12.1.0

Keywords: CLARITYKB, CLRT-54116, clarity12resolved, clarity1210resolved.


Release: ESPCLA99000-12.1-Clarity-Extended Support Plus