Input Forms

In Allegra, you can define any number of input forms that can be used to create items, edit items, change item state, add comments to items, and move items to other projects or item types.

Forms contain fields that represent system attributes and user-defined attributes. If an attribute appears on a form, it is a field there. Forms are associated with the actions mentioned above, such as creating items. These mappings can be configured:

  • Globally

  • Item type specific

  • Project type and item type specific

  • Project and item type specific

This approach supports configuration efficiency while maintaining flexibility.

../../_images/formOverview.png

Each form consists of three elements:

  • Tabs

  • Panels

  • Fields

The procedure for creating and using a new form is as follows:

  • Create the new form using the interactive form designer.

  • Assign this form to the desired action, either globally or at a more specific level.

You can modify forms at any time.

Tabs

Each form consists of at least one tab. Tabs contain panels and panels contain fields. The figure shows a form with three tabs. The first tab page can be designed as required. The other two tab pages were automatically added to this form because the corresponding function (Observer Lists and Settlement) has been activated for this project. These tab pages are predefined by the system and cannot be changed interactively.

../../_images/formOverviewTabs.png

The number of custom tabs you can add to your form is limited only in practice. You can set the tab label as you wish.

Panels

Tabs contain panels. All fields are placed on panels. A panel consists of rows and columns. A panel organizes space for fields in a grid.

../../_images/formOverviewPanel.png

Unused grid positions are specially marked in the form designer and left blank in the rendered form.

There is only one practical limit to the number of panels you can use. You can move panels at any time using drag & drop.

Actions

In Allegra, forms are associated with actions. For example, you can keep the form to create an item as simple as possible, while editing an item should display all item properties available.

Adding a comment should only include a comment description field and nothing else. Changing a state is often accompanied by a change in the person responsible, so this action requires a comment field, the state field, and the agent field.

Allegra knows the following actions:

  • Create item

  • Edit or change an item

  • Move an item to a new project or item type

  • Add a comment to the item

  • Change activity status

  • Add subordinate item to existing item

Each of these actions can be assigned a specific form.