Completing post-upgrade tasks

Security is added to the On Behalf Of role to allow only Full users to be assigned to this role. After upgrade, all Casual or Public users who were previously assigned to the On Behalf Of role are removed from this role. To add this role back to contacts, change the contact to a Full user.

Version 15.2 optimized and improved the APIs that support content items. Therefore, you must modify any content items you developed for Version 15.1 to have those content items work with these API changes. Do the following:

1. In your content item project, remove references to Asi.Web.iParts.Common.Utilities and Asi.Web.iParts.Common.WebControls. Version 15.2 deprecated these assemblies and moved their functionality.
2. In your content item code, remove any using statements that reference the namespaces from Step 1.
3. If you are using the TitleBar control, make sure your project references the Asi.Web assembly. In your web controls and pages, update the TitleBar control to reference the new assembly and namespace:
   • Assembly change: Asi.Web.iParts.Common.WebControls becomes Asi.Web
   • Namespace change: Asi.Web.iParts.Common.WebControls becomes Asi.Web.UI.WebControls

   For example, the line:

   <%@ Register TagPrefix="ipartCommon" Assembly="Asi.Web.iParts.Common.WebControls
   	Namespace="Asi.Web.iParts.Common.WebControls" %>

   becomes:

   <%@ Register TagPrefix="ipartCommon" Assembly="Asi.Web"
   	Namespace="Asi.Web.UI.WebControls" %>

4. Replace the use of AppContext.CurrentIdentity.ContactMaster with SecurityHelper.LoggedInImisId.

Note: When you only need to check for a logged-in user, use SecurityHelper.IsAuthenticatedUser.

5. Version 15.2 deprecated Asi.Web.iParts.Common.Utilities.Helper class and moved its methods to Asi.Security.Utility.SecurityHelper and Asi.Utilities.PartHelper. Modify any uses of the Helper class as shown in the following.

Note: When using the new classes, you must either fully qualify the class namespace or add the appropriate using statement to your code.

• Methods moved:
  • Helper.CheckDisplayAsEmpty > PartHelper.CheckDisplayAsEmpty
  • Helper.FindControls > PartHelper.FindControls
  • Helper.FindControlsRecursive > PartHelper.FindControlsRecursive
  • Helper.GetSelectedImisId > SecurityHelper.GetSelectedImisId
  • Helper.LoggedInImisId > SecurityHelper.LoggedInImisId
• Methods no longer supported, so refactor:
  • Helper.GetSelectedImisIdWithException

  When used to check for an authenticated user, replace with SecurityHelper.IsAuthenticatedUser.

  • Helper.ImisConnection

  When used to check for an authenticated user, replace with SecurityHelper.IsAuthenticatedUser. When used to retrieve a CContactUser object, use iBO.ContactManagement.CContactUser.LoginByWebLogin(AppPrincipal.CurrentIdentity.LoginName).

  Note: It is recommended to use the SOA data access library in place of the iBO library when possible.

  • Helper.SetCurrentContactKey
  • Helper.SetSelectedImisId

If you are upgrading from iMIS 15.2.7-and-higher to the current iMIS release, and your website uses the Cities, Forest, Mountains or Planets master pages, you must add a Create Account navigation item to your sitemap. You can copy from one of the quick start sites. Do the following:

1. Go to RiSE > Site Builder > Manage sitemaps.
2. Select Member in the drop down list.
3. Select the Create Account navigation item.
4. Select Organize > Copy.
5. In the drop down list, select your website.
6. Select the root (~) navigation item
7. Select Organize > Paste.
8. Place this navigation item where you want it to appear.
9. Select Publish.

When you upgrade to a new version of iMIS, several system alert tasks are enabled and set up to display to website users by default. After an upgrade, you should review the system alerts tasks to confirm that you do want these alerts to display to users. The review process will differ depending on whether or not you are licensed for advanced tasks.

If you have the advanced tasks license

