Repeat prior process steps

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

choeller

Hello everybody,

we are currently trying to solve a problem, that seems to be some kind of tricky. Probably someone here ran into the same situation and can give me a hint what to do…

We have a service-task, calling a remote system to execute some write-operation asynchronously. After that service-task, we enter a "Receive-Task", that waits for a Callback of the remote system.

Last night we ran into a situation, where the remote system accepted our request, but then lost the operation. So, currently we are waiting for a Callback of an operation that was never executed…

Is there any best practice for a situation like this?

We were trying to set the

act_id_‍

in

act_ru_execution‍

table to the prior step and then trigger the execution manually, but this caused some internal errors like NullPointerExceptions in ExecutionEntity.ensureProcessDefinitionInitialized() -  so we seem to miss something here

Any ideas for that kind of problems?

Thanks in advance and best regards
Christoph

frederikherema1

Why not create an administrative application (or screen in your app) that allows the administrator to signal a process? That admin-module could just allow easy process-lookup and have a button "Force continue" that just calls runtimeService.signal().

Messing in the database is NOT a good idea!!