Merative ™ Social Program Management 8.0.1.0 iFix4

Merative ™ Social Program Management is now Cúram ™ by Merative™

Release Notes

Abstract

Merative Social Program Management 8.0.1.0 iFix4 Release Notes

Content

Introduction
System Requirements
Download
Installation
Improvements, Resolved Issues, Third Party Updates
Known Issues
Notices

Introduction

Welcome to the Merative Social Program Management 8.0.1.0 iFix4 release.

This is a cumulative release which incorporates the Improvements, Resolved Issues and Third Party Updates contained in all previous 8.0.1.0 iFix releases. Details of these Improvements, Resolved Issues and Third Party Updates are included separately in the release notes for each of the previous iFix releases. For the latest version of the release notes, see https://curam-spm-devops.github.io/wh-support-docs/spm/release-notes

Full product documentation can be found in the documentation

System Requirements

For information about the supported software and hardware for this release, see the Merative Social Program Management Prerequisites

Download

See the download instructions for this release at /support/curam

Installation

Before running the installer please ensure all files in your Merative Social Program Management installation are writable.

The installation steps are as follows:

• Extract the contents of the .zip file to a local drive location.
• Run the Merative Social Program Management installer, which can be found in the INSTALLER folder at that location.
• After installing, the appropriate build targets must be run as necessary for your installation.

Additional installation instructions can be found in the Development Environment Installation Guide.

Upgrading

If you are upgrading from a previous version, the Merative Social Program Management Upgrade Helper contains documentation and tooling to help you to upgrade your Merative Social Program Management application codebase and database to work with your new version of Merative Social Program Management. The Merative Social Program Management Upgrade Guide describes a recommended process for performing application and database upgrades. The Upgrade Helper contains tools to assist you with implementing the upgrade, including tooling to produce a schedule of required migrations for your upgrade, tooling to provide information about database schema changes and tooling to generate initial SQL scripts for applying changes to your database.

To download the appropriate version of the Merative Social Program Management Upgrade Helper, see the download instructions at /support/curam

Improvements, Resolved Issues, Third Party Updates

Look and Feel

PO09810, WorkItem:277279 - Passive modal dialogs can display buttons when opened from a modal dialog

Issue Description:

If a passive modal dialog (a modal dialog with no action controls), is opened from another modal dialog in the application, it incorrectly shows buttons from the previous modal dialog. Users can get confused and think that the buttons can be used in the new context.

User Interface Impact: No

Steps to Reproduce: N/A

Resolution:

The buttons are now hidden as expected in passive modal dialogs that open from a modal dialog in the application.

Curam Enterprise Framework

Application Development Environment

CLIENT DEVELOPMENT ENVIRONMENT

WorkItem:277613 - Session timeout is not logging out user correctly under certain conditions

Issue Description:

The user is not correctly logged out when a modal such as Register Person is displayed without a tab open in its background. The user is not logged out when the user clicks Logout from the session timeout modal or when the countdown on the session timeout modal runs out.

User Interface Impact: No

Steps to Reproduce:

1. Log in as a caseworker.
2. Close any open tabs.
3. Open the Register Person modal.
4. Wait for the session to time out and for the session timeout modal to appear.
5. Click Logout.
6. Issue: The user is not logged out and remains logged in.

Resolution:

The user is now logged out when the user clicks Logout from the session timeout modal or the countdown on the session timeout modal runs out.

Technical:

The session timeout JavaScript was updated to ensure that a user is always logged out when the user selects Logout from the session timeout modal and the countdown on the session timeout modal runs out.

PO09838, WorkItem:277643 - Custom search page with multiple searches display all of the search result counts on the first search list

Issue Description:

Custom search pages with multiple searches display all of the search result counts on the first results list instead of displaying separate counts for each result list on the page. The search result count needs to be displayed on each results list to give the user context.

User Interface Impact: No

Prerequisite(s):

