Error while importing Activity Definition XML file

Troubleshooting

Problem

Error "Failed to import Activity Definition. Contact the system Administrator" during the import of an Activity.

Symptom

Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'DialogXSLT'. One of '{DialogDependency, EntryCondition, ExitCondition}' is expected.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.startElement(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.ValidatingUnmarshaller.startElement(ValidatingUnmarshaller.java:98)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:165)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:261)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:232)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:168)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:215)
at com.ibm.vch.base.ie.JaxbSerializer.unmarshal(JaxbSerializer.java:123)
at com.ibm.vch.base.ie.JaxbSerializer.unmarshal(JaxbSerializer.java:94)
at com.ibm.vch.base.ie.ImportHandler.getUnmarshalledResource(ImportHandler.java:89)
... 72 more

Cause

Activity Definition xml is being modified during creation of the activity by adding an extra element to the XML Dialog. This issue does not allow the exported activity to be imported to the PEM system.

Diagnosing The Problem

This issue occurs due to an extra element added to the activity definition XML file.

Resolving The Problem

Navigate to the failed activity and create a backup of the XML file.
Analyze the activity which was last imported successfully.
Analyze the failed activity.
Compare the activities in Step 2 and 3 (file comparator).
Find the duplicate or extra element (DIALOG or TASK) added to the failed activity. For more information, see the examples below.
Delete the duplicate or extra element.
Re-create the deleted element from the Activity Definition UI.
Save or mark the file as final.
Export, and then import the activity.

Examples

In the following activity definition, the element type GENERAL is referring to the Dialog UI.
```
<ns2:Dialog Name="Customer data filling UI Dialog" Type="GENERAL" Left="526" Top="44">
    <DialogAPI Name="xslt_d" Height="400"/>
    <DialogUI Name="Dialog" Width="900" Height="400">
        <TextBox Width="200" Name="C-1" Top="37" Left="108"/>
    </DialogUI>
```
Problem: The Dialog element type GENERAL must only contain DialogUI, and not DialogAPI or any other type of dialog element.
Resolution: Delete the extra element DialogAPI and re-create it from the Activity Definition UI. Save and import the activity.

In the following activity definition, the element type API_DIALOG is referring to the Dialog API.

<ns2:Dialog Name="API Dialog to create Partenrs" Type="API_DIALOG" Left="325" Top="110">
    <DialogXSLT Name="xslt_d" EscapeInput="false" OutputType="XML"/>
    <DialogAPI Name="API" UrlPrefix="true" Url="mrm/login" EscapeRequest="false" RequestMethod="GET" TestModeCall="true" ApiCallCount="0" InputOutputFormat="XML"/>
    <DialogDependency>
        <Dialog Name="Start"/>
    </DialogDependency>
</ns2:Dialog>

Problem: The Dialog element API_DIALOG must only contain DialogAPI, and not DialogXSLT or any other type of dialog element.
Resolution: Delete the extra element DialogXSLT and re-create it from the Activity Definition UI. Save and import the activity.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFG8Z","label":"IBM Sterling Partner Engagement Manager Software"},"ARM Category":[{"code":"a8m50000000L0kkAAC","label":"Activities-\u003EImport\/Export"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Was this topic helpful?

Document Information

More support for:
IBM Sterling Partner Engagement Manager Software

Component:
Activities->Import/Export

Software version:
All Versions

Document number:
7083933

Modified date:
28 November 2023

UID

ibm17083933

IBM Support

Tips