Functionalities that would be very helpful for the improvement of the forms module include:
Limitation of the number of columns one can allocate to fields such as the Radio button or checkbox list. The limit is currently set to 6 so if I wish to display a full line item of 10 columns this is not possible. So the ability to select up to at least 10 columns would be great.
Ideas such as AM-I-723 and AM-I-691 - Being able to duplicate fields and groups in forms and safety reports, would be highly beneficial.
Currently, while building a form, one needs to delete a field if the wrong one was chosen and when this happens one is then redirected to the root page which makes creating forms very time-consuming. Therefore the following would be useful: either remove the redirect to the root page and stay on the area on which you were working OR the ability to amend the field type after updating which would eliminate the need to delete the field altogether.
The ability to define custom dimensions on all field types would be beneficial. For example, it is not possible to define the dimensions for the personnel picker field type which then spills over into other fields if you built a small data entry interface.
The ability to include tables per AM-I-293 would be very beneficial.
Currently, it is not possible to pull information from the Locations Register. We are limited to adding only Base names in a drop-down list. Therefore, it would be beneficial to add Bases, Locations and some of their respective properties as well such as contact information as an example.
Allow for search capabilities with the Tree field.
Allow for the ability to link nested drop-down lists to other drop-down lists or Nested drop-down lists.
Move the delete button (generally across Air Maestro) to the last column, currently, it is in the way in the middle column and can lead to the accidental deletion of items.
Allow for the ability of a signature field type especially within the PWA to allow for an electronic signature. AM-I-330 also addresses this need.
In addition to the above, tiered form sign-offs would be highly beneficial for process management structures. AM-I-374.
The ability to assign sign-offs per Form instance as per the Safety Report Type setup/Discretion Reports, where users can, on each form, allocate designated sign-off personnel. Currently, this is restricted to a 'global' setting on a form type which means that everyone added to the sign-off personnel list gets notifications for sign-off instead of only the individuals that are allocated on the new form instance itself.
Allow for the bulk import of data for fields such as Check Boxes, Drop-down lists, Radio buttons and Tree fields. Also allow for the bulk delete of data within these fields.
Allow for the ability to add update rules to personnel pickers.
Currently, when an update rule is applied to a text or other field, the affected field does not clear/refresh when the triggering field has been altered. For example, an item selected in a drop-down list is to update information in a text field. However, when the drop-down list item is changed to a null value or another value, the text field does not clear or adjust its values.
It would be great to have an option to apply alpha-numerical organisation to fields such as Drop-down lists.
This needs to be broken down into individual ideas please.