| 42 | | Table to store data for completed assessments will be defined dynamically when that assessment is first filled. The name of this table will be stored in the template table. The Survey will be accessed via the REST Controller to be filled out, analysed, exported, etc. |
| | 42 | Table to store data for completed assessments will be defined dynamically when that assessment is first filled. The name of this table will be stored in the template table. The Survey will be accessed via the REST Controller to be filled out, analysed, exported, etc.[[BR]] |
| | 43 | This can certainly utilise the new S3Request capability to handle foreign table access, so that you do not need a dedicated controller per survey table, but can just create a suitable request substitute from the controller, like: |
| | 44 | {{{r = s3mgr.parse_request(prefix=xxx, name=yyy) output = r()}}} |
| | 45 | or, if you want more granular control, then use it URL-like: |
| | 46 | {{{r = s3mgr.parse_request(c=xxx, f=yyy, args="create", vars="...") output = r()}}} |
| | 47 | |
| | 48 | |
