Service Packs

This page details Service Pack features that have related Help site documentation as well as other must-read information. iMIS 2017 Service Packs are cumulative; only the most recently released service pack is available for download.

Download the iMIS 2017 Service Pack.

Review the ReadMe file (included in the above download) for information about what was fixed in the Service Pack.

Warning! After applying the Service Pack, do not use the Reset functionality located in the DB Maintenance Utility. Initiating any resets will overwrite database changes made in a Service Pack.

Includes important security updates to IQA queries. Please refer to the IQA Security Update Tech Alert for more details.

No related feature documentation.

DataVault

Compatible DataVault version: Same as 2023 Q3 (4.4.63.22351)

Includes bug fixes.

No related feature documentation.

DataVault

Compatible DataVault version: Same as 2022 Q4 (4.4.63.22351)

Includes bug fixes.

No related feature documentation.

DataVault

Compatible DataVault version: Same as 2022 Q3 (4.4.63.22351)

Includes security enhancements and bug fixes.

No related feature documentation.

DataVault

Compatible DataVault version: Same as 2022 Q1 (4.4.63.22351)

Downloading documents in a multi-instance panel

For multi-instance panels where a file upload link is displayed, the link would sometimes point to the wrong file. This Service Pack includes a fix that will correct the download links and point to the right file.

DataVault

Compatible DataVault version: Same as Service Pack Z (4.4.63.22351)

Security change

Previously implemented security changes have been revised in this service pack. The restriction that prevented publishing of new objects in the root content folder has been lifted.

DataVault

Compatible DataVault version: Same as Service Pack Y (4.4.63.22351)

Security enhancement for root content folder

Due to necessary security changes implemented in Service Pack W (and further enhanced in Service Packs X and Y), it is no longer possible to publish newly created content folders and content records under the root (@) content folder. Any newly created non-system content folders and content records added under the content root (@) folder will not have the necessary file system permissions to be published. All newly created content folders and content records must be created under an existing content folder below the root to have the necessary permissions for successful publishing.

Existing non-system content folders and content records created under the root (@) content folder (added prior to applying Service Pack W, or later) are not impacted by these changes. These existing items will be granted the necessary file permissions and publishing will continue to function as it did prior to applying the latest service pack.

Additional security improvements

  • IMPORTANT - Cross site scripting (XSS) prevention for URLs that contain an ID
  • IMPORTANT - JavaScript code updated for cookie check
  • IMPORTANT - Modernizr updated to latest version
  • IMPORTANT - Telerik controls updated

DataVault

Compatible DataVault version: Same as Service Pack X (4.4.63.22351)

Security enhancement for root content folder

Due to necessary security changes implemented in Service Pack W (and further enhanced in Service Packs X and Y), it is no longer possible to publish newly created content folders and content records under the root (@) content folder. Any newly created non-system content folders and content records added under the content root (@) folder will not have the necessary file system permissions to be published. All newly created content folders and content records must be created under an existing content folder below the root to have the necessary permissions for successful publishing.

Existing non-system content folders and content records created under the root (@) content folder (added prior to applying Service Pack W, or later) are not impacted by these changes. These existing items will be granted the necessary file permissions and publishing will continue to function as it did prior to applying the latest service pack.

DataVault

Compatible DataVault version: Same as Service Pack W (4.4.63.22351)

Security enhancement for root content folder

Due to necessary security changes implemented in Service Pack W (and further enhanced in Service Packs X and Y), it is no longer possible to publish newly created content folders and content records under the root (@) content folder. Any newly created non-system content folders and content records added under the content root (@) folder will not have the necessary file system permissions to be published. All newly created content folders and content records must be created under an existing content folder below the root to have the necessary permissions for successful publishing.

Existing non-system content folders and content records created under the root (@) content folder (added prior to applying Service Pack W, or later) are not impacted by these changes. These existing items will be granted the necessary file permissions and publishing will continue to function as it did prior to applying the latest service pack.

Additional security improvements

  • IMPORTANT - Cross site scripting (XSS) prevention for ReturnUrl parameter
  • IMPORTANT - Cross site scripting (XSS) prevention for text fields
  • IMPORTANT - Cross site scripting (XSS) prevention for URL ID parameter
  • IMPORTANT - jQuery and jQuery-Migrate updated (CVE-2019-11358)
  • IMPORTANT - jQuery UI for jquery-ui.custom.min.js updated (CVE-2016-7103)
  • Net web.config appSettings encrypted
  • Net web.config updated with two additional Telerik appSetting keys
  • Installer updated to handle newly encrypted appSettings in the net web.config
  • Installer updated to make files read-only by privilege

