Create Case from an External Application (createCases)

[Pluto]

Hi there,

I’m trying to create an instance of a workflow from an external application in Biz Agi.

The Information is as follows:

BizAgi version 9.1.8.1005

Process: AgencyRegistration
Entity: Agency
Fields looked for in the first step of the process: AcceptTermsConditions, TermsConditions

I have tried passing the following xml through to the WorkflowEngineSOA web service method createCases():

With case variables
<BizAgiWSParam>
<domain>domain</domain>
<userName>admon</userName>
<Cases>
<Case>
<Process>AgencyRegistration</Process>
<Entities>
<Agency>
<AcceptTermsConditions>true</AcceptTermsConditions>
<TermsConditions>I am a terms and condition</TermsConditions>
</Agency>
</Entities>
</Case>
</Cases>
</BizAgiWSParam>

Without case variables (Blank Case)
<BizAgiWSParam>
<domain>domain</domain>
<userName>admon</userName>
<Cases>
<Case>
<Process>AgencyRegistration</Process>
</Case>
</Cases>
</BizAgiWSParam>

Both of these cases return the following XmlNode:
<process>
<processId>0</processId>
<processRadNumber>0</processRadNumber>
<processError>
<errorCode>1</errorCode>
<errorMessage>An error occurred while parsing EntityName. Line 1, position 1396.</errorMessage>
</processError>
</process>

I've emailed support and they've asked to check the XML Schema for the Name of the entity. Below is the Schema.

<xs:schema attributeFormDefault="qualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Agency">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="1" name="AcceptTermsConditions" type="xs:boolean" />
<xs:element minOccurs="0" maxOccurs="1" name="TermsConditions" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>

I am very confident of the cases of all of the Attributes as well as the structure of the XML. I think that the problem occurs with the Xml on the webservices side. The entity being used originally had both of the Attributes passed to is with display names containing an ampersand (&) character. These have since been updated to ‘And’. Is it possible that this could be the cause of the on-going issue? How can we resolve this?

Please help me with what I may or may not be doing wrong. This issue is mission critical, we need to be able to create a case from an external web application asap.

Kind regards

Bryan Thomson

[BizAgi Xpress Support]

Dear Bryan ,
Thank you for your interest in Bizagi.

This issue is being currently analyzed by our support team, who will contact you directly for the solution.

Best regards,
Bizagi BPM Suite Support.