You should review the system alerts tasks to confirm that they are configured appropriately for your organization. If you do not want a system alert task to generate an alert that displays to users, you need to disable the task.

1. In the Staff site, go to RiSE > Process automation.
2. Select the Tasks tab.
3. Open and review the alert tasks.
   1. If you do not want to use a system task, deselect Enabled.
   2. Confirm that the task uses an appropriate Conditions data source. The task only runs when the data source returns records.
   3. Confirm that the Alert is configured appropriately.
4. Review the query data sources used as conditions in the enabled tasks. Data sources are located at $/Common/Tasks/Queries in the Document System. If you want to modify a query data source:
   1. Copy the query.
   2. Modify your version of the query.
   3. Update the task to use the new Conditions data source.
5. Go to RiSE > Process automation.
6. Select the Alert sets tab and confirm that the alert tasks are located in the appropriate alert set.

If you do not have the advanced tasks license

You cannot edit the out-of-the-box alert tasks, but you can control whether or not they display on your website by including or removing them from the system alert sets. If an alert task is not included in an alert set, it does not display.

1. In the Staff site, go to RiSE > Process automation.
2. Select the Alert sets tab.
3. Open the alert set you want to edit.
4. To add an out-of-the-box alert task to the set:
   1. Select Add New.
   2. Select the alert task you want to include from the Task drop-down.
   3. Save the task.
   4. Use the arrows to arrange the alert tasks in the desired order.
5. To remove an out-of-the-box alert task from the set:
   1. Select the alert set.
   2. Choose Delete selected.
   3. Click OK to confirm the deletion.
6. Save the alert set.

See Displaying automated alerts for more information.

iMIS uses a request validation mode of 4.5. Request validation is a feature built into ASP.NET to protect against users submitting potentially dangerous content such as HTML or JavaScript.

ASP.NET 4.5 has the ability to deactivate request validation for a particular user input or control. All of the standard pages in iMIS that allow HTML input take advantage of this feature.

If you have any custom pages that previously depended on a request validation mode of 2.0, you must do one of the following:

• Update the custom pages to use the request validation features in 4.5.

Use ValidateRequestMode to disable request validation for a particular control (recommended):

1. Add ValidateRequestMode="Disabled" in the control that needs to allow HTML:

<asp:TextBox runat="server" ID="TxtHtml" ValidateRequestMode="Disabled" />

2. Encode the HTML value when retrieving it:

var htmlValue = System.Web.HttpUtility.HtmlEncode(TxtHtml.Text);

3. (optional) Retrieve an HTML value directly from the request:

var htmlValue = System.Web.HttpUtility.HtmlEncode(Request.Unvalidated.Form["MyFormField"]);

• Edit the web.config file to specify which pages need a request validation mode of 2.0.

  At the bottom of the web.config file, right before the final </configuration> tag, add a reference to your custom page:

  <location path="Custom/MyCustomPage.aspx">
       <system.web>
            <httpRuntime requestValidationMode="2.0" />
       </system.web>
  </location>
  

To determine if any pages previously depended on request validation mode 2.0, search your .aspx files for ValidateRequest="false" in the page directive, for example:

<%@ Page Language="C#" AutoEventWireup="true" Inherits="My_Custom_Page" 
Title="My Custom Page" Codebehind="MyCustomPage.aspx.cs" 
ValidateRequest="false" %>

If you decide to use ValidateRequestMode to disable request validation for a particular control, delete ValidateRequest="false" from the page directive.

iMIS no longer supports installs to the default website. If you previously installed to the default website, you will need to use the URL Rewrite module to redirect the URL of your default website to the URL of the virtual directory.

For example, an organization that had previously installed iMIS to the http://golive.advsol.com/ default website has uprgraded and now installs to an /ASI/ virtual directory. The organization wants users who try to access http://golive.advsol.com/ to be redirected to http://golive.advsol.com/ASI/.

Note: You can only use the URL Rewrite module to redirect the URL of the default website to the URL of the virtual directory when the default website and virtual directory use the same application pool.