1. Set LIST_ROW_COUNT to be true in the curam-config.xml configuration file.
2. Customize Person_search1.uim and Person_search1.properties to have more than one LIST element.
3. Rebuild and deploy the application.

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to Person under Searches in the Shortcuts panel.
3. Search for an existing person (using search criteria such as Last Name).
4. Issue: The first set of search results shows '(Number of Items: X)' twice, where X is the number of items in the list.

Resolution:

The search result count is displayed separately on each list which helps provide appropriate context to the user.

Technical:

When LIST_ROW_COUNT is configured in the application and when multiple lists are present on a page, the page correctly displays the search result count on each list separately.

WIDGETS

PO09775, WorkItem:276724 - The date picker is unnecessarily opened when certain modal dialogs open

Issue Description:

The date picker is activated by default when you open a modal dialog where the first field accepts a date value. The open date picker can block some of the modal dialog content that the user needs to see.

**User Interface Impact: **No

Steps to Reproduce:

1. Log in as a caseworker.
2. Register a new Person.
3. On the Evidence tab for the person, select New to add email address evidence.
4. Issue: When the New Email Address modal dialog opens, the date picker for the Received Date field opens and blocks some content on the modal dialog.

Resolution:

When a user opens a modal dialog that has the date picker form control as the first field, the date picker stays closed until the user goes to the field and selects a date.

PO09827, WorkItem:277400 - Incorrectly entered dates are converted to random dates in the application

Issue Description:

When a user manually enters an incorrect date value into a date field on a form in the application, a seemingly random date is displayed.

User Interface Impact: No

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to Person under Registration in the shortcuts panel.
3. Manually enter an incorrect date into the Date of Birth field on the first step of the Register Person wizard.
4. Click the Search button.
5. Issue: An incorrect random date is generated and displayed in the field when the search is being done in the system.

Resolution:

When a user manually enters an incorrect date into a form within the application, an error message now notifies them that an incorrect date was entered. Users can enter a new date by clearing the incorrect date and manually entering the correct date.

PO09817, WorkItem:277408 - A button is displayed as a link where an ACTION_CONTROL has a nested CONDITION element

Issue Description:

A button in the application is incorrectly displayed as a link if the corresponding ACTION_CONTROL element has a nested CONDITION element.

For example, when a conditional Cancel button on a modal dialog is configured in UIM/VIM with a nested CONDITION element on an ACTION_CONTROL element that does not have TYPE="SUBMIT", it is not displayed correctly to the user.

User Interface Impact: No

Prerequisite(s):

1. RegisterPerson_duplicateCheckForPDCWizard.uim is customized to have a Cancel button ACTION_CONTROL element that is a nested CONDITION element.

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to and open the person registration wizard.
3. Issue: The Cancel action button is displayed as a link.

Resolution:

The button is correctly displayed on the customized page.

Technical:

The infrastructure that generates JavaServer Pages from UIM has been updated. A button on a modal dialog is now correctly rendered when the associated ACTION_CONTROL element has a nested CONDITION child element.

PO09836, WorkItem:277625 - The progress spinner is not displayed when fetching search results

Issue Description:

When you click a Search button on a modal or wizard to search for data in the system, the progress spinner is not displayed to indicate that the search is in progress.

User Interface Impact: No

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to Person under Searches in the Shortcuts panel.
3. Enter some search criteria into the fields provided in the form.
4. Click the Search button.
5. Issue: A progress spinner does not display as expected while the system fetches the data to populate the search results.

Resolution:

When a Search button on a modal or wizard is clicked to search for data in the system, the progress spinner is displayed to indicate that the search is in progress.

DT036250, WorkItem:277969 - Some labels are not displayed on the person home page

Issue Description:

When a user navigates to the person home page, the 'Date of Birth Verified' and 'Date of Death Verified' labels are not being displayed. The user has no context for the Yes or No information displayed on the page.

User Interface Impact: No

Steps to Reproduce:

1. Log in as a claim worker.
2. Register a new Person.
3. Issue: On the person home page, the 'Date of Birth Verified' and 'Date of Death Verified' labels are not displayed.

