@Vlad & Stephan: You're right, Lotus should change the type of the field to NAMES. But as you also stated correct that LWF is almost dead (well, not officially yet) we can't expect this to happen any more.
So for the customers with existing LWF applications I need a solution to fix this !
I think that the road is something between SSJS and existing API. Our team here, using a short kind of reverse engineering, managed to create Xpage custom controls that simulate (or reproduce if you like) the same functionality with the existing commercial IBM's product. As a matter of fact, finally, we are using the already known API. That means that, anyone who already got the Domino Workflow product, can simply drug and drop those custom controls in an Xpage and take advandance of the workflow capabilities that this product provide. An Xpage can be part of a work flow process and a work flow participant can act by using a web browser or his mobile, and generally all the good staff that Xpage technology provides.
It is so obvious to promote stanards within workflow tools that we have already implemented XPDL support (as a result of BPMN diagrams) in our DYSANT Framework for Lotus Domino. You can model processes in any BPMN (XPDL) supporting solution and than import it directly into DYSANT Framework what results in number of configuration documents representing each element from BPMN diagram
We have done this already two years ago for one of our customers. Only problem is that either the server has to login to sametime every time, or some persitent code has to reside somewhere to keep to connection to sametime.
If you need more info, please contact me - firstname.lastname@example.org
This would be extremely useful when supporting LWF-applications! I know, the process database is "just a technical thing" used by the engine, but in real life it'll make lots of things easier, if this db would be somewhat more accessible by human beings!