Financial Development Enhancements

  • Modified all programs utilizing the Financial Development Datamart including report listings, options 21, 22, 23, 24 and 25 to correctly process the newly expanded pledge type code field (previously known as campaign organization code).
  • Enhanced the “Campaign Copy” procedure located on the System Utility Menu (SYSUTIL) to copy the campaigner information and automatically add the campaigner to the campaigner tree structure table file.  This issue caused the Financial Development Key Indicator, annual campaign by campaigner, to appear as though it was not processing correctly.
  • Enhanced the pledge entry process for Campaign and Special events to make the pledge type code mandatory if a pledge amount has been entered.
  • Corrected the field prompting issues when entering a special events pledge.
  • Modified the “Campaign Copy” procedure to correctly copy the campaigner structure from one year to the next.  If the campaigner does not already exist in the tree structure for the new campaign it is automatically created, if the tree structure has been reassigned to a new campaigner, the campaigner is reassigned a new structure within section zero.  Campaigners located within section zero must then be reassigned.  If the Campaigner combined with the campaigner structure already exists in the new campaign, that information will remain with the new campaign record.  Prior to this change the majority of copied campaigners were inadvertently reassigned to section zero and allowed multiple campaigner member numbers to be assigned to the same worker number causing inaccurate pledge reporting.
  • Modified the “Campaign Copy” procedure so that hidden members, deceased members and members flagged as no solicitation are not copied to the new campaign.
  • Modified the Copy Campaign Records from one campaign to another process so that the *PLEDGE option is based on the member's net pledge.
  • Modified pledge reminder print program to specify that the pledge reminder work file should be processed in key sequence not arrival sequence in order to print the reminders alphabetically by branch.   Also removed the hard coded library name specified on the query used to create the Pledge Reminder Register.
  • The Copy Financial Development Year process has been modified to copy the general ledger account information. 
  • Modified the copy campaign feature to properly load the FD number extension field during the copy campaign function.  This was only an issue for those using designation codes (FD number extension) other than 01.  In this case, the copied records were not always set to the required value of 01.                                         
  • Modified the Campaign, Special Events and Grants entry panels to properly update pledge amount field.   Theses processes properly handled creation of a new donation, but if an existing donation record already existed the associated file was never updated with the entered pledge amount (the payment screen never appeared).
  • Campaign Pledge Cards and Pledge Reminders for “Green Screen”
    • Allows pledge cards and reminders to be printed on the iSeries.
    • Pledge cards can now be selected in a fixed or query based method.
    • Fixed based pledge cards allows for section/division/team/campaigner.
    • ALL activity branches now available for selection.
    • Queries no longer necessary for pledge card printing.
    • Pledge reminders offer a simple one step printing process.
  • FD Tree Structure Enhancements
    • "Number of Assignments" now exists in the last part of the column beside each campaigner. The system totals up the number of codes that exist in FDCAMPAIGN or FDEVENTS for that campaigner.
    • New "9=Reassign" features allows a user to automatically reassign the campaigner code to another code in FDCAMPAIGN or FDEVENTS file in a matter of seconds. This saves a lot of time going in and manually doing a "WD" beside each donor. 
  • Identified and fixed problem with Campaigns and Special Events. The 01 designation record was not being automatically created when a pledge was being entered (WD or WS) for a designation other than the primary designation.  The pledge entering process has been modified to properly create the 01 designation when it does not already exist.