ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Clarity: XOG out a process which contains step that calls a Clarity job will not XOG back in due to "invalid XML".


Article ID: 52202


Updated On:


CA Identity Manager CA Identity Governance CA Identity Portal Clarity PPM SaaS Clarity PPM On Premise



XOG out of process that contains a step which calls a job. The output of this XML read results in an incomplete job definition section which results in an "Invalid XML" error when XOG'd in to another or the same system.

Steps to Reproduce:

  1. Create a process with a step that calls either a stock or custom job

  2. XOG out the process using the content pack XOG (using ProcessQuery Filter)

    Error Message:
    <ErrorInformation>     <Severity>FATAL</Severity>     <Description>[Error] :0:0: uncompleted content model. expecting: <jobDefinition>     </Description><Exception type="java.lang.Exception"><![CDATA[java.lang.Exception: Invalid xml data

Expected Result: XOG to import job definition step
Actual Result: XOG fails on write with invalid XML error


Create a copy of the process and leave a blank dummy step for that one step. XOG the process out and in and recreate only the one step.

Resolved in Clarity 12.1.0

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


Release: ESPCLA99000-12.1-Clarity-Extended Support Plus