ACR Rules

⌘K
  1. Home
  2. Docs
  3. ACR Rules
  4. Performance (29)
  5. Microflows should perform database actions at the end

Microflows should perform database actions at the end

Introduced in version: 1.3 (29 Jan 2020)

To make sure records in the database are locked as briefly as possible all database actions should be done at the end of the microflow. After a database action, there should be no long-running actions, e.g. rest calls. These can potentially lock the records for a long time.
See this blog post for more information – https://blog.mansystems.com/mendix/top-10-performance-improvement-tips-for-mendix

Noncompliant example:

Compliant example:

Configuration of what action are not allowed after a commit:

[ {“Action”:”AppServiceCallAction”}, {“Action”:”DownloadFileAction”}, {“Action”:”JavaActionCallAction”}, {“Action”:”RetrieveAction”, “Database”: true}, {“Action”:”RestCallAction”}, {“Action”:”GenerateDocumentAction”}, {“Action”:”ExportXmlAction”} {“Action”:,”ImportXmlAction”} ]

Leaving the configuration empty takes this default.