NW BPM Mapping error

[Former Member]

Hello Experts,

i have designed a NW BPM which was working fine but has failed for a test case. Request your help for the same.

The mapping is failing in the node attchment wherein the 2 fields Size(which is an attribute and is optional) and text1 are not coming from the source and hence its failing in BPM.

the structure on the right is the input of the mapping which has been imported into BPM from ESR.

after the import. the fields size and text() are being shown as mandatory whereas in ESR they are optional.

Just wanted to confirm how can we change the cardinality of these fields or is there any other way to avoid failure.

Request your response for the same.

Regards,

Shubham

[Snavi]

Hi Shubham,

check the wsdl source of the operation mapping that you imported in BPM, if the fields are optional in ESR, it should come as optional in the BPM.

also, if you had made any changes to the ESR components, you need to re-import the objects to BPM.

match the wsdl source from ESR with what is in BPM, if it is different re-import

[Former Member]

HI Navdeep,

I did not make any changes to the WSDL. The field size is an attribute which is optional in ESR and also in the data object but during the mapping it shows them as 1:1.

Regards,

Shubham

[Snavi]

HI Shubham,

you can try re-importing it from ESR, if the input structure is used in some other interface with different cardinality, which could have overwritten the xsd in BPM

or modify the corresponding datatype in BPM under "Data Types"

Regards,

Navdeep