Page History
...
First step is to create the file from the Document and store it on the filesystem, second step is to get all necessary metadata to display in the list. This results in this flow:
| UI Text Box | ||
|---|---|---|
| ||
The first servicecall is of type 'AQ_Document_Generate', the second of type 'AQ_File_GetMetaData'. |
...
Shown below is the screen for the AQ_Document_Generate service.
Parameters
In AQ_Document_Generate all parameters are discussed. In this article, the focus is on the following parameters:
- CreateInstance
Because the document/file has to appear in an instancelist, I have to create a new instance. In this example a 'Document' instance is created, based in on the entity mentioned in the FileID parameter. - Relation
The new Document instance will be added to the VergunningCase.Bewijs Documents relation, because in my example the instancelist only contains 'VergunningCase' documents. - Persistence
Persistence has to be permanent - in this example on the filesystem - because the file has to be kept in storage due to audittrails. Temporary persistence in memory isn't a suitable solution, because the file will be gone when restarting the Runtime for example.
In the example above Summary: a Document instance is created and added to the VergunningCase.Bewijs Documents relation.
| UI Text Box | ||
|---|---|---|
| ||
The AQ_Document_Generate service doesn't retrieve the metadata - like filename and date created - from the file. To retrieve this information from the created file, the service AQ_File_GetMetaData can be used. |
...
Shown below is the screen for the AQ_File_GetMetadata service.
Parameters
In AQ_File_GetMetaData all parameters are discussed. In this example the filename, type, size and creation info are added as information to the Document instance, because this is the metadata set when generating the file.
...
Overview
Content Tools