Saving all components
When you save all components, the InForm Architect application saves generated XML files for all trial components in cache, whether or not they are used in the active trial definition. Each type of component is saved in a separate XML file; for example, there is an XML file for text box controls, one for pulldown list controls, one for rules, and one for events. Additionally, the InForm Architect application generates and saves a response file containing the names of all component XML files and saves the trial definition file for the active trial.
This method of saving trial components creates files that MedML Installer can process efficiently. You may find this method most useful when you plan to load a complete trial definition into a test environment. To save all components:
- Select File > Save Trial. As a shortcut, you can click the Save All button
on the Main toolbar.
- Then, choose Save All.
- In the Specify the Trial Directory dialog box, specify the root directory in which to save the XML files for all defined components.
- Click OK.
The following table describes the response and XML files created when you save all components. The XML files are shown in the order in which they appear in the response file, and thus the order in which they would be processed if you loaded the response file by using the MedML Installer.
Filename |
Description |
---|---|
ADM_US.xml |
User definitions |
AllObjects.rsp |
Response file containing the name of each saved XML file |
CLCCTL.xml |
Calculated control definitions |
ConvertRuleStorage.xml |
Unit conversion rule definitions |
DATECTL.xml |
Date/time control definitions |
ELTCTL.xml |
Simple control definitions |
EXP_CH.xml |
Execution plan definitions |
FLTELT.xml |
Float element definitions |
FORM.xml |
Form definitions |
GPCTL.xml |
Group control, radio group control, and check box control definitions |
GROUP.xml |
Query group, rights group, and signature group definitions, as well as the definition of the predefined manager user group for reporting |
ITM.xml |
Item definitions |
ITMSET.xml |
Itemset definitions |
LBCTL.xml |
List box control definitions |
NUMELT.xml |
Numeric element definitions |
PDCTL.xml |
Pulldown control definitions |
RIGHT.xml |
Standard right definitions |
RUL_CH.xml |
Rule definitions |
RUL_EV.xml |
Event definitions |
SECT.xml |
Section definitions |
SEQUENCE.xml |
Sequence definitions |
SITE.xml |
Site definitions |
SITEGROUP.xml |
Sitegroup definitions |
SPONSOR.xml |
Sponsor definitions |
STRELT.xml |
String element definitions |
StudyVersionName.xml |
Trial definition and association with sites; filename is the version name of the trial definition |
SVSITE.xml |
Studyversion site definitions, associating a trial definition with a site. |
SYSCONFIG.xml |
System configuration settings |
TDEDATAMAP.xml |
Data mapping definitions (metadata) |
TXTCTL.xml |
Text control definitions |
UNIT.xml |
Unit definitions |
Note: When you save all trial components repeatedly, the InForm Architect application creates backup copies of the most recently saved files. Each time you save, the InForm Architect application overwrites the backup with the previously saved version and overwrites the previously saved version with the new version.