The page is used to define which columns are displayed in the data view, the order the fields are displayed, and to set various display options.

• The order of the fields can be changed via drag & drop
• The Aggregate option provides a way to automatically display count, average and sum totals.
• Group By causes the output to be automatically grouped for each unique value in the selected data.
• Display Type identifies how the data in a column should be interpreted for presentation.
• Localization is used to adjust the formatting of date, datetime, and currency types.
• File Name is only accessible when the data type of the column is binary, blob, or varbinary . See Note 1 below.

Note 1

A Data View can display a file for download. The file can be stored in the file system or in the DB in a binary field

• Disk Source Files should be included by using the full path name in the field.
  • The source files must be in a folder location that can be accessed by Versago and Windows IIS. What this means is that files will typically need to be in a network share, e.g. “\\ShareName\FolderPath\FileName” and not in a typical file path like “C:\Data\FileName”.
    • The Display Type should be set to File

• Database Source Files are identified by reference to specific records in a database. The information provided below refers to files uploaded via a Versago form.
• The data is found in a table named “TWBS_VGO_FormAttachments”. This table is found in the database where the data captured in the form is stored.
  • Two values are required from the record: FileName and FileContent. FileContent is the binary data that will be converted for download. FileName is used as the reference to the binary data.
  • When the data type of the column is binary, blob, or varbinary the File Name field for the FileContent row presents a drop-down list of fields from the report query. Select the column name that contains the associated file name.
  • It is not necessary to display the FileName value in the report, but showing the user the name of the file is typically very helpful.

The files in a database approach does require that the FileContent value is not NULL. As it is very possible that a report row will not have a corresponding report to download, use the following SQ. Setting FileContent to 0 when the database value is NULL allows the report to execute without errors.

isnull(t1.FileName, 'No File') as [FileName], isnull(t1.FileContent,0) as [FileContent]

In both cases, keep in mind that any user that has access to the report can download any file listed in the report. If certain files should be available to certain group(s) of users, different reports may be needed.

Highlights are a simple visual cue presented when the data matches the defined conditions. Highlighs can be configured for any numeric value in a Versago Data View.

It is possible to calculate values at the time a report is executed and present them as a new column. This is done using the [Derived Field]button at the bottom of the page.

1. Enter the name for the new derived field
2. Use the available functions to build your formula
3. Click validate to check your syntax
4. Save the derived field

The following image formats are supported.

• PNG (preferred)
• JPG
• GIF
• BMP (not recommended)

Each image must be provided in four (4) sizes.

• 45 x 45 for thumbnail image
• 65 x 65 for thumbnail image
• 250 x 250 for mouse-over (hover) image
• 1024 x 1024 for on-click (large) image

Images are held in the folder C:\Program Files(x86)\TWBS\Versago\WebApp\SiteImages.

The images must also be registered in the Versago common database in the versago_image_files table. A Bizweaver workflow is available to assist with this process. Images can also be registered manually as described elsewhere in this page.

This example displays a list of production orders with an image of the finished product.

• The database for “vgoCommon” may need to be changed for your installation.
• “isnull(t1.filepath,'\SiteImages\NoImage_45.png')” assumes you have an image to be displayed when an actual image is not available.
• Use either “45” or “65” in the selection. 45 is used in this example. The other sizes (for the other thumbnail, image rollover and image click) are determined automatically by Versago.

SELECT
t0.ItemCode, t1.ItemName, isnull(t2.filepath,'\SiteImages\NoImage_45.png') AS [ImagePath], t0.DueDate, t0.Status, t0.DocEntry, t0.DocNum
FROM OWOR t0
INNER JOIN OITM t1 ON t0.ItemCode = t1.ItemCode
LEFT JOIN [vgoCommon].dbo.[versago_image_files] t2 ON t0.ItemCode = t2.IntersectionID COLLATE database_default
WHERE t0.Status IN ('R','P')
AND isnull(t2.filepath,'\SiteImages\NoImage_45.png') LIKE '%45%'

In most cases, using a Bizweaver workflow will be the quickest and easiest way to register images for use with Versago. A standard workflow named “Versago Image Loader” is available from Third Wave as a download from https://portal.twbs.com (login required). Following are the steps to use the workflow.

• Create the four sizes of each image as noted above. There are a number of applications that can assist with this process. One that Third Wave has used with good success is FastStone Image Resizer (www.FastStone.org).

• Place the files in a Windows folder that can be accessed by Bizweaver.
• Open the Bizweaver workflow. The steps will appear as shown in the following image.

• Set the variable SourceFilePath in the Variables_Init (as shown in yellow below) step to folder path from the previous step.

• Execute the workflow
  • The Versago images table is updated with the needed information and the files are copied to the folder used by Versago.
  • If an image already exists for a given ID and size, it will be updated. Otherwise, the new image is added.

Versago images are most commonly imported and registered using a Bizweaver workflow. It is also possible to manage image information manually, as described here.

Four image sizes are required as noted above. The images should be placed in the older C:\Program Files(x86)\TWBS\Versago\WebApp\SiteImages.

The Image Maintenance form can be used to update information created through the Bizweaver upload process or to add image information manually.

• File Name is the name of the image file without the extension; for example 12345 rather than 12345.png.
• File Size is the size of the file in pixels. Values will be 45, 65, 250, or 1024.
• File Path is the abbreviated file path of the image file. It will always be \SiteImages\FileName.Ext. So using our previous example the entry will by \SiteImages\12345.png.
• Intersection ID is used to match the image file to its associated object. In the example image below, the image file is associated with item 790824300010.

Add/Edit Data View

Home