PCI

  • iMIS version number advanced to 20.2.66 to meet PCI versioning requirements

DataVault

Compatible DataVault version: Same as Service Pack V (4.4.63.22351)

DataVault

Compatible DataVault version: Same as Service Pack U (4.4.63.22351)

Note: This service pack includes remedies related to a cross-site scripting issue (REST API only). The remedy has been tested and validated.

This service pack is focused mainly on the implementation of accessibility features.

DataVault

Compatible DataVault version: Same as Service Pack T/T.2 (4.4.63.22351)

New features

The following items were added for Service Pack T.2:

No related feature documentation.

Note: This service pack includes remedies related to a cross-site scripting issue (REST API only). The remedy has been tested and validated.

DataVault

Compatible DataVault version: Same as Service Pack T (4.4.63.22351)

New features

The following items were added for Service Pack T.2:

No related feature documentation.

DataVault

Compatible DataVault version: 4.4.63.22351

New features

The following items were added for Service Pack T:

  • LinkedIn API v2: The LinkedIn API v1 was deprecated on March 1, 2019. IMIS now works with LinkedIn API v2.
    Version 2 updates the APIs with more modern technologies, including OAuth 2.0 for authentication.
  • LinkedIn public profile links: The LinkedIn public profile links defined in the Social Profile List Creator are no longer self-populating. Users must enter LinkedIn public profile links in the Social Profile List Creator manually.
  • Source codes and premium sets: If a system does not contain campaign licenses, the Source codes drop-down is unavailable when adding a new premium set to a gift item.
  • Settlement Status column in Retrieve processed payments tab: The Settlement Status column in the Processed payments area indicates that a payment has been received and applied to the invoice.
  • Reviewing payment details live from DataVault: The AutoPay processing steps has a new tab: DataVault Live. The DataVault Live tab allows you to review details about AutoPay payments in real time as the payment goes through the processing stages.
  • Limiting returns for a segmentation job: When creating an IQA query for use in a segmentation job, do not select the Limit the number of results returned option in the query's Filters tab. If this option is enabled, the query returns all rows in the source tables. To limit the number of rows returned, add another property to the filter instead.

DataVault

Compatible DataVault version: 4.4.55.15673

New features

The following items were added for Service Pack S:

Strong Customer Authentication (SCA) is a new European regulatory requirement (part of the Payment Services Directive (PSD2)). The purpose of this requirement is to reduce fraud and to secure online payments.

The initial deadline for all companies that accept payments from customers within the EU to comply with this requirement was September 14 2019:

ASI is prepared to address any requirement concerns with regards to Payflow Pro/Paypal.

Note: iATS has confirmed that they have delayed implementation of the Strong Customer Authentication requirement and will not decline credit card payments.

If your organization uses Payflow Pro/Paypal and you have clients using European-issued credit cards, it is recommended that you fill out the following 3DS Registration form:

https://paypal3dsregistration.cardinalcommerce.com/UI/Registration.aspx

For more information about this requirement, refer to Payment services (PSD 2) - Directive (EU) 2015/2366.

If you have any additional questions about this requirement, please contact your Authorized iMIS Solution Provider.

DataVault

Compatible DataVault version: 4.4.52.12510

New features

The following items were added for Service Pack R:

  • Allowing members to renew after their paid-through date has passed: The Invoice Payment Link content item can be configured to display the Renew Now button for all members, including expired members. This allows expired members who have a Paid through date in the past to renew their membership without a staff user running a mass-dues billing.
  • Angular.js added as an optional setting: Angular.js has been moved to the web.config file as an optional setting. This allows users to enable or disable access to Angular.js. By default, the UseAngularJs setting is disabled. If you would like to use Angular.js, add the UseAngularJs setting to the web.config's AppSettings:
    • <add key="UseAngularJs" value="true" />

DataVault

Compatible DataVault version: Same as Service Pack P (4.4.43.6545)

New features

The following items were added for Service Pack Q:

  • 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 50,000 contacts.
  • Vantiv/WorldPay can be used to make single ACH/Direct Debit transactions without AutoPay: Vantiv/WorldPay can be used to make single, non-recurring transactions using ACH or Direct Debit without AutoPay. In order to use Vantiv/WorldPay you must have a license key.
  • No limit on payment method sets: There is no longer a limit on the number of payment methods that can be added to a payment method set.
  • Resubmitting a failed AutoPay invoice: If the recurring donation or recurring membership is modified to use a different payment option, the AutoPay invoice can be submitted again up to the three-submission threshold. Additionally, if a staff user cancels or credits the AutoPay invoice, the invoice is not available to be submitted because the balance is 0.00.
  • Update to the change log's property field for multi-instance panels: The change log for multi-instance panels has been updated. The property field is now formatted as the following: SEQN-1234 || Changed.Property. The sequence number is prepended to the property name, allowing users to report on multi-instance panel changes. Single-instance panels remain unchanged.

