The stucture of groups is rather simple:

Each group can contain multiple buttons that only will be enabled when the group is active

The form stores data related to a main document code. The document is only reported the first time, while each iteration keeps the value filled in the document, which remains displayed in the form

Each apps_wms_formatl must belong to a group, a group can contain multiple apps_wms_formatls:

During the iterations of the form we can access the previous group by using the application button. So we can enter a value from a field that is retained.

In the following example a form with 3 groups:

1. Location
2. Bucket
3. Item

The operator retells locations and buckets. As a location there are several buckets, operator goes back in groups to modify buckets or locations.

Table Model

• A group can have a collection of action buttons.
• The buttons can be enabled or disabled at runtime.
• Allows execute actions during the form input or redirect to other form
• To execute an action is necessary inform button_action. To execute a form is necessary inform form_code.
• Auto launch flag indicates to execute the action or the form automatically without pressing the button.

In this example the operator works around a location, placing product on the same. Two buttons will be added to the group. one button for block location, indicating that it's full and other button to reprint the label location.

Groups can contain buttons, which allow manually launching specific apps_wms_formath. Buttons can be visible or hidden depending on button_cond, when true the button will be visible and hidden otherwise. Only buttons belonging to the group of the current field will be displayed.