Histórico da Página
...
Responsive Form: On the market today there are varying sizes of screens and resolutions, so any form developed for Mobile should be responsive, i.e. it should fit any screen size.
Aesthetics: The visual appearance and HTML design must be attractive to users; we have achieved it through CSS or jQueryMobile, which will be explained in the next sections.
Usability: The form must be easy to use, containing only fields that are important for tasks or processes.
Click area: HTML elements must be well positioned in a manner that facilitates the click area because there are devices today whose screens are too small. Here is an example:
Positioning of the actions: The most important actions must be placed where the user can easily access them, as shown in the figure:
- Customizations: The customizations must be made within the process events or form definitions on the Web. All the events that are applied in web forms are also applied in Mobile Forms. For more information, visit the guide Customization of forms.
- Attached files: The attached files from the Web form are not loaded onto the Mobile form, so the CSS and Javascript functions should be implemented within the HTML Mobile.
- Access to internal and external services: Any access to Webservices or other external or internal services must be done via javascript. We recommend the use of jQuery Soap for Webservices.
- Not all information needs to be in the Mobile Form: The great restrain in Mobile is the screen size, so map the most important fields so that they are prioritized in the form. There are informative fields that don't have great utility for the process or tasks; they don't need to be included in Mobile Form.
- Types: The Mobile Form definitions support types:
- text
- textArea
- radio
- select
- combobox
- checkbox.
...
Deck of Cards | |||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||
|
...
Process events
In the process events, the property WKMobile identifies if the action was performed by the mobile device, it can be used in the process events as in the example:Bloco de código language javascript function beforeStateEntry(sequenceId){ var isMobile = getValue("WKMobile"); if (isMobile!=null && isMobile==true){ throw "this process cannot be executed by mobile."; } }
...
Example
Faça o download dos arquivos exemplo aqui.
Please download the example files here.
Below is an example of a form that has been mapped for use on mobile devicesAbaixo segue um exemplo de formulário que foi mapeado para uso em dispositivos móveis:
- Web Form
- Mobile Form
Informações | ||
---|---|---|
| ||
As we can see, the Web Form has many fields and its mapping for mobile devices must be done very carefully. The fields Proposal Data were mapped for Mobile, note that there are fields that do not exist in the Mobile as they are not necessary in this context: |
...