I have a document that is saved via an external service. The event is defined as “event_submit” in the JSON and I use a data provider for this document type.
{
"label": {
"text": [
{
"value": "Senden",
"lang": "de"
}
]
},
"parameter": [
{
"value": "event_submit",
"name": "event"
},
{
"name": "validate"
},
{
"value": "partial",
"name": "validationMode"
}
],
"type": "EVENT",
"primary": true,
"destructive": false,
"id": "button-55691",
"name": "SendenB",
"iconName": "send"
}
In the data provider we currently do the httpRequest responsible for the document saving and the we finish the method with a yield put(actionCreator.saving.done({})); to tell A12 the document has been saved.
Problem, the customer wants the view to stay open after save (it contains a list of previously submitted forms). What can I do to keep the view open and reload it ?
to summarize:
is it possible to use the save case of data-provider but prevent cancellation of the activity (on saving done)?
Or is it possible to just cancel the saving operation without done or failed.
+ stop all related sagas that are waiting for such action
+ get back editable ui state of form (since at leas it will be blocked by progress indication)
I would be interested in a solution for this as well.
Did you solve that problem and if so, could you share your solution? 
There are currently two ways to save activity data: the ActivityActions.save and the ActivityActions.commit action.
The save action is used to save the activity data and reload the activity (if the reload flag is passed in the action payload).
The commit action is a combination of save and cancel. The activity is only cancelled if the saving was successful.
Depending on the Form Engine view component that is used, which of those actions is dispatched is based on the events that are configured for the respective buttons.
The popular FormEngine CRUD component dispatches a commit action when using “event_submit” and a save action when using “CRUD::save” (Those event names are also documented in the form modeling documenation). I assume this is what you currently use.
However, with a custom Form Engine view component you can, of course, implement the behavior yourself.
If I remember correctly we stored the relevant information to reopen the view after the save was done and then opened a new view replacing the one we closed by saving.
The commit action is a combination of save and cancel.
Is it really true? I have an overview which is a child of a form. I open both of them and when I put an ActivityActions.commit.done action after saving data successfully on that form, the application crashes (I cannot do anything with my application). However, if I put an ActivityActions.save.done and cancel action, the application works normally. I suspect there is something different here.