Service Packs

This page details Service Pack features that have related Help site documentation as well as other must-read information. See the official Service Pack and Hotfix page to download the most current Service Pack and for more information about all of the fixes included in the Service Packs.

Warning! After applying the Service Pack, do not use the Reset/Rebuild functionality located in the DB Maintenance Utility to initiate any rebuilds that modify the structure of your database. Initiating any rebuilds that modify your database structure will overwrite database changes made in a Service Pack.

Service Packs and the DataVault

You must ensure your DataVault version is compatible with your Service Pack update. If your DataVault is hosted by ASI, you must contact ASI for assistance determining DataVault compatibility.

Do the following to determine whether your DataVault is hosted by ASI or your organization:

  1. From the Staff site, go to Settings > Finance > General.
  2. Locate the DataVault service address:
    • If the DataVault service address contains asidv1.advsolhosting.net, the DataVault is hosted by ASI on a separate server.
    • Enter a ticket informing ASI Hosting of the Service Pack to which you want to upgrade, and verify your DataVault version is compatible.

    • If the DataVault service address does not contain asidv1.advsolhosting.net, the DataVault is self-hosted on your own system. Run the setup.exe application on the DataVault application server to upgrade the existing DataVault install.

DataVault updates are not required for every Service Pack update. Review the Compatible DataVault version for the Service Pack to which you want to upgrade.

Service Pack K (20.2.64.9193)

  • Compatible DataVault version: Same as Service Pack J (4.4.23.984)

No related feature documentation.

Service Pack J (20.2.64.9190)

  • Compatible DataVault version: 4.4.23.984
  • Advanced Email performance improvements: Advanced Email has been updated with performance and reliability enhancements for large communication jobs. These large communication jobs should not exceed 10,000 contacts.
  • For large communication jobs, the individual communications will not display a status for at least 10 minutes. After about 10 minutes, statuses are displayed for some of the communications. As time progresses, more communications display a status, and all communications should display a status after about one hour. The times will vary depending on the amount of communications that are sent.

    Note: You cannot send more than one large communication job at a time. After all statuses for a communication job are present in the Communication Log, you can begin the next large communication job.

    Additionally, two new settings were added to the web.config file that allow you to control the communication batch mode and cancel the communication job if errors are found:

    • Communication.BatchMode - This setting controls how quickly communication data records are saved to the database. The value can be set to true or false:
      • True – (default) Data is saved to the database 1,000 records at a time. This method can process large datasets in a shorter amount of time.
      • False – Data is saved to the database one record at a time. This method may take an undesirable amount of time for a large dataset.
    • Communication.CancelCampaignOnError - This setting controls whether campaigns are sent if errors are found. The value can be set to true or false:
      • True – When errors are found, no communications are sent.
      • False – (default) Communication jobs continue to be sent even when errors are found.
  • iMIS websites have been upgraded to jQuery 3.3.1 and jQuery Migrate 3.0.1 to enhance PCI compliance.
  • Erasing a contact's personal data: Staff can request the removal of a contact's personal data from the system. This request is submitted to a system administrator for approval. Once the removal request is approved the contact is marked for erasure until the Contact erasure task is run. This task signals the system to remove all the personal data from contact records that are marked for erasure.
  • Updating current Certification enrollments: After editing a program definition, Staff users can update the requirements for all current enrollees. The updated enrollment reflects any requirements that are completed, and the Stages and Requirements will reflect the new program definition.
  • Minimum-password-requirements message: System administrators can tailor the message that appears when someone has created a password that does not meet the minimum-password requirements.
  • Importing additional recurring donations (Workbook Converter): Additional recurring donations can be imported using the Workbook Converter, as long as the donor already exists in the iMIS database and the iMIS Id of the donor is referenced.
  • Auto-populating the date and time a panel source is updated: The CreatedByUserKey property is now auto-populated when a Panel Designer panel is updated or edited.
  • Gift Aid: Split gifts are now supported as part of the Gift Aid reclaim process.
  • The following IQA queries have been updated to remove the column Frequency:
    • $/Membership/DefaultSystem/Queries/AutoPay/Automatic payment enrollments
    • $/Membership/DefaultSystem/Queries/AutoPay/Members enrolled in automatic payments
    • $/Samples/Dashboards/AutoPay/Membership/Auto-pay membership details
    • $/Samples/Dashboards/AutoPay/Membership/Cancelled membership enrollments
  • The restriction preventing non-staff users from modifying payment methods tied to existing enrollments has been removed.
  • Service Pack C (20.2.64.8556) introduced a tighter certificate validation policy for secure communication with the iMIS service. The certificate validation policy requires that the certificate is in date, has been issued by a recognized certificate authority and is for the domain by which the service is being accessed.
    Using a certificate that does not meet this validation policy results in application errors being logged on the server and displayed in the browser. The error logged on the server is of type SecureConnectionFault and provides additional details.
    If the iMIS website is being accessed from a browser installed on the application server then a Secure Connection error is displayed, along with a reason and guidance for resolving the error; otherwise, a generic error is displayed. The cause of the error can be reviewed in the server Application log.

