Help

Script Basics:

• Public scripts are those found in PledgeDriver's public bins and are available to all PledgeDriver clients to use as-is or to edit/save to a private bin. Public scripts and public bins are identified by the * in front of the script ID number or bin ID letters. You are encouraged to save the public scripts you want to use as private scripts. 
• Private scripts are those imported from your own sources or public scripts that you save to your private bins. Your private scripts will remain in your password-protected account, whereas some public scripts may eventually be updated or deleted.
• Remove bullets from your original scripts before importing them into PledgeDriver to avoid formatting problems.  Re-bulleting is easy and explained below.
• It is recommended that the same script not be saved in more than one bin because the automatic counter and highlighter features will not be accurate.
• A script that exceeds 3,000 characters will evoke an error message.

Rich Text vs HTML: Scripts imported into the Script Editor will be automatically converted to HTML text (it looks computer-ish). You will need to convert your scripts to Rich text before saving (it looks like Times New Roman in this case). See specific directions below.

Save a Public Case/Close Message to a Private Bin: Any public script can be edited and/or saved as a private script. Click on the script's title, click Edit to open the Script Editor popup. Choose which private bin it will go to, make desired changes (or save as-is), then click Save as Private Script. (You don't need to convert the text from Rich to HTML. Edit within Rich.) If you need to create a private bin for the script, click on +/- to the right of the Script Bin menu and follow the prompts.

Importing Your Own Scripts: Just below the Case or Close bin title window, click New to open the Script Editor popup. Position your original scripts document side-by-side on your computer screen with the Script Editor window. For the script's Name: drag/drop, copy/paste, or type a title. Select/highlight the script text from your original document and copy/paste or drag it to the Script Editor window. If you didn't successfully drag/drop or copy/paste ALL of a script's text at once, start over - don't do it two stages or you will import formatting problems. You can also type the script's text directly in the Script Editor window. Imported text is automatically converted to HTML to strip any embedded formatting. Your script must be converted to Rich to save properly. Click the Bullets icon to instantly convert the text to Rich and add bullets to your script, or click the RICH tab at the bottom of the Script Editor window. Click on Save Script.

Importing or Editing Multiple Scripts:  Click the Enable Batch Mode box in the upper right corner of the Script Editor window.  This will reopen the Script Editor after each entry is saved.

Typing in Scripts:  Open the Script Editor window (as explained above). Select a bin for this new script, type your title, then type your text.  Click on the Rich tab, or add bullets, then Save Script.

Add Bullets: Click the Bullets icon, then click again in front of the first line of text. Place your cursor in front of the second place you want a bullet, backspace to meet the end of the first line, then hit Enter, and so on.  Then click Save Script.

No Bullets: You must still convert to Rich before saving. Click on the Rich tab near the bottom of the Script Editor window, then insert line breaks as desired. Note: double spacing between talking points takes a lot of vertical space on your script pages, so bulleting is recommended. 

Bulk Importing Public Scripts to a Private Bin:  Click on Bin Manager, found under Tools in the toolbar. Click on Create a New Bin to prepare a private bin for the bulk import - or you can import the public scripts into an existing private bin. Find the public bin you'd like to import and click on Bulk Import. (Public bins are "owned" by admin@pdp.com.) In the next popup window select the "destination" private bin, then click on Import Bin.

Consolidating Private Bins: You can bulk import all scripts from one private bin into another private bin using the procedure described above.  Be sure to delete the exported bin(s) after you are done.

Bin Search or Sort:  Bin Manager, found under Tools on PledgeDriver's toolbar, gives the full list of all public and private case and close bins available to your account and the number of scripts in each. To sort the list, use the Bin Selector pull-down menus to select Case, Close or All, and Public or Private.  The search window allows you to type in a key word to quickly locate a specific bin.

Line Breaks: You can only enter line breaks after converting the script text to Rich.

About Tokens: Tokens reserve text areas to be automatically in-filled by PledgeDriver. The text that replaces the tokens is taken from the information entered into Station Information found under Plan on the toolbar. Changes to Station Information will automatically update all of your scripts that have tokens. The [DRIVE_NAME] is especially convenient - you don't need to edit your intro/setup/open scripts for each drive.

Inserting Tokens: The token generator is located in the Script Editor window and offers five choices: [DRIVE_NAME], [PROGRAM_NAME], [STATION_NAME], [STATION_PHONE], and [STATION_WEBSITE]. If you are importing private scripts and they are in Word, you can use Find/Replace to insert tokens into your scripts before importing them into PledgeDriver. For scripts already in a private bin, select the script title and click Edit to open the Script Editor window. Highlight the text to be replaced with a token, then choose the token from the pull-down menu, and click on the binoculars icon. This step needs to be done after your script is in Rich text - it doesn't work when the font is still HTML. OR type in a token using the same [FORMAT].

[PROGRAM_NAME] Token: The [PROGRAM_NAME] token will not infill until you have clicked a script containing it into the planning grid and saved to the server - it draws its information from the program pull-down menu for each hour.

User Defined Tokens (UDTs): These tokens are customized to your needs, and will make updating your scripts from drive to drive very easy. You can create any number of UDTs. Use them for your drive’s member/caller goal, dollar goal, number of days, premiums, and more. By inserting these user-defined tokens into your scripts, you need only change the Token Value to simultaneously update all scripts containing those tokens for your next drive.

