Table of Contents
Tahiti is using communication protocol DEP2. There is description of attributes and objects send over this protocol. Specification of DEP2 is available as a separate document.
Tahiti can be used as a mail reader and also can be used to write answer on such email. There is description of attributes used to direct Tahiti behaviour.
Attribute Document.canResponse is voluntary. Possible values: 0|1.
If this attribute is set and value is 1 user is allowed to write response on given document/mail. If this attribute is not set or value is 0 user cannot response such email.
Response on email or new email has mime/type Tahiti.ComposeMail.
Header of the mail based on which the document was created. If this attribute is present Tahiti assumes that document is based on mail. Header has same format as the mail (rfc822) and contains only body of the email (no attachments) and should be limited on some reasonable size e.g.16kb. If this attribute is not present and first page of the document is email Tahiti will treat such document as an email and will use information from the header of such email.
Attribute Document.responseID is voluntary. Attribute is id of the original document on which is current document respons. This attribute is send by Tahiti to the server when user responding to the email.
Attribute Document.responseTo is voluntary. Attribute can be used only when Document.canResponse=1. Attribute contains target address/addresses to be used when user respons to the email. If this attribute is not set address from the email header will be used.
Attribute Document.responseFrom is voluntary. If this attribute is present it contains address to be used as a sender of the email in response. If this attribute is not present Tahiti will set sender to the receiver of the original mail (from the Document.mail.header or from the original email).
There is list of objects which can be send over protocol DEP2
using method pushObject. Such objects can be
send to the Tahiti or from Tahiti to the server. Support for other
objects can be easily added using XPCOM API.
Type: Tahiti.System.DisplayURL
Dispatch URL from the Document Management System to the Tahiti. It will call system handler for this URL and display it.
Type: Tahiti.DistrIdent.DocSet.Open
Notification about new scan job. Tahiti should download list of objects for identification from the server.
Table 2.2. Attributes of Tahiti.DistrIdent.DocSet.Open
| Attribute | Description |
|---|---|
| name of the server (defined in Damis.xml) |
| id of document set |
| value 0|1, allow to re-insert documents to the DAMIS Server (check Damis documentation for more information). |
Type: Tahiti.System.Message
Display message box to the user. System can notify user about some state changes etc. This message box can be only confirmed by user (button OK).
Table 2.3. Attributes of Tahiti.System.Message
| Attribute | Description |
|---|---|
| Type of the message:
|
| Displayed text |
| Detail description (technical information) |
Type: Tahiti.System.CleanCache
Object clean cache in running Tahiti. All pages in the cache are invalidated.
Type: Tahiti.Update.Start
Start update. This object force Tahiti to check if there is newer version. It is possible to specify file to be used for update configuration.
Table 2.4. Attributes of Tahiti.Update.Start
| Attribute | Description |
|---|---|
| File to be used for update. If this attribute is empty default file will be used. |