Introduction

The Forms modeling tile is available on the dashboard for users with the YUUVIS_TENANT_ADMIN or YUUVIS_SYSTEM_INTEGRATOR roles.

...

The labels displayed in the metadata forms for the client can not be customized in the form modeler, but by means of the Localization view of the yuuvis® Momentum architect.

Modeling Forms for Metadata

In your client, the properties of your business objects are presented in different aspect areas. The properties provided by document an folder object types themselves are displayed in the summary aspect area that can not be customized in the yuuvis® Momentum architect. However, the properties provided by assigned secondary object types are displayed in the metadata aspect area which can indeed be customized. For each type of your business objects, you can customize separate forms in the yuuvis® Momentum architect for the Create and Edit working scenarios. For example, you can hide fields from an edit form that are only necessary to create an object. The corresponding form is provided to the user in the yuuvis® Momentum client accordingly.

...

In general, metadata aspect area forms consist of a form model with arranged groups of fields and optionally a script for manipulating field values. The following instructions will help you to customize the forms displaying metadata in your client in case of an object edit or creation.

• Click the Forms modeling tile to open view for the form modeling. Alternatively, click the menu button on the top left and choose Forms modeling. 

• In the column Select object type, find a tree to navigate through all object types for which you have the permission to model the metadata forms.
  

  Node	Content	Required Role
  Application	Further nodes are displayed, each of them corresponds to one specific application with an own app schema. Each node contains types defined in the specific app-schema: Document and folder object types. Pseudo-types determined by a primary-classified floating secondary object type.	YUUVIS_SYSTEM_INTEGRATOR
  Extending Types	Floating secondary object types without the classification primary or required defined in the system schema, the app schema or the own tenant schema.	For system and app schema: YUUVIS_SYSTEM_INTEGRATOR For tenant schema: YUUVIS_TENANT_ADMIN
  System	Types defined in the system schema: Document and folder object types. Pseudo-types determined by a primary-classified floating secondary object type.	YUUVIS_SYSTEM_INTEGRATOR
  Tenant	Types defined in the own tenant schema: Document and folder object types. Pseudo-types determined by a primary-classified floating secondary object type.	YUUVIS_TENANT_ADMIN

  
  

• Click either EDIT in order to customize the edit form or CREATE in order to customize the create form displayed in your client. 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.

The browser window is now divided in 3 areas: On the left a building set area, the Model tree and the Layout area. After the click onto a field in the Model tree or Layout area, an additional Properties area is opened on the right-hand side.

Building set area

The left-hand area is now showing the selected type and the kind of form (EDIT or CREATE) you are currently modifying. Below, you can find a list of all available elements you can use to build up your metadata aspect area form. On the top, there are two structuring elements: Group and GroupStack. Below, metadata properties are listet that are always assigned to the selected object type via the secondary object types. All these properties will be assigned to each object of this business object type, independently of the form of presentation.

...

Note: Properties provided by the document or folder object type itself are not available for form modeling. However, they are always assigned to all instances of the corresponding object type and are provided in the summary aspect area in the client.

Model tree area

In this area you define the structure of your metadata aspect area form. By means of drag and drop, you add elements from the building set on the left. You can arrange the form elements using drag and drop to design groups and compositions of properties. Click x to delete unwanted GroupStacks, Groups, and properties from the form. Properties, groups and compositions can be rearranged by drag and drop within a form.

...

Save your form via Save and thus apply it to your client.

Group

Groups combine properties and group them visually. Properties whose contents are related, can thus be logically combined (e.g., a person’s name, contact details, and postal address, etc.) like in an address book entry. The corresponding fields in the form will be visually grouped by means of background color and layout.

...

In the Properties area, you can give groups a unique identification key. This key is required in order to display a label for the Group in your form. Customize the labels via Localization. If not specified in the corresponding localization configuration, the identification key will be displayed in the metadata form.

GroupStack

GroupsStacks combine several groups. Groups combined via GroupStack are shown as tabs within the GroupStack area. The name of the Groups in a GroupStack is shown as title of the tabs.

The Data Area is per default an empty GroupStack. Thus, no property fields can be arranged here outside of groups.

Layout area

In this area you can see the properties as fields displayed in their Groups and GroupStacks. The arrangement corresponds to the structure defined in the Model tree. If you select an element in the Model tree, it will be highlighted in the Layout. The highlighting of elements within a GroupStack will be visible only if the corresponding tab is selected.

...

Via Open script you can open a scripting window providing further form modeling possibilities. Thus, yuuvis® architect makes it possible to assign situation-specific scripts to the current form. As a scripting support, IntelliSense is available: Click Copy to clipboard on the left corner to choose a technical field name. Add the selected string surrounded with the correct syntax to your script at the position of your cursor via Ctrl + V.
>> Form Scripting (Client-side)

Properties area

After the click onto any element in the Model tree or Layout area, an additional Properties area is opened on the right-hand side. Information on the selected element is provided here.

...

• For a single property field, you can tick or untick the checkbox Read-only in order to define the behavior in the client. For a string property, you can modify the number of Lines that will be provided for the property field in the client.
  Under Schema you can see the attributes of the schema property definition for the selected property.
• For a table property, you get the Read-only checkbox together with the Schema attributes of the property definition, too. Additionally, an overview of the available columns is provided. They are named with their identification key and their type (string etc.). By clicking one of them, you can define for the individual column the number of Lines for each entry and to be Read-only or not. By drag and drop, you can change the order of the colums or move them between Colums used and Columns not used. Thus, you can include or exclude columns from the metadata form.
• For a Group, you can select either Row or Column as Layout for the arrangement of the included property fields. Except for the Main Area, you can define a unique identification key for the Group. This key is required in order to display a label for the Group in your form. Customize the labels via Localization.
• For a GroupStack, there is no second information block displayed.

Summary

The form modeling in yuuvis® Momentum architect allows for a user with YUUVIS_TENANT_ADMIN or YUUVIS_SYSTEM_INTEGRATOR role to customize CREATE and EDIT forms that are offered in your client. The role authorizes the user to model forms in the metadata aspect area for object types of either tenant-specific or global schema definition, respectively. Furthermore, situation-specific modeling is possible via form scripting.

The labels displayed in the metadata forms for the client can not be customized in the form modeler, but by means of the Localization view of the yuuvis® Momentum architect.

...