You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
This service is used to extract the document meta data from the DMS in order to present it on your screen. It does this by creating an instance for every document in the DMS that was found.
See How to setup a CMIS connection for using a DMS in combination with Blueriq..
Parameters
Name | Description |
---|---|
Select entity | Select the entity which contains the attributes you want to map in the document properties. Instances of this entity will be created. |
Assign to relation | This option will add each created instance into this relation. The 'to entity' of this relation must match the selected entity. Additionally, the 'from entity' in this relation must be a singleton, and it cannot be abstract. |
Document location | With this option you can hard set the document location as attribute path within the DMS |
Document properties
The following default document properties can be set. They are used as a filter when retrieving document metadata.
Name | Description | Type | Required |
---|---|---|---|
Name | File name of the document | String | No |
Object Id | Unique object ID | String | No |
Created by | Who created the document | String | No |
Creation date | When is the document created | String | No |
Last modified by | Who has modified the document | String | No |
Last modification date | Document last changed on | String | No |
Version | Version number of the document | String | No |
It's also possible to define multiple custom properties, for example CaseID.
A search criteria expression can be provided for each property, such that only documents that match the result of the criteria expression are included. If a search criteria expression is used for multiple properties, then only documents that match all criteria all included. If the search criteria expression evaluates to unknown then a document matches if it does not have a value for this property.
You can map these in the "Custom Properties" table. For example
Property | TargetAttribute | Search Criteria |
---|---|---|
br:string | CustomCaseID | |
br:date | CustomDatePropertie | |
br:boolean | CustomBoolean |
Events
Do not forget to map an event, in case the service fails.