Symptoms
When opening a given worklist item for a process the user was being navigated to a form "hosted" on an http site. This created problems as there was no http site for smartforms on the environment, only https.
Diagnoses
The root cause of this was that the workflow itself was built in an environment that only used http and deployed into one that only used https meaning that under all circumstances http was used by the process. Whenever a process assigns a task (client event) with a form it will commit an entry to the Server.WorklistItemHeader table which contains a link to the form of the worklist item. To construct that URL the Smartforms Runtime URL is used and while there is a default URL that can be manipulated in the environment library there is also an option to change this URL when building a given SmartForms client event. In this case there was not another option apart from http because the process was built in an environment that only had that.
Resolution
In this case the process itself had to be corrected in the development environment by creating an https site binding and reconfiguring the client events to use the desired url.
