Nigel, I think you're missing the point. The point was and still is that with BWL you can not create real bot logic/implementation, you need to develop that separately using the WDG Studio. Just does not make any sense to do anything else or use any other tools for that.

When it comes to requirements management and modelling the bot logic you are of course right. I'm just trying to make clear that you can NOT convert your plain BWL / BPMN model to a meaningful bot - like your blog title suggest. You still need to develop it using the Studio. Hope we can agree on that :)

Well, that would be like coding your bot with a notepad - what is actually possible using the WDG Automation Language (WAL), if you remember over 600 commands and their possible configurations by heart - and something that is definitely not recommended. The Studio is the tool you should be using for the actual bot logic development/testing/debugging, wouldn't you agree?

What I'm saying here, that we need to understand that BPMN is not an implementation standard. Therefore we really can not use it to create any meaningful runnable implementations, but models (skeletons) that business can easily understand and even create themselves with IBM BWL. So, the asset might bring value by giving you kind of a shortcut to start your model based implementation, but we should be aware of the limitations of this approach. That's all.

The point being, that you still need to create the WAL files - the actual bot logic - first some how. There’s no way to create fully working bot logic from plain BPMN model except a skeleton that can then works as a ”placeholder” for your actual bot code that you need to create using WDG Studio. Right? Just trying to make that clear.

Perhaps good to add that with BWL BPMN design, you can only generate an empty skeleton for your WDG bot / WAL file. You still need to implement the actual bot logic in WDG Studio like you would do when developing your bots without the asset.