Andrej Koelewijn is a Product Manager at Mendix responsible for the Runtime, data storage and integration aspects of the Mendix platform. He is an experienced IT professional with over 20 years of experience in different roles, ranging from development, to architecture, to pre-sales, to scrum master and scrum product owner.
Bart Luijten is a results-oriented, enthusiastic and pragmatic IT professional with six years of Mendix architecture and consulting experience across a variety of sectors. As a member of the Mendix professional services team, he helps customers design, build and test web and mobile applications using the Mendix platform and Scrum methodology. Bart is well immersed in solution architecture, project design, technical support, project delivery, quality assurance and customer support. Moreover, he possesses excellent knowledge of the possibilities and applications of the Mendix platform.
Jan is Product Documentation Manager in the Mendix Community team. He is responsible for increasing the expertise level of community members through documentation, training, and other forms of knowledge transfer. At any given moment he works on multiple projects to enable the community and achieve these goals.
ABOUT THE WEBINAR
We recently released Mendix 7.0, a release that improves the scalability and availability of your Mendix applications considerably. In this webinar we will explain what these changes mean to your Mendix apps and look at some new best practices for modeling your app in a scalable way. We will also cover moving your app from Mendix 6 to Mendix 7.
During this webinar you will learn the following:
- Stateless architecture and scalability
- Best practices for modeling non-persistent entities
- Java API changes and platform extensibility
QUESTIONS & ANSWERS
Is this new runtime in use for the mobile app?
Yes, this runtime is used for all Mendix apps, browser based and mobile.
What is the data on the runtime is newer than the data in the client? What data will the runtime use if the client? What data will the runtime use if the client executes a microflow on the runtime?
The behavior when data is changed by multiple clients is the same as in Mendix 6. Changes from a client are applied to the object as it is stored in the database. When saving changes from a client, the acurrent state of the object is refreshed from the database, then changed attributes are applied. You can use a microflow to influence this behavior, for example by first checking what the status of the object is in the database before applying the changes from the browser.
What if the user’s client is not refreshed in between?
If the user’s client is not refreshed, but the user has modified an object he will be seeing his modified version of the object, not any changes made elsewhere in the meantime.
Are the Mendix modules in the App Store updated for Mendix 7? For example, the SAML module.
Most of the most commonly used appstore modules have been updated and tested with Mendix 7, including the SAML module. Other modules will be updated in the near future, e.g., the Deep Link. Other modules that are provides and maintained by 3rd party developer will need to be updated by the authors. In many cases this has already been done. For those that haven’t yet been updated it may help to contact the author to indicate that an update would be appreciated.
You have announced the Web Modeler. Do you have a release date for the Web Modeler? And will it be a replacement for the Desktop Modeler?
The release date of the webmodeler will be announced later this year. The webmodeler and the Desktop modeler will live side by side, at this moment there are no plans to replace the Desktop modeler.
Will you, next to the Web Modeler, also make it possible to attach online development platforms for coding to Mendix? The same as projects for Eclipse. For example, Cloud9 or Codenvy.
That is an interesting idea, but at this moment we not have any concrete plans to announce in this direction.
What kind of changes are needed regarding widget development going from Mendix 6 to Mendix 7?
It is important to ensure that widgets indicate what objects they are using and to indicate when they no longer needs to objects. You can do this using widget.subscribe() or data.subscribe(). We advise you to use widget.subscribe() as in this situations the Mendix platform will ensure that the widget insubscribes from the object when no longer in use. You can find more info on this topic here: https://apidocs.mendix.com/7/client/mxui_widget__WidgetBase.html. Other widget changes can be found in the release notes and migration documentation.
How can we access the Web Modeler Beta program?
Please contact your CSM to discuss your use case.
When using the textbox widget with a decimal attribute, you have to enter a decimal precision. Can that be dynamic?
That is currently not possible.
Is there a plan to use the in-memory database for sessions?
Not at this moment. Most databases when provided with enough memory will cache often used data. As persistent session are often used, this means that the Mendix database will access it in-memory.
View past Expert Webinars on-demand at developers.mendix.com.