View source for BestPractices:Getting to the bottom of the Line of Business Application

<message>Write the content here to display this box</message>
__NOTOC__

After creating business applications for many years, we tried to codify the '''most''' basic feature set required from any application. Following these simple "rules", we will reach far in our quest for a fully declarative application. 
[[File:ImageOnly3things.png|none|thumb|438x438px]] 

You will find that everything in the MDriven Turnkey user interface is based on this Manifest.

=== Applications have three kinds of forms. ===
# The ''seek form'' can search - from nothing - for objects in persistent storage and show them in a list.
# The ''document form'' is designed for a specific use case and shows information based on a root object and its associations in as many navigational steps as necessary.
# The ''report form'' differs from the document form by being non-interactive, paginated, and expanding all combinations in master-detail relationships at once (non-cursored).

=== The seek form can be used in two different modes.===
* The first mode is typically accessible from the main menu as in a context-less seek operation restricted by any number of filtering parameters.
* The second mode called “''seek and pick''” is a modal form that aims to seek out one or several objects for a specific reason, such as assignment to some association. The “''seek and pick''” is commonly used to set a 0..1 association end when a combo box would not suffice due to too large a data quantity. 

=== Applications have four kinds of actions.===
# Actions that act on an object based on its class. 
# Actions that act in a given context or use case; a document or seeker form.
# Actions that are global and act on neither of the above contexts, like main menu actions.
# Actions that can be organized in structures, like sub-menus.
Any action can be enabled or disabled based on the state of the context.

===  When an action is executed, the following things can happen:===
* Some code is executed.
* A form may be opened.
* The opened form is assigned an optional root object by execution of some code.
* The opened form can be opened Modal or not, and if Modal, an optional piece of code will be executed when the Modal form closes with OK (like with ''seek and pick'').
Forms have UI-Validations to communicate rule breaks in the current input.

Objects follow business rules by implementing Statemachines with guards.
[[Category:Architecture]]
[[Category:Discovery]]
{{Edited|July|12|2025}}