Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| docs:3500:0600 [2023/04/05 05:52] – ↷ Page name changed from docs:3500:0600_adding_custom_document_types to docs:3500:0600 sean | docs:3500:0600 [2025/06/12 04:00] (current) – Change to AwareIM aware_support3 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ====== Adding custom document types ====== | ====== Adding custom document types ====== | ||
| - | //**Aware IM**// comes with a number of predefined document types: - Report, MS Word, Text, MS Excel, HTML. These documents types should be sufficient for most applications. If, however, an application uses other document formats new document types can be added to //**Aware IM**//. | + | //**AwareIM**// comes with a number of predefined document types: - '' |
| - | Note that adding new document types is only necessary if you want to include tags in documents and you want //**Aware IM**// to replace tags with specific attribute values at run time. If you want to use documents without modifying them you can just attach a document in any format to a form of a business object that has an attribute of the Document type defined and //**Aware IM**// will store the document in the database. In this case //**Aware IM**// does not need to know about the internal structure of the document. | + | Note that adding new document types is only necessary if you want to include tags in documents and you want //**AwareIM**// to replace tags with specific attribute values at run time. If you want to use documents without modifying them you can just attach a document in any format to a form of a business object that has an attribute of the '' |
| - | To add a new document type to //**Aware IM**// follow the steps below: | + | To add a new document type to //**AwareIM**// follow the steps below: |
| - | - Write the code for the component that will work with documents of the new type on the client side (see section 6.1 for details). | + | - Write the code for the component that will work with documents of the new type on the client side (see [[docs: |
| - | - Write the code for the component that will work with documents of the new type on the server side (see section 6.2 for details). | + | - Write the code for the component that will work with documents of the new type on the server side (see [[docs: |
| - | - Compile the source code of your components and package them in a jar file(s). Make sure that the jar file resides in the AwareIM/ | + | - Compile the source code of your components and package them in a jar file(s). Make sure that the jar file resides in the '' |
| - | - Add the definition of a new document type to the BASServer.props file located in the BIN directory of your //**Aware IM**// installation. You have to modify the line that sets the DocumentEngines property to add the fully qualified name of your server side component. | + | - Add the definition of a new document type to the '' |
| - | DocumentEngines=com.bas.basserver.documents.JasperReportsEngine, | + | DocumentEngines=com.bas.basserver.documents.JasperReportsEngine, |
| - | Note that you have to make sure that the jar file with your server side component as well as the modifications to BASServer.props file are available to the Aware server that hosts your application (see “Aware IM Installation Guide” for details). | + | Note that you have to make sure that the jar file with your server side component as well as the modifications to '' |
| - | If everything has been done correctly the new document type must appear in the list of document types displayed by the Document Template Property Editor (see “Adding/ | + | If everything has been done correctly the new document type must appear in the list of document types displayed by the Document Template Property Editor (see [[docs: |
| - | {{simplenavi> | + | {{simplenavi> |