Clarity: OBS Association through XOG does not work when overrideAutoNumbering is used in the xml file

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

Description:

OBS Association through XML Open Gateway (XOG) does not work when overrideAutoNumbering="false" is used in the XML file. When overrideAutoNumbering is not used in the XML file, or when the element is set to true, the OBS association works.

Steps to Reproduce:

  1. Create a custom object

  2. Create auto-numbering on the ID attribute of this custom object

  3. Associate an OBS to this custom object

  4. Make sure OBS shows up on the properties page of an instance of this custom object

  5. Create a XOG write XML file to create a new instance for this custom object (do not include override element in header)|

    View the Object Instance through the Clarity application UI - Note that the OBS association shows up as expected
    |
  6. Edit the XML file to create a new instance of the object and to include overrideAutoNumbering="true" in the <Header> tag

  7. XOG write the XML file

    View the Object Instance through the Clarity application UI - Note that the OBS association shows up as expected

  8. Edit the XML file to create a new instance of the object and to include overrideAutoNumbering="false" in the <Header> tag

  9. XOG write the XML file

Expected Result: OBS Association to be there on the instance of the custom object

Actual Result: OBS Association is not there on the instance of the custom object

Solution:

WORKAROUND:

None.

STATUS/RESOLUTION:

Resolved in Clarity 13.2.0 Generic Patch. Reference TEC599354

Resolved in Clarity 13.3.0 Generic Patch. Reference TEC605767