|
|
|
|
|
A form is a container for one or more items. A form can contain one or more sections and supports multiple locales and layouts. (A section is a form embedded within a form.)
Order in which to create forms
The order in which you can create forms and items depends on the current view of a study:
Working with multiple forms
The topics in this section focus on working with a single form. The Workflow Diagram and the Workflow Grid tabs of the Study Event Editor enable you to specify how forms relate to each other in the workflow of a study event. For more information, see About study workflows.
Naming conventions
Sometimes lists of forms in the Central Designer application include sections, and in the Study Forms Container Editor, sections and forms have the same icon. To more easily identify sections and forms, Oracle recommends that you use a naming convention. For example, you can preface a form name with frm and a section name with sct.
Repeating, common, and associated forms
Certain types of forms have specialized characteristics when deployed in a study.
Repeating, common, and associated forms
Type of form | Characteristic | Property used to define form |
|---|---|---|
Repeating | The form holds multiple instances of the same set of data. | Repeating. If this property is set to True, the form is repeating. |
Common | The same data is visible in all study events that contain the form. | Common. If this property is set to True, the form is common. |
Associated (Two repeating forms in the same study event) | Data from both forms in the association is accessible when a study user works with either form. | AssociatedForm. (This property is visible only in the Structured view of a study.) Two repeating forms in the same study event are associated if the AssociatedForm property of one form is set to the Title of the other form. |
| Copyright © 2013 Oracle and/or its affiliates. All rights reserved. |
|---|