ProImage Help

Using the File Handler

Using the File Handler

Previous topic Next topic  

Using the File Handler

Previous topic Next topic  

ProImage has an File Handler included with it that is a part of the ProSeries tools.

 

You do not have to use this file handler - it is optional.

 

This file handler can take care of moving your external files to/from a storage folder or drive.

 

It can also automatically take care of storing images in blob fields or in separate blob files linked to the parent record with a LONG (BlobID).

 

 

A note for SQL Users

If you want to use a GUID field (typically a STRING) as the link between your parent record and the Blob Automation record, you will need to edit the blob definition in the dictionary and change it from a LONG to a STRING of the length you require.  Then when you use the ProImage template to map the fields everything should work as expected.

 

 

There are demos for both ABC and Legacy in the examples folder that show exactly how to configure for any of these modes.

 

 

Note: To use the blob automation (external blob storage) you will need to import the PSABlob.txd into your dictionary.

 

A note for SQL Users

If you want to use a GUID field (typically a STRING) as the link between your parent record and the Blob Automation record, you will need to edit the blob definition in the dictionary and change it from a LONG to a STRING of the length you require.  Then when you use the ProImage template to map the fields everything should work as expected.

 

 

Note: You will see references in the File Handler templates to manipulating image sets and name mangling of those sets by the File Handler template.  These features are in place in the template, but not yet implemented in code.

 

When using the file handler with this version, always use the Single File mode.

 

We will  update the docs as the feature is turned on.

 

Also note that right now the ProImage editor is already doing file name mangling for you.

 

 

Short Notes:

 

To use the file handler, add it to the parent form extensions (after adding the ProImage support template).  Then set the properties (see the examples).  Finally add the CODE templates in the Before/After embeds of the ProImage Call Button.

 

 

You can expect an update on the docs in this area in our next release.

 

Since the file handler is designed to work with other tools besides ProImage, these two code templates must be added manually after you add the ProImage Call Button.