DataVault

Compatible DataVault version: 4.4.43.6545.

Note: The DataVault version has changed. Be sure to upgrade.

New features

The following items were added for Service Pack P:

  • Optimization to SEQN field renumbering process: Service Pack P includes an optimization to the SEQN field renumbering process that was implemented in Service Pack O. Applying Service Pack P causes the SEQN columns in all multi-instance Customizer tables to be reordered only when the columns contain a SEQN value of 1,000,000,000 (one billion) or more.

    • If renumbering is necessary, a table called CustomMISeqnMapping is created that has a row for each Table/ID/SEQN that is renumbered, with the old and new SEQN value.

  • Name changes to stored procedures and functions: Copies of existing stored procedures and functions have been added with new names that conform to iMIS EMS naming standards. Before you upgrade to iMIS EMS, integrations that reference any of the following stored procedures or functions should be updated to reference the new name:

    Existing name New name
    CalculateDeferralConversionAmount asi_CalculateDeferralConversionAmount
    CalculateFiscalPeriod asi_CalculateFiscalPeriod
    fn_asi_CompareVersions asi_CompareVersions
    fn_asi_convert_foreign_chars asi_convert_foreign_chars
    fn_asi_convert_foreign_string asi_convert_foreign_string
    fn_asi_DatabaseVersion asi_DatabaseVersion
    fn_asi_generate_login asi_generate_login
    fn_asi_GetCompanySort asi_GetCompanySort
    fn_asi_GetDupMatchKey asi_GetDupMatchKey
    fn_asi_GetFullName asi_GetFullName
    fn_asi_GetLastFirst asi_GetLastFirst
    fn_asi_SoftCreditCMDM_Amount asi_SoftCreditCMDM_Amount
    fn_asi_SoftCreditCMDM_Exists asi_SoftCreditCMDM_Exists
    fn_asi_StripParens asi_StripParens
    GetUserKeyByUserId asi_GetUserKeyByUserId
    GetValueListTable asi_GetValueListTable

DataVault

Compatible DataVault version: 4.4.34.2475

New features

The following items were added for Service Pack O:

  • Updated look to CAPTCHA security: The CAPTCHA security check now uses the I am not a robot checkbox instead of the distorted letters and numbers.
  • Limiting results for multi-instance panels in Panel Designer: The Panel Designer uses the PagedResults.Maxrecords value to determine how many results to display for a multi-instance panel. The PagedResults.Maxrecords option can be found in the C:\Program Files (x86)\ASI\iMIS\Net\web.config file.

    • Note: If you are not self-hosted, you must contact your host for assistance modifying web.config files.

  • Updating an AutoPay membership payment method from the Cart: Upon renewal of an AutoPay membership, a member who wants to use a new payment method is presented with two new options in the Cart:
    • Pay only this renewal with the selected payment method – This option pays the current renewal with the newly entered payment method. All future renewals will continue to use the existing payment method.
    • Pay this renewal and future renewals with the selected payment method – This option pays the current renewal with the newly entered payment method and is used as the payment method for all future recurring membership renewals.
  • Importing recurring membership enrollments using the Workbook Converter: Use the Auto Renew Members tab in the iMIS20-300 Conversion- Importing AutoRenew and RecurringDonors data using existing iMIS ID.xlsx workbook to import recurring membership enrollments for contacts who already have an iMIS ID.
  • Maximum page size for REST calls: The setting <add key="MaximumPageSize" value="500" /> was added to the scheduler web.config file (C:\AsiPlatform\Asi.Scheduler_iMIS20264\web.config) to allow setting the maximum page size in REST calls. The default value is 500.

      • Additional notes:

      • If the MaximumPageSize setting is not in your scheduler web.config file, you must add it to the <iMIS><SystemParams> section:
        • <iMIS>
           <SystemParams>
               <add key="MaximumPageSize" value="500">
      • Warning! It is recommended that the MaximumPageSize setting be kept as small as possible. Increasing this value can lead to HTTP request size errors.
      • If you are not self-hosted, you must contact your host for assistance modifying web.config files.

  • Communities no longer accepting JavaScript events: Various areas throughout Communities were updated to no longer allow JavaScript events. Before upgrading, JavaScript events should be removed from Communities blogs, comments, announcements, and wikis.
  • Prefix and suffix business objects and queries: The PrefixList and SuffixList queries ($/Common/Queries/ValueLists) now use the NamePrefixes and NameSuffixes business objects, respectively. All contact business objects use these queries as their value source. This update ensures more consistent reporting on prefixes and suffixes when using the contact business objects.
  • PaymentMethodName in the Workbook Converter: If the PaymentMethodName in the Workbook Converter does not match one of the following credit card names:
    • Visa
    • MasterCard
    • AmericanExpress
    • DinersClub
    • Discover
    • JCB

    then the credit card is described as Card in the Autopay enrollment.

