We've switched over to using SSL for Forms 10.3 and thus had to update Workflow's connection (10.2) to it to also use SSL. This is fine for new instances of workflows, however our in-process workflows are still trying to connect to the non-SSL URL. We then went into each of those workflows, updated them, republished them, and told them to update active workflows. However those active workflows still show the old connection non-https connection when you open them and fail when they attempt to run that step. Is there a way to force Workflow to update to the new values for an external connection?
Question
Question
Replies
replied on June 14, 2018
Hey Beau,
Did you ever get an answer for this question? I am planning to switch all our connections to SSL and your described issue will certainly be my issue as well.
Thanks.
0
0
replied on June 15, 2018
Nope, we never received an answer/fix. The workflows that were in process were stopped and then restarted with the updated workflow. For those that failed, we had to manually handle anything they did (e.g. database updates, document moves, ...). I've not seen it happen again but that doesn't mean it wont be an issue. Sorry I don't have better or more complete news for you.
0
0
You are not allowed to follow up in this post.