Resolution:

All the field labels are now displayed correctly on the person home page.

Technical:

The infrastructure that generates Java Server Pages from UIM/VIM has been updated. A label that is associated with a form control on an application page or modal is now correctly rendered when a FIELD element has a nested LABEL child element in UIM.

Business Services

WORD INTEGRATION

PO09745, WorkItem:277855 - Edits to Word document on Google Chrome browser are not saved when the Word editing session is closed and user delays in confirming the edits

Issue Description:

Using the Microsoft Word Integration feature in the Google Chrome browser, when a user makes an update to a Word document they can choose to save their changes. Saving can be done either by closing the Word Editing session and confirming in a pop-up modal that is displayed or by selecting the commit changes button on the File Edit Control Panel. When users select to save changes by closing the Word editing session, if they wait more than 5 seconds before confirming in the pop-up dialog that appears in the browser (asking if they want to save their edits to the Cúram server), the edits are not saved.

User Interface Impact: No

Prerequisite(s):

1. Install Microsoft Word.
2. Install a supported (supported for Social Program Management Word Integration) Java Runtime Environment.
3. Install Google Chrome.
4. Install and enable the Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
5. Install the Social Program Management Word Integration Assistant. This is distributed with the Cúram Client Development Environment.
6. Log in as a system administrator.
7. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
8. Select the New page action to create a new Microsoft Word template.
9. Enter a name and template document ID for the template and upload a file to be used as the template.
10. Select a suitable category and sub-category. To allow the template to be used for any communication, set the category to All Communication and the subcategory to All Communications. Click Save.

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to a Person homepage.
3. Go to the Client Contact tab and choose Communications.
4. Click the page-level menu to create a new Microsoft Word communication.
5. On the New Microsoft Word Communication modal, specify a Correspondent and click Next.
6. Enter the Subject and Address. Choose the Template Name that was configured previously. Click Save.
7. The Word File Edit Screen is loaded in the Tab Content page and the File Edit Control Panel modal is shown.
8. Microsoft Word opens.
9. Make an edit to the Word document.
10. Close the Word editor.
11. The pop-up dialog appears in the browser window asking if you want to save your edit to the Cúram server. Wait 5 seconds, then press OK.
12. Issue: The file changes are not saved to the Cúram server.

Resolution:

When a user closes the Word Editing session, the changes are now saved. The Word Integration Assistant no longer deletes the Word file from the local file system before the browser code can attempt to save the changes to the Cúram server. The delete of the local file now only happens after the operation to save the document to the Cúram server has finished.

PO09747, WorkItem:277856 - File Edit Control Panel is closed on Google Chrome without informing the user that an error has occurred

Issue Description:

Caseworkers are able to edit the contents of Word documents using the Word Integration Assistant. When the Word Integration Assistant is used through a Google Chrome browser and a user chooses to save changes by closing the Word Editing session, if an error is encountered the File Control Panel closes. In this instance, the caseworker is unable to see that an error has occurred. This is in contrast to when a user uses the commit changes button on the File Control Panel to save periodically to the Cúram server, where the same error is visible in the File Edit Control Panel.

User Interface Impact: No

Prerequisite(s):

1. Install Microsoft Word.
2. Install a supported (supported for Social Program Management Word Integration) Java Runtime Environment.
3. Install Google Chrome.
4. Install and enable the Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
5. Install the Social Program Management Word Integration Assistant. This is distributed with the Cúram Client Development Environment.
6. Log in as a system administrator.
7. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
8. Select the New page action to create a new Microsoft Word template.
9. Enter a name and template document ID for the template and upload a file to be used as the template.
10. Select a suitable category and sub-category. To allow the template to be used for any communication, set the category to All Communication and the subcategory to All Communications. Click Save.

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to a Person homepage.
3. Go to the Client Contact tab and choose Communications.
4. Click on the page-level menu to create a new Microsoft Word communication.
5. On the New Microsoft Word Communication modal, specify a Correspondent and click Next.
6. Enter the Subject and Address. Choose the Template Name that was configured previously. Click Save.
7. The Word File Edit Screen is loaded in the Tab Content page and the File Edit Control Panel modal is shown.
8. Microsoft Word is launched.
9. Copy and paste the content of a 1MB text file into the Word document. The resulting Word document will be too large to be saved by the Cúram server and will cause an error.
10. Close the Word editor.
11. The File Edit servlet responds with a 500 HTTP response code indicating an error and the document is not saved.
12. Issue: The File Edit Control Panel closes. It should remain open and display an error message to the user. Having reviewed the error message, the user should be able to close the File Edit Control Panel.

