Clarity: XOG read causing double parsing error

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

Description:

When performing a XOG read action, the action fails due to a 'com.niku.xql2.eval.ParseException' error message when attempting to read an existing username containing a special character.

Steps to Reproduce:

  1. Download and install the Clarity XOG Client software (Administration, Client Downloads) in your local PC
  2. Modify the 'test.properties' file with the appropriate server information and input file name
  3. For the input file, use the following request to read out a Clarity User that exists with special characters such as apostrophe or hyphens used in the example below (such as user'001--):

    <?xml version="1.0" encoding="UTF-8"?>
    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd">
    <Header version="6.0.11" action="read" objectType="user" externalSource="NIKU"/>
    <Query>
    <Filter name="userName" criteria="EQUALS">user'001--</Filter>
    </Query>
    </NikuDataBus>

Expected Result: XOG action should be successful if the user exists

Actual Result: XOG action fails - User Object read failed because of com.niku.xql2.eval.ParseException

Solution:

WORKAROUND:

Use different filtering criteria to perform the XOG read action on this record.

STATUS/RESOLUTION:

CLRT-73882

Resolved in Clarity 13.3.0 Generic Patch. Reference TEC605767

Resolved in CA PPM 14.1