I'm creating a web service SOAP in adobe campaign that can be called by a tier application.
I want this web service to call a workflow and get the result of datas from this workflow.
My workflow looks like this :
The temporary 'temp:enrich_broadlog' schema is not defined in the current contex
My only solution is to store data in a ftp file and do more process. But I'd like to know if is it possible to get workflow datas directly by calling the workflow by the web service.
Thank you for your help.
To my mind, it could not work from the external jsSoap.js because through soaprouter.jsp you can accede only to schemas defined, with WSDL definition. And temp:enrich_broadlog doesn't have such a WSDL definition.
So I suggest you to:
Alternative way: instead of extending a factory schema, create a custom schema if it is more convenient for you.
I didn't want to modify any attributes or elements in the schema but seems that I have to.
Thank you for your clarification.
Hi, thank you for your reply.
Sorry I was not clear.
Tier service :
Web service soap :
So here how it works :
1) JsTier.js call soap service in jsSoap.js.
2) jsSoap.js launch signal to workflow and wait until workflow end.
3) workflow go to query > enrich (the value would be @statut for example) > jsWkf.js.
4) jsWkf.js change the value of @statut via queryDef in enrich temporary schema
Here is what I want to do :
5) jsSoap.js still waiting then retrieve @statut value by querydef in the enrich temporary schema (not purged yet). And return the value to jsTier.js.
But I get the error : The temporary 'temp:enrich_broadlog' schema is not defined in the current context
As several posts related to workflow query/enrichment activities mentioned, you can't accede directly to your xml context but must run a queryDef, because query/enrichment elements (targetData) are only made for delivery activity or standard activity access, and not accessible directly from the context (it is different from webApp).
See 2 posts mentioning it:
So please confirm that it is this data set that your try to accede from your external call.