govService Release 484: September 10, 2021

govService Platform

Improvements

• The Upload component now allows larger files to be uploaded to processes. The current 10 MB-per-file limit is being increased to 30 MB, with a lower limit when files are being used with certain Integration types.

The new limits are as follows:

• Maximum size for an individual file upload: 30 MB*
• Maximum (cumulative**) file size compatible with Email and HTTP Integrations: 23 MB
• Maximum (cumulative**) file size compatible with File Integrations: 19 MB

*Note that this is the maximum weight of file that can be uploaded; however, multiple files of this size can be included in a single process.

**The file-size limit for Integrations is cumulative, meaning that multiple files can be included within an Integration but cannot exceed the above limits without causing Integration failure.

The limit can be configured within the Forms Designer by selecting an upload field, navigating to the Validation tab and selecting your required limit from the Maximum File Size menu.

Integration data passes through your site’s LIM and, therefore, larger files being used within Integrations will mean more traffic going through your LIM. Below are further points for consideration if you plan on using larger uploaded within Integrations.

• Check if you have a file titled 'lim.config' on the LIM. If not, the LIM is out of date and requires an update. Follow these steps if you have the file:
  1. Open the file and check whether it contains a 'max_request_length' key.
  2. If the key is present, make sure that its value is greater than 31457280.
  3. If it is missing add the following: <add key="max_request_length" value="419430400"/>
  4. Recycle the application pool hosting the LIM before attempting to use the new config.
• An SMTP server will be configured in the lim.config file for the platform to send emails through. If you plan on attaching user uploaded files to emails, please check the maximum file size allowed on the SMTP server. This will need to exceed, by at least 5 MB, the maximum file size you are using within Email Integrations. This 5 MB buffer accounts for the email content and the slight size increase of the file due to base64 conversion that is required for transmission. As above, govService currently supports the passing of files up to 23 MB within an email integration.
• File integrations allow for files uploaded within a process to be saved to a local folder on the LIM. You will need to consider the space available on the LIM and how quickly it may fill up. As above, govService currently supports the use of 19 MB files within a File integration.
• HTTP integrations allow for uploaded files to be sent via HTTP POST. These can be sent via the platform LIM (commonly known as LIM 14) or the locally installed LIM. As above, govService currently supports the use of 23 MB files within an HTTP integration. This is the same for both the platform LIM and local LIM.

• When uploading files to a form, currently, a notification appears informing users that their file is being uploaded, and the message disappears only once the upload is complete. This text appears as so: "Waiting for all files to finish uploading."
  In this release, the message has been expanded to ask users not to navigate away from the page until uploading completes. The new notification text: "Waiting for all files to finish uploading, please do not close or navigate away from this screen."
  Remaining on the form until uploads are complete ensures that the file uploads successfully.
• Realtime Reporting:  We have added a new table for reporting on integration_logs which will allow you to access results logged from integration calls. This table is updated in realtime. The data model in the Realtime Reporting Guide has been updated to reflect the addition of the table to the Redshift database.
• Realtime Reporting: We have added a comment field on the IP Allowlist tab so users can annotate a brief description of what the IP address is. Please note: If you've already added IP addresses and want to add a comment, you will need to remove it and add it back in.
• We have restored querying transaction result functionality for card payments in Civica eStoreSSO payment connector.