Optimize current implementation of S3 cloud storage

The current implementation of S3 cloud storage has some disadvantages. It's a "fire-and-forget" approach which has the following disadvantages in detail from our point of view:

• Files with the same name will be overwritten in S3.

  • Idea: add a timestamp to the file name

• The xml file with the metadata is not configurable (for example the location of the file but also the content).

  • Idea: the localtion could be in a separate subfolder to the bucket like '/meta' and the output files are in a parallel folder like '/data'

• The user must choose the delivery option S3 on every run again. There is no option to set a system default, that all outputs should be saved/exported in S3 instead of content store or additionally to content store

  • Idea: Configuration which delivery options are the system default.

• The selection of the S3 bucket must be done manually on every run

  • Idea: Pre-Select the first S3 bucket. This should be similar to what happens with data source connections. If the user has only one connection (or has permission to only one connection), this is automatically selected without user prompting. Only if the user has more than one connection, he/she is being prompted.

• User capabilities not available for every delivery option, there is one for Save-To-Cloud, but not for 'Mobile" and 'Print'. This irritates our user, because they cannot use mobile option and cannot printing

  • Idea: Add user capabilities for 'Mobile' and 'Print'