Skip to main content
Extended QR Code on Files

This article shows you how to use extended QR codes on files.

Updated over a week ago

Asite enables configuring of QR code function for files uploaded in all formats supported by Asite File Viewer with the help of workflow system tasks. Without the help of workflow system tasks, QR code function is limited to files uploaded in PDF format only based on the project and folder configuration.

Let's take an example of a project wherein QR code is enabled both at project level and folder level. To configure QR code function for files uploaded in all formats supported by Asite File Viewer, user has to follow below steps based on type of QR code:

________________________________________________________________________________________

1. Steps to follow in case of Static QR code type

Step 1: Configure a file system task for executing the groovy script in the relevant project. Here, use the groovy script to embed QR code (of 'Static' Type) while printing and downloading the document having any of the file format supported by Asite Viewer as required.

Step 2: Configure another file system task for executing the groovy script in the same project. Here, use the groovy script to enable 'Include QR code' option in download preference.

Step 3: Configure another file system task for executing the groovy script in the same project. Here, use the groovy script to display required details while scanning QR code (for 'Static' type) as required.

Step 4: Once the system task containing groovy script is configured, user can configure a file workflow trigger for the relevant folder in the same project. This workflow trigger is meant to be configured in a way that the first system task can be triggered upon 'Download Documents' event in the selected project folder in 'Pre' task mode.

Step 5: Once the system task containing groovy script is configured, user can configure a file workflow trigger for the relevant folder in the same project. This workflow trigger is meant to be configured in a way that the second system task can be triggered upon 'Download Documents' event in the selected project folder in 'On-Load' task mode.

Step 6: Once the system task containing groovy script is configured, user can configure a file workflow trigger for the relevant folder in the same project. This workflow trigger is meant to be configured in a way that the third system task can be triggered upon 'QR Code Scan' event in the selected project folder in 'On-Load' task mode.

2. Steps to follow in case of Dynamic QR code type

Step 2: Configure another file system task for executing the groovy script in the same project. Here, use the groovy script to enable 'Include QR code' option in download preference.

Step 3: Once the system task containing groovy script is configured, user can configure a file workflow trigger for the relevant folder in the same project. This workflow trigger is meant to be configured in a way that the first system task can be triggered upon 'Download Documents' event in the selected project folder in 'Pre' task mode.

Step 4: Once the system task containing groovy script is configured, user can configure a file workflow trigger for the relevant folder in the same project. This workflow trigger is meant to be configured in a way that the second system task can be triggered upon 'Download Documents' event in the selected project folder in 'On-Load' task mode.

________________________________________________________________________________________

Once configured, the QR code will be visible while printing / downloading the file from the listing page. Accordingly, there would be an additional option for including QR code in 'Download Files' window as shown below:

If the 'Include QR Code' option is checked while downloading files, there will be an additional PDF file included within the downloaded .zip file. This additional file will be a PDF version of the original parent file and will also include the QR code.

Users can scan this QR code and retrieve file details as per the QR code configuration within the relevant project.



Did this answer your question?