Elizabeth Esswein

There is a quick answer to your point about bpmn id -> spiff name and bpmn name -> spiff description. Spiff tasks have auto-generated ids, so we don't overwrite those...

I believe the BPMN way of setting types would be to use an `ItemDefinition` (https://www.omg.org/spec/BPMN/2.0.2/PDF#G11.91155), but unfortunately we don't support it (we are considering adding it later). Also, the issue...

I also should have mentioned that we use the updated bpmn js in a react app (repo here https://github.com/sartography/spiffworkflow-frontend). Also in development, but maybe potentially useful to you.

Trying to keep things simple is definitely one of our priorities. We decided early on that sticking with task data was simpler than process data but we really wanted to...

Better callback functionality would allow some performance improvements to be made.

Resolved with https://github.com/sartography/SpiffWorkflow/pull/408

Yes, we discussed this. It is definitely a valid use case.. However, I ran into a problem doing some testing. I created a simple diagram (had to change the extension...

> For the first issue of losing output element value with that example, I'm not able to regenerate it again by running only bpmn editor, @essweine could you please verify...

The best way to do this is via customizing the script engine. If you run into an error during some sort of external call, the script engine can catch it...

This PR https://github.com/sartography/SpiffWorkflow/pull/403 contains documentation for a new example that sends an event to a running workflow based on the outcome of a service task.