Signature Integration

The Signature Pad Integration with Power Broker 4 enables the broker to hand the pen over to the customer, allowing the client to sign on the dotted line, and anchoring the signature to the application/form, and then storing it in the clients Power Broker abeyances section. With the signature pad installed you are also able to store signatures for each Producer and CSR by using the Capture Signature button in the respective tables. These signatures can then be pulled into CSIO applications and forms with buttons - Producer Signature and CSR Signature. The signature will be pulled based on the producer or CSR recorded on the customer screen for this customer.

For this integration to work, you would need:

1) The Power Broker Scanning/Digital Camera option

Contact - sales@power-broker.com and request an invoice for the Scanning/Digital Camera option
Cost - $500.00 plus Tax

NOTE: ( To check and see if you already have the Scanning/Digital Camera option, you would first go to the main Power Broker desktop, and just above 'General Ledger' you would see a 'Help' option. Click Help, and then 'About Power Broker 4' and if you already have an 'Enabled' located next to Scanning/Digital, then you do NOT need to send an email to purchase it, as you already have this feature.)

2) You would need to purchase the TOPAZ T-S460-HSB-R TOPAZ SIG LITE SIG CAPT 1x5 USB (HID) [T-S460-HSB-R]

NOTE: ( It specifically needs to be this exact same make and model for the integration to work)

Click here to launch WWW.GOOGLE.COM SEARCH for this item.

TOPAZ T-S460-HSB-R TOPAZ SIG LITE SIG CAPT 1x5 USB (HID) [T-S460-HSB-R]

Quantity 1 - PRICE - $129.99

When you click on the Capture Signature button you will see the Form that displays the captured signature.

The client would use the sign their signatures on the Signature pad.

If the signature is clear, then the 'write to Power Broker' button is pressed.

The signature would then be attached to the application or Form that was being generated.

Click here to download the install file
Updated September 19/2011

Sample Install:

Sample Workflow

Producer Signature / CSR Signature – click one of these buttons to pull the signature as previously stored in the

Producer or Customer Service Rep table.

Reviewing Your Saved Signature

TERMINAL SERVER USERS SECTION:

If you are NOT using a terminal server setup, then please ignore:

Installation procedures for Topaz Signature pad in a terminal services environment

Ports Required:

TCP Ports 47289 and 47290 used. (In our testing, there were no port adjustments needed to be made.)

Download and SAVE sigsockinstall.zip to MyDocuments

Server Configuration:

Install Sigsockinstall.exe using the same settings as from the instructions at the top of this page.

Locate sigplus.ini in the \Windows folder and copy this to c:\documents and settings\<<username>>\Windows

Edit sigplus.ini changing the TabletPortPath = clientname.

Note: ClientName defined here must be derived from the following step.

In this example, the userid in Power Broker Version 4 is KV

Use PB + my PB userid = PBKV ( as seen at the bottom right of this screen capture )

Workstation Configuration:

Create a folder C:\Sigplus

Copy <Server>\windows\sigplus\tools\sigsock\sigsock.exe to c:\sigplus

Create a batch file that will launch the sigsock.exe with 3 paratmeters:

<<Servername.domainname>> << clientname>> 6

In this example, we are looking at C:\Sigplus and we have created a blank batch file and called it sigsock.bat.

Right click and edit the sigsock.bat

