Page Properties | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
Ressources
Remarks
|
...
- CREATE form - used during the creation steps
- EDIT form - used for changing the metadata of a saved object
In general forms consist ofof a form model with arranged groups of fields
...
and optionally a script for manipulating field values.
>> Form Scripting (Client-side)
After clicking onto EDIT or CREATE and no model has been saved before you see a list of all object type fields in the left area and a somewhat empty model tree beside. In the case, you have saved a model for EDIT but not for CREATE you are asked whether to reuse the EDIT model for CREATE as well while opening it.
You can export your model as JSON-file and import such. During import, the file is validated and specific errors are reported.
...
Available Object Type Fields
Depending on the object type you get the following fields to be used in a form
Object Type | Short | Fields that offered |
---|---|---|
Object Type | OT | All fields that are directly referenced and those fields that are part of a statically referenced SOT. |
Extendable Floating Secondary Object Type | EFSOT | All fields that are directly referenced. |
Primary Floating Secondary Object Type | PFSOT | All fields that are directly referenced, and all fields of the OT that references this PFSOT, and all fields of the Required Floating Secondary Object Type (RFSOT) that are referenced from this OT as well. The EFSOTs that are referenced from the OT are not part of the list. |
Arranging Fields in a Form
You can arrange the form fields using drag and drop to design groups and compositions of fields. Click the Click 'x' to delete unwanted compositions, groups, and fields from the form.Like Like fields, groups and compositions can be dragged and dropped within a form or copied to another form.
By default, form layouts are organized into a Core Area core area for the most important index data metadata and a Data Area data area. This layout structure is optional. You may only use the Core Areacore area. Later in time the Data Area data area should be used for grouping the metadata within the summary aspect of the object details in the client.
All areas and groups can be collapsed or expanded for a better overview.
...
Groups
Groups combine fields and group them visually. Fields whose contents are related are logically combined (e.g., a person’s name, contact details, and postal address, etc.) in an address book entry.
- In the Core Area core area of the form, fields are visually combined into groups with a color background and layout.
- In the Data Areadata area, groups are shown as tabs like they are in compositions.
...
You can give groups a technical name that can be localized in the same way as the technical names for object types and fields can be. Therefore, the naming has to follow the same rules.
...
Composition
Compositions combine several groups. Groups combined via compositions are shown as tabs within the composition area. Groups in compositions logically get a label, which is shown as tabs of the tabs.
The extended area functions automatically like a composition area and displays groups as tabs. No form fields can be arranged here outside of groups.
...
Scripts
yuuvis® makes it possible to assign situation-specific scripts to forms. You can open a script editor that lets you edit a script for the current form.
There are various editing features available to help you create the script in the ribbon on the SCRIPT context tab and in the context menu of the script area. In addition, IntelliSense is available as scripting support.
>> Form Scripting (Client-side)
Anchor | ||||
---|---|---|---|---|
|
...
Form preview
You can open a form preview . The form preview which provides a visual aid when you are designing and laying out your form. This preview allows debugging the form via the browser tools as well. Only the scope.data cannot be handled well because no object is touched.
...