The model can be edited during a debug session, when logic execution is halted.

The debug session responds differently, depending on the nature of the change to the model:

Logic changes

Logic changes to the model are not saved upon resumption of logic execution, they must be saved manually. Logic is validated before a method is called. If the logic changes are not successfully validated, you can choose to correct the error (if the method is already on the call stack or called from within another method being debugged), skip the method call, or terminate the debug session.

User interface changes

For user interfaces that have already been displayed during the debug session, user interface changes to the model are not applied immediately upon resumption of logic execution, or even when the changed user interface is next displayed (recalled). User interface changes are displayed only after the debug session is restarted.

For user interfaces that have not yet been displayed during the debug session, user interface changes to the model are displayed during the debug session. However, adding or removing a field leads to a mismatch between the user interface and the debug session. Only display changes such as color and position is applied.

Database changes

Logical reorganization occurs if database changes to the model result in a model that does not match the schema of the physical database.