In several rules a check is done for heavy actions. For good performance or a fast response in the UI you don’t want what is called heavy actions.
Now in different situations different actions can be considered heavy, so we made this configurable. Take the following example: [
{"Action":"AppServiceCallAction"},
{"Action":"DownloadFileAction"},
{"Action":"JavaActionCallAction"},
{"Action":"RestCallAction"},
{"Action":"GenerateDocumentAction"},
{"Action":"ExportXmlAction"},
{"Action":"ImportXmlAction"},
{"Action":"RetrieveAction", "Database": true},
{"Action":"ChangeObjectAction","Commit":true},
{"Action":"DeleteAction"},
{"Action":"CommitAction"},
{"Action":"RollbackAction"},
{"Action":"CreateObjectAction"}
]
In this example lots of actions are considered heavy:
- Integration actions like rest, web service, app service, import, export, download, java actions
- CRUD actions like ChangeObject, Delete, Commit, Rollback and Create. For ChangeObject and CreateObject you can set to apply only when committing
- Retrieve actions, optionally only database retrieves
Now for different situations we have different defaults, for example the rule where you want commits at the end of the microflow you off course allow other commits after the first commit.
Also in buttons and on change actions people often commit/rollback as a replacement of standard save changes or rollback changes actions.