Known Issue: SEQN column reordered in Customizer tables

Applying Service Pack O causes the SEQN column in Customizer tables to be reordered. This can cause problems where those SEQN numbers are used or stored in tables or other data sources as reference to specific rows.

Note: If you use SEQN numbers in any Customizer tables as pseudo-foreign-keys into other Customizer tables, do not apply Service Pack O.

If you have applied Service Pack O but have not yet gone live, restore from backup and roll back the Service Pack.

DataVault

Compatible DataVault version: Same as Service Packs J through N (4.4.23.984)

New features

The following items were added for Service Pack N.2:

No related feature documentation.

DataVault

Compatible DataVault version: Same as Service Packs J through M (4.4.23.984)

New features

The following items were added for Service Pack N:

  • Processing AutoPay invoices with expired credit cards: Previously, AutoPay invoices associated with expired credit cards were always included in invoice submissions until the payment reached three failed attempts. After three failed attempts, the invoice needed to be reprocessed.

    • With this Service Pack, invoices associated with expired credit cards are only submitted once. After the first failed attempt, the invoice is excluded from payment submission until the credit card’s expiration date is updated.

DataVault

Compatible DataVault version: Same as Service Packs J through L (4.4.23.984)

New features

The following items were added for Service Pack M:

  • Starting with Service Pack M, the iMIS 2017 version number is 20.2.65 instead of 20.2.64.
  • The setting <add key="Authentication.ShareCookieWithSubDomain" value="true"/> was added to the web.config file to allow website domain login cookies to be shared across subdomains. For instance, example.org will share its login cookie with staff.example.org.

    • This setting was added in the following location:

    <iMIS>
  <SystemParams>
    <add key="Authentication.ShareCookieWithSubDomain" value="true" />
  </SystemParams>
</iMIS>

    If you set the value to false, individual cookies are applied to each sub domain, and are not shared with the root domain. For instance, example.org, staff.example.org, and members.example.com will all have individual cookies and will need to be logged into individually.

    If you use multiple domains, such as sample.com and example.com, these domains cannot share cookies.

    The default value is false.

    Note: If you are not self-hosted, you must contact your host for assistance modifying web.config files.

  • Configurable warning message: The option, Message when an existing user attempts to create an account, allows system administrators to configure the warning message that displays when an existing user attempts to create a new account. Tailor this message from Settings > Contacts > Account management.
  • NetContactData business object: A new business object, NetContactData, allows you to return the organization record for combo records. This business object is an alternative to NetContactBasic, which returns individual records for combo records.

Known Issue: iMIS DB Maintenance Utility

An error related to the version number change prevents the iMIS DB Maintenance Utility from loading after Service Pack M is applied. While the DB Maintenance Utility is not maintained with the iMIS 2017 Service Packs, this issue will be corrected in a future service pack. Until this issue is resolved, connect to the iMIS database with SQL Server Management Studio and run one of the following commands:

  • Rebuild the SQL Service Broker:
    • EXEC dbo.asi_EnsurePublishQueueAndServiceBroker;
  • Rebuild Name_All View: 
    • EXEC dbo.asi_RebuildNameAllView;
  • Rebuild Counters:
    • EXEC dbo.asi_RebuildCounters;

Note: If you move an iMIS database to a new SQL server or restore an iMIS database under a new name to the same server, you must run the Prepare iMIS Database process:
-- Self-hosted customers must run the CreateSqlLogins.sql script located in the C:\Program Files (x86)\ASI\iMIS20.2.64.8405\net\IMISDBUpgrade folder.
-- Hosted customers can contact Cloud Services to run the CreateSqlLogins.sql for you.

For any other functionality, such as purging unused users and contacts, contact tech support for a script to perform the function (self-hosted), or ask Cloud Services to run the script for you (hosted).

DataVault

Compatible DataVault version: Same as Service Packs J & K (4.4.23.984)

New features

