Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column

palette offers a rich variety of controls that let you create virtually any form. All controls provide functionality as soon as you drop them into your form but need to be customized (edited) to suit the form you are designing. The purpose of each control is described below.

Column
width240px

On this page:

Table of Contents
maxLevel2

...

The control options default to "true=Yes" and "false=No". When you drag the control from the palette, only the "Yes" option will be visible. You can change the option labels from Yes and No to whatever you want. It is important to note changes to the label for false are irrelevant as it will never be visible on the form. The option values cannot be changed and will always stay as true and false. Blank labels for options are not allowedChecking the “Yes” checkbox will result in a true value in the XML document for the control data while leaving it unchecked will translate to a false value( no value will show in the XML document).

...

A Message Control dropped into a table will not have hint, help, or enabled properties. Be sure to check the "hide label" property if you have a message control as a column in your table and you do not want a column label on it. The column label will be hidden in use and edit modes if "hide label' is selected.

 Deleting Deleting a Table Control

Select the entire table control by clicking in the table label. A red  will display. Click on the x to delete the entire table.

...

You can design  for a range of displays: desktop, tablet or smart phones. Forms designed for a desktop may not work as efficiently when used on mobile devices. You can get some Mobile Form Design Strategies from this article by Chui Chui Tan.  screen flows performed on a an iPad or desktop can be quickly approved or rejected by the appropriate individual on their mobile device. For example, employees can submit Expense Reports, Travel Requests, Time Sheets etc via their ipad or desktop browsers as the first activity in the flow. These forms are routed to their respective managers for approval/rejection. The managers can access the requests on a mobile device an iPhone using their Tasks List, accept or reject them and route them to the next step in the flow. Refer to Employee On Boarding Tutorial for an example of an Employee On Boarding a flow that uses mobile forms plus other exciting features.

...

Drag and drop a Page Break control from the palette into your form to specify pages on your mobile devices. You can set a page break for Phone, Tablet or both by checking the Tablet and Phone checkboxes on the Properties panel of the control. If neither is selected, it has no effect.  When the designer clicks Finish, will generate a Smartphone layout and a Tablet layout with the page-breaks specified. If page-breaks are not specified, there will be just one page. The Employee on Boarding form shown below uses the first page break control to display the , if rendered on the iPhone, displays the company information, the new employee's date of birth and manager's name on one page of the mobile device the first page and the new employee's name, social security number and home phone on the next page. The second page break control will show ensures the new employee's address controls will appear on the next page....and so forth.  The tablet layout will show the  

The PageBreak control cannot be dropped BELOW any control. It can be dropped BETWEEN 2 controls or ABOVE any control. Let's say you are designing a form for mobile devices. You drag and drop one control on the form. Now you want to add the PageBreak control and then add other controls below it. You cannot drop the PageBreak below any control so you will have to add the other controls first and then drop the PageBreak control where you want it. Once you add more than one control to the form, you can drop controls from the palette or the form above or below the page break. You can drag and drop the PageBreak itself anywhere at the root of the form. The PageBreak control should not be inside sections, panels, tables or repeat group controls. The only exception is the Tab control. See below for the details.

...