2020: Release Notes

To improve performance, the Access Key property has been removed from the NetContact business object.

The following access-level changes have been incorporated into the iMIS REST API:

• Read and write access to iMIS tables and views is no longer permitted.
• Write access to BODs are no longer permitted. Read access to BOD is still supported.
• Read and write access to user-defined panel sources is still supported.
• Read access to IQA queries is still supported.
• Read and write access to services defined with related data contracts are still supported.

Third-parties are encouraged to make any necessary changes using the iMIS REST API.

Two default error pages (404NotFound and 500InternalError) have been added to the document system for errors of type 404 and 500.
The default error pages reuse Content Collection Organizer logic.

The Web.config file has also changed to point to the new 404 and 500 error pages within the webAppRoot project.

The Global Payments gateway uses the Pay Central service (formerly DataVault). Benefits include credit card/ACH support and the Decline Minimizer, an automated card updating service.

To strengthen and enhance our PCI-compliance responsibility, credit cards and direct debits will be set up using the ASI-hosted DataVault in future releases. As part of this effort, current third-party gateways and related configurations are being removed from the iMIS application. Clients can use Global Payments which includes features such as credit card/ACH support and the Decline Minimizer (US and Canada only), an automated card updating service at no extra cost. In addition, iMIS Pay Central provides a verified PCI-compliant environment that many third-party gateways cannot provide. The benefits granted by the Global Payments gateway will not be available for use by third-party gateways. This currently only applies to US and Canada.

Note: iMIS AutoPay is not available for third-party gateways. Using the Global Payments gateway allows for taking full advantage of the features in iMIS AutoPay.

The Separate posting cycle required option allowed users to prevent transactions from automatically being posted. Since the Staff site encourages users to be more self-serving, requiring transactions to be posted immediately, the Separate posting cycle required option is obsolete and has been deprecated. If you need to edit transactions, you must instead adjust or reverse the invoice directly.

Warning! If you are using the Separate posting cycle required option, it is recommended that all batches are posted before upgrade. If you cannot post all batches before an upgrade, it is recommended that batches are posted as soon as possible, because iMIS no longer includes unposted payments when showing invoice balances. Until batches are posted, end users will not see their payments as processed. Ensuring all transactions are posted prior to upgrade will eliminate any confusion for end users. If you are not using the Separate posting cycle required option, this does not affect you.

The Payments navigation item under Finance has been renamed to Pay Central.

The CSC field is only required for public users when checking out. The CSC field will be optional for all staff users.

The following API data contracts have been modified:

• InvoiceSummaryData / InvoiceData:
  • InvoiceAmount now represents the full invoice total, including all adjustments.
  • OriginalInvoiceAmount is a new property which contains the original amount of the invoice before any adjustments were made.
  • PaymentAdjustmentAmount has been split into PaymentAmount and AdjusmentAmount.
  • PendingPaymentAdjustmentAmount is now just PendingPaymentAmount. This represents payments sent to DataVault that have not been reconciled yet (all transactions now auto-post, so there are not any more pending adjustment amounts).
• InvoiceLineData:
  • PaymentAdjustmentAmount is now just PaymentAmount (AdjustmentAmount remains unchanged).
  • PendingPaymentAdjustmentAmount is now just PendingPaymentAmount. This represents payments sent to DataVault that have not been reconciled yet (all transactions now auto-post, so there are not any more pending adjustment amounts).

As an enhancement to iMIS security, staff user accounts are now automatically logged out of iMIS when someone logs in with the same credentials from another browser; for example, you are logged in to iMIS on your Desktop computer when you open your laptop and log in to iMIS. The sign in from your laptop will automatically sign you out from the session on your desktop.

Important! This security enhancement applies to the MANAGER account when logged in through the UI. This change does not impact API users and has no effect on logging out other users when accessed through the API.

This security enhancement does not apply to a single browser session with multiple tabs but does apply to separate browsers, such as using Chrome for one session and Firefox in another session.

To learn how you can obtain additional staff user licenses, do one of the following:

• Contact your ASI Client Success representative
• Contact your AiSP or partner who helps you use iMIS

The overall PCI approach has been modified, and iMIS no longer requires the Password expiration, Password reuse, and Session timeout settings for system administrators. If the non-administrator settings were enabled pre-upgrade, the settings remain enabled post-upgrade and apply to all public users. If you need the settings enabled for all staff users, you must enable the staff settings post-upgrade. See Password security for more information.

The Enable multi-factor authentication option has changed to include all staff users instead of only system administrators (now Enable multi-factor authentication for staff). This setting is disabled after the upgrade. If you need multi-factor authentication for all staff users, you must enable the setting after upgrade.

The out-of-the-box Cookie Policy document has been updated, and all users who use the out-of-the-box cookie policy document must update the document. To update the cookie policy document, do the following:

1. Make a copy of the Cookie Policy content record (@/iSamples/SharedContent/Cookie_Policy).
2. Make the required changes to the copy. The Cookie Policy content record has specific instructions about what must be updated.
3. Add the new content record to your website:
   • If you have a sitemap item specifically for a Cookie Policy, update the sitemap item to point to the new content record (RiSE > Site Builder > Manage sitemaps).
   • If your website has Show a cookie warning enabled, update the Content or URL to link to field to point to your new content record (RiSE > Site Builder > Manage websites > Look and feel tab).

The following website attributes for out-of-the-box websites are preserved on upgrades and are no longer overwritten (also applies to the Staff site and Club Staff site):