Service Pack I (20.2.64.8949)

  • Compatible DataVault version: 4.4.15.715
  • A new business object, GiftHistorySummaryBasic, is available for when there are no yearly roll-ups needed, for example, when the only value needed is the lifetime giving amount. This new business object improves performance of queries using GiftHistorySummary table data.
  • The $/Fundraising/DefaultSystem/Queries/Dashboards/Major Donors For Manager query has been updated to use this new business object to improve the performance of the Moves management dashboard.

  • General lookup tables: A new default option, None selected, has been added to the General tables drop-down. This allows the General lookup tables page to load without any tables selected, increasing performance.
  • The Fundraising report, Outstanding Pledges, has been updated with the optional date parameter, Exclude Pledge Dates before. This filter was added to improve the run time of the report.

Service Pack H (20.2.64.8807)

  • Compatible DataVault version: 4.4.15.715

No related feature documentation.

Service Pack G (20.2.64.8771)

  • Compatible DataVault version: Same as Service Packs D, E, and F (4.4.6.357)
  • Note: If the initial Service Pack install results in a failure, you can reapply the Service Pack from a command line.
    Do the following:
    1. At a command prompt, navigate to the SP_20.2.64.8771 directory created by the iMISv300ServicePack.exe application.
    2. Enter the following:
    InstallServicePack -f
    The -f option allows for the Service Pack to be reapplied.

    This capability is available for Service Pack G and later.

  • The Email a friend functionality is deprecated. Although the configuration options are still available (Settings > RiSE > Quick Setup/Page builder configuration), they have been deprecated. The associated email button is still available on the bottom-right in the Staff site's footer, but should be removed to avoid a display error. The Social Share content item is the suggested replacement.
  • A new column, PaymentTerms, is added to the Recurring Donors worksheet in the Workbook Converter. The PaymentTerms define the payment schedule for a recurring installment pledge.

Service Pack F (20.2.64.8730)

  • Compatible DataVault version: Same as Service Packs D and E (4.4.6.357)
  • Single-Sign On (SSO): Configure Single-Sign On from the iMIS Staff site.

Service Pack E (20.2.64.8677)

  • Compatible DataVault version: Same as Service Pack D (4.4.6.357)
  • Donor notes: Allow donor to enter a note when they are donating.
  • Removing TLS 1.0 dependence: After June 30, 2018, all entities must have stopped use of SSL/early TLS as a security control, and use only secure versions of the protocol.

Service Pack D (20.2.64.8598)

  • Compatible DataVault version: 4.4.6.357
  • Premium products: Kit products are available to be used as a premium.
  • Workbook Converter: Ability to use the Workbook Converter to import external gateway tokens along with recurring instruction details.
  • Pledge Invoices: Ability to pay pledge invoices from the Open Invoice List Display content item.

Service Pack C (20.2.64.8556)

  • Compatible DataVault version: 4.3.86.3909

No related feature documentation.

Service Pack B (20.2.64.8516)

  • Compatible DataVault version: 4.3.85.3896
  • Updated password requirements for PCI compliance: If the MaxInvalidPasswordAttempts value in the web.config file is modified to a value of 6 or greater, users will be locked out of iMIS. PCI requires limiting access after six logon attempts.

Service Pack A (20.2.64.8465)

  • Compatible DataVault version: Same as iMIS 2017 GA (4.3.84.3817)

No related feature documentation.