Triggering SCXML from REST request

[gen_den]

Hi Experts,
I have a solution for GMS call back. GMS call back out of box works fine.
I have a requirement where whenever any customer submits the request for a call back from Mobile client or web client we want to verify if this number is blacklisted or not. If it's not blacklisted then we can take the request and schedule a call back.

In order to achieve the above scenario i found from ORS documentation that i can start the scxml session or trigger any scxml from the REST request :

https://docs.genesys.com/Documentation/OS/8.1.3/Developer/ExternalIntf


Now in order to do so , i have created a Service in GMS wiith name "blacklist" and in that service. From the REST request I am just trying to trigger my SCXML code. In service i have this section which points to my SCXML:

_service= http://192.168.21.128:8090/GMS_Basic/src-gen/IPD_default_defaultWorkflow.scxml

my request looks like this:

http://192.168.21.128:8111/genesys/1/service/blacklist?_phone=9005

I am passing this value in _phone paramter but GMS logs says timed out and ORS logs stops at and particular point always and nothing happens and i get below error:

{"message":"ORS request failed: cannot connect to ORS. IO issue.","exception":"com.genesyslab.gsg.services.ors.OrsServiceException"}


The issue here which i see is that ORS is finding the SCXML but not at all going inside the ENTRY block. Not sure if i need to handle some variables or expressions?

Any pointers?

[47245]

You need to set the IPD as interaction-less or create a custom IPD to start the workflow.

[gen_den]

Thank you for the response. But I am struggling here to create a Customized IPD. I thought when i create a project it automatically links IPD with Workflow.

[Kubig]

No, the IPD has to be created manually - under Interaction Process folder within project.

[gen_den]

I created the same , and even linked the IPD with workflow but somehow , transition doesn't happen from IPD to workflow and  flow fails

[eugene]

you have to create an interaction less process as the previous poster suggests - this will automatically call the requisite application.start event to trigger or flow instead of hanging there.