Workflow outbound custom handler

[Former Member]

Hi,

I had followed Edward Liu's blog:

The blog provides the development work and configurations required in the SAP ECC backend system. Are there any development work needed in the SCL system as well for this? I mean, from the creation of the service interface/ server proxies to the creation of SCL business objects?

Thanks,

Kuttappa

[Former Member · Accepted solution]

Hi Kuttappa,

Workflow exposure does not require additional work within SCL.

The first role of SCL in Duet Enterprise Workflow handling is that of publishing XML payload, constructed in (pipeline) of OutboundHandlers in ERP upon reaching the decision task that is exposed via Duet, via Duet Enterprise Workflow Service to document library in the related SharePoint workflow subsite.

The 2nd role is upon propagating the made decision in SharePoint workflow [task] to the SAP decision task; the architecture of this is via standard Duet Enterprise TaskFlow BDC entity; and then picked up within ERP via [pipeline] of InboundHandler.

Wrt pipeline: you always have at minimal one / the standard Duet Enterprise Outbound and InboundHandler.

However, when required to expose contextual information into SharePoint front-end; you are required to proceed the standard OutboundHandler with your own custom version.

But this is done within ERP system; in the SCL it is in case of Duet Workflow handling all standard / OOTB Duet Enterprise.

Best regards, William.

[Former Member · Accepted solution]

Thank you William.