Trigger Workflows/PROCESS_EVENT from the overview List

Is it possible to run a custom Workflows Event from the List of Tasks, not from the details?

I tried already to run FormEngine Event:

 dispatch(
                FormEngineActions.event({
                    activityId: activity.id,
                    engineEvent: { type: rowAction?.event }
                })
            );

which gives me the error: " EngineState cannot be assembled for the activity 1." I guess it is because the model is not loaded to the activity.

I also tried to call the custom event manually. In this case I see neither errors nor RPC Requests:

dispatch(
                WorkflowsActions.processEvent.started({
                    eventName: 'PROCESS_EVENT_FRAGEBOGEN_LOESCHEN',
                    eventType: 'message',
                    processInstanceId: processInstanceId,
                    shouldCompleteCurrentTask: false,
                    activity: {
                        ...activity,
                        dataHolders: [
                            {
                                ...activity.dataHolders[0],
                                data: {
                                    document: data.documents[0],
                                    completeTask: false
                                },
                            }
                        ]
                    }
                })
            );

Thank you.

Hey Dimitri,
thank you for your question. We’ve forwarded your request to our workflows dev team. Currently, they are very busy, there may be a delay in processing. We apologize for this but hoping to be able to provide an answer in a timely manner.

Your discourse team

Hi @dmytro-clear-peat,

You’re right, our saga which handles WorkflowsActions.processEvent.started is expecting a form activity.

I suppose the only way to achieve this is to send the request yourself instead of dispatching the action. Or you could trigger the process event from within a form.


Note: in our new architecture which was released in 2023.02 and stabilized in 2023.06, your approach would work because there, our saga is not coupled to a form.

Best,
Peter