ScottBub | 2017-03-03 15:57:49 UTC | #1
Hello,
Is there anywhere that we can promote ideas? I was hoping that PureCloud might be willing to make an adjustment on published connector actions. I would like to see that it be possible to change the endpoint of a published call flow.
If you are developing an integration the only way that you can test is to publish the actions and the call flow (to test using the call flow, not using Postman.) But, once you are done with testing and everything is working as designed you might be trying to point to a different endpoint for the final production version of your integration.
This is currently the scenario that we are going through. All testing will be done on a development server, but the live web service will be on a different server.
That means we have to create a new call flow and re-design all of the variables that we are using just to point to the new endpoint. It is a lot of work to go back and do if you struggled to complete it the first go around.
anon5606108 | 2017-03-03 17:39:04 UTC | #2
Hi Scott,
A non-published call will not be available to Architect, but will still be available to execute with a POST, using Postman or some other utility. This is not perfect, but can give you some level of testing without having to delete and re-create actions.
To answer your question, you are welcome to promote ideas and feedback at https://community.mypurecloud.com. At that site, you can view and submit questions and feedback, and connect with other PureCloud users.
ScottBub | 2017-03-03 19:34:14 UTC | #3
Hey Ian,
Thanks for your response. Are you saying that I would be able to execute the actual call flow without publishing it? We could actually simulate a call using Postman? Not just testing the connector action, but that the call flow works too?
anon5606108 | 2017-03-03 19:56:41 UTC | #4
Hi Scott,
I apologize for the confusion. Unfortunately, you cannot test the call flow on un-published actions, as the call flow needs created in Architect. You can isolate and test the Call Bridge Action step of the call flow by instead using Postman for that. However, the flow itself will require published actions.
If this is something which is a major roadblock for you to work around, I would encourage posting it at https://community.mypurecloud.com, so that product management can prioritize better solutions to your problem.
ScottBub | 2017-03-03 20:15:27 UTC | #5
Okay. That's what I thought you meant, but had to clarify. I have posted this as an idea or feedback. Hopefully it makes sense to them because I created a call flow with tons of logic based on the information retrieved in the callout to the database and screen pops too. This impacts our deliverable significantly.
Thanks, Ian!
system | 2017-08-28 19:32:36 UTC | #6
This post was migrated from the old Developer Forum.
ref: 1002