Hi Stef Groenendaal,
I'm a little bit surprised why you use a dotted syntax? Normally, if you want to trigger the command binding of the Process Framework in order to proceed with the dispatching steps, you need to use Proceed/* and substitute the asterisk with you arbitrary command name. E.g. my typical next button command is Proceed/Next
You're right, you'll see the command in the client debug window, because the button fires the command indeed, but there is no commandBinding, which would catch this. I'd discourage you to use the dot in commandBIndings, because this is not a convention in the client js framework.
Hi Miklos Moricz,
Thank you for the reply and the confirmation that this indeed isn’t working as I would expect, but maybe Aurea can elaborate on this?
There is no reason to be surprised. This is based on an example from the Web Administrator guide.
the convention might be to use a slash between Proceed and your custom command name, but in theory you can use (almost) any seperator you want. I tried with "." and with "#" and both work fine, also when called from a button in a special header. Of course you must use the same seperator in the action and in the dispatching.
Feel free to open a case in the support portal and please pass on the whole configuration of the process.