# OZ e-Form Overview

## Key Product Release

* Jan 2000: **OZ Report 1.0**
* Mar 2012: **OZ e-Form 1.0 ( = OZ Report +&#x20;**<mark style="color:red;">**fillable form**</mark>**&#x20;)**
* Nov 2018: [***eformsign***](https://www.eformsign.com/global/index.html) (cloud document signing service)
* Apr 2019: **OZ Report 8.0**, **OZ e-Form 8.0**
* Jan 2021: **eformsign On-premise**
* Mar 2024: **OZ Report 9.0**, **OZ e-Form 9.0**

## Product Family <a href="#oz-e-form-product-family" id="oz-e-form-product-family"></a>

### ⭐ Designer <a href="#e-form-designer" id="e-form-designer"></a>

#### 👉 OZ Query Designer

* Create dataset definition from data sources:
  * Database: RDBMS, MongoDB, SAP RFC, SAP HAHA
  * File: XML(no DTD/XSD), CSV
  * HTTP: XML(no DTD/XSD), CSV
  * Web service: XML(DTD/XSD), SOAP, ADO dataset
* Create RDBMS dataset definition with SQL&#x20;
  * Write SQL manually
  * Use interactive Query wizard
  * Scripted Query for run-time dynamic Query&#x20;
* Save the results as <mark style="color:red;">**ODI**</mark> files

#### 👉 OZ Report Designer

* Import data sources from the <mark style="color:red;">**ODI**</mark> files
* Build reports with list tables, cross-tabulations, master-detail table, and various charts from datasets retrieved from imported data sources
* Aggregation and calculation of field values
* Save the results as <mark style="color:red;">**OZR**</mark> files

#### 👉 OZ e-Form Designer

* Includes all the Report Designer features
* Pixel perfect professional fillable forms designer
* Rich input components such as:

  TextBox, ComboBox, CheckBox, RadioButton, Button, DatetimePicker, NumericUpDown, Photo Capture, Barcode Scan, NFC scan, Voice Recording, VideoPlayer, SignPad (scribble signature), HandWriting, etc.
* Rich component properties that can be controlled in detail
* Create forms by copying contents from MS Office documents (DOC, PPT, XLSX)
* Create forms by importing PDF documents and adding input components
* e-Form API for business logic and dynamic actions inside forms with various events and JavaScript methods
* Viewer API for integrating e-Form into web applications
* Prefill data into e-Form
  * Data Services (CSV, JSON, XML)
  * Data sources (ODI)
* Extract input data from e-Form (JSON, XML)
* DialogueFlow
* Save the results as <mark style="color:red;">**OZR**</mark> files

#### 👉 OZ in Office

* MS Office Add-In for end-user
* Build fillable e-forms in MS Word, Excel, or PowerPoint
* Easy and quick design of e-Form
* Limited features and no API supported
* Excel Add-in supports Excel expression
* Upload a finished document to the server
* The document is converted to OZR and saved on the server
* Download **OZinOfficeforOZe-Form\_version.zip** from 👉 [Product Downloads](/product-downloads.md).

### ⭐ Servers <a href="#e-form-servers" id="e-form-servers"></a>

#### 👉 OZ e-Form Server <a href="#e-form-server-enterprise-server" id="e-form-server-enterprise-server"></a>

* Process e-Form request from the client OZ Viewer
* Get datasets from data sources as defined in ODI files.
* Send e-Form and datasets to the client OZ Viewer.
* OZ Server Console
  * Server monitoring and management
  * Essential for managing multiple servers
  * Modification of server configurations without shutting down
  * Create and manage e-Form batch jobs to be run by the Scheduler server.
  * Upload or download e-Form files (OZR and ODI) and other files to/from OZ Server Repository.
  * File sharing and version control for multi-user collaboration
  * [oz.ozeform.io:8080/training/server](http://oz.ozeform.io:8080/training/server)
* 3 types of OZ Server:
  * Servlet type (integrated into the JAVA platform)
  * .NET type (integrated into the .NET framework)
  * Daemon type (standalone)

#### 👉 OZ Scheduler <a href="#scheduler-server" id="scheduler-server"></a>

* Automate repeated or bulk report generation by scheduling
* Run batch jobs to generate reports, export to documents, and print or email documents
* Batch jobs can be registered and scheduled with the OZ Server Console.
* Generate HTML5 SVG preview of OZR

### ⭐ Viewers <a href="#e-form-viewers" id="e-form-viewers"></a>

#### 👉 OZ e-Form Viewer <a href="#e-form-viewer" id="e-form-viewer"></a>

* Integrated into web or mobile applications with Viewer API
* Receive e-Form and data from the server, bind and render them on viewer pages
* Export(save) e-Form to <mark style="color:red;">**OZD**</mark>, or document files (**PDF**, **XLSX**, **DOC**, **PPT**, **HTML**, **CSV**, **TXT, JPG, PNG, etc.**)
* Extract input data in JSON format from e-Form
* Various printers are supported for printing e-Form documents.
* Viewer types:
  * HTML5 viewer for HTML5 supported browsers
  * ActiveX viewer for Internet Explorer
  * Native mobile viewers for iOS, Android, and UWP

#### 👉 OZ Multi-Screen Viewer <a href="#multi-screen-viewer" id="multi-screen-viewer"></a>

* Multi-Screen Viewer synchronizes data between viewers on the main screen and sub-screens connected to the desktop by USB interface cables.
* Multiple sub-screens can be synchronized
* Sub monitor: Wacom tablets, etc.
* [Watch demo](https://drive.google.com/file/d/1Y07XnX2N0wbAyKZHiFG8-LTmtcd71Se6/view)

![](/files/h49y6lV1foroQoj7rCUL)

### ⭐ OZ Sync-Server

* OZ Sync-Server synchronizes data between an agent viewer and client viewers over the internet.
* An agent viewer and client viewers can be configured as desktop-to-desktops or desktop-to-mobile devices.
* Sync-Server and e-Form Server can run on the same server or different servers.
* Client device: iPad, Galaxy Tab, etc.

![](/files/NEQwR5TkRkD9cNkZMOuk)

{% content-ref url="/pages/-MjDNXLc5R5uooqLfgtP" %}
[Sample Application](/server-developer/sync-server/sample-application.md)
{% endcontent-ref %}

### ⭐ OZ Dialogue Flow Option

* DialogueFlow enables the user to fill in input fields with the interactive question-answer dialogue instead of entering data in the actual form on mobile devices.&#x20;
* Dialogues will ask questions by voice and text for input fields and the user can answer by voice or text.
* There is no need to develop additional small forms for small screens. And the user does not need to zoom in on the form to enter data into input fields.
* The question order can be set in the DialogueFlow list for the user to answer in a predefined sequence.

![](/files/XTzGAnCSoRBHZ2O1Nflz)

### ⭐ OZ Toto Framework

* A HTML framework to develop **hybrid mobile apps** with the e-Form mobile viewer.
* Android 5.0 or later, iOS 8.0 or later

### **💻 System Requirements** <a href="#system-requirements" id="system-requirements"></a>

<table><thead><tr><th width="193">Product</th><th>Platform (minimum)</th><th>Requirement (minimum)</th></tr></thead><tbody><tr><td>OZ Server Servlet</td><td>JRE 1.8 supported OS</td><td>2GB Mem</td></tr><tr><td>OZ Server .NET</td><td>.NET 3.0 supported OS</td><td>2GB Mem</td></tr><tr><td>e-Form Designer</td><td>Windows 10</td><td>1GB Mem, 1920x1080 pixels</td></tr><tr><td>HTML5 Viewer</td><td>HTML5 supported browsers</td><td></td></tr><tr><td>iOS Viewer</td><td>iOS 11, XCode 13 or above</td><td></td></tr><tr><td>Android Viewer</td><td>Android 8.0 or above</td><td></td></tr></tbody></table>

## OZ e-Form Service Flow <a href="#oz-e-form-lifecycle" id="oz-e-form-lifecycle"></a>

![](/files/8o0Cy5k4PGarYN292o6g)

#### **1. Install e-Form Server in WAS server (Server admin)** <a href="#id-1-install-eform-server-in-was-server" id="id-1-install-eform-server-in-was-server"></a>

* Deploy and configure the e-Form Server on the WAS server.

#### **2. Develop and upload e-Forms (e-Form Developer)** <a href="#id-2-create-and-upload-e-forms" id="id-2-create-and-upload-e-forms"></a>

* Develop e-Forms (OZR) and upload them to the Server Repository with e-Form Designer.

**3. Integrate e-Form in your applications (Server Developer)**

* Integrate e-Forms into your front-end e-Form applications.
* Develop your back-end applications to process data and forms submitted by clients.

**4. Fill out and submit e-Forms (End User)**

* The user accesses the e-Form application with a web browser or mobile App.
* The user opens and fills out the e-Form with the HTML5 or Mobile Viewer.
* The e-Form web application or mobile App sends the completed e-Form with input data back to the backend application.

**5. Save data and documents (Backend Developer)**

* The backend application saves data into the database.
* The backend application saves e-Form as PDF in local or external storage (AWS S3, etc.), or integrates with EDMS/CMS.
* The backend application can request Timestamping and digital certificate services from TSA(Timestamping Authority) and CSP(Certificate Service Provider) to secure legal proof of PDF documents.

#### 6. Manage Servers and export eforms (Server Admin) <a href="#id-6-manage-server-and-service" id="id-6-manage-server-and-service"></a>

* Manage e-Form Server and Scheduler configuration
* Upload eform files to the server and manages eforms repository
* Manage user groups, users, and category permissions (Repository with RDB configuration)
* Export eforms to documents with the Scheduler

## Typical e-Form Application

### Frontend application

1. Show the list of forms
2. Open the selected form
3. Save a draft on the client or send it to the server
4. Validate user input
5. Submit: extract input data and send it to the server
6. Show the list of PDF files saved on the server

### Backend application

1. Receive draft form from the client and save it
2. Receive input data from the client and process or save it to the database
3. Bind input data with form template and export it to PDF file

### Example

* [Web example](http://oz.ozeform.io/oz/edu/clientbind/export.html)
* Mobile example


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://edu.ozeform.io/e-form-developer/day-1-welcome-on-board/oz-e-form-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.