The following items were added for Service Pack L:

No related feature documentation.

Warning! Review the information in the related Read Me extremely carefully. There are important steps that must be followed when applying this service pack to a system that hosts multiple instances of iMIS Desktop at different iMIS 2017 service pack levels.

DataVault

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

New features

The following items were added for Service Pack K:

No related feature documentation.

DataVault

Compatible DataVault version: 4.4.23.984

New features

The following items were added for Service Pack J:

  • 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.

  • 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 columnFrequency:
    • $/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.

In cases where customers have both a pre-Service Pack J and a Service Pack J-or-newer version of iMIS installed on the same server, additional steps must be taken to enable running Desktop or Advanced Accounting Console.

Do the following for all installed instances of iMIS Service Pack J or newer:

  1. Close all instances of Desktop or Advanced Accounting Console.
  2. For all installed instances of iMIS Service Pack J or newer:
    1. Rename Omnis7.exe to Omnis7IE11.exe.
    2. Update all relevant shortcuts to point to Omnis7IE11.exe.
  3. Open the Registry Editor.
  4. Browse to the relevant key:
    • (32-bit systems) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
    • (64-bit systems) HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
  5. Right-click the Omnis7.exe value and select Rename.
  6. Rename the value Omnis7IE11.exe.

Note: If you do not rename the Omnis7.exe value in the key, Desktop and Advanced Accounting Console running on versions of iMIS prior to Service Pack J will not function properly.

DataVault

Compatible DataVault version: 4.4.15.715

New features

The following items were added for Service Pack I:

  • 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.

DataVault

Compatible DataVault version: 4.4.15.715

New features

The following items were added for Service Pack H:

No related feature documentation.

DataVault

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.

New features

The following items were added for Service Pack G:

  • 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.

DataVault

Compatible DataVault version: Same as Service Packs D and E (4.4.6.357)

New features

The following items were added for Service Pack F:

Review the following list to determine additional dependencies and requirements that must be addressed for this Service Pack:

  • Verify web.config file settings:

    • ..\AsiPlatform\Asi.Scheduler_(iMIS App)\web.config

    ..\Program Files (x86)\ASI\(iMIS Dir)\Net\web.config

    • EntityManagerDefaultBaseUri:

      • This value must be the fully qualified machine name of the iMIS Application Server, for example:

      value="https://<www.yourdomain.com>/Asi.Scheduler_(iMIS App)" />

    • IMISWebServerUrl:

      • This value must be the fully qualified machine name of the iMIS Application Server, for example:

      <add key="ImisWebServerUrl" value="https://<www.yourdomain.com>/(iMIS Virtual App)" />

  • Ensure the appropriate DNS and Subject Alternative Names are clearly specified on the SSL certificate used for the iMIS deployment.
  • Verify registry keys used to enable TLS 1.1 or 1.2 as default secure protocols in WinHttp:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\

    The following keys must be present:

    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\Multi-Protocol Unified Hello
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\PCT 1.0
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server

    If the preceding keys are not present, then do the following:

    1. Download IISCrypto from https://www.nartac.com/Products/IISCrypto/Download.
    2. Launch the installer.
    3. Select Templates.
    4. In the drop-down, select PCI 3.1.
    5. Click Apply.
    6. Reboot the iMIS App Server.

    Once the reboot is complete, confirm the registry adjustments.

  • The ODBC Driver 11 for SQL Server is required on all systems running the iMIS GA 2017, Service Pack E Desktop client:
    1. Install the Microsoft® ODBC Driver 11 for SQL Server (64-bit) on all systems running the iMIS GA 2017, Service Pack E Desktop client.
    2. Delete extant iMIS Desktop ODBC connection objects:
      1. Go to Start > Run.
      2. Enter the following program name:

        3. %windir%\SysWOW64\odbcad32.exe

      3. Select the System DSN tab.
    3. Launch the Desktop client (run as Admin). Re-create the necessary ODBC connection object to enable the GA 2017, Service Pack E Desktop client to function.

DataVault

Compatible DataVault version: Same as Service Pack D (4.4.6.357)

New features

The following items were added for Service Pack E:

  • 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.

DataVault

Compatible DataVault version: 4.4.6.357

New features

The following items were added for Service Pack D:

  • 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.

DataVault

Compatible DataVault version: 4.3.86.3909

New features

The following items were added for Service Pack C:

No related feature documentation.

DataVault

Compatible DataVault version: 4.3.85.3896

New features

The following items were added for Service Pack B:

  • 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.

DataVault

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

New features

The following items were added for Service Pack A:

No related feature documentation.