Resolution:

The FIle Edit Control Panel modal now stays open so the error is visible to the user. The user can then close the modal after they have been shown the error message.

Technical:

The issue has been resolved by updating the functionality so that the browser does not close the File Edit Control Panel modal if there are any errors during the saving of the document. The user will be able to close the modal manually.

PO09782, WorkItem:277861 - Microsoft Word closes unexpectedly in Google Chrome if an unrelated Chrome browser is also open and is closed

Issue Description:

When using the Microsoft Word Integration feature through the Google Chrome browser, if a separate Chrome browser window is also open and a user closes this browser, Microsoft Word closes unexpectedly in the other browser.

User Interface Impact: No

Prerequisite(s):

1. Install Microsoft Word.
2. Install a supported (supported for Social Program Management Word Integration) Java Runtime Environment.
3. Install Google Chrome.
4. Install and enable the Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
5. Install the Social Program Management Word Integration Assistant. This is distributed with the Cúram Client Development Environment.
6. Log in as a system administrator.
7. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
8. Select the New page action to create a new Microsoft Word template.
9. Enter a name and template document ID for the template and upload a file to be used as the template.
10. Select a suitable category and sub-category. To allow the template to be used for any communication, set the category to All Communication and the subcategory to All Communications. Click Save.

Steps to Reproduce:

1. In Google Chrome, go to 'chrome: settings/system' and enable 'Continue running background apps when Google Chrome is closed.'
2. Open a second browser tab and move it out to be its own window.
3. In the first window, log in as a caseworker.
4. Navigate to a Person homepage.
5. Go to the Client Contact tab and choose Communications.
6. Click the page-level menu to create a new Microsoft Word communication.
7. On the New Microsoft Word Communication modal, specify a Correspondent and click Next.
8. Enter the Subject and Address. Choose the Template Name that was configured previously. Click Save.
9. The Word File Edit screen is loaded in the Tab Content page and the File Edit Control Panel modal is shown.
10. Microsoft Word opens.
11. Close the second browser window (the one that did not open the Word editing session).
12. Issue: Microsoft Word closes after the browser window is closed.

Resolution:

When an unrelated Chrome browser window is closed, the browser window in which the Word editing session opened is no longer closed

Technical:

The code executing in the browser mistakes the event of closing an unrelated Chrome browser window as the closing of the browser window that started the Word editing session. Therefore, a message is sent in error by the browser to the Word Integration Assistant instructing it to close Word and then itself. The Word Integration Assistant now ignores these events from other Chrome browser windows. Changes were also made to bring the actual behavior in line with the preferred behavior described here. If the user chooses to leave the page, the editing session is terminated and the document or Microsoft Word (if it was the only document open) closes along with the browser.

PO09746, WorkItem:277865 - Editing a Word document on Google Chrome browser displays 'X' error randomly

Issue Description:

Caseworkers are able to edit the contents of Word documents using the Word Integration Assistant. An intermittent issue occurs after a caseworker edits a document and then shuts down the Word Integration Assistant when the Google Chrome browser is used. When the caseworker then tries to edit another document, a red X icon is displayed in the File Edit Control Panel in the browser window.

User Interface Impact: No

Prerequisite(s):

