Wiki

Scale Your Enterprise

User Tools

Site Tools


versago:images_in_reports

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
versago:images_in_reports [2020/06/16 10:31]
runger [Register Images Manually] - additional detail information
versago:images_in_reports [2020/07/08 13:23] (current)
Line 35: Line 35:
 AND isnull(t2.filepath,'\SiteImages\NoImage_45.png') like '%45%' AND isnull(t2.filepath,'\SiteImages\NoImage_45.png') like '%45%'
 </code> </code>
 +
 +====Register Images Using Bizweaver====
 +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).
 +
 +<WRAP center round tip 80%>
 +The Bizweaver process provided by Third Wave assumes that the file name is structured as ID_Size.  As an example for image A00001, the file names will be A00001_45, A00001_65, A00001_250, and A00001_1024.
 +
 +Further, the "ID" is used to map to a value in the Versago report.  In the previous example, "A00001" will map to an item number in SAP Business One that is included in the report.
 +</WRAP>
 +
 +    * 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.
 +
 +{{ :versago:versago_image_loader_1.png?800 |Image Loader Overview}}
 +
 +    * Set the variable __SourceFilePath__ in the Variables_Init (as shown in yellow below) step to folder path from the previous step.
 +
 +{{ :versago:versago_image_loader_2.png?600 |Image Loader Variable}}
 +
 +  * 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.
  
 ====Register Images Manually==== ====Register Images Manually====
-Versago images are most commonly imported and registered using a Bizweaver workflow.  Information on this workflow is found <color #ed1c24>here</color>.  It is also possible to manage image information manually, as described here.+Versago images are most commonly imported and registered using a Bizweaver workflow. It is also possible to manage image information manually, as described here.
  
 ===Image Files=== ===Image Files===
Line 48: Line 72:
  
   * //File Name// is the name of the image file without the extension; for example 12345 rather than 12345.png.   * //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, 125, or 250.+  * //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__.   * //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.   * //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.
versago/images_in_reports.1592317908.txt.gz · Last modified: 2020/06/16 10:31 by runger