...
Name | Type | Required | Description |
id | string | yes | unique identifier |
entity | yes | The entity that this DMS will provide documents for | |
name | string | yes | The name of this DMS |
datadefinition | yes | A reference to a data definition that will supply the attributes and URL link for each document | |
acl | no | A reference to an ACL to attach to the dms. Only available since Weave 2.5.16. |
Sub-tags
Name | Type | Cardinality |
acl | 0..1 |
Content
None
Notes
- The
nameis used because there may be more than one DMS attached to an
entity type and this helps the user differentiate beween them
...
A simple example that uses a table that has a description and url column
| Code Block | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
<data:datadefinition id="property_doclink">
<datasourcedataconnection datasource="docsource" table="PROPERTY_DOCLINK" key="PID">
<parameter column="description"/>
<parameter column="url"/>
</datasourcedataconnection>
</data:datadefinition>
<dbdms:dms id="old_docs">
<name>Uploaded Documents</name>
<entity>property</entity>
<datadefinition>property_doclink</datadefinition>
</dbdms:dms>
|
Creating a list of documents to display properties in google maps.
The data definition constructs the url by concatenating a the first part of a google maps search to a pre-formatted address column from the database.
| Code Block | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
<data:datadefinition id="property_google">
<datasourcedataconnection datasource="docsource" table="PROPERTY_DOCLINK" key="PID">
<parameter name="url" type="url" text="Display in Google Maps" url="'http://maps.google.com.au/?q='|address"/>
<parameter column="address"/>
<datasourcedataconnection>
</data:datadefinition>
<dbdms:dms id="google">
<name>Google Maps</name>
<entity>property</entity>
<datadefinition>property_google</datadefinition>
</dbdms:dms>
|