1. Install Microsoft Word.
2. Install a supported (supported for Social Program Management Word Integration) Java Runtime Environment.
3. Install Google Chrome.
4. Install and enable the Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
5. Install the Social Program Management Word Integration Assistant. This is distributed with the Cúram Client Development Environment.
6. Log in as a system administrator.
7. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
8. Select the New page action to create a new Microsoft Word template.
9. Enter a name and template document ID for the template and upload a file to be used as the template.
10. Select a suitable category and sub-category. To allow the template to be used for any communication, set the category to All Communication and the subcategory to All Communications. Click Save.

Steps to Reproduce:

Note that this is an intermittent issue, there is no known method to force this.

1. Log in as a caseworker.
2. Navigate to a Person home page.
3. Go to the Client Contact tab and choose Communications.
4. Click the page-level menu to create a new Microsoft Word communication.
5. On the New Microsoft Word Communication modal, specify a Correspondent and click Next.
6. Enter the Subject and Address. Choose the Template Name that was configured previously. Click Save.
7. The Word File Edit Screen is loaded in the Tab Content page and the File Edit Control Panel modal is shown.
8. Microsoft Word opens.
9. Make an edit to the Word document.
10. Close the Word editor.
11. The document will be saved and the File Edit Control Panel will close.
12. In the same browser window, try editing another Word document.
13. Issue: A red X icon appears in the File Edit Control Panel.

Resolution:

A caseworker is now able to edit multiple Word documents without seeing the red X icon.

Technical:

This issue was caused by the improper handling of an initial exception that occurs when the user attempts to shut down the Word Integration Assistant Java process. The Java process is prevented from exiting correctly after the Word editor is closed. The red X icon is the result of starting a second Word Editing session in an inconsistent state. The fix also contains changes to ensure the problem state data that was previously long-lived is now short-lived.

Curam Modules

Provider Management

WorkItem:277633 - Optimize method for preventing creation of unnecessary notifications for provider management cases used for financials processing

Issue Description:

In a prior release, a mechanism was introduced to prevent the generation of unnecessary notifications for provider management case types that should not generate notifications because they are intended only for use in generating financials. This mechanism for excluding certain case types from generating notifications worked by checking the case type in identified workflows. The previous approach included case types that did not generate any notifications, which could cause a performance overhead.

User Interface Impact:** **No

Steps to Reproduce:

This issue is dependent on user data so it is not directly reproducible.

Resolution:

This issue has been resolved now and the mechanism for excluding provider management case types that should not generate a notification has been updated, to only generate notifications for the following case types:

• CASEREASSESSMENTNOTIFICATION
• DEFAULTCASENOTIFICATION

For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

Third Party Updates

WorkItem:277637 - Updates to some of the libraries present in Axis 2 and Rampart

Merative Social Program Management web services are based on Apache Axis2. With the Rampart security module of Axis2, Social Program Management web services can be secured for authentication, integrity (signature), confidentiality (encryption/decryption), and non-repudiation (timestamp).

The versions of some of the JARs in both Axis 2 and Rampart have been updated. As a result of these updates, the following changes have been made in the JDE Axis 2 deliverable.

• CuramSDEJ\lib\third_party_version.properties - the versions of the specified Axis 2 and Rampart JARs have been updated.
• CuramSDEJ\lib\axis2\axis2-ant-plugin-1.8.0.jar - version updated from 1.6.2 to 1.8.0.
• CuramSDEJ\lib\axis2\xmlbeans-3.1.0.jar - version updated from 2.3.0 to 3.1.0.
• CuramSDEJ\lib\axis2\esapi-2.2.3.1.jar - version updated from 2.0GA to 2.2.3.1.
• CuramSDEJ\lib\axis2\velocity-engine-core-2.3.jar version updated from velocity-1.5.jar to velocity-engine-core-2.3.jar.
• CuramSDEJ\lib\axis2\xmltooling-1.4.4.jar- version updated from 1.3.2-1 to 1.4.4.

Note that any references in custom scripts and other artifacts to the updated JAR files listed above must be updated.

WorkItem:277783 - Update the versions of the Jackson JARs to the latest version - 2.13.2

