How to Sent ITS your custom Toolbar before a Unicorn upgrade

• For the JAVA client: Go to C:\Documents and Settings\libuser\Sirsi\Workflows\ToolLocal and look for your _____.tb (toolbar file under the name you gave it). Send that file to ITS as an attachment.

• For the old C Client: Go to your Start/Explore and then go to C:\Program Files\Sirsitest\Workflows\ToolCust

• In that directory you should see your _______.tb (toolbar file under the name you gave it).

• Send that file __________.tb to ITS as an attachment.

How to Send ITS your custom Wizard Properties before a Unicorn upgrade

• For the JAVA client the file to send ITS is in C:\Documents & settings\libuser\Sirsi\Workflows\Property and is called property

• For the C client Workflows: The property.dat file is related to the behaviors/helpers/and defaults that wizards use. prop.dat is brought down fresh each time from the server to your PC but if you change behaviors/defaults etc of a wizard and save them to your desktop then these custom local changes you make are saved into the property.dat file and override the ones that are in prop.dat.

• So, you only have to send ITS your C:\Program Files\Sirsitest\Workflows\property.dat file IF you have made new default/behaviors/helper settings for the acq wizards, which you want me to put on the server and deliver from the server to all of your staff.

Once ITS has put them on the server, you need to test them to ensure all is working as you expect it for your staff. Do the following steps to test them:

• You will have to move the local custom files out of the way so that you KNOW that you are actually getting this from the server and not from your PC. So, do the following , please:

• JAVA client rename C:\Documents and settings\libuser\Sirsi\Workflows\Property\property to something like propertybak

• C Client: rename C:\Program Files\Sirsitest\Workflows\property.dat to something like property.bak or property.local

• JAVA client testing custom toolbars: If your custom toolbars have the same names as what they were named on the server, you will have to rename them so C:\Documents and settings\libuser\Sirsi\Workflows\ToolLocal\______.tb to _______.bak or something like that. Then you can check the toolbar delivered from the servrver instead of the one on your own PC that you just sent to ITS!

• Old C Client: If your custom toolbars have the same names as what they were named on the server, you will have to rename them so C:\Program Files\Sirsitest\Workflows\ToolCust\_______.tb to _________.bak or something like that. Then you can check the toolbar delivered from the server instead of the one on your own PC that you sent to ITS!