Bump! It can't be that hard. Beanshell? Anything? Anyone?
You can directly query the database and get the invocation_id using Sql Activity.
Table Name : tb_process_instance
Coloumn : long_lived_invocation_id
Query : SELECT long_lived_invocation_id FROM tb_process_instance WHERE id=11111
Thanks Nith - works like a charm (although a bit odd having to ask the database).
Why separate id and invokation-id?
I'm not sure why two separate Ids.
I suspect in this way:
An invocation to a long-lived process will be queued and assigned with an unique invocation Id. The uniquie Process Id will be assigned to it only when it comes to a running status.
This invocation id is not applicable to short-lived process invocations.