( To create a batch file, right click in Windows Explore ( in the c:\sigplus folder ) and choose New and then Text, and then
name the file sigsock.bat, and then say 'yes when it warns you that you are changing the file extension and that it may not work)

In the empty batch file, you would type in your own details:

Example: sigsock.exe myserver.mydomain.com MyClientName 6

Click FILE and then SAVE to record the changes made in the batch file.

RUNNING SIGSOCK.BAT

Ensure that the sigsock.bat is loaded before the terminal services connection is initiated.

One method would be to include this in a Log-in script or another option would be have an icon on your local workstation
desktop that points to c:\sigplus\sigsock.bat and the user would need to manually launch this file for the integration to work.

Before connecting, the file would need to be initialized with either method.

( In this example, we've simply launched it from Windows explorer and a DOS window sits on the desktop.
If it were installed with a log-in script, your local technical support representative can hide the dos window by adding a few lines to the batch file. )

The user would then launch the Terminal Server connection to connect to the server, and then proceed with your
test signature.

This integration has been tested on Windows XP, Vista, and Windows 7 using both local and Terminal Services method.

Black Box Error - Third party software may interfere with the Signature Integration by changing an important element of the computers registry. Should you receive a black box in your form or application, you would need to edit your registry. A WORD OF WARNING - EDITING YOUR REGISTRY MAY DAMAGE YOUR COMPUTER - PLEASE ENSURE THAT YOU BACKUP YOUR REGISTRY BEFORE HAND - Once backed up, you would go to Start, Run or Seach and type regedit.

In your registry, you would browse to this path and ensure that it does indeed say Paint.Picture.

If it says something else, write that down for future reference, and then change it to Paint.Picture.

Should you find that this creates an issue with another program like PhotoShop, you would have to weigh which is more important to you.

If it does indeed say Paint.Picture, close the registry and contact tech support.



Signature Pad - Power Broker 4

The Signature Pad Integration with Power Broker 4 enables the broker to hand the pen over to the customer, allowing the client to sign on the dotted line, and anchoring the signature to the application/form, and then storing it in the clients Power Broker abeyances section. With the signature pad installed you are also able to store signatures for each Producer and CSR by using the Capture Signature button in the respective tables. These signatures can then be pulled into CSIO applications and forms with buttons - Producer Signature and CSR Signature. The signature will be pulled based on the producer or CSR recorded on the customer screen for this customer. For this integration to work, you would need: 1) The Power Broker Scanning/Digital Camera option Contact - sales@power-broker.com and request an invoice for the Scanning/Digital Camera option Cost - $500.00 plus Tax NOTE: ( To check and see if you already have the Scanning/Digital Camera option, you would first go to the main Power Broker desktop, and just above 'General Ledger' you would see a 'Help' option. Click Help, and then 'About Power Broker 4' and if you already have an 'Enabled' located next to Scanning/Digital, then you do NOT need to send an email to purchase it, as you already have this feature.) 2) You would need to purchase the TOPAZ T-S460-HSB-R TOPAZ SIG LITE SIG CAPT 1x5 USB (HID) [T-S460-HSB-R] NOTE: ( It specifically needs to be this exact same make and model for the integration to work) Click here to launch WWW.GOOGLE.COM SEARCH for this item. TOPAZ T-S460-HSB-R TOPAZ SIG LITE SIG CAPT 1x5 USB (HID) [T-S460-HSB-R] Quantity 1 - PRICE - $129.99 When you click on the Capture Signature button you will see the Form that displays the captured signature. The client would use the sign their signatures on the Signature pad. If the signature is clear, then the 'write to Power Broker' button is pressed. The signature would then be attached to the application or Form that was being generated. Click here to download the install file Updated September 19/2011 Sample Install: Sample Workflow Producer Signature / CSR Signature – click one of these buttons to pull the signature as previously stored in the Producer or Customer Service Rep table. Reviewing Your Saved Signature TERMINAL SERVER USERS SECTION: If you are NOT using a terminal server setup, then please ignore: Installation procedures for Topaz Signature pad in a terminal services environment Ports Required: TCP Ports 47289 and 47290 used. (In our testing, there were no port adjustments needed to be made.) Download and SAVE sigsockinstall.zip to MyDocuments Server Configuration: Install Sigsockinstall.exe using the same settings as from the instructions at the top of this page. Locate sigplus.ini in the \Windows folder and copy this to c:\documents and settings\<<username>>\Windows Edit sigplus.ini changing the TabletPortPath = clientname. Note: ClientName defined here must be derived from the following step. In this example, the userid in Power Broker Version 4 is KV Use PB + my PB userid = PBKV ( as seen at the bottom right of this screen capture ) Workstation Configuration: Create a folder C:\Sigplus Copy <Server>\windows\sigplus\tools\sigsock\sigsock.exe to c:\sigplus Create a batch file that will launch the sigsock.exe with 3 paratmeters: <<Servername.domainname>> << clientname>> 6 In this example, we are looking at C:\Sigplus and we have created a blank batch file and called it sigsock.bat. Right click and edit the sigsock.bat ( To create a batch file, right click in Windows Explore ( in the c:\sigplus folder ) and choose New and then Text, and then name the file sigsock.bat, and then say 'yes when it warns you that you are changing the file extension and that it may not work) In the empty batch file, you would type in your own details: Example: sigsock.exe myserver.mydomain.com MyClientName 6 Click FILE and then SAVE to record the changes made in the batch file. RUNNING SIGSOCK.BAT Ensure that the sigsock.bat is loaded before the terminal services connection is initiated. One method would be to include this in a Log-in script or another option would be have an icon on your local workstation desktop that points to c:\sigplus\sigsock.bat and the user would need to manually launch this file for the integration to work. Before connecting, the file would need to be initialized with either method. ( In this example, we've simply launched it from Windows explorer and a DOS window sits on the desktop. If it were installed with a log-in script, your local technical support representative can hide the dos window by adding a few lines to the batch file. ) The user would then launch the Terminal Server connection to connect to the server, and then proceed with your test signature. This integration has been tested on Windows XP, Vista, and Windows 7 using both local and Terminal Services method. Black Box Error - Third party software may interfere with the Signature Integration by changing an important element of the computers registry. Should you receive a black box in your form or application, you would need to edit your registry. A WORD OF WARNING - EDITING YOUR REGISTRY MAY DAMAGE YOUR COMPUTER - PLEASE ENSURE THAT YOU BACKUP YOUR REGISTRY BEFORE HAND - Once backed up, you would go to Start, Run or Seach and type regedit. In your registry, you would browse to this path and ensure that it does indeed say Paint.Picture. If it says something else, write that down for future reference, and then change it to Paint.Picture. Should you find that this creates an issue with another program like PhotoShop, you would have to weigh which is more important to you. If it does indeed say Paint.Picture, close the registry and contact tech support.