Posted: 7 Dec 2018 4:26 EST Last activity: 10 Dec 2019 21:27 EST
Soap Service - Leverage type substitution in parse rule
I've been using Pega 7.3
I want to build a SOAP service which exposes in addition to some information an abstract type SpecificBodyContentType which can be substituted runtime by other elements which inherits from the abstract type (SpecificBodyContentType1, SpecificBodyContentType2) . Following part of the xsd I would like to generate:
I created all the parse rules using type substituion as suggested in different articles I found on the web. Anyway each tyme I download the WSDL generated by the service I see only a type (see snippet below).
Do you have any suggestion? Is it possible to leverage Type substitution in SOAP Services exposed by Pega? In case not, do you have any workaround I could apply to reach my goal (expose a generic object?)