The Jackson API contains multiple functions to read and build JSON using Java. It has powerful data binding capabilities and provides a framework to serialize custom Java objects to JSON strings and deserialize JSON strings back into Java objects. The Java Development Environment (JDE) and the REST infrastructure use these utilities.

The versions of these JARs have now been updated to a later version. As a result of this upgrade, the following changes have been made in the JDE and REST deliverables.

• CuramSDEJ\lib\third_party_version.properties - the versions of the specified Jackson JARs have been updated.
• CuramSDEJ\lib\jackson-annotations-2.13.2.jar - new JAR added.
• CuramSDEJ\lib\jackson-core-2.13.2.jar - new JAR added.
• CuramSDEJ\lib\jackson-databind-2.13.2.2.jar- new JAR added.
• CuramSDEJ\lib\jackson-annotations-2.12.1.jar - old JAR removed.
• CuramSDEJ\lib\jackson-core-2.12.1.jar - old JAR removed.
• CuramSDEJ\lib\jackson-databind-2.12.1.jar- old JAR removed.
• CuramCDEJ\lib\ext\jar\jackson-annotations-2.13.2.jar - new JAR added.
• CuramCDEJ\lib\ext\jar\jackson-core-2.13.2.jar - new JAR added.
• CuramCDEJ\lib\ext\jar\jackson-databind-2.13.2.2.jar - new JAR added.
• CuramCDEJ\lib\ext\jar\jackson-annotations-2.12.1.jar - old JAR removed.
• CuramCDEJ\lib\ext\jar\jackson-core-2.12.1.jar - old JAR removed.
• CuramCDEJ\lib\ext\jar\jackson-databind-2.12.1.jar - old JAR removed.
• EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-annotations-2.13.2.jar - new JAR added.
• EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-core-2.13.2.jar - new JAR added.
• EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-databind-2.13.2.2.jar - new JAR added.
• EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-annotations-2.12.1.jar - old JAR removed.
• EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-core-2.12.1.jar - old JAR removed.
• EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-databind-2.12.1.jar - old JAR removed.
• EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-jaxrs-base-2.13.2.jar - new JAR added.
• EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-jaxrs-json-provider-2.13.2.jar - new JAR added.
• EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-module-jaxb-annotations-2.13.2.jar - new JAR added.
• EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-jaxrs-base-2.12.1.jar - old JAR removed.
• EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-jaxrs-json-provider-2.12.1.jar - old JAR removed.
• EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-module-jaxb-annotations-2.12.1.jar - old JAR removed.

GraphQL JARs:

• EJBServer\components\Rest\graphql_lib\jackson-datatype-jdk8-2.13.2 - new JAR added.
• EJBServer\components\Rest\graphql_lib\jackson-dataformat-yaml-2.13.2 - new JAR added.
• EJBServer\components\Rest\graphql_lib\jackson-datatype-jdk8-2.12.1 - old JAR removed
• EJBServer\components\Rest\graphql_lib\jackson-dataformat-yaml-2.12.1 - old JAR removed

Note that any references in custom scripts and other artifacts to the updated JAR files listed above must be updated.

WorkItem:277961 - JDom library update

The JDOM library is a Java-based solution for accessing, manipulating, and outputting XML data from Java code. Its usage in Merative Social Program Management is widespread across all areas of the application.

The jar file jdom-1.0.jar has been updated to jdom-1.0-1.jar.

As a result of this upgrade, the following changes have been made to the JDE deliverables.

• CuramSDEJ\lib\third_party_version.properties - the version of the specified JDom JAR has been updated.
• CuramSDEJ/lib/jdom-1.0.jar has been removed.
• CuramSDEJ/lib/jdom-1.0-1.jar has been added.

Note that any references in custom scripts and other artifacts to the updated JAR file listed above must be updated.

Known Issues

See the Known Issues section in the 8.0.1.0 release notes.

Notices

Before using this information and the product it supports, read the information in "Notices"