• Is this website active?
• Website base URL(s)
• The base URL(s) above are used on more than one RiSE website
• Make this website the default
Click to view image



• Use breadcrumbs on this website
• Favicon
• Mobile favicon
• Theme
• Template (master page)
Click to view image

Website Access settings are also preserved after an upgrade but only for the Make this available to configuration; for example, if you have configured specific roles, groups, users, or member types to have access to a website, those are preserved on upgrades. Changing the Security set from one set to another is not considered a custom change and will be overwritten on upgrade.

Click to view image

The Sign In/Out link was replaced with the Account drop-down on the Member and Annual Conference out-of-the-box websites. If you are using either out-of-the-box websites, you will have two sign-in/out links. To remove one of the duplicate links, do the following:

1. Remove the sign-in link from the sitemap.
Click to view image



2. Copy the out-of-the-box website template and remove the Account drop-down from the auxiliary navigation.

Non-SSL connections (HTTP) are no longer supported, and all clients are required to have an up-to-date SSL certificate to use iMIS. The URL(s) pointing to the IIS website root setting has been removed and the Secure URL(s) pointing to the IIS website root setting has been renamed to Website base URL(s). Any URL in the Website base URL(s) setting must begin with https://.

The setting The IIS website root (above) points to more than one RiSE website has been renamed to The base URL(s) above are used on more than one RiSE website.

Several changes were made to the primary navigation with this upgrade. As a result, there are action items you must take if your theme is a copy of one of the out-of-the-box themes:

• Review the Changes to CSS classes and primary navigation require updates to custom theme files article for step-by-step instructions on what you must update (summarized in #2 below).
• Review the below for more details on the primary navigation attributes that were affected.

The following changes were made to the primary navigation:

1. Several CSS classes have been removed. The removal of these items will affect you if you are using a website theme that is a copy of an out-of-the-box website theme (such as Austin Responsive or Glacier Bay Responsive), or if you are using a custom theme that is utilizing any of the listed CSS classes:
Click for details
• .RadSiteMap
• .RadSiteMap_[ThemeName]
• .MegaDropDownMenu
• .rsmList
• .rsmLevel
• .rsmOneLevel
• .rsmTwoLevels
• .rsmItem
• .rsmLink
• .rsmColumnWrap
• .rsmColumn
• .rsmSelected
• .rsmDisabled
• .rsmLevel1, rsmLevel2
• .LargerWidth10
• .LargerWidth14
• .LargerWidth 18
• .LargerWidth22
2. By default, the styling of the primary navigation's first level will cascade to the sub levels. If you require different styling for the second and third navigation levels, you must add the below CSS to the very end of your custom theme's CSS. Review the Changes to CSS classes and primary navigation require updates to custom theme files article for step-by-step instructions on what you must update . Before adding the code, make sure you change the attributes within the square brackets to what you wish to use:
Click for details

* Second Level */
.RadMenu.MainMenu .rmTwoLevels .rmLevel1 > .rmItem > .rmLink {
	color: [#color];
	font-family: [font-family];
	font-size: [font-size];
	font-weight: normal;
}
/* Second Level - Hover state */
.RadMenu.MainMenu  .rmTwoLevels .rmLevel1 > .rmItem > .rmLink:hover,
.RadMenu.MainMenu .rmTwoLevels .rmLevel1 > .rmItem > .rmLink:focus {
	background-color: [#color];
	color: [#color];
}
 /* Third Level */
.RadMenu.MainMenu .rmSlide .rmSlide a.rmLink {
	color: [#color];
	font-family: [font-family];
	font-size: [font-size];
	font-weight: bold;
}
/* Third Level - Hover State */
.RadMenu.MainMenu .rmSlide .rmSlide a.rmLink:hover,
.RadMenu.MainMenu .rmSlide .rmSlide a.rmLink:focus,
.RadMenu.MainMenu .rmSlide .rmSlide a.rmLink.rmFocused {
	background-color: [#color];
	color: [#color];
}

@media (min-width: 768px) {
.RadMenu.MegaDropDownMenuOuter ul.rmLevel1 div.rmSlide,
.RadMenu.MegaDropDownMenuOuter ul.rmLevel1 ul.rmVertical 
div.rmSlide {
display: block !important;
}
}

3. The number of navigation levels for out-of-the-box themes is now limited to three.
4. Within the .skin file, the MegaDropDownMenuRepeatColumns attribute has been deprecated for the PageNavR control.
5. Breadcrumbs were updated to use the proper <nav> tag and a numbered list of items. If you have custom breadcrumb styling, you may notice a change in the presentation of your breadcrumbs and will need to modify your CSS accordingly.

Before this upgrade, it was not required that all query sources have a defined relationship. When sources did not have a defined relationship, iMIS would automatically apply a Cross Join to the sources.

After this upgrade, two sources can no longer have an undefined relationship, and users must manually update all queries that contain unrelated sources. If you have queries with unrelated sources, an error displays prompting you to update the query.

For performance reasons, it is strongly recommended that cross joins are not used. If you would like to keep the Cross Join relation, you must manually add it to the sources. Make sure the query is in Advanced mode to see the Cross Join option.

The query definition window now encourages users to set a maximum timeout period, so the query stops running after the specified time. The default value for the new setting is 30 seconds.

To change the default value after an upgrade, open the queries in Advanced mode, select the Filters tab, then change the Allow query to run for (maximum) setting. Choosing 1 minute or 3 minutes is not recommended and could severely decrease the site’s performance.