FsWebReportTemplate.xsd

A sample report XSD, FsWebReportTemplate.xsd, is installed into Inetpub\wwwroot\FsWebReports\Source.

This applies to the sample report XML template (FsWebReportTemplate.xml).

Here is a description of the contents of the sample FsWebReportTemplate.xsd schema.

Schema header

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:element name="report">
<xs:complexType>

Report name, title, language

<xs:sequence>
<xs:element name="name" type="xs:string" nillable="true"/>
<xs:element name="title">
<xs:complexType>
<xs:attribute name="lang" type="xs:string"/>
</xs:complexType>

Data elements

</xs:element>
<xs:element name="job" type="xs:string" nillable="true"/>
<xs:element name="user" type="xs:string" nillable="true"/>
<xs:element name="passwd" type="xs:string" nillable="true"/>
<xs:element name="presservername" type="xs:string" nillable="true"/>
<xs:element name="servercookie" type="xs:string" nillable="true"/>
<xs:element name="tmpdir" type="xs:string" nillable="true"/>
<xs:element name="objsymbol" type="xs:string" nillable="true"/>
<xs:element name="objdtls" type="xs:string" nillable="true"/>
<xs:element name="xmlstyle" type="xs:string" nillable="true"/>
<xs:element name="defaultmode" type="xs:string" nillable="true"/>

Nillable means that the field can be in the XML file with no value (null). For example, an item may not have a CAS number. A field with a null value is typically not in an XML file. However, Optiva allows it for nillable fields.

Input parameter

<xs:element name="inputparams">
<xs:complexType>
<xs:sequence>

Text parameter (no limit)

<xs:element name="textparam" nillable="true" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="name" type="xs:string"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>

Number parameter (no limit)

<xs:element name="numberparam" nillable="true" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:double">
<xs:attribute name="name" type="xs:string"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>

Date parameter (no limit)

<xs:element name="dateparam" nillable="true" minOccurs="0"
maxOccurs="unbounded">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:dateTime">
<xs:attribute name="name" type="xs:string"/>

Report schema and object schema used for the Report

<xs:element name="SchemaList">
<xs:complexType>
<xs:sequence>
<xs:element name="Schema" type="xs:string" nillable="true" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="object">
<xs:complexType/>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>

Report schema and object schema used for the Report

<xs:element name="SchemaList">
<xs:complexType>
<xs:sequence>
<xs:element name="Schema" type="xs:string" nillable="true" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="object">
<xs:complexType/>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>

Completion tag for the schema files

</xs:schema

Use Optiva Workflow to send the input parameters to an Optiva WebReport XML job file.

You must include this schema as a data source for Crystal.