Specifying the IEG files to create and store

The intake process provides the facility for the user to enter the information to be stored within the data store. The files that are created are the IEG script, the schema, and domains specific for the fields that are defined in the IEG script.

Procedure

  1. Create the IEG script, the schema, and the domains files.
    File name Description
    <IEGScriptName>.xml The IEG script consists of various element references to configure such as questions, list-questions, help-text, summary-page to name just a few. It also includes meta-display elements, which provide information on how elements to be displayed. The IEG script can be configured so that display elements are configured with a logical flow. The flow-control elements include loops, validations, and conditions.

    The IEG script also consists of structural elements to allow for grouping of sections. The ability to create Java callouts to start code that is not part of IEG to run operations for the script execution. You also can split a large IEG script up in to maintainable sub scripts.

    <ScriptName>.xsd The Cúram Data Store entity and entity fields are defined within the <ScriptName>.xsd file.
    <ScriptName>Domains.xsd The domains for each of the fields that are referenced in the schema are defined within the <ScriptName>Domains.xsd file.
  2. Create the following DMX files to store the reference to the IEG script, the schema, and the domains files created.
    File name Description
    IEGSCRIPTINFO.dmx The script provides the facility for the user to enter the information to be stored within the data store. Each script's location is defined in IEGSCRIPTINFO.dmx file.
    DATASTORESCHEMA.dmx The location of the <Script>.xsd and <Script>Domains.xsd are defined within the DataStoreSchema.dmx.
    APPRESOURCE.dmx Images (.png files) and text descriptions (.properties files) used by the IEG script must be defined and their locations that are referenced in the AppResource.dmx.
  3. From %CURAM_DIR%\EJBServer, run build database.
  4. Save your configuration files.