Page History

...

To build this functionality the following steps have to be taken.

1. Define a connection name (or as in the example project two connections) and distinguish whether it should be in memory or on a file system. In this cookbook it 'connection1' and 'connection2' will be 'used: connection1 ' which uploads files to a uploads to the memory, connection2 to the file system. The aquima.properties file has to be extended by the following entryentries:

   Code Block
   connection.connection1.memory connection.connection2.filesystem.path=C:\<...>\aquima.home\UploadedFiles/UploadedFiles/

2. Create an entity 'File' in your model.
3. Create at least one attribute: File.Id. For convenience add also File.Name, File.Type and File.Size.
4. Create an event called 'UploadAction'.
5. Create an exposed flow.
6. Create a page which is put in the flow and is connected.

7. Create a container of type AQ_File_Upload (and put it at the page) with the following parameters:

   Parameter	Value	Comments
   Connection	connection1
   Persistence	Temporary
   Mode	Multiple files
   FileInstance	File	The name of the entity defined in step 2.
   FileID	File.Id
   FileName	File.Name
   FileType	File.Type
   FileSize	File.Size

8. Click the tab 'Events' and select the event 'UploadedAction' at the 'FileUploaded' parameter.
9. Create a container of type AQ_InstanceSelectorPlus.
   1. Let the containment be:
      1. File.Id, File.Name, File.Type, File.Size, all of them read-only
      2. A button 'Delete' (with a corresponding event, connect it in the flow with the AQ_File_Delete service)
      3. A download container (see 'Download File')
   2. Let the parameters be:

      1. Parameter 'entity' should be 'File'.

10. Let the instance selector container be the second container on the page.

...