I think that the call might have been dropped by the time the PNC task was executed. The system drops the call if it is not engaged immediately after making the call ( play announcement or connect with other party). MakeCall does not work well with step by step debugging. The delay between MakeCall and PNC that causes the call to be dropped can not be avoided in step by step debugging. You could try setting up a breakpoint in the gateway you have after the PNC. And just continue after start task instead of stepping through the MakeCall and PNC.

If the workflow uses call intercept events in the start event then it requires WebRTC snapin for debugging. Please install the WebRTC snapin in the same cluster where ED is installed and configure it (follow the instructions in the help. Look for "Debugging a call-intercept WFD").

If the workflow does not use call intercept events then it can be debugged straight away.
Just for your information, the ED help has a section for debugger if you have not seen it yet.

I was doing some investigation on this topic. The library that we use to render the dynamic control does have support for multiselect.

Please change your dynamic control schema and select type as array and include "format": "select".

e.g.

{
"type": "array",
"format": "select",
"uniqueItems": true,
"items": {
"type": "string",
"enum": ["value1","value2"]
}
}

Try this and let us know if there are any issues.

Hi Andrew,

1. No. The schedule options are set in the workflow and will be effective when it is deployed.
2. ED uses EDP server's timezone. EDP server timezone is set during the OVA deployment of the EDP node. I am not sure if there is a way to change the EDP cluster's timezone after the nodes are created. I don't see it in cluster management.
3. No. I will create an enhancement request for this.
4. Looks like there is a misunderstanding of how the scheduling works. ED server will automatically create an instance when schedule time is met after the workflow is deployed. In case of recurring pattern, an instance would be created whenever schedule interval is met (once a day, once every week and so on depending on the schedule options). If you create an instance manually, it will be created immediately bypassing the scheduler. So please don't create the instance yourself. Wait for the scheduled time after the workflow is deployment to see the instance.

Hope these answer your questions.