Error creating incident via javascript

[thorben]

@StephenOTT

@thorben this usage (assuming its correct with accessing the variables through connector.getParentVariableScope(), would be a good thing to add into the docs and explain the chain/path it takes to get there. I would think in bullet #3 in: Scripting | docs.camunda.org would be a good small note to make about connector allowing access to the parent scope through connector.getParentVariableScope(), it is very unclear that it would function given the deep layers it takes to get there…

Hi Stephen,

I consider the workaround you found rather a hack, because it involves internal API (implcitly by calling parentScope.getCurrentActivityId() etc. where parentScope in java is declared as AbstractVariableScope, while #getCurrentActivityId is a method declared on its subclass ExecutionEntity; so the implicit cast (in Java terms) is where you are leaving public API). Thus, I would not document it.

I’d rather we make execution available in connector parameters. This would also make implementing this use case more straightforward. Feel free to raise a feature request for that and/or provide an implementation.

Cheers,
Thorben