Dynamic sessions and dynamic forms

The following list is an overview of the key characteristics of dynamic sessions and dynamic forms.

• Form layout
  The form layout is dynamic: the position of fields and labels is not fixed, but can differ per situation. At runtime, the same form can be displayed in multiple ways. The runtime appearance of the form is based on:

  • the content (labels and fields) and the structure (grouping of labels and fields) of the form and the sequence of fields and groups in the form definition.
  • the table field authorizations of the user (if any): if a user is not authorized for a table field, the field (including its label) completely disappears from the form. The position of the remaining form fields is rearranged automatically. Refer to Impact of table field authorizations for an example.
  • the mode in which the session is run. Dynamic sessions can run in overview mode and in details mode.
• Editor
  Forms are edited through the Dynamic Form Editor ( DFE). This editor is a separate utility and must be installed, from the LN installation CD, on the client PC. Refer to Dynamic Form Editor for details on the editor.
• Session generation
  You can create sessions through the Sessions (ttadv2500m000) session. For each session, an empty dynamic form is generated automatically. You must use the Dynamic Form Editor to generate the form fields.
• Session and form integration
  Sessions and forms are integrated. There is a one to one relationship between sessions and forms: each form is linked to a session and each session has only one form. You can directly edit the form by clicking Edit Form in the Sessions (ttadv2500m000) session.
• Single form for each session
  Each session has only one form. A form can consist of multiple field groups. At runtime, these groups can be displayed as parallel form tabs. In the Dynamic Form Editor, fields can be moved very easily from one field group to another.
• Combination of overview and details session
  Dynamic sessions can run in 2 modes: overview mode and details mode. Therefore, a single dynamic session can be used as an overview session and as a details session. Refer to Combined overview and details session for details.
• Dynamic Index Switching
  If Dynamic Index Switching is implemented for a session, the layout of the form changes automatically when a user selects another index (through the Sort by command in the session's View menu). The runtime layout of the form changes according to the selected index. For example:

  • The order of fields in the session's grid changes.
  • Different fields are displayed in the view area above the session's grid.

  Refer to To implement dynamic index switching for details.
• Text boxes
  Text fields can be displayed as text boxes, where you can type the text directly. However, it is also still possible to edit texts via a text editor.
• Appearance of enum and string fields
  In the Dynamic Form Editor, you can define how enumerated fields and string fields must be displayed. For example, you can indicate whether an enumerated field is displayed as a check box, a drop down list box, or as an option set (a set of radio buttons).
• Form commands
  Multiple form commands can be defined for each session/form. Form commands are used to start a session, a function, a business method or a menu. Form commands can be started via buttons or via the session's Specific menu. You can create form commands in the Form Commands (ttadv3518m000) session.

The dynamic form in this figure contains various types of components:

• Table fields, e.g. the tccom001.emno field.
• Table fields with a reference to another table, e.g. the tccom001.clan field.
• Non-table fields, e.g. variables from the session's program script. For example: the user.desc field.
• Field groups, e.g. the General and Employment groups.

For example:

• Employees - General (tccom0101m000)
• Items - Freight Management (fmfmd1100m000)
• Standard Routes (fmlbd0150m000)
• Tasks (tsmdm0115m000)
• Service Areas (tsmdm1105m000)

In LN you can use the following sessions to maintain dynamic sessions and dynamic forms:

• Sessions (ttadv2500m000)
• Forms (ttadv3500m000)
• Form Commands (ttadv3518m000)
• Convert session to dynamic (ttadv2900m000)