No More MXP015: Integrating Best Practices Recommender and Logic Recommender for Automatic XPath Order Optimization
We all know that optimizing the order of XPath queries during retrieval significantly enhances performance. To assist with this, we have the Mx Performance Bot in place, which identifies unoptimized XPath queries across the app and provides recommendations through the "MxAssist Performance Bot" under code "MXP015". However, the challenge we’re facing is that many, especially new developers, are not paying attention to these recommendations.
I was thinking that it would be extremely helpful if Mendix could automatically reorder XPath queries in an optimized way. This would not only reduce our daily workload but also improve app performance.
I suggest two possible solutions:
- Option 1 (Without Developer Intervention): Integrating "Mx Performance Bot" and "Mx Logic Bot." When the Performance Bot detects an unoptimized XPath, it could trigger the Logic Bot to automatically reorder it in the optimal way. This would remove the need for user involvement, allowing the bots to handle the process seamlessly. As a result, there would be no need to list out this Anti-Pattern (MXP015) under "MxAssist Performance Bot" at the platform level.
- Option 2 (With Developer Intervention): Introduce an Auto-Fix option for the MXP015 Anti-Pattern. Similar to "MXP006" and "MXP007", adding an "A" icon for Auto-Fixing within the Performance Bot would allow users to resolve unoptimized XPath conditions with a single click.
That said: To enable automatic XPath reordering, we would need to train the Logic Bot for various scenarios. However, this would greatly benefit all Mendix developers by improving performance and reducing manual work on a daily basis.
Please find the related example screenshots below:
1. Unoptimized Order of XPath Query:
2. Optimized Order of XPath Query: