Page History
...
The created instances will be placed in a table using the AQ_InstanceSelectorPlus with a set of buttons, for example. This results in the example shown underneath at runtime.
| UI Text Box | ||
|---|---|---|
| ||
After a delete or update action you often want to refresh the list. Before retrieving the metadata again you should delete the instances that are already in the profile to avoid double entries. |
Open a document
To open documents that are available on a DMS the container AQ_CMIS_DownloadDocument is available. This container will download the requested document to your session. It can be placed directly in the AQ_InstanceSelector container to work with the corresponding document.
...
The AQ_CMIS_Documentmanager for deleting a document.
| UI Text Box | ||
|---|---|---|
| ||
The update action is developed to update the metadata, not to add a new version of the file. Creating a new version of a file is done by saving a file with the same name in the same directory. Version management is done by the DMS, not by the Blueriq platform. |
Save an uploaded document to a DMS
...
The AQ_CMIS_DocumentManager service that stores a document in a directory with the CaseID and the Case ID as a custom parameter.
| UI Text Box | ||
|---|---|---|
| ||
When a second file with the same name in the same folder is stored, Alfresco creates a new version. To prevent this, use the case ID in the folder structure or the name of the file. |
Save a Blueriq document to a DMS
...
Overview
Content Tools