Redirecting to the virtual directory URL using URL Rewrite

Do the following to redirect the URL of your website to the URL of the virtual directory using URL Rewrite:

1. Go to IIS Manager > Sites >Default Web Site. The URL Rewrite module will be visible in the IIS group.

Note: When creating a URL Rewrite rule at the Default Web Site root level, you must make sure to disable that rule for any virtual directories under the Default Web Site where you do not want the rule to be applied. If you do not disable the rule, those virtual directories can inherit the URL Rewrite rule.

2. Double-click URL Rewrite.
3. In the Actions pane, select Add Rule.
4. Select Blank Rule and click OK.
5. Specify a Name for the rule.
6. In the Match URL area, do the following:
   1. Select Matches the Pattern for the Requested URL.
   2. In the Using drop-down list, select Regular Expressions.
   3. Enter .* for the Pattern.
   4. Select the Ignore Case checkbox.
7. Expand Conditions. In the Conditions area, do the following:
   1. Click Add….
   2. Enter the following for the first condition:
      • Enter {HTTP_HOST} as the Input.
      • In the Check if input string drop-down list, select Matches the Pattern.
      • Enter ^FQDN$ as the Pattern. (For example, ^golive.advsol.com.)
      • Click OK.
   3. Click Add….
   4. Enter the following for the second condition:
      • Enter {PATH_INFO} as the Input.
      • In the Check if input string drop-down list, select Does Not Match the Pattern.
      • Enter /VirtualDirectoryName/ as the Pattern.
      • Click OK.
8. In the Action area, do the following:
   1. Select Rewrite as the Action type.
   2. Enter /VirtualDirectoryName/{R:0} as the Rewrite URL.
   3. Select the Append query string checkbox.
   4. Select the Stop processing of subsequent rules checkbox.
9. In the Actions pane, click Apply.

Setting up an iMIS site at the root of an IIS web site

Do the following to set up an iMIS site at the root of an IIS web site:

1. Launch IIS Manager.
2. In the left navigation, right-click Sites and select Add Web Site.
3. Enter the following information:
   1. Site name: www.domainname.com
   2. Physical path: The default path is C:\Program Files (x86)\ASI\iMIS\Net. Change this path to reflect your new iMIS path (for example, C:\Program Files (x86)\ASI\domainname\Net).
   3. Binding: Change the IP address to the address assigned to this site.
   4. Host name: www. domainname.com
4. Add an SSL site binding. Select the site, then click Bindings and then Add.
5. Enter the following information:
   1. Type: HTTPS
   2. IP address: The IP address of the site.
   3. Port: 443
   4. SSL Certificate: Select the certificate for www.domainname.com.

Note: A new DNS record will need to be added to your DNS Server to associate the new www.domainname.com with the external IP address.

6. To test the new www.domainname.com, add a host file:
   1. Open the C:\Windows\System32\drivers\etc\hosts file in a text editor application.
   2. Add the following line to the end of the hosts file:

   [IP address of the site]    www.fullurl.com

7. You must update the URLs for your RiSE websites to reflect the new URL:
   1. In the Staff site, go to RiSE > Site Builder > Manage websites, and select your website.
   2. Change the following fields:
      • URL(s) pointing to the IIS website root – http://www.domainname.com
      • Secure URL(s) pointing to the IIS website root – https://www.domainname.com

Do the following tests as appropriate for your system.

1. Test the administrative view:
   • On the iMIS server, choose Start > All Programs > ASI > iMIS > iMIS Desktop.
   • Test that you can log on as MANAGER.
   • Verify that the iMIS Home page is displayed, indicating that the connections are working.

Note: Allow several minutes for the Home page to open for initial logons after installing or restarting.

2. Test the staff view:
   • On the iMIS server, browse to your staff view, such as http://<iMIS server>/iMIS/staff.
   • Verify that the iMIS Home page is displayed, indicating that the connections are working.
   • Test that you can log on as MANAGER.