Creating User Defined Tokens: After opening your account, pull down the Tools menu and select Your Account. Scroll down to see the User Defined Tokens box. Type your token’s name - PledgeDriver will format the token for you. Token Description is where you can note any specific information such as “Spring 2011”. Token Value is the specific information this token will infill in any scripts containing this script (ex. $50,000). Then click Create New Token. You can create as many different UDTs as you want.

Major Giving Club Scripts: Save these scripts to a private bin and use the edit feature to replace (INSERT MAJOR GIVING CLUB NAME) with your station's major giving club name. This is not an active token.

Edit Private Scripts: Edit the text or title of a private script by clicking on its title, then Edit, make the changes, and Save Script. (You don't need to convert the text out of Rich. Edit as is.) You can move private scripts to a different bin from here (see below). Note: If you edit the text of a private script already clicked into the planning grid, and then right-click to read that script in the grid, the unedited text will appear until the grid has been saved to the server - either by clicking on the Save (floppy disc) icon on the toolbar, or when you go to the print screen and a forced save occurs.

Removing "&nbsp;" from Scripts: This is an encryption code for a non-breaking space - an extra space between words or sentences.  It may appear in scripts when you use the Word output option.  All of PledgeDriver's public scripts have been edited to remove this "bug," but if you saved affected public scripts as private scripts before the purging, you may see it in those scripts or in scripts imported from your own sources. To remove this critter, open the affected script in the Script Editor window, click HTML to convert the text, delete the &nbsp; and then click Save Script.  Do not delete other code encryptions inside <these things> and do not click Rich before saving as you do when importing scripts.  Contact us if you'd like more help or tips for searching whole bins at a time.

Funky Script Formatting: To repair a case or close message that has funky formatting is to select that script in the bin, click Edit to open the Script Editor window, then click on the icon that looks like a page with < > over it. This strips away all format coding. Now click the bullet icon, add bullets as usual, and resave. If this script's ID has already been used in your planning grid, the repaired text will automatically appear after you refresh your browser. Another thing you can try: open the script in the Script Editor window, click HTML to expose format coding, delete unwanted coding (keep <UL> at the beginning and end and <LI> at the start of each line), and Save Script. Do not convert back to Rich before saving.

Search a Bin for Key Word or Phrase in a Script: Select a bin, then click on the script counter (ex. 23 scripts) below the selector window and to the right of the controls marked edit|delete|new. Click OK on the popup "View printable version of all scripts in this bin?" After the window of all scripts in that bin has opened do CTRL + F and enter a word or phrase in the Find window. There is no replace feature with this method, but you can make a note of which scripts contain the searched text and edit them individually.

Search Your Drive Plan for Key Word or Phrase:  Click on the printer icon, select all days and all hours, choose the Word output option, then click Generate Printable Materials. Under the Edit pull down menu at the top of the screen, select Find on this Page…(CTRL+F) and type your word or phrase in the Find window. You can also find/replace text this way, but this will only change the script in output, not in the bin. For a permanent edit, note the script's ID and make changes in the Script Editor window.

Delete a Script: Select the script title in the Script Manager and click on Delete in the edit|delete|new row.  Follow the prompts.

Deleting Many Scripts: If you don't wish to delete an entire bin, but rather a number of obsolete scripts within a bin, consider building a new bin called Trash. Transfer the unwanted scripts to the Trash bin (see Move a Script to Another Bin below), then delete then entire Trash bin.

Move a Script to Another Bin:  From the Case or Close Script Manager, select the script title, click on Edit in the edit|delete|new row.  In the Script Editor pop-up window, select the desired bin from the Script Bin menu.  A pop-up will ask if you are sure about this change.  If you are, click OK.

Script/Bin Highlighter: To highlight all of the placements of a particular script in the grid, select the script title in its bin and  open the Case or Close highlighter pull-down menu to select Script.  Scripts will stay highlighted until you deselect the highlighter feature. To see placement of all scripts from a particular bin, select that bin, then choose Bin from the highlighter pull-down menu.

Saving All Scripts in a Bin to Word: Select the case or close bin you wish to copy. Click the script counter (ex. 23 scripts) below the selector window and to the right of the controls marked edit|delete|new. Click OK on the popup "View printable version of all scripts in this bin?" Select all scripts using CTRL+ A. Then Copy and Paste to your Word document as usual. You can edit public scripts in Word and then import them to a private bin, but you will need to convert to rich text as explained in the Importing Your Own Scripts section above.

Copy an Hour to an Hour on a Different Day: From the Hours menu, select the hour you wish to copy. Re-open the Hours menu and click on Copy Selected Hour.  Ope the Days menu and select the day to which you wish to copy the hour.  Re-open the Hours menu and select the hour you wish to overwrite.  Re-open the Hours menu and click on Replace.

Copy an Entire Day to Another Day: From the Days menu on the toolbar select the day you wish to copy. Re-open the Days menu and click on Copy Selected Day. Re-open the Days menu and select the day that you wish to overwrite. Re-open the Days menu and click on Replace.

Copy a Day or Hour from an Old Drive to a New One: Same as above, EXCEPT if the day you are copying doesn't "exist" in the drive you will paste to. Ex: You want to copy Day 7 from your Fall drive to Day 3 of your Winter drive and your Winter drive has only three days. In this case, copy the desired Day 7 in Fall, return to Day 1 in Fall, then open Winter, select Day 3 and paste as above. 

Print Version