We'd love to hear from you! Provide  feedback  to earn a badge today. Take our quick survey
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

PCS service interface SOAP endpoint changes with every deployment

Accepted answer
17
Views
7
Comments
edited Dec 16, 2017 8:00AM in Process Automation 7 comments

Summary

PCS service interface SOAP endpoint changes with every deployment

Content

I built an C# AddIn for Oracle Service Cloud's desktop agent that invokes a PCS process message interface (SOAP service) when clicked.  However, I've noticed that each time I deploy a new version of this application the SOAP endpoint changes.  The endpoint is essentially always in this form:

https://{hostname}/soa-infra/services/default/{application-name}!{version}{uuid}{process-name}.service

The {hostname}, {application-name}, and {process-name} are always the same , however the version and the UUID change for every deployment.  So every time we deploy this process the AddIn triggers the previous deployed process (since it doesn't undeploy the previous one), but doesn't deploy the most current process.  This is a serious issue because I don't want to make a code change every time we deploy.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!