Error code expression ${} doesn't evaluated

Mikhail.Savelov · August 8, 2021, 12:12pm

Hello, can you explain, why errorCode of the throwing error is treated as a String and not as an expression? See screenshot and bpmn file

jonathan.lukas · August 8, 2021, 6:16pm

this is because the error code is always related to the process directly.

What are you trying to do by using an expression as error code?

Jonathan

Mikhail.Savelov · August 11, 2021, 8:28am

I want to catch random error and re-throw it with the same code, for example

jonathan.lukas · August 11, 2021, 9:30am

for catching any error, you can just leave the error code empty.
Then, you could handle the error inside a service task and rethrow it from there.

The error code can be mapped to a variable when catching. By this, you can rethrow the error from inside the service task.

I hope this helps

Jonathan

jackyjoy123 · August 11, 2021, 1:18pm

thanks for the awesome information.