Merative ™ Social Program Management 7.0.0.0

Release Notes

Abstract

These are the release notes for Merative Social
Program Management 7.0.0.0

Content

Introduction
System Requirements
Installation
Improvements, Resolved Issues and Third Party 
Notes on Deprecation
Notices

Introduction

Welcome to the Merative Social Program Management 7.0.0.0 release.
Read this document to find important installation information, and to learn
about product improvements and resolved issues in this release.

For information about what's new in version 7.0.0.0, see the What's new in Version 7.0.0.0 
topic in the product documentation.

Full product documentation can be found in the Product documentation and PDFs.

For the latest version of the release notes, see https://curam-spm-devops.github.io/wh-support-docs/spm/release-notes.

This 7.0.0.0 release incorporates content from previous 6.2.x releases, which is documented separately in the following sets of online release notes:

• Merative Social Program Management 6.2.0.0
• Merative Social Program Management 6.2.0.1
• Merative Social Program Management 6.2.0.2

System Requirements

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

Installation

Install the Merative Social Program Management and supported related software according to the Installing Merative Social Program Management instructions in the documentation.

Ensure that you install the Merative Social Program Management Platform, enterprise modules, and program-based offerings in the correct sequence as described in the Overview of the installation steps topic.

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

For the latest version of the release notes, see https://curam-spm-devops.github.io/wh-support-docs/spm/release-notes.

Improvements, Resolved Issues and Third Party Updates

Third Party Updates

WorkItem:159728 - DB2 for z/OS V12 Support

Support for DB2 for z/OS V12 has been introduced in v7.0.0.0

WorkItem:107687 - Drop support for the browser plug-in - Adobe SVG Viewer

Support for the Adobe SVG viewer has been discontinued in the product. This viewer, which was previously required for application pages that contained a dynamic rules tree view or a workflow process view, is no longer used in the application. These views have now been modified to use the native SVG rendering functionality in the various supported browsers.

WorkItem:107728 - Support Microsoft Edge for the Universal Access application

Support has been added for the Microsoft Edge browser to access the Universal Access application. The version certified for this release is Microsoft Edge 38.

WorkItem:159792 - Browser support upgrade

The following browser versions have been updated and certified for this release

Case Worker Application Browser Support

• Google Chrome updated to 53

Universal Access Application Browser Support

• Google Chrome updated to 53
• Mozilla Firefox updated to 49

WorkItem:159797 - Introduce support for JAWS 17 and IE11

The version of JAWS used by the application has been updated to 17. This new version of JAWS has been certified against Internet Explorer 11.

WorkItem:159886 - Update the version of Apache Ant to 1.9.7

The supported version of Ant used in the Merative SPM development environment has been increased from 1.9.6 to 1.9.7.

WorkItem:159913 - Eclipse for development - upgrade to a later version - Luna 4.4

Support has been added for Eclipse version 4.4 (Luna) as a development tool. See the associated development tools pre-requisites for this version of the product for further details of this support.

WorkItem:160243 - Upgrade to the latest version of the Adobe Flash Plugin

The Adobe Flash Player browser plugin is required for application pages which contain charts (e.g. bar-charts) and for using the IEG, Datastore, Dynamic Evidence, and CER Editors. The version tested and certified with this version of the product is Adobe Flash Player 23.

WorkItem:160261 - Browser Plugins JRE Upgrade

The following JRE levels for Word Integration are supported for this release:

• JRE 1.7 u80
• JRE 1.8 u111

WorkItem:160282 - Windows 10 - support as a development environment

Windows 10 is now supported as a development environment. See the associated development tools pre-requisites for this version of the product for further details of this support.

WorkItem:160323 - Introduce support for DB2 11

DB2 11.1 support has been introduced. See the associated database pre-requisites for this version of the product for further details of this support.

WorkItem:160348 - Introduce support for RHEL 7

Support has been added for Red Hat Enterprise Linux (RHEL) Server 7. This platform may be used for both the building and deployment of the Merative SPM application.

WorkItem:160354 - Add Java 1.8 support for the SPM application

Java 1.8 support has been certified for the Merative Social Program Management application. This includes using Java 1.8 to develop, test, build and deploy the application. The Java 1.8 version included in both the WAS and WLS application servers have been included in this certification effort.

WorkItem:160359 - Change the recommended minimum screen resolution for the product

The minimum recommended screen resolution has been increased from 1024x768 to 1366x768.

WorkItem:161331 - Drop Support for the z/OS platform version 1.13

Support for the z/OS 1.13 platform as a remote database access or application deployment environment has been dropped for this version of the product.

WorkItem:161838 - Remove support for RHEL 5

Support for Red Hat Enterprise Linux (RHEL) 5 Server as a build environment has been dropped for this version of the product.

WorkItem:161842 - Remove support for DB2 10.1 from the product

Support for all editions of DB2 10.1 (Advanced Enterprise Server Edition, Enterprise Server Edition, Express Edition and Workgroup Server Edition) has been dropped for this version of the product.

WorkItem:168815 - Upgrade Dojo version from 1.10.4 to 1.10.5

Dojo framework has been upgraded to the next minor version 1.10.5.

WorkItem:177839 - Remove support for the Windows version of Apple Safari as a supported browser for the Universal Access application

Apple Safari 5.1.7 became the latest version of Safari developed for Windows. However, there have been no updates to this version of Safari for the last number of years and hence it has been effectively discontinued. Therefore, support for Apple Safari 5.1.7, which can be used to connect to the Universal Access application, has been discontinued. References to it in the associated prerequisites have been removed.

WorkItem:177849 - Support the latest version of the macOS Apple Safari browser for the Universal Access application.

Support has been added for the macOS operating system Apple Safari browser to access the Universal Access application. The version certified for this release is Apple Safari 10.

Cúram Enterprise Framework

PO06032, WorkItem:172334 - User not re-directed to the Login page when session expired

Previously, when a user session had expired, the application became unresponsive, for example when the user clicked on an action link in the Quick Links pod within the user Home section of the Application. This caused confusion because the users were not aware that the system session had expired and may have assumed the system had crashed. This issue has now been resolved so that when this scenario occurs, the user is redirected to the Login page as is consistent with the expected behavior of the application.

WorkItem:150260 - Provide more information about Quick Links

The 'Quick Links' section of the 'Configuring Personalized Pod Pages' guide of the Merative Social Program Management documentation has been updated to provide more information describing Quick Links. For more information see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

PO06150, WorkItem:153430 - Configuration of allowlist property for Rich Text Editor is not documented

The product documentation in Merative documentation has been updated to include details of the allowlist property and its configuration. For more information see, https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

WorkItem:159270 - Deprecate the Spell Checker utility

The Spell Checker add-on to the rich text editing feature that is found in functionality such as Notes is deprecated. All supported browsers now include built in spell checking capabilities that can be used as an alternative.
Please refer to the Configuring Spell Checking section within the Application Configuration Guide for a description of the deprecated functionality.

Artefacts were deprecated as a result of this change. For more information, please see the "Notes on Deprecation" section.

EVIDENCE MAINTENANCE

PO04152, WorkItem:122858 - Future Date of Birth can be captured when editing Birth and Death Details

Previously, a future date of birth could be captured when editing Birth and Death Evidence. The following validation has been added to the PDCBirthAndDeathValidationRuleSet

• ValidationResult.isDateOfBirthBeforeToday - this validation checks if the date of birth is not later than today.

Now, when editing the Birth and Death Evidence, if a case worker enters a date of birth that is greater than today the following validation is thrown: 'Date of birth must not be later than today'.

PO06481, WorkItem:168742 - Update 'Read Only Evidence' documentation to be implicit about the ability to delete evidence

The Merative Social Program Management documentation has been updated to clearly state that read-only dynamic evidence can be deleted by a case worker.
For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

Technical Services

PO06324, WorkItem:158985 - UA External Access Security implementation now supports implementing ExternalAccessSecurity.getRegisteredUsername()

The Merative SPM Security Guide has been updated to include the Merative SPM External Users table diagram in the following figures:

1. Authentication architecture figure in Section 2 Security, Subsection : Authentication
2. Default authentication figure in Section 2 Security, Subsection : Default authentication
3. Identity only authentication figure in Section 2 Security, Subsection : Identity Only Authentication

WorkItem:179998 - RMILoginClient has been updated to contain a set of buttons that enable a developer to easily log in as a different user

Previously, when using the RMILoginClient developers had to type the user credentials. The RMILoginClient has been updated to support the following pre-defined user roles:

• Sysadmin.
• Admin,
• Caseworker, and
• Superuser.

BUSINESS INTELLIGENCE

WorkItem:161245 - Deprecate Oracle Warehouse Builder (OWB) and DB2 ETLs

Oracle has announced that Warehouse Builder has reached its end-of-life. OWB ETL code is deprecated. DB2 ETLs are also deprecated. Please refer to the Developing Business Intelligence Reports Guide for a description of the deprecated functionality.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

DATASTORE

WorkItem:164649 - Reduce the size of the Datastore Infrastructure DATASTORE_QNAME domain definition to allow automatic index generation

The length of the string based Datastore domain definition, DATASTORE_QNAME, has been reduced from 400 characters down to 256 characters.

The intentional usage of this domain in the Datastore infrastructure was in the definition of the entity types specified in datastore schemas (e.g. names such as "Household", "Person" seen in datastore schema files). However, it was also mistakenly used to define the value that could be specified for these entity types and hence the required length was specified to be 4000 characters for this purpose. This had the added affect of not being able to index properly any search which used a field defined in terms of the DATASTORE_QNAME domain definition due to length restrictions on overall index lengths.

This issue has been alleviated by reducing the length of the DATASTORE_QNAME as outlined above to 256 characters and introducing a new domain definition called DATASTORE_ENTITY_VALUE whose length is 4000 characters and on which the datastore entity value is now based on.

There is no expected impact for this change as the new length for the DATASTORE_QNAME is envisaged to be more than enough characters to defined even the most verbose of the currently datastore entity types.

GENERIC SEARCH SERVER

WorkItem:159363 - Deprecate the Generic Search Server (GSS) feature

The Generic Search Server (GSS) that uses Lucene for indexing and search functionality within the product is deprecated. Please refer to the Developing with the Generic Search Server Guide for a description of the deprecated functionality.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

WORKFLOW

PO06064, WorkItem:150393 - The Task ID in the Task page, and the Person Reference number in the Person Search are rendered incorrectly when a user returned to the respective pages after a lengthy delay

Previously, when a user navigated to the Task Search tab and performed a search by entering a 'Task ID' (in the Task ID field) then selected the 'Search' action, opened the task from the search results and subsequently closed the Task page and navigated back to the search results page, the ID displayed in the 'Task ID' field was not displaying correctly (i.e. it was rendering halfway down the field display). This issue only occurred when there was a lengthy delay (70 seconds or more) between leaving the search page and returning to it. This issue has been resolved so all search field content renders correctly.

Integrated Case Management

PO06062, WorkItem:150324 - Product Delivery End Date Documentation Clarification

The ‘Configuring Integrated Case Management’ guide on the Merative Social Program Management documentation contained incorrect information relating to the functionality of the ‘End Date’ on Product Delivery Case.

The guide has been updated to include information on the product delivery end date functionality. This updated section is: Configuring -> Configuring Integrated Case Management -> Configuring Case Types -> Configuring Common Case Information -> Date Settings.

WorkItem:159366 - Deprecate legacy employment contribution entities

Entities that enabled customers to implement contribution-based solutions in employment areas such as pensions and unemployment insurance tax have been deprecated. Existing framework functionality including the liability product, financial manager, and employer participant type can be used for the basis of an employment contribution solution.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

PO06423, WorkItem:165071 - Skip to main content link appears after multiple tabs

Previously, when a user logged in to the application and then selected tab, Announcements were the first area to get focus. From an accessibility perspective this was incorrect. Now, this issue has been resolved. When a user logs into the application and selects tab, the “Skip to main content” is the first element to get focus. When the user selects the “Skip to main content”, the focus moves to the main content.

PO06518, WorkItem:170596 - Application Home page missing refresh button and help button for some users

Previously, the home page was missing the refresh and help buttons. This issue has been resolved. Now, the refresh and help buttons appear on the Application Home page.

ELIGIBILITY & ENTITLEMENT

PO05449, WorkItem:123451 - Performance issues on Oracle with SQL statement InstructionLineItem.readLastPaymentAndEffectiveDate() as payment volumes increase

Previously, the SQL statement readLastPaymentAndEffectiveDate() located in the InstructionLineItem entity performed poorly in Oracle as payment volumes increased. The query reads the amount and the effective date of the last payment made and processed on the case for a specified case ID. Where more than one payment was issued on this date, the total amount of the payments (excluding cancelled payments) is returned.

The SQL statement has been updated to perform more efficiently.

PO06170, WorkItem:154133 - Records with references to another entity with an ID of zero incorrectly written to Dependency and PrecedentChangeItem tables

When using Merative SPM Express Rules, it was possible that a rule set could cause some rows to be written to the Dependency and PrecedentChangeItem tables which refer to another entity with an ID of zero.

The system will now prevent these zero ID rows from being written to the tables during rule execution, with one caveat: if the row being written is of precedentType "R_A_MATCH", it is still possible that a precedentID can refer to a zero ID if the attribute in the precedent is not a primary key attribute.

If the system prevents a row from being written to either table because of a zero ID, it will write a warning in the application log with this signature: "WARN_PRECEDENT_WITH_ZERO_ID_NOT_STORED"

PO06174, WorkItem:154140 - Provide information about how the Dependency Manager handles Zero ID records

The Storage of Dependency Records section of the 'Merative SPM Express Rules Reference' guide of the Merative Social Program Management documentation has been updated to provide more information on how the Dependency Manager manages zero ID's that could be generated by a rule set. For more information see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

WorkItem:159369 - Deprecate CER Key Decision Factors (graphical and list view)

Key Decision Factors rules and the graphical / list view display of key events within a case that form part of the CER infrastructure is deprecated. Decision Details rules are available to implement the display of similar key event information. Please refer to the Calculating and Displaying Key Decision Factors section and the Calculating and Displaying Decision Details section within the Developing with Eligibility and Entitlement by using Cúram Express Rules Guide for a description of the deprecated functionality.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

PO06330, WorkItem:161098 - ReassessmentAggregationManager:CLAIM_ERROR error message reported in log file

When Reassessment Aggregation is enabled, it is possible that two or more workflows will attempt to reassess the same case if multiple changes are made to a case in quick succession. In this scenario, one workflow will take control of reassessing the case, while the other workflows will be backed off and exit processing. When a workflow is backed off, a CLAIM_ERROR does not need to be documented during the ReassessmentAggregationManager.reassessCase() activity.

WorkItem:168376 - Enhance reassessment aggregation to support interaction with existing deferred processes

There are some execution paths that will invoke a case reassessment outside of the reassessment aggregation infrastructure. For these scenarios, we now add the calling deferred process details to the DependencyTrace table when reassessment happens. The following deferred processes invoke reassessment and their details will be stored in the DependencyTrace table:

• ASSESSCASE
• CLOSECASE
• ELIGIBILITYASSESSMENT
• REGENCASEFCS

WorkItem:175884 - Missing Index causing high page response times on Determination pages

The sql query which checked to see whether a case reassessment was pending in the Dependency Manager batch changeset performed poorly as it used the incorrect indexes on the Dependency table. This query is used in the Current Determination screen. The query has been corrected and an index has been added to the PrecedentChangeItem table:

CREATE INDEX PrecedentChangeItemTypeHashIDX ON PRECEDENTCHANGEITEM(PRECEDENTTYPE, PRECEDENTIDHASH);.

EVIDENCE MANAGEMENT

WorkItem:159367 - Deprecate the Evidence Flow feature

The Evidence Flow view of evidence displayed within the Evidence Workspace is deprecated. The Evidence Dashboard view is available to users to manage evidence within a case. Please refer to the Using the Evidence Flow View section in the Curam Evidence Overview guide for a description of the deprecated functionality.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

WorkItem:159372 - Deprecate Superseded Non-Identical Evidence Mapping

The original version of non-identical evidence mapping functionality that supported evidence sharing only where evidence was identical down to the domain definition level is deprecated. A new version that provides enhanced ability to map evidence with different domains is available.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

COMMON

WorkItem:159371 - Deprecate Referrals (Legacy) functionality

Referrals functionality that allows for the capture of basic information related to the referral of a client to the Service Supplier participant type is deprecated. Enhanced referrals functionality is available within the Cúram Provider Management (CPM) module. Please refer to the Scheduling a Referral section within the Cúram Calendaring Guide for a description of the deprecated functionality.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

PO06403, WorkItem:160846 - Provide a description of how 'My Cases' pod should be used.

The ' Pre-defined Pods' page in the Merative Social Program Management documentation has been updated to provide more information about the 'My Cases' pod. For more information see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

PARTICIPANT MANAGEMENT

PO03790, WorkItem:122755 - Register Prospect as Person search incorrectly pre-populates Reference Number field

Previously, while registering a prospect person as a person, the prospect person's reference number was being pre-populated in the 'Register Prospect Person as Person' modal, meaning only that prospect person was returned in the results. Now, the reference number is no longer pre-populated.

WorkItem:156841 - Browser based emails opening up in context panel rather than new tab.

Previously, in Chrome, when the user selected a Person's email address on the home page and an email server was configured, the email opened in the context panel. Now, when a user clicks on the email address, it opens in a new window, providing a proper compose email page.

WorkItem:169673 - Remove 'Applied by" text from the 'Latest Activity' column on evidence list in the Person Case

Previously, each entry in the ‘Latest Activity’ column on the person Evidence List page was proceeded by the text ‘Applied by’. Evidence for a person is always applied on a successful save, displaying this text didn't provide any information the caseworker wasn't already aware of and the text took away from the important information. This text has now been removed so that the caseworker will be presented only with the relevant information which is the name of the user who made the change and the date/time on which it was changed.

ORGANIZATION

PO06360, WorkItem:161340 - Documentation for 'Organizational Announcements' is not available

Documentation on the announcement functionality has been added to the Knowledge Center. For more information see, https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

Intake

WorkItem:173461 - Application search page is not opening for the users' iwuser' and intakesupervisor'

The WEBADDRESS.dmx entry with WEBADDRESSID 19000 has been updated with the latest application search page. Previously this entry pointed to ApplicationSearch_TabDetails. The entry now points to ApplicationSearch_TabDetails4.

Application Development Environment

CLIENT DEVELOPMENT ENVIRONMENT

PO03448, WorkItem:106787 - Merative SPM print from browser truncated at the bottom of the list when it is inside a in-page navigation.

When printing a list contained within a in-page navigation tab, the rows towards the end of the list were truncated. This issue has now been resolved.

PO05389, WorkItem:107516 - Right aligned ACTION CONTROLS not displaying correctly at 200% zoom in modal on minimum resolution

Previously four or more right aligned ACTION CONTROLS were not displaying correctly at 200% zoom on minimum screen resolutions. This issue has now been resolved.

PO06245, WorkItem:157285 - Documentation for PROMPT attribute on the FIELD element is inaccurate

In the Web Client Reference Guide, the description of the PROMPT attribute on the FIELD element was inaccurate. The guide has been updated to read as follows:

The PROMPT attribute is used to configure a placeholder value in the text field associated with a Date Selector, if the text field is blank. On focus, the placeholder text will disappear to allow for data entry.

WorkItem:159718 - Form Controls - Search Popups

There is a new hover state for single search and multiple search popup pages. The image for the hover state is configurable and documented in the Pop-up Pages section in the Knowledge Center.

ACCESSIBILITY

WorkItem:103214 - Mandatory state for search and frequency pattern fields not correctly marked up for screen reader.

Previously the mandatory state of the search/frequency pattern field was not marked up correctly for screen reader user. This issue has now been resolved.

WorkItem:106394 - Shortcut panel splitter screen reader support

The shortcut panel splitter has been updated to support screen readers via the addition of an aria label. The aria label consists of a new text property appended to the panel's existing title. This new text property is configured in CDEJResources.properties and out-of-the-box it is set as follows:

shortcut.panel.splitter.aria.label.postfix=Splitter

WorkItem:107123 - Year Field Is Clipped In Select A Frequency Pattern Modal in 200% zoom

Previously a user was unable to see the full year field in the 'Select A Frequency Pattern' modal on a 200% zoom. This issue is now resolved.

WorkItem:107273 - JAWS reads out list action items incorrectly

Previously there was an issue on list action menu items affecting screen reader users. The screen reader was announcing all menu entry with extra unnecessary text. This lead to confusion for screen reader users. Now this issue has been resolved.

WorkItem:107274 - JAWS 15 & 16 doesn't read out all the elements inside Org Tree

The keyboard navigation and screen reader support of the organization tree viewer has been enhanced. When expanding a lazy loading folder, focus will now remain on the folder being expanded. Also, when navigating past the expanded folder, the screen reader will continue to announce the correct level for the folder.

PO04887, WorkItem:107281 - No Tooltips on popup search fields

Previously the pop-up search field did not display any tooltip, when no selection was made. This has been resolved by displaying the field's label in the tooltip, when no selection has yet been made.

PO04925, WorkItem:107290 - JAWs user unable to navigate tabs using JAWS

Previously it was not possible to navigate to the application's user interface tabs using JAWS' form field dialog. This issue is now resolved with JAWS 17.

PO05126, WorkItem:107350 - Tooltip support for dynamic page title

Previously, the tooltip text for a dynamic page title was not displaying all of the content. This was occurring for page titles that were generated dynamically from both static and dynamic content. Under this condition, the tooltip would only display the static part of the title and the dynamic content was not shown. The issue has been resolved so the tooltip provides all title content to the user.

PO05260, WorkItem:107426 - Enabling the optional header causes display issues with application tabs

The behaviour of the application, when the optional header is specified in addition to the application banner, has been enhanced. Even when zooming at 200% with the lowest supported screen resolution, the application sections remain all visible, with no overlapping between them and the optional header/banner.

WorkItem:143055 - JAWS: Region List shows a region with no text for the pages where UIM doesn't have a title.

Previously, on first load, a content panel region displayed as unlabelled when PAGE_TITLE was not defined in the corresponding UIM file. This issue has been resolved by using the corresponding tab name to populate the region title where a PAGE_TITLE does not exist. This makes the behaviour consistent with what happens on subsequent reloads of the page.

PO06402, WorkItem:163713 - When the browser size is reduced and multiple tabs are opened the navigation tab list icons are displayed incorrectly

Previously tab scroll buttons were not labelled correctly for screen reader users. This issue has been resolved by adding informative labels to each tab scroll button.

WorkItem:165130 - Selected items in IEG drop-down, JAWS reads as '(Selected Gender) dash dash please select dash dash'

Previously, there was an accessibility issue when using JAWS with IEG drop-down fields. Instead of JAWS reading out the value that was pre-selected in the drop-down, JAWS would always read out "dash dash Please Select dash dash". This issue has now been resolved. JAWS now reads out the pre-selected value in the drop-down correctly.

WorkItem:173693 - Notification that the High Contrast Mode User Preference is deprecated

The High Contrast Mode User Preference is now marked as deprecated and will be removed in a future release. For further information on High Contrast, you can refer to the User Preferences section in the Knowledge Center. Going forward, it is recommended that any customized pages should be designed in accordance with the Web Content Accessibility Guidelines (WCAG 2.0) Level AA, so that they are High Contrast by default.

LOOK & FEEL

WorkItem:106785 - Provide visual feedback during application processing

A progress indicator has been added to the application to signal to a user that the system has acknowledged an action and is currently busy. If the loading of content in any panel or modal dialog in the application takes longer than 2 seconds, a progress spinner will now appear.
The indicator is configurable using two properties in the ApplicationConfiguration.properties file:

• curam.progress.widget.enabled: This property toggles the feature on/off. Default: true.
• curam.progress.widget.threshold: This property specifies in milliseconds, the time offset before an indicator is displayed on the screen. Default: 2000 (2 seconds).

WorkItem:167176 - User interface look and feel upgrade impacts from Version 6.x to Version 7.0.0

The Merative Social Program Management user interface has been updated and, therefore, the underlying HTML structure of the application banner has been updated. Consequently, when you upgrade to Version 7.0.0, the updates to the HTML structure might impact customizations that you have implemented in previous versions. In particular, the following customizations might be affected by upgrading to Version 7.0.0:

• If you have implemented custom widgets that add new HTML to the default application; to obtain the new look and feel for custom widgets, see the color palette section.
• If you have previously added CSS rules to customize the look and feel of the default application.

Color palette

The updated Merative Social Program Management user interface uses the following colors from the Merative SPM Design full-spectrum color palette:

• #FFFFFF – “White”: Primary use: Page, modal and wizard background
• #E0E0E0 – “Grey10”: Primary use: Content background (for example, content panel, divider Lines)
• #777677 – “Grey50”: Primary use: Disable state (for example, disabled text and icon color)
• #464646 – “Grey70”: Primary use: Default body text (for example, list text, cluster text, context panel text)
• #C0E6FF – “Blue10”: Primary use: Drag and drop. This color is used to change the background color when an item is being dragged.
• #4178BE – “Blue50”: Primary use: Live or clickable item (for example, link text, actionable and clickable icons)
• #325C80 – “Blue60”: Primary use: Hover state item (for example, hover state for link text, hover state for actionable and clickable icons)
• #264A60 – “Blue70”: Primary use: Navigation (for example, shortcuts panel, cluster titles, page titles)
• #1D3649 – “Blue80”: Primary use: Application banner, large body copy text (for example, cluster titles, page titles)
• #AD1625 – “Red60”: Primary use: Attention, alert, warning (for example, required text message, warning message)
• #F9F9F9 – “Neutral2”: Primary use: Background color (for example, list headings)
• #F4F4F4 – “Neutral3”: Primary use: Background panel color (for example, smart panel)

New CSS class name

A "curam" CSS class name has been added to all HTML elements in the application. For example, CSS stylesheet rules that were previously named ".soria" should be named ".curam.soria".
Upgrade impact

• Analyze the CSS stylesheets in the custom component to determine which CSS rules should be updated with the "curam" CSS class name in order to apply the new look and feel to the customizations.

Logon/Logout Page

The look and feel of the logon and logout pages have been updated in line with the rest of the application.
Upgrade impact

• The width of the main content panel has been increased from 480 pixels to the full width of the logon and logout pages. Review any customizations that have been made to the main content panel on the pages to determine whether they are still relevant. If customizations have been made that rely on the main content panel being 480 pixels wide, then the position of the copyright notice must be updated.

Application banner role

The role that was previously displayed on the left side of the banner is no longer supported, for example, "Caseworker".
Upgrade impact

• Remove any customizations to the look and feel of the role that was displayed within the banner.

Application title and logo

The application logo and title are now positioned in the middle of the banner. The CSS rules have been updated.
Updated CSS rules

• Previous path: #app-banner .left-box .title
• Current path: body.curam.soria #app-banner . program-name-div .program-name-text-div span

Upgrade impact

• Review any customizations to the application title. Any customizations that modify any of the following aspects of the application logo and the title are no longer relevant:
  • The position of the title within the banner. The length of the title that can be displayed is now limited to 41 characters.
  • The default size of the container for the application logo is now 20 pixels x 20 pixels.

Application person menu

Previously, the application banner contained separate links for Preferences, Log out and About. The links are now included in a single application person menu that you access through the banner. The CSS rules for the links have been updated.
Updated CSS rules

• Preferences
  • Previous path: #app-banner-dc #app-banner .right-box .right-cell .pref-list a
  • Current path: body.curam.soria div.dijitPopup.dijitMenuPopup .dijitMenuItem .dijitMenuItemLabel
• About
  • Previous path: #app-banner-dc #app-banner .right-box .right-cell .logout-list a
  • Current path: body.curam.soria div.dijitPopup.dijitMenuPopup .dijitMenuItem .dijitMenuItemLabel
• Log out
  • Previous path: #app-banner-dc #app-banner .right-box .logo img
  • Current path:body.curam.soria div.dijitPopup.dijitMenuPopup .dijitMenuItem .dijitMenuItemLabel

Upgrade impact

• Review any customizations to the Preferences, Log out and About links to determine if the customizations are still relevant in relation to the new look and feel. You must also consider the following additional points:
• For customizations to be displayed correctly, you must apply the important selector to the CSS properties. For example, if a customization is implemented to set the background color to orange for each of the Preferences, Log out and About links, apply the following CSS rule:

body.curam div.dijitPopup.dijitMenuPopup .dijitMenuItem .dijitMenuItemLabel {
background-color: yellow !important;
}

• If each of the Preferences, Log out and About links needs to be styled differently, then you must implement a separate, specific CSS rule for each link.

Application welcome message

The position of the application welcome message has changed slightly to accommodate the new application person menu.
Updated CSS rules

• Previous path: #app-banner .right-box .left-cell
• Current path: body.curam.soria #app-banner .right-box .left-cell

Upgrade impact

• Review any customizations to the application welcome message.
• Any customizations that adjust the margins on either side of the welcome message are no longer relevant.

Application search

The look and feel of the application search field has been updated and is now positioned at the top of the banner next to the welcome message. Also,the structure of the underlying HTML has been updated considerably. The CSS rules for the application search box have been updated.

Updated CSS rules

• Search Text Box
  • Previous path: div.application-search input
  • Current path: body.curam.soria #app-banner .application-search .dijitInputField

Upgrade impact

• Review any customizations to the application search field to determine whether the customizations are still relevant in relation to the new look and feel.

Check boxes, radio buttons and file upload buttons

The look and feel of check boxes, radio buttons, and file upload buttons has been updated so that they are displayed and behave the same way in all supported browsers. In order to satisfy this implementation, the generated HTML for the widgets has been updated with two hidden LABEL elements after the associated INPUT element.
Upgrade impact

• Review any customizations to the widgets to determine if they are still relevant in relation to the new look and feel.

Modal dialogs

The default width of modal dialogs has been updated from 600 pixels to 700 pixels.

Evidence Dashboard

Minor updates have been made to the generated HTML for the Evidence Dashboard (Core Evidence Map) widget so that icons are displayed correctly in Right-to-Left (RTL) mode.
Upgrade impact

• Review any customizations to the Evidence Dashboard to determine if they are still relevant in relation to the new look and feel.

WIDGETS

PO03643, WorkItem:106840 - Application Search Copy/Paste Issue

The application search feature in the application banner is supposed to dynamically enable the search link when there is content in the search text box. Previously, the search link was not enabled correctly when content was pasted into the search text box via the the mouse, right-click, context menu. This now works as originally intended.

PO05048, WorkItem:107313 - Search fields not being cleared when a modal dialog is closed and the parent page is refreshed

Previously search popup action fields were not correctly cleared following a page refresh. This issue has now been resolved.

PO05757, WorkItem:143479 - No documentation for the File Upload widget uses browser specified controls

The documentation for the FILE_UPLOAD widget has been updated to clarify that the widget uses browser-specified controls, the text on the button is displayed in whatever locale the browser is set to, regardless of the locale that is configured in the application. For more information see, https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

CORE DEVELOPMENT INFRASTRUCTURE

WorkItem:164670 - Change the default tnameserv port from 900 to 1221

The default tnameserv port has been changed from 900 to 1221. This change is being done in this release to minimise future impact where some platforms restrict usage of the available lower ports.

Impact to custom web.xml files serving Eclipse development - this target port for RMI communication is maintained within this file and if the new default is used on the server, you should change any custom.xml files to match.

SERVER DEVELOPMENT ENVIRONMENT

WorkItem:165409 - TLS 1.2 Support

Application servers are now configured with SSL enabled in a TLSv1.2-only mode. The TLS protocol provides communication security over the Internet, and allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.

Documentation update for TLSv1.2 in WebSphere application server:

A new section "Configure Transport Layer" that provides instructions for manually enabling TLSv1.2 in WebSphere applications server has been added to the chapter Manual WebSphere Application Server Configuration in Cúram Deployment Guide for WebSphere Application Server.

Documentation update for TLSv1.2 in Weblogic application server:

A new section "Setup Transport Layer Security" that provides instructions for manually enabling TLSv1.2 in Weblogic applications server has been added to the chapter Manual WebLogic Server Configuration in Merative SPM Deploying on Oracle WebLogic Server.

MISCELLANEOUS

WorkItem:173411 - DataExtractor only extracting tables from the Merative SPM model and infrastructure and missing Workflow, CREOLE tables

An issue has been resolved whereby when extracting all tables from the database using the extractdata build target, Workflow and CREOLE tables would not be extracted.

Common Intake

WorkItem:149940 - Update documentation for show-container-help attribute within IEG containers

The product documentation for show-container-help attribute within IEG containers is updated. For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

WorkItem:156705 - Introduce multi-select to Application Search

Previously the application search page used drop-down widgets to select type, program, and status for application search. This page has now been deprecated and replaced with ApplicationSearch_TabDetails4.uim. The new page uses multi-select widgets instead of drop-down widgets to select types, programs, and statuses. Searches can now be constructed from multiple criteria for each field allowing the user to execute more powerful searches for applications.

The application search page can be accessed through a quick link on the home page. The quick link has been updated in EJBServer/components/Intake/data/initial/WEBADDRESS.dmx. Previously, ApplicationSearch_TabDetails2.uim was loaded from the quick link which has been updated to ApplicationSearch_TabDetails4.uim.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

Cúram Modules

Outcome Management

PO04342, WorkItem:97687 - Orphan Case Type Code in Outcome Management resulting in un-handled server exception

Previously, an un-handled server exception occurred when a customer installed Citizen Context Viewer and Assessment Planning components without the Social Enterprise Collaboration case type. The SEF case type was being referred in Citizen Context Viewer and Assessment Planning components' application properties.

This has been resolved by removing the affected codetable entry from Citizen Context Viewer and Assessment Planning application properties.

WorkItem:169579 - The Planner Application View is missing Quick Links and Shortcuts

In the Planner Application View, a number of Quick Links and Shortcut links were found missing when compared to the previous versions of the application.

This has been resolved by re-introducing the missing links.

The "Quick Links" pod has now been updated to further include following links

• Search for an application case
• My application cases
• Register a Person
• Search for a referral case
• My Referrals
• Search for a person

The "Searches" section of the shortcuts panel has been updated to include following links

• Person
• Case
• Application Case
• Referral

Additionally, a new section called "Intake" has been added to the shortcuts panel with following new links

• My application cases
• My referrals
• Pending Application forms

Social Enterprise Collaboration

CASE & PARTICIPANT INDEX

WorkItem:159268 - Deprecate Case & Participant Index (CPI)

CPI functionality provided as part of the Social Enterprise Collaboration (SEC) module to enable Master Data Management (MDM) capabilities and display of information from an external system within Cúram is deprecated. Please refer to the Cúram Case and Participant Index (CPI) section within the Cúram Social Enterprise Collaboration Guide for a description of the deprecated functionality.

SOCIAL ENTERPRISE FOLDER

WorkItem:159365 - Deprecate the Social Enterprise Folder (SEF) case

The Social Enterprise Folder (SEF) case type provided as part of the Social Enterprise Collaboration (SEC) module to enable Multidisciplinary Team (MDTs) to collaborate on cases and clients is deprecated. The collaborative outcome plan and MDT portal functionality is available within the SEC module to support MDT collaboration on the delivery of services to clients. Please refer to the Social Enterprise Folder section in the Cúram Social Enterprise Collaboration guide for a description of the deprecated functionality.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

Provider Management

WorkItem:165340 - JAWS screen reader does not read description field

Previously, JAWS screen reader was not able to read description field on create new plan item modal window. This issue has been resolved now and the screen reader reads the field label as expected.

MISCELLANEOUS

WorkItem:159267 - Deprecate CPM Taxonomy

The taxonomy functionality that provides the ability to establish a hierarchy of terms and index those terms to provider service offerings for use in searching for services is deprecated. Please refer to the Services Taxonomy section in the Cúram Provider Management Guide for a description of the deprecated functionality.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

WorkItem:159364 - Deprecate CPM Performance Monitoring

The Performance Monitoring functionality that provides the ability to configure performance measures and evaluation criteria for a provider to enable agencies to measure provider performance is deprecated. Please refer to the Performance Monitoring section in the Cúram Provider Management Guide for a description of the deprecated functionality.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

Universal Access

WorkItem:118703 - The text ‘Your application has been submitted’ is missing heading on Application Submitted Page Player Page

Previously, when a user submitted an application through the citizen portal, the confirmation page displayed the heading "Your application has been submitted." without any HTML formatting. This resulted in the heading getting lost with the rest of the descriptive text in regular font.

This is resolved now by using the heading specific HTML tag for the text "Your application has been submitted." making it to appear in bold letters.

PO06030, WorkItem:149093 - 'Skip to Main Content' navigation Link is not working as Expected

Previously, when the users clicked the 'Skip to main content' link in any Universal Access application page, they were not navigated to main content of the page, and instead the focus was brought to the navigation menu.

Now, this has been resolved by adding a tab index value to the main content of the page and clicking on the "Skip to main content" link now navigates the user to the main content of the page as expected.

PO06205, WorkItem:155467 - Language drop-down menu tooltip does not get displayed in the correct language

Previously, the tooltip on the language drop-down menu was always getting displayed in English in all localized application.
Now, this has been resolved by reading the tooltip of the Language drop-down menu from the properties file and having it localized for all the applications.

PO06299, WorkItem:164952 - The JAWS screen reader reads the HTML code instead of descriptions for the items present on the Application Banner

Previously, the JAWS screen reader used to read HTML code from the help button drop down list of the Application banner.
Now, this has been resolved by adding description to the banner items using the 'aria-label' attribute and the screen reader correctly reads the descriptions of the respective application banner items.

WorkItem:168153 - Tooltips missing for Navigation Items in Universal Access

Previously in Universal Access, some of the navigation bar items did not include the tool tip text.

This has now been resolved by adding a tool tip text for each of the navigation items.

Appeals

PO06368, WorkItem:161998 - Search icon in New Desk-Based Hearing modal reached after multiple tabs

Previously, when a user opened the 'New Desk-Based Hearing' modal, the field focus was not set to the 'Hearing Official search' field, requiring the user having to tab multiple times to reach the field.

This has now been resolved by setting the default focus on the 'Hearing Official Search' field.

Intelligent Evidence Gathering

PLAYER

PO05598, WorkItem:105479 - User is unable to select radio buttons in IEG by clicking on the radio button label text

There was an issue where certain radio buttons could not be checked or unchecked by clicking on their associated label. This issue has been resolved.

Financial Management

WorkItem:123362 - Improve documentation on Reconcile Case Batch functionality

The description of the Reconcile Case batch process in the Knowledge Center documentation is improved. For more information see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

WorkItem:159370 - Deprecate the Over / Under Payment Graphical View

The graphical view of over / under payments generated within a product delivery case is deprecated. The statement view is available to users for understanding the history of over / under payments within a case.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

Solutions

Income Support

WorkItem:101574 - Spend Down page not conforming to Merative SPM accessibility standards

The Spend Down page did not conform to Merative SPM accessibility standards, the formatting has been altered and this has now been resolved.

WorkItem:156666 - Launch an application for HCR and Income Support from the Person tab using the same action

Previously two separate actions were included on the Person tab actions menu for launching the Health Care Reform (HCR) Intake application script and the Income Support Intake application script. The New Application Form action launched the HCR Intake application script, and the New Application action launched the Income Support intake application script. Having two different action labels which launched the same business function was inconsistent and non intuitive.

In order to have a consistent user experience, the two actions have been replaced with a single New Application action that launches the relevant intake application script depending on user role access. Some minor retraining will be required for caseworkers used to launching the Income Support intake application.

WorkItem:156694 - Rename tab actions on Income Support and HCR applications to be more consistent

Updates have been implemented to improve consistency for users who navigate both the Income Support and the Health Care Reform (HCR) application tabs. Aswell as reordering the display of the tab level menu items, the following updates have been applied to the Income Support application tab level actions:

• "Edit Details" has been renamed to "Edit"
• "Review Eligibility Result" has been renamed to "Authorize"
• A new menu item, "New Program Appeal", has been added

For the HCR application tab level menu items, the "Find Client" and "Add Client" menu items have been removed as they have been replaced by the Guided Change wizard.

Some minor retraining will be required for caseworkers who are used to working with HCR and Income Support applications.

WorkItem:156697 - Renaming of fields on Income Support and HCR application case context panels to be more consistent

To improve consistency between the Health Care Reform (HCR) application case context panel and the Income Support application context panel, the following label changes have been implemented:

• Occurrences of 'Application Case' have been updated to 'Application'.
• Occurrences of 'Date' when referring to an application date have been updated to 'Application Date'.
• The label 'Programs Applied For' has been updated to 'Programs'.
• Occurrences of 'Programs Requested' have been updated to 'Programs'

Some minor retraining will be required for caseworkers used to working with HCR and Income Support applications.

WorkItem:157645 - Remove New Application Case button from tab actions and page level actions

For the Health Care Reform (HCR) and Income Support user roles, the "Person" tab action menu has been updated to remove the "New Application Case" menu item because the application is created by launching the intake script from the "New Application" menu item.
The "New Application Case" and "New Referral" buttons have been disabled by default on the Applications page of the "Care and Protection" page level tab on the "Person" tab. The buttons can be enabled again at this level if needed by selecting the "Direct Creation" checkbox in the application case configuration settings in the administration console.

Having multiple actions that launched the same business function was inconsistent and nonintuitive.

The actions have been replaced with a single "New Application" action that launches the relevant intake application script depending on user role access. Some minor retraining will be required for caseworkers who are used to launching HCR and Income Support intake applications.

WorkItem:157647 - Income Support pending applications on Person home page

The ‘Pending Application Cases’ cluster on the person home page has now been renamed to ‘Pending Applications’.
Previously the list displayed only the person's pending Health Care Reform (HCR) applications. Now the list displays the person's pending Income Support applications as well, giving a fuller view of the person's current pending applications, irrespective of whether the user's role is HCR or Income Support. Income Support applications that have a status of 'Submitted', 'Submit Failed' or 'Ready for Determination' are displayed in the Pending Applications list. Having a single business function that behaved differently across applications was inconsistent and non intuitive.

In order to have a consistent user experience, these functions now exhibit the same behaviour. Some minor retraining will be required for caseworkers used to working with HCR and Income Support applications.

PO06102, WorkItem:158612 - Incorrect Allowable and Non-allowable Self Employment expense amounts are displaying incorrectly on the Food Assistance product delivery decision page

Previously, the Allowable and Non-allowable self employment expense amounts were incorrectly displayed on the Food Assistance product delivery decision page. The values displayed were more than they should have been.

Now, these values have been corrected. They are no longer being multiplied and all Farm, Non Farm, Conservational, Feed and Purchase allowable and Non-allowable self employment expenses on the Income screen, Household and Member screen are displaying correct values.

The Employment Expense Decision Table has also been updated. The expense types Freight and Trucking, and Office Expenses have now Business or Total Amount for Farm Allowable expenses and the expense types Depreciation, Transportation Costs and Meals/Entertainment have now Business or Total Amount for Non Farm allowable expenses.

Technical details:

/EJBServer/components/ISFoodStamps/CREOLE
_Rule_Sets/FoodAssistanceRuleSet.xml

Class: FASelfEmploymentIncomeHelper

• totalAllowableEmploymentExpensesTimeline: Updated - Condition added to verify non farm expenses which was being counted as farm expenses.

Class: FAEmploymentExpenseTypesDecisionTable

• allowableFarmExpenseTypesTimeline: Updated - Freight and Trucking, Office Expenses, Dependent Care Assistance Programs, Interest on Loans for Business Property types have now Business or Total Amount for Farm allowable expenses. Accident and Health Plans has been updated to have 0 for Farm allowable expenses.
• allowableNonFarmExpenseTypesTimeline: Updated - Depreciation, Transportation Costs, Meals/Entertainment types have now Business or Total Amount for Non Farm allowable expenses. Accident and Health Plans has been updated to have 0 for Farm Non allowable expenses.

Class: FAExcludedEmploymentExpenseTypesDecisionTable

• excludedFarmExpenseTypesTimeline: Updated - Freight and Trucking, Office Expenses, Dependent Care Assistance Programs, Interest on Loans for Business Property have now 0 Amount for Farm excluded expenses. Conservation and Feed Purchases expenses also have now 0 amount as their value was incorrectly displayed on non allowable expenses if they were counted as allowable. Accident and Health Plans has been updated to have Business or Total Amount for Farm excluded expenses.
• excludedNonFarmExpenseTypesTimeline: Updated - Depreciation, Transportation Costs, Meals/Entertainment have now 0 Amount for Non Farm excluded expenses

Accident and Health Plans has been updated to have Business or Total Amount for Non Farm excluded expenses.

/EJBServer/components/ISFoodStamps/CREOLE
_Rule_Sets/FoodAssistance/ProductDisplay/
Income/Household/FAHouseholdIncomeCategory.xml

Class: FAHouseholdIncomeCategory

• allNonFarmFASelfEmploymentHelpersForHousehold: New attribute - Filters all Non Farm Self Employment Helpers records to avoid duplicated records.
• allFarmFASelfEmploymentHelpersForHousehold: New attribute - Filters all Farm Self Employment Helpers records to avoid duplicated records.
• partialAllowableSelfEmploymentExpensesDisplayList: New attribute - Filters all Farm Self Employment expenses to avoid duplicated records.
• partialExcludedSelfEmploymentExpensesDisplayList: New attribute - Filters all Farm Self Employment expenses to avoid duplicated records.
• allAllowableNonFarmSelfEmploymentExpensesDisplayList: Updated - Refers to the new attribute allNonFarmFASelfEmploymentHelpersForHousehold instead of allFASelfEmploymentHelpersForHousehold
• allAllowableFarmSelfEmploymentExpensesDisplayList: Updated - Refers to the new attribute allFarmFASelfEmploymentHelpersForHousehold instead of //allFASelfEmploymentHelpers ForHousehold
• allAllowableSelfEmploymentExpensesDisplayList: Updated - Refers to partialAllowableSelfEmploymentExpensesDisplayList for calculation of Farm and Non Farm allowable expenses.
• allExcludedNonFarmSelfEmploymentExpensesDisplayList: Updated - Refers to the new attribute allNonFarmFASelfEmploymentHelpersForHousehol instead of allFASelfEmploymentHelpersForHousehold.
• allExcludedFarmSelfEmploymentExpensesDisplayList: Updated - Refers to the new attribute allFarmFASelfEmploymentHelpersForHousehold instead of allFASelfEmploymentHelpersForHousehold.
• allExcludedSelfEmploymentExpensesDisplayList: Updated - Refers to partialAllowableSelfEmploymentExpensesDisplayList for calculation of Farm and Non Farm allowable expenses.

/EJBServer/components/ISFoodStamps/CREOLE
_Rule_Sets/FoodAssistance/ProductDisplay/
Income/Member/FAMemberSEExpensesDisplayCalculator.xml

Class: FAMemberSEExpensesDisplayCalculator

• selfEmploymentExpensesDisplayList: Updated attributes - Condition added to verify non farm expenses which was counted as farm expenses.

WorkItem:158613 - Launch an application for HCR and Income Support from the Prospect Person tab using the same action

Previously two separate actions were included on the Prospect Person tab actions menu for launching the Health Care Reform (HCR) Intake application script and the Income Support Intake application script. The New Application Form action launched the HCR Intake application script, and the New Application action launched the Income Support intake application script. Having two different action labels which launched the same business function was inconsistent and non intuitive.

In order to have a consistent user experience, the two actions have now been replaced with a single New Application action that launches the relevant intake application script depending on user role access. Some minor retraining will be required for caseworkers used to launching the Income Support intake application.

WorkItem:158807 - Remove New Application Case button from Prospect person menu

For the Health Care Reform (HCR) and Income Support user roles, the "Prospect Person" tab action menu has been updated to remove the "New Application Case" menu item because the application is created by launching the intake script from the "New Application" menu item.
The "New Application Case" and "New Referral" buttons have been disabled by default on the Applications page of the "Care and Protection" page level tab on the "Prospect Person" tab. The buttons can be enabled again at this level if needed by selecting the "Direct Creation" checkbox in the application case configuration settings in the administration console.

Having multiple actions that launched the same business function was inconsistent and nonintuitive.

The actions have been replaced with a single "New Application" action that launches the relevant intake application script depending on user role access. Some minor retraining will be required for caseworkers who are used to launching HCR and Income Support intake applications.

WorkItem:159065 - Income Support pending applications on Prospect Person home page

The ‘Pending Application Cases’ cluster on the prospect person home page has now been renamed to ‘Pending Applications’. Previously the list displayed only the prospect person's pending Health Care Reform (HCR) applications. Now the list displays the prospect person's pending HCR and Income Support applications together to give a fuller view of the prospect person's current pending applications, irrespective of whether the user's role is HCR or Income Support. Income Support applications that have a status of 'Submitted', 'Submit Failed' or 'Ready for Determination' are displayed in the Pending Applications list. Having a single business function that behaved differently across applications was inconsistent and non intuitive.

In order to have a consistent user experience, these functions now exhibit the same behaviour. Some minor retraining will be required for caseworkers used to working with HCR and Income Support applications.

WorkItem:161589 - Rename Income Support application tabs to be consistent with HCR

Updates have been implemented to improve consistency for users who navigate both the Income Support and the Health Care Reform (HCR) application tabs. The following updates have been applied to the Income Support application page level tabs to make the tabs more consistent with the HCR application:

• The tab display order has been updated.
• The Notes, Attachments, and Communications content from the Contact tab has been moved to the Administration tab.
• The List View and Calendar View content from the Interviews tab has been moved to the Administration tab.
• The Roles tab under the Administration tab has been renamed to Users.

Some minor retraining will be required for caseworkers used to working with HCR and Income Support applications.

WorkItem:163524 - Consistent search criteria on Application Search for HCR and Income Support

Occurrences of the following labels on the application search page have been renamed for consistency across Income Support and Health Care Reform (HCR).

• “Case Reference” has been changed to "Application Reference"
• “Application Reference” has been changed to ”Form Reference"
• “Application Received” has been changed to "Date"
• “Application Type” has been changed to “Type”
• “Application Date” has been changed to “Date”

Validation messages for search criteria have also been updated to reflect these changes and the word "case" has been removed. This change has been made to provide a more consistent user experience for caseworkers who are working on both HCR and Income Support applications. Some minor retraining will be required for caseworkers who are used to working with HCR and Income Support application searches.

WorkItem:163525 - Consistent search results on Application Search for HCR and Income Support

Both Health Care Reform (HCR) and Income Support application search pages have been updated to display more consistent search result labels.

On the application search page for HCR, the following labels have been updated:

• 'Case' has now been changed to 'Application'
• 'Application' has now been changed to 'Form'.

On the application search page for Income Support, the following labels have been updated:

• 'Reference' has now been changed to 'Application'
• 'Client' has been changed to 'Clients'
• 'Programs Requested' has been changed to 'Programs'
• 'Application Date' has been changed to 'Date'

This change has been made to provide a more consistent user experience for caseworkers who are working on both HCR and Income Support applications. Some minor retraining will be required for caseworkers who are used to working with HCR and Income Support application searches.

WorkItem:168339 - Application Type search criteria on Income Support Application Search should only display application types relevant to Income Support

The application type search criteria on the Income Support application search page was displaying irrelevant options for eligibility and intake workers. Having irrelevant options being displayed resulted in extra effort for the caseworker to find applications. In order to make the application search process more intuitive, the application type is now filtered by user role and only relevant application types are presented for application case searches. Items for the Income Support user role that have been filtered out are ‘Health Care' (Code ‘AT26001’) and ‘Unemployment Insurance' (Code 'AT19002’). Some minor retraining will be required for caseworkers who are used to working with Income Support application search.

WorkItem:169696 - Program search criteria on Income Support Application Search should only display programs relevant to Income Support

The program search criteria on the Income Support application search page was displaying irrelevant options for Income Support workers. Having irrelevant options being displayed resulted in extra effort for the caseworker to find applications. In order to make the application search process more intuitive, the programs are now filtered so that only relevant programs are presented for application case searches. The Insurance Affordability program type is no longer displayed as an option for these users. Some minor retraining will be required for caseworkers who are used to working with Income Support application search.

WorkItem:171486 - Registration Date for a Prospect Person is blank after running triage/screening process

Previously, after running the triage and screening process for a Prospect Person, their registration date was not displayed on the home page.

Now, this has been fixed and after running the triage and screening process for a Prospect Person, their registration date is displayed correctly.

WorkItem:175648 - Error displayed when opening application search page from shortcuts panel.

Previously an error occurred when the 'owuser' tried to open the application search page from the shortcuts panel. This was caused by an incorrect tab configuration that has now been corrected.

MEDICAL ASSISTANCE

WorkItem:101740 - Solution Alignment: Consistent Case Management between HCR and CGISS

As part of ongoing improvements to improve the consistency in the user interfaces of the application and case management between the Health Care Reform (HCR) and Income Support (IS) solutions, we have implemented some changes to the pages, actions and navigations of the HCR and IS application management. Previously the intake script for HCR and IS was launched from different action menu items from the Person tab actions menu. The intake script can now be launched from a single action menu item on the Person tab actions menu and will launch the relevant intake script based on the user access. A Pending Applications list on the Person home page will display both the person's in progress HCR and IS applications instead of previously, which displayed only the person’s HCR in progress applications. The labels and actions on the tab level and page level action menus and the context panels have now been made more consistent between the HCR and the IS applications. A multi-select search has been introduced to the IS application search page for the Type, Program and Status search criteria and also the labels in the search criteria and search results have now been made more consistent between the HCR and IS application search pages.

PO02247, WorkItem:103816 - SSN of non-applicant application filer not mapped to evidence

Previously, when a non applicant SSN was submitted in an application form, via the case management or the citizen portal, the corresponding evidence was not mapped in the application case.

Now, the SSN evidence is mapped when a SSN number is submitted in an application form for a non applicant.

The following changes have been made:

Added the mapping of attribute 'nonApplicantSSN' to 'alternateID' attribute on dynamic evidence entity 'SSNDetails' within evidence mapping configuration EvidenceMappingConfiguration_1_7 located in

/EJBServer/components/HCR/data/initial/clob/
EvidenceMappingConfiguration_1_7.xml

WorkItem:104195 - Slider indicators on the home page do not change when high contrast mode is on

Previously, the Slider indicators on the HCR home page did not change to High Contrast when High Contrast mode was selected.

Now, selecting High Contrast mode enables the High Contrast Slider indicators.

Files Changed
/Curam/components/HCROnline/HomePages/css/protohomepage-high-contrast.css

PO04618, WorkItem:104819 - Incorrect results on Medicaid PDC for a member returning to household

Previously, when a member left the household and then returned back after a period of time, they were not included in the eligibility determination. This resulted in incorrect decisions when a member left the household and was added to the case again by creating another Application Details evidence to indicate their return.

This issue is now resolved such that the eligibility determinations take in to account periods for which a member is part of the household.

WorkItem:104986 - When using JAWS, links with the same name on different sections are being read by the same link name

Previously, when using JAWS on the Citizen Portal Homepage, when the Frequently Asked Questions sections in the Slider were accessed, only "Frequently Asked Questions" was being read by JAWS. Now, "Frequently Asked Questions about <panel specific text>" is being read correctly.

PO05325, WorkItem:105085 - Eligibility is not determined when a previously removed member is added back to the household

Previously, when a household member was removed from a case and then returned back after a period of time, they were not included in the eligibility determination. When they left and then added back to the case again by creating another Application Details evidence to indicate their return, the resulting decisions were incorrect.

This issue is now resolved such that the eligibility determination takes in to account periods for which the member is part of the household.

PO03875, WorkItem:107061 - Focus on the blue dropdown button on the Motivation Results page is not clear

Previously, the focus on the blue drop down button on the Motivation Results page was not clear.

Now, this has been fixed and the contrast modes are now quite distinct from each other and are clear.

PO04165, PO03480, WorkItem:122862 - Unhandled Server Exception when transferring Income Evidence between two Insurance Affordability Integrated Cases

Previously, Income Evidence between two Insurance Affordability Integrated Cases could not be transferred if the evidence broker was disabled. This resulted in an Unhandled Server Exception error.

Now, Income Evidence can be transferred between two Insurance Affordability Integrated Cases.

The change affected the /EJBServer/components/HCR\CREOLE_Rule_Sets/
HealthCareVerRuleSet.xml, the dateOfBirth and dateOfDeath attributes in the HealthCareVerRuleSet on the Person attribute.

WorkItem:156708 - Application Case renamed to Application in Administration Application

In the administration application, the name and description fields configured for Health Care Reform (HCR) Application Cases within the Universal Access section have been updated to use the term ‘Application’ rather than ‘Application Case’. For example, ‘Account Transfer COC Application Case’ is now labelled as ‘Account Transfer COC Application’.

This change has been made to provide a more consistent user experience, bringing it in line with other areas of the application. Some minor retraining will be required for administrators used to configuring HCR Applications.

WorkItem:159216 - My Application Cases renamed to My Applications for HCR caseworkers

The page title and tab name of the ‘My Application Cases’ screen has been renamed to ‘My Applications’ for Health Care Reform (HCR) case workers. This is now in line with the labelling on the shortcuts panel as well as the Income Support application.
Having differing page titles and tab names for the same functionality was not user friendly for users using both HCR and Income Support.
In order to have a consistent user experience, the page titles and tab names are now the same. Some minor retraining will be required for HCR caseworkers used to working with applications.

WorkItem:161693 - Deprecate HCR Intake Reports

The HCR Intake Reports provided to help address the ability for agencies to manage failed applications are deprecated. Please refer to the Intake Reports section within the Income Support Guide for a description of the deprecated functionality.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

PO06397, WorkItem:163469 - Incorrect eligibility period displayed on the Graph View of the Eligibility Viewer if being viewed in a different time zone

Previously, the Graph View of the Eligibility Viewer would display the incorrect eligibility periods if being viewed in a different time zone.

This has now been fixed and the Graph View of the Eligibility Viewer will now consistently show the same dates across all time zones

WorkItem:163523 - Rename title on Application Case Search for HCR

The application case search page title in Health Care Reform (HCR) has been renamed from ‘Application Case Search’ to ‘Application Search’, bringing it in line with Income Support.

Having differing page titles for the same functionality was not user friendly for users who use both HCR and Income Support.
In order to have a consistent user experience, the page titles are now the same. Some minor retraining will be required for HCR caseworkers who are used to searching for applications.

WorkItem:165971 - New rule added to HCR Streamline Medicaid Summary Category display ruleset to reference those eligible for retroactive medicaid by ConcernRoleID

In the HCR Streamline Medicaid summary category display ruleset, members who are eligible for retroactive medicaid were referenced by name.

A new rule, retroStatusForParticipantRoleIDs, has been added to the Streamline Medicaid summary category display ruleset, StreamlineMedicaidSummaryCategory.xml, which references the members who are eligible for retroactive medicaid by ConcernRoleID.

WorkItem:166133 - A household member being re-added to a case are not included in eligibility determination.

Previously, when a household member was being re-added to a case, they were not included in the eligibility determination. This caused incorrect decisions when the member was added to the case again by creating another Application Details evidence to indicate their return.

Now, changes have been made to support the re-adding of a household member by creating a new HCRApplicant record. Previously, rules expected a household member to have a single HCRApplicant record. To support multiple HCRApplicant records all references to HCRApplicant within the Rules have been replaced by calls to one of two new calculators:

• HCRApplicantCalculator (for IC level attributes)
• HCRApplicantMemberCalculator (for member level attributes)

Technical details

EJBServer/components/HCR/CREOLE_RuleSets/
ARIncomeAdvisorRuleSet.xml

Class: ARIncomeAdviceItem

• applicantMemberCalculator: new
• applicantRecords: removed
• isApplicantRecordsAvailable: removed
• isIncomeVerificationRequired: modified

EJBServer/components/HCR/CREOLE_RuleSets/
ChipEligibilityAndEntitlementRuleSet.xml

CHIPProductCase

• applicantCalculator: new
• allCaseParticipantRoleRecords: modified
• change callout from getAdverseActionsForCHIPAndSM1 to use getAdverseActionsForCHIPAndSM2 to pass additional flag
  • isEligibleUnitsExtendedPeriod: modified
  • adverseActionEligibleUnits: modified

MemberEligibilityCalculator

• applicantMemberCalculator: new
• memberExistenceTimeline: modified
• change callout from getAdverseActionsForCHIPAndSM1 to use getAdverseActionsForCHIPAndSM2 to pass additional flag
  • isMemberEligibleTimeline: modified

EJBServer/components/HCR/CREOLE_RuleSets/
CoverageCategoryRuleSet.xml

MedicaidCoverageCategoryCalculator

• parentOrCareTakerRelativeRelationships: modified
• spouseParentCaretakerRelationships; modified

EJBServer/components/HCR/CREOLE_RuleSets/
ESIAdvisorRuleSet.xml

ESIAdviceItem

• applicantMemberCalculator: new
• applicantRecords: removed
• isApplicantRecordsAvailable: removed
• exemptionOrESICase: modified
• isESIVerificationRequired: modified

EJBServer/components/HCR/CREOLE_RuleSets/
ESIEligibilityAndEntitlementRuleSet.xml

ESIProductCase

• applicantCalculator: new
• allCaseParticipantRoleRecords: modified

ESIEligiblityCalculator

• esiApplicantDetails: removed
• enrolledMembersCoverageList: modified
• applicantCalculator: new
• primaryESIApplicantDetail: modified
• eligibleCPRUnitTimeline: modified

EnrolledMembersCoverage

• insuranceAffordabilityIntegratedCase: new
• applicantCalculator: new
• allEnrolledPlanRecords: removed
• applicantDetails: removed
• hcrApplicantMemberCalculators: new
• filteredApplicantDetails: removed
• applicantCoverageList: removed
• enrolledPlan: modified

EJBServer/components/HCR/CREOLE_RuleSets/
EmergencyMedicaidEligibilityAndEntitlementRuleSet.xml

EmergencyMedicaidProductCase

• applicantCalculator: new
• allCaseParticipantRoleRecords: modified
• change callout from getAdverseActionsForCHIPAndSM1 to use getAdverseActionsForCHIPAndSM2 to pass additional flag
• adverseActionEligibleUnits: modified
• isEligibleUnitsExtendedPeriod: modified

MemberEligibilityCalculator

• change callout from getAdverseActionsForCHIPAndSM1 to use getAdverseActionsForCHIPAndSM2 to pass additional flag
  • isEligibleTimeline: modified

EJBServer/components/HCR/CREOLE_RuleSets/
ExemptionEligibilityAndEntitlementRuleSet.xml

ExemptionEligiblityCalculator

• exemptionApplicantDetails: removed
• applicantAppDate: modified
• memberExemptions: modified

EJBServer/components/HCR/CREOLE_RuleSets /HCRApplicantVerDataRuleSet.xml

HCRApplicant

• livesWithExternalParent: modified (annotation name updated)

EJBServer/components/HCR/CREOLE_RuleSets/
HCRProgramGroupRuleSet.xml

HCRProgramGroup

• applicantCalculator: new
• programsListTimeline: modified
• esiApplicantDetails: removed

EJBServer/components/HCR/CREOLE_RuleSets/
HealthCareRuleSet.xml

MemberUnit

• applicantCalculator: new
• applicantIncomeTimeline: new
• isLivingExternallyTimeline: modified

IncomeCPRCalculator

• appliedForCoverageTimeline: modified

MemberCPRCalculator

• applicantMemberCalculator: new
• applicantRecord: removed
• appliedForCoverageTimeline:modified
• appliedForRetroCoverageTimeline: modified
• appliedThroughQuickShopTimeline: modified

RelationshipUtility

• relationshipTypeTimelineForApplicants: new

InsuranceAffordabilityIntegratedCase

• applicantCalculator: new
• applicantAppDate: modified
• allApplicantConcernRoleRecords: modified

AppliedMembers

• caseParticipantRoleID: removed
• applicantRecord: modified
• appliedForRetroCoverageTimeline: modified
• appliedForCoverageTimeline: modified
• onlineApplicantRecords: removed
• appliedThroughQuickShopTimeline: modified
• caseParticipantRoleRecord: new
• applicantCalculator: new
• applicantMemberCalculator: new

HCRApplicantCalculator

• New Calculator use in place of direct usage of HCRApplicant throughout rules. The calculator provides the ability to access HCRApplicant records for the IC across various criteria e.g. earliest HCRApplicant record on the IC. This calculator requires the insuranceAffordabilityIntegratedCase to be specified on creation.

HCRApplicantMemberCalculator

• New Calculator use in place of direct usage of HCRApplicant throughout rules. The calculator provides the ability to treat multiple application details (where a person leaves then re-joins the application) as one timeline as well as give access to the initial application start. This calculator requires the participantRoleID (concernRoleID) and the insuranceAffordabilityIntegratedCase to be specified on creation.

HCRApplicantMotivationFilter

• New Calculator providing the means to filter lists of HCRApplicant by motivation type, used by HCRApplicantCalculator and HCRApplicantMemberCalculator.

HCRApplicantTimelineUtil

• New Calculator providing the means to create HCRApplicant timelines from lists of HCRApplicant, used by HCRApplicantCalculator and HCRApplicantMemberCalculator.

EJBServer/components/HCR/CREOLE_RuleSets/
HealthCareVerRuleSet.xml

IncomeCPRCalculator

• appliedForCoverageTimeline: modified

MemberCPRCalculator

• applicantMemberCalculator: new (HCRApplicantMemberCalculator)
• applicantRecord: removed
• appliedForCoverageTimeline: modified
• appliedThroughQuickShopTimeline: modified

InsuranceAffordabilityIntegratedCase

• applicantCalculator: new
• applicantAppDate: modified
• allApplicantConcernRoleRecords: modified

AppliedMembers

• caseParticipantRoleID: removed
• applicantRecord: modified
• appliedForCoverageTimeline: modified
• onlineApplicantRecords: removed
• appliedThroughQuickShopTimeline: modified
• caseParticipantRoleRecord: new
• applicantCalculator: new
• applicantMemberCalculator: new

HCRApplicantCalculator

• New Calculator use in place of direct usage of HCRApplicant throughout rules. The calculator provides the ability to access HCRApplicant records for the IC across various criteria e.g. earliest HCRApplicant record on the IC. This calculator requires the insuranceAffordabilityIntegratedCase to be specified on creation.

HCRApplicantMemberCalculator

• New Calculator use in place of direct usage of HCRApplicant throughout rule s. The calculator provides the ability to treat multiple application details (where a person leaves then re-joins the application) as one timeline as well as give access to the initial application start. This calculator requires the participantRoleID (concernRoleID) and the insuranceAffordabilityIntegratedCase to be specified on creation.

HCRApplicantMotivationFilter

• New Calculator providing the means to filter lists of HCRApplicant by motivation type, used by HCRApplicantCalculator and HCRApplicantMemberCalculator.

HCRApplicantTimelineUtil

• New Calculator providing the means to create HCRApplicant timelines from lists of HCRApplicant, used by HCRApplicantCalculator and HCRApplicantMemberCalculator.

EJBServer/components/HCR/CREOLE_RuleSets/
HouseholdCompositionRuleSet.xml

TaxFilerFinancialUnit

• financialUnitTimeline: modified

TaxDependentFinancialUnit

• financialUnitTimeline: modified

TaxDependentFinancialUnit

• financialUnitTimeline: modified

TaxExemptedIndividualFinancialUnit

• financialUnitTimeline: modified

TaxHouseholdCompositionCalculator

• taxHouseholdTimeline: modified

EJBServer/components/HCR/CREOLE_RuleSets/
HouseholdCompositionVerRuleSet.xml

TaxFilerFinancialUnit

• financialUnitTimeline: modified

TaxDependentFinancialUnit

• financialUnitTimeline: modified

TaxExemptedIndividualFinancialUnit

• financialUnitTimeline: modified

TaxHouseholdCompositionCalculator

• taxHouseholdTimeline: modified

EJBServer/components/HCR/CREOLE_RuleSets/
IncarcerationAdvisorRuleSet.xml

IncarcerationAdviceItem

• applicantMemberCalculator: new
• applicantRecords: removed
• isApplicantRecordsAvailable: removed
• isIncarcerationDetailsAvailable: new
• isIncarcerationVerificationRequired: modified

EJBServer/components/HCR/CREOLE_RuleSets/
IncomeAdvisorRuleSet.xml

IncomeAdviceContext

• applicantMemberCalculator: new
• applicantRecords: removed
• isApplicantRecordsAvailable: removed
• isIncomeDetailsAvailable: new
• isIncomeVerificationRequired: modified

EJBServer/components/HCR/CREOLE_RuleSets/
InsuranceAssistanceEligibilityAndEntitlementRuleSet.xml

InsuranceAssistanceProductCase

• applicantCalculator: new
• allCaseParticipantRoleRecords: modified

TaxHouseholdEligibilityCalculator

• isEligibleTimeline: modified
• adverseActionMemebersNotPassingCascadingEligibility: modified
• adverseFilteredTaxHouseholdTimeline: modified

EJBServer/components/HCR/CREOLE_RuleSets/
NonFinancialRuleSet.xml

ResidencyCalculator

• applicantCalculator: new
• allCaseParticipantRoleRecords: modified
• applicantCalculator: new
• allCaseParticipantRoleRecords: modified

EJBServer/components/HCR/CREOLE_RuleSets/
ResidencyVerificationByAddressRuleSet.xml

ResidencyVerificationByAddressDeterminator

• applicantMemberCalculator: new
• isApplicant: modified
• hcrApplicant: removed
• insuranceAffordabilityIntegratedCase: new

EJBServer/components/HCR/CREOLE_RuleSets/
StateBasicPlanEligibilityAndEntitlementRuleSet.xml

StateBasicPlanProductCase

• applicantCalculator: new (HCRApplicantCalculator)
• allCaseParticipantRoleRecords: modified (uses applicantCalculator.allParticipantRoleRecords)

TaxHouseholdEligibilityCalculator

• isEligibleTimeline: modified
• adverseActionMemebersNotPassingCascadingEligibility: modified
• adverseFilteredTaxHouseholdTimeline: modified
• adverseActionEligibleUnits: modified

EJBServer/components/HCR/CREOLE_RuleSets/
StreamlineMedicaidEligibilityAndEntitlementRuleSet.xml

StreamlineMedicaidProductCase

• applicantCalculator: new
• allCaseParticipantRoleRecords: modified ;

MemberEligibilityCalculator

• applicantMemberCalculator: new
• memberExistenceTimeline: modified
• applicant: modified
• applicantAppDate: modified
• change callout from getAdverseActionsWithNewBornProcessing to use getAdverseActionsWithNewBornProcessin1 to pass additional flag
• isMemberEligibleTimeline: modified
• isEligibleForRetroTimelineAdjusted: modified

FinancialsCPRCalculator

• replace call to getExtendedSMCategories to getExtendedSMCategories1 to take member applicant timeline in place of single application date
  • extendedEligibleCoverageCategory: modified

EJBServer/components/HCR/CREOLE_RuleSets/
UQHPEligibilityAndEntitlementRuleSet.xml

UnassistedQualifiedHealthPlanProductCase

• applicantCalculator: new
• allCaseParticipantRoleRecords: modified
• allMemberUnitsTimeline: modified
• onlineApplicantDetails: removed
• change callout from getAdverseActionsForAPTCPrograms to use getAdverseActionsForAPTCPrograms1 to pass additional flag
• adverseActionEligibleUnits: modified

MemberEligibilityCalculator

• change callout from getAdverseActionsForAPTCPrograms to use getAdverseActionsForAPTCPrograms1 to pass additional flag
• isEligibleTimeline: modified

MotivationHelper

• insuranceAffordabilityIntegratedCase: new
• applicantMemberCalculator: new
• motivationType: modified
• onlineApplicantDetails: removed

EJBServer/components/HCR/CREOLE_RuleSets/
InsuranceAssistance/ProductDisplay/
InsuranceAssistanceSummaryCategory.xml

InsuranceAssistanceSummaryCategory

• membersPassingCascadingEligibility: modified

EJBServer/components/HCR/CREOLE_RuleSets/
StateBasicPlan/ProductDisplay/StateBasicPlan
SummaryCategory.xml

StateBasicPlanSummaryCategory

• membersPassingCascadingEligibility: modified (use memberCPRCalculator.applicantMember
  Calculator.memberApplicantRecordsTimeline in place of in-line logic)

EJBServer/components/HCR/CREOLE_RuleSets/
StreamlineMedicaid/ProductDisplay/
StreamlineMedicaidIncomeCategory.xml

StreamlineMedicaidIncomeCategory

• incomeCountedFor: modified
• participantRoleIDList: modified
• memberMagiIncome: modified

Class: curam.hcrcase.creole.statics.impl.Statics

• Deprecated getAdverseActionsForCHIPAndSM1 and added getAdverseActionsForCHIPAndSM2 New method takes additional Boolean flag indicating whether timeline being evaluated represents program eligibility for the concernRoleID passed. This affects whether the timeline is used in subsequent calls for program alignment.
• Deprecated getAdverseActionsWithNewbornProcessing and added getAdverseActionsWithNewbornProcessing2 New method takes additional Boolean flag indicating whether timeline being evaluated represents program eligibility for the concernRoleID passed. This affects whether the timeline is used in subsequent calls for program alignment.
• Deprecated getAdverseForAPTCPrograms and added getAdverseForAPTCProgram1 New method takes additional Boolean flag indicating whether timeline being evaluated represents program eligibility for the concernRoleID passed. This affects whether the timeline is used in subsequent calls for program alignment.
• combineIncomeAndApplicant - This is a new method used to combine the applicant timeline with the income start date.

PO06443, WorkItem:166769 - SSN entered for non-applicants being displayed on the in Summary tab of app, internal script and change of circumstance script

Previously, when a SSN was entered for Non-Applicants, it was not shown on the summary pages of Case Management, Citizen Portal and Change of Circumstance. SSN was only displayed for the Person.

Now, this has been fixed and a new attribute 'displaySSN' has been added to the Person. It gets populated with either the SSN value for the Person or 'nonApplicantSSN' attribute value for the Non-Applicant.

A new custom function has been created to handle the population of the new attribute 'displaySSN' containing either the 'SSN' attribute value for the Person or the 'nonApplicantSSN' attribute value.

The following IEG script files have been modified to reflect the change:

• HealthCareCW.xml
• HealthCarePortalScript.xml
• HealthCarePortalSummarySubScript.xml
• ChangeOfCircumstance.xml
• ChangeOfCircumstanceSummarySubScript.xml

PO06447, WorkItem:167049 - Update Number of Unborn message and enforce validation parameters

Previously, in the Citizen Portal and Change Of Circumstance script, when the number of unborn entered was 0 or over 10, a warning message was displayed that stated "The number of Unborn must be between 0 and 10". Further to this, there was no validation mechanism above 10 which the message implies.

Now, the warning message states that "The number of Unborn must be between 1 and 10" and enforces both limits. It is now not possible for the user to enter either 0 or over 10.

WorkItem:167479 - SSN not being displayed in the Citizen portal under 'My Information' when a new applicant is added through the Guided Wizard

Previously, when a new applicant was added through Guided Wizard, the corresponding SSN was not displayed on the 'My Information' screen of Citizen Portal.

Now, when a new member is added through the Guided Wizard, the default AlternateID Type 'Social Security Number' is associated with the SSN evidence and this will allow for the record to be shown on the 'My Information' screen of Citizen Portal.

PO06468, WorkItem:168204 - Medicaid enrollment status on date of birth for newborn's mother is not asked when newborn is the primary applicant

Previously, a Medicaid enrollment status question was not asked when a newborn was the primary applicant.

Now, a condition has been added to ask the question "Was <child's name>'s mother enrolled on Medicaid that covers labor and delivery(including Emergency Medicaid) on his/her date of birth?" on all relevant pages. This is presented for an applicant child under one years of age.

The following files have now been changed:

Citizen Portal

• HealthCarePortalScript.xml
• HealthCarePortalAboutYouSubScript.xml
• ChangeOfCircumstance.xml

Internal Application

• HealthCareCW.xml
• HealthCareCWSection_AboutYou.xml
• HealthCareCWSection_Household.xml

PO06490, WorkItem:169398 - Eligibility Viewer display is incorrect for overlapping program eligibility

Previously, the Eligibility Viewer did not display the correct eligibility when the participant was eligible for more than one program for an overlapping period. This issue has now been resolved.

WorkItem:171828 - When applying on the behalf of someone else in the Citizen Portal, pregnancy information is not being validated if the due date is in the future

Previously, within the citizen portal, if the user selected the option 'I am applying as an individual acting responsibly on behalf of someone else', the pregnancy information could not be validated on the due date selected, if the date was in the future.

Now, this issue has been solved and the validation is working properly when the due date entered is a date in the future.

PO06571, WorkItem:172070 - Update to Income Support guide for Annual Renewal

The Merative SPM Income Support for Medical Assistance (Health Care Reform) business overview has been updated in the Knowledge Center. The section

Annual Renewals for Medicaid and CHIP has been updated. This section now describes when the product delivery is created and how the certification period is created.

PO06559, WorkItem:172580 - Multiple updates to the Absence evidence making client losing eligibility for the past period although intent to return home set to true

Previously, when multiple updates were being made on Absence Evidence, it was making the client losing eligibility for the past period although intent to return home was set to true.

Now, this has been fixed as part of a defect in Program Group Logic, where it was possible for reassessment to run for incorrect periods. Reassessment will now only run over certification periods.

PO06567, WorkItem:172874 - Extended eligibility in the past for Streamline is getting lost when there is multiple Income CoC

As part of on-going development work, a defect in Program Group Logic was found where extended eligibility in the past for Streamline was lost when there was multiple Income CoC. This has now been corrected so that extended eligibility will not be lost.

PO06567, WorkItem:174368 - Reassessment running for incorrect periods while performing a Change of Circumstances for Income

Previously, it was possible for reassessment to be run for incorrect periods while performing a Change of Circumstances for Income.
This has now been corrected so that reassessment will only run over certification periods. The calculation of the Adverse period has also been amended so that it is now consistent on subsequent reassessments.

Child Welfare

WorkItem:116559 - High Contrast: The AA and AAA conformants fail on Narrative Text Renderer

Previously, the icons for save, cut, copy, paste, and text formatting in the narrative rich text editor of the smart panel, were not meeting the color contrast ratio standard. This was happening due to the use of non accessible images as icons.

Now, this has been resolved by using new high contrast images as icons.

WorkItem:116561 - New Allegation Renderer: Zooming Issues

Previously, the date text and allegation type fields on the the screen to create new allegation for the intake were not displayed properly when they were viewed with a zoom level of 200%. This has been resolved now.

WorkItem:116568 - Dispose Allegations Page: Zooming Issues

Previously, the users were not able to view "Dispose Allegations" page completely at a zoom level of 200%.
This has been resolved now by adjusting various visual elements on the page.

Cúram Workers Compensation

WorkItem:117558 - High Contrast: The AA and AAA conformants fail on the Employer Context panel renderer.

Previously, the elements in the Employer context panel like "Common Events" links and "reference number" were not in right contrast ratio and were not displayed as expected in high contrast mode. This issue is now resolved by changing the color of above mentioned elements to the right high contrast ratio.

WorkItem:117560 - High Contrast: The AA and AAA conformants fail on the Prospect Employer Context panel renderer.

In the prospect person context panel, the following elements "Common Events" links , "reference number" and "Prospect " were not in right contrast ratio and were not displayed as expected in high contrast mode. This issue is now resolved by changing the color of above mentioned elements to the right high contrast ratio.

WorkItem:117563 - High Contrast: The AA and AAA conformants fail on the Common Event Context panel renderer.

The link in Common Event Home page like "Employers", "Workers", "Merged Events" and "Common Event Name" text were not in right contrast ratio and were not displayed as expected in high contrast mode. This issue is now resolved by changing the color of above mentioned elements to the right high contrast ratio.

Notes on Deprecation

This section describes artefacts that have been deprecated in this release and the functionality that supersedes them.

Enhancements or defect fixes may require the contract of a development artefact to be changed. In this context the contract of an artefact is its API or signature (e.g. name, parameters, return values, etc) in conjunction with its documented statement of functionality (e.g. JavaDoc).

In these cases, deprecation is used to reduce the impact of the change on custom applications. The original artefact is preserved and marked as 'deprecated' to indicate that it has been superseded by other functionality (often a new artefact). Infrastructure is provided to assist in identifying custom dependencies on these deprecated artefacts. This can affect customizations in a number of different ways and has some implications for customer support. For more information about deprecation, please see the 'Deprecation' chapter in the Merative SPM Server Developer's Guide. This chapter describes what deprecation is, how it can affect custom code, what it means for support and the build infrastructure that helps pinpoint custom artefact dependencies on deprecated artefacts.

You can find out whether or not your code is affected by any of the following deprecations (and precisely where) by running the deprecationreport build target. If that build produces deprecation warnings, then you are affected by one or more of the deprecated artefacts itemized below. See the 'Deprecation' chapter in the Merative SPM Server Developer's Guide for further information on using this build target and analyzing its output.

Cúram Enterprise Framework

WorkItem:159270 - Deprecate the Spell Checker utility

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

The environment variable curam.spellcheck.enable has been marked as deprecated. To enable the feature, set the curam.spellcheck.enable property to true.

Itemised List of Changes:

Below is a list of the artifact(s) that have been marked as 'deprecated' as part of the deprecation of this feature.

../CEFWidgets/properties/Environment.xml

• Inside the section 'Infrastructure - Locale parameters', the environment variable curam.spellcheck.enable is marked as deprecated, and its default value is now set to false.

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

Technical Services

BUSINESS INTELLIGENCE

WorkItem:161245 - Deprecate Oracle Warehouse Builder (OWB) and DB2 ETLs

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is the itemized list of deprecation changes for all the ETLs and metada used by OracleWarehouse Builder(OWB). Any dependencies on these deprecated ETLs \ artifacts should be broken in preparation for the physical removal of the feature in a future release.

The following configuration files have been deprecated:

• ../components/ChildServices/BIAConfiguration.xml
• ../components/core/BIAConfiguration.xml
• ../components/IncomeSupport/BIAConfiguration.xml

All Oracle ETLs and metadata data files in the following folder and its subfolders have been deprecated:

• ../components/ChildServices/etl/oracle
• ../components/core/etl/oracle
• ../components/IncomeSupport/etl/oracle

All DB2 ETLs and metadata data files in the following folder and its subfolders have been deprecated:

• ../components/ChildServices/etl/CuramBIWarehouse
• ../components/core/etl/CuramBIWarehouse
• ../components/IncomeSupport/etl/CuramBIWarehouse

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

GENERIC SEARCH SERVER

WorkItem:159363 - Deprecate the Generic Search Server (GSS) feature

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

The Generic Search Server (GSS) infrastructure is used out-of-the-box in the PersonMatch default implementation. Customers can now provide their own implementation of the PersonMatch interface as a means of moving away from the deprecated (GSS) infrastructure. For additional information about implementing the PersonMatch interface, please refer to the javadoc associated with the interface.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

..EJBServer/components/core/properties/Environment.xml

• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneOnlineSynchronizationEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedPersonSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedEmployerSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedProductProviderSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.externalUpdateEventsEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedCaseSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedCaseSearchTypes is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedPaymentReceivedSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedPaymentIssuedSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedLiabilityIssuedSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedInvestigationSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedExternalPartySearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedInformationProviderSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedServiceSupplierSearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam.lucene.luceneEnhancedUtilitySearchEnabled is marked as deprecated.
• Inside the section 'Application - Lucene enhanced search parameter', the environment variable curam .lucene.luceneEnhancedAllParticipantSearchEnabled is marked as deprecated.

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

Integrated Case Management

WorkItem:159366 - Deprecate legacy employment contribution entities

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

../EJBServer/components/core/model/Packages/
Contributions Manager/Insurance Return
Consolidation Processes_cat.efx

• Deprecated the process class MaintainConsolidationDetails

../EJBServer/components/core/model/Packages/
Contributions Manager/Insurance Return Header
Processes_cat.efx

• Deprecated the process class EmployerInsuranceRetHeader
• Deprecated the process class EmployerInsuranceRetHeaderAssistant

../EJBServer/components/core/model/Packages/
Contributions Manager/Insurance Return Line
Item Processing Assistant_cat.efx

• Deprecated the process class MaintainInsuranceLineItemAssistant

../EJBServer/components/core/model/Packages/
Contributions Manager/Insurance Return Line Item Processing_cat.efx

• Deprecated the process class MaintainInsuranceLineItem

../EJBServer/components/core/model/Packages/
Contributions Manager/Insurance Return Period
Control Processing_cat.efx

• Deprecated the process class MaintainInsurancePeriodControl

../EJBServer/components/core/model/Packages/
Contributions/Business Processes_cat.efx

• Deprecated the process class ElectronicEmployerReturn
• Deprecated the process class ConsolidationProcess

../EJBServer/components/core/model/Packages/
PresentationLayer/Contribution/Contribution_cat
.efx

• Deprecated the facade class Contribution.java

All of the classes below have been deprecated in their entirety:

• ../EJBServer/components/core/source/
  curam/core/facade/impl/Contribution.java
• ../EJBServer/components/core/source/
  curam/core/impl/ConsolidationProcess.java
• ../EJBServer/components/core/source/
  curam/core/impl/ElectronicEmployerReturn.java
• ../EJBServer/components/core/source/
  curam/core/impl/EmployerInsuranceRetHeader.java
• ../EJBServer/components/core/source/
  curam/core/impl/EmployerInsuranceRetHeaderAssistant.java
• ../EJBServer/components/core/source/
  curam/core/impl/MaintainConsolidationDetails.java
• ../EJBServer/components/core/source/
  curam/core/impl/MaintainInsuranceLineItem.java
• ../EJBServer/components/core/source/
  curam/core/impl/MaintainInsuranceLineItemAssistant.java
• ../EJBServer/components/core/source/
  curam/core/impl/MaintainInsurancePeriodControl.java
• ../EJBServer/components/core/source/
  curam/core/impl/ProcessConsolidation.java

The following contributions entities are now deprecated:

• InsuranceConsolidation
• InsurConsolidationDetails
• InsurancePeriodControl
• InsuranceReturnHeader
• InsuranceReturnHeaderDetail
• InsuranceReturnLineItem
• InsuranceRetLineItemDetail

The application configuration files below have been updated to remove any contributions related links, and any associated properties have been marked as deprecated :

• ../EJBServer/components/PFMAppViews/
  tab/Admin/InsuranceReturnPeriods.nav
• ../EJBServer/components/PFMAppViews/
  tab/Admin/InsuranceReturnPeriods.tab
• ../EJBServer/components/PFMAppViews/
  tab/Admin/InsuranceReturnPeriodsMenu.mnu
• ../EJBServer/components/PFMAppViews/
  tab/AdminAppView/ADMINAPPSection.sec
• ../EJBServer/components/PFMAppViews/
  tab/AdminAppView/ADMINAPPSectionShortcuts.ssp
• ../EJBServer/components/PFMAppViews/
  tab/Financial/FinancialAdministrat ion.nav
• ../EJBServer/components/PFMAppViews
  /tab/Financial/FinancialAdministrationMenu.mnu
• ../EJBServer/components/PFMAppViews/
  tab/FinancialAppView/FINAPPSection.sec

All of the UIM / VIM files below and their associated properties have been deprecated:

• ../webclient/components/core/Employer/
  InsuranceReturn/Employer_createInsurance
  Return.uim
• ../webclient/components/core/Employer/
  InsuranceReturn/Employer_listInsurance
  Return.uim
• ../webclient/components/core/Employer/
  InsuranceReturn/Employer_modifyInsurance
  ReturnView.vim
• ../webclient/components/core/Employer/
  InsuranceReturn/Employer_viewInsurance
  Return.uim
• ../webclient/components/core/Employer/
  InsuranceReturn/Employer_viewInsurance
  ReturnFurtherDetails.uim
• ../webclient/components/core/Employer/
  InsuranceReturn/Employer_viewInsurance
  ReturnHistory.uim
• ../webclient/components/core/Employer/
  InsuranceReturn/Employer_viewInsurance
  ReturnHistoryDetails.uim
• ../webclient/components/core/Employer/
  Insurance Return/LineItems/Employer_
  cancelInsuranceReturnLineItem.uim
• ../webclient/components/core/Employer/
  Insurance Return/LineItems/Employer_
  createInsuranceReturnLineItem.uim
• ../webclient/components/core/Employer/
  Insurance Return/LineItems/Employer_
  modifyInsuranceReturnLineItem.uim
• ../webclient/components/core/Employer/
  Insurance Return/LineItems/Employer_
  viewInsuranceReturnLineItemView.vim
• ../webclient/components/core/Organization
  /Insurance ReturnPeriod/Organization_
  cancelInsuranceReturnPeriod.uim
• ../webclient/components/core/Organization
  /Insurance Return Period/Organization_
  createInsuranceReturnPeriod.uim
• ../webclient/components/core/Organization
  /Insurance ReturnPeriod/Organization_
  listInsuranceReturnPeriod.uim
• ../webclient/components/core/Organization
  /Insurance ReturnPeriod/Organization_
  modifyInsuranceReturnPeriod.uim
• ../webclient/components/core/Person/Insurance/
  Consolidations/Person_listConsolidation
  LineItem.uim
• ../webclient/components/core/Person/
  Insurance/Consolidations/Person_listInsurance
  Consolidation.uim
• ../webclient/components/core/Person/
  Insurance/Consolidations/Person_listInsurance
  ConsolidationForDuplicate.uim
• ../webclient/components/core/Person/Insurance/
  Consolidations/Person_viewInsurance
  Consolidation.uim
• ../webclient/components/core/Person/
  Insurance/LineItems/Person_listInsurance
  LineItem.uim
• ../webclient/components/core/Person/Insurance/
  Line Items/Person_listInsuranceLineItem
  ForDuplicate.uim
• ../webclient/components/core/Person/Insurance/
  LineItems/Person_listInsuranceLineItem
  ForEmployment.uim
• ../webclient/components/core/Person/Insurance/
  LineItems/Person_listInsuranceLineItem
  History.uim

The following UIM pages have been updated to remove the mapping of the contributionsInd flag for liability product, and the associated properties marked as deprecated:

• ..webclient/components/core/Product/Liability/
  Product_createLiability.uim
• ..webclient/components/core/Product/Liability/
  Product_createLiability1.uim
• ..webclient/components/core/Product/Liability/
  Product_createLiabilityWizard.uim
• ..webclient/components/core/Product/Liability/
  Product_liabilityHome.uim
• ..webclient/components/core/Product/Liability/
  Product_liabilityHome1.uim
• ..webclient/components/core/Product/Liability/
  Product_modifyLiabilityView.vim
• ..webclient/components/core/Product/Liability/
  Product_modifyLiabilityView1.vim
• ..webclient/components/core/Product/Liability/
  Product_summaryForLiabilityWizard.uim
• ..webclient/components/core/Product/Wizard/
  Wizard_liabilityProduct.uim
• ..webclient/components/core/Product/Wizard/
  Wizard_liabilitySummary.uim

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

ELIGIBILITY & ENTITLEMENT

WorkItem:159369 - Deprecate CER Key Decision Factors (graphical and list view)

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

The following efx file contains deprecated operations:

..EJBServer/components/core/model/Packages/
Presentation Layer/Product Delivery/
CaseDetermination_cat.efx

• Deprecated the process listKeyData()
• Deprecated the process viewGraphicalKeyEvents()
• Deprecated the process getKeyEventData()

The following class contains deprecated methods:

..EJBServer/components/core/source/curam/core
/facade/infrastructure/assessment/impl/
CaseDetermination.java

• Deprecated the process listKeyData()
• Deprecated the process viewGraphicalKeyEvents()
• Deprecated the process getKeyEventData()

The following UIM / VIM pages and their associated properties have been marked as deprecated:

• ..webclient/components/core/Product
  Delivery/CaseDetermination/TimeLine/ProductDelivery_
  listDeterminationTimeLine.uim
• ..webclient/components/core/Product
  Delivery/CaseDetermination/TimeLine/ProductDelivery_
  listDeterminationTimeLineView.vim
• ..webclient/components/core/Product
  Delivery/CaseDetermination/ProductDelivery_
  determinationFlexView.uim
• ..webclient/components/core/Product
  Delivery/CaseDetermination/ProductDelivery_
  getKeyEventData.uim

The following VIM pages has been updated to remove the display of key decision events:

• ..webclient/components/core/
  ProductDelivery/CaseDetermination/
  ProductDelivery_listAllCreoleDecisionsView.vim
• ..webclient/components/HCR/Product Delivery/
  CaseDetermination/ProductDelivery_
  listAllCreoleDecisionsView.vim

In the Administration Application, the 'Key Decision Factors Rule Set' and 'Key Decision Factors Rule' fields of a product period have been removed from the 'Product Periods' section of the CREOLE Product Rule Sets configuration pages. This has been done for the Published, In Edit and History sections on the Rule Sets tab. The following client pages have been modified accordingly to remove the fields above, and the associated properties have been marked as deprecated:

• ..webclient/components/core/CREOLE
  ProductAdmin/History/CREOLEProductAdmin_
  listHistoryProductPeriodDispCat1.uim
• ..webclient/components/core/CREOLE
  ProductAdmin/InEdit/CREOLEProduct
  Admin_listInEditProductPeriodDispCat1.uim
• ..webclient/components/core/CREOLE
  ProductAdmin/Published/CREOLEProduct
  Admin_listPublishedProductPeriodDispCat1.uim
• ..webclient/components/core/CREOLE
  ProductAdmin/InEdit/CREOLEProductAdmin_
  createSandboxProductPeriod.uim
• ..webclient/components/core/CREOLE
  ProductAdmin/InEdit/CREOLEProductAdmin_
  modifyProductPeriod.uim

The following infrastructural CREOLE Rule Sets have been deprecated:

• ..EJBServer/components/core/CREOLE_
  Rule_Sets/ProductKeyDataRuleSet.xml
• ..EJBServer/components/core/CREOLE_
  Rule_Sets/DefaultProductKeyDataRuleSet.xml

Updated the following DMX content:

In the Administration Application, the list of CER rule-set names displayed are taken from the text translation for that rule-set, if a text translation exists. If one does not exist, the rule-set name is used (i.e. the key for the rule-set on the Creole RuleSet entity). To highlight the fact that the key decision factor infrastructure rule-sets are deprecated via the rule-set listing, it was necessary to append the word 'Deprecated' onto the name of the rule-set. As the key decision factor rule-set names were used, a text translation for each rule-set was added to faci litate the appendage of the word 'Deprecated' to the rule-set name. These changes are contained with the following DMX files:

• ..EJBServer/components/core/data/initial/
  CREOLERULESETCATEGORY.dmx
• ..EJBServer/components/core/data/initial/
  CREOLERULESET.dmx
• ..EJBServer/components/core/data/initial/
  LOCALIZABLETEXT.dmx
• ..EJBServer/components/core/data/initial/
  TEXTTRANSLATION.dmx

The following element inside the ..webclient/components/core/
curam-config.xml configuration file has been deprecated:

<POPUP_PAGE PAGE_ID="CREOLEProductAdmin_
selectKeyDecisionFactorRuleClass">
<FILE_DOWNLOAD CLASS="curam.interfaces.
CaseDeterminationPkg.CaseDetermination_
getKeyEventData_TH" PAGE_ID="ProductDelivery_
getKeyEventData">
/>

As part of the deprecation of Key Decision Factors, it was necessary to suppress the 'Eligibility and Entitlement: Key Decision Factors' CREOLE Rule Set Category anywhere it was exposed in the user interface. This was in the following two locations:

• The Category drop down on the Current tab of the Cúram Express Rule Sets page
• The Category check-boxes on the New Rule Set modal dialog.

As CREOLE Rule Set Categories are stored on the
CREOLERULESETCATEGORY database table, it was necessary to introduce new functionality to enable or disable a CREOLE rule set category. This meant that the 'Eligibility and Entitlement: Key Decision Factors' CREOLE Rule Set Category could be disabled out-of-the-box:

• If a CREOLE Rule Set Category is enabled it will be listed on the pages mentioned above.
• If a CREOLE Rule Set Category is disabled it will not be listed on the pages mentioned above.

Three new operations were added to provide new business processes visible to the client.

..EJBServer/components/core/model/Packages/Presentation Layer/CREOLERuleSetAdmin.efx

• Added the process enableCREOLERuleSetCategory()
• Added the process disableCREOLERuleSetCategory()
• Added the process listAllCategories()

The facade layer struct CREOLERuleSetCategory was updated with the following attributes:

• filteredInd
• versionNo

The following java file has been updated with new operations:

..EJBServer/components/core/source/curam/
core/facade/infrastructure/creole/rulesetadmin/
impl/CREOLERuleSetAdmin.java

• Added the process enableCREOLERuleSetCategory()
• Added the process disableCREOLERuleSetCategory()
• Added the process listAllCategories()

The following UIM page has been updated to include a row level menu option for enabling / disabling a CREOLE Rule Set Category:

• ..webclient/components/core/CreoleAdmin/
  Category/Admin/CreoleRuleSetCategory_list.uim

New UIM pages have been adding for enabling and disabling CREOLE Rule Set Categories :

• ..webclient/components/core/CreoleAdmin/
  Category/Admin/CreoleRuleSetCategory_setFiltered.uim
• ..webclient/components/core/CreoleAdmin/
  Category/Admin/CreoleRuleSetCategory_unsetFiltered.uim

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

EVIDENCE MANAGEMENT

WorkItem:159367 - Deprecate the Evidence Flow feature

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

..EJBServer/components/core/model/Packages/Reference Model/Service Layer/Temporal Evidence/EvidenceController/EvidenceController_cat.efx

• Deprecated the process getEvidenceFlowDetails()

..EJBServer/components/core/model/Packages/Presentation Layer/Evidence_cat.efx

• Deprecated the process getEvidenceFlowDetails()

..EJBServer/components/EvidenceFlow/model/
Packages/Facade/Facade_cat.efx

• Deprecated the EvidenceFlow facade class

..EJBServer/components/core/source/curam/core
/facade/infrastructure/impl/Evidence.java

• Deprecated the process getEvidenceFlowDetails()

..EJBServer/components/core/source/curam/core
/infrastructure/implEvidenceController.java

• Deprecated the process getEvidenceFlowDetails()

The following entities are now deprecated:

• CaseEvidenceStack
• CaesEvidenceStackData
• EvidenceFlowReload

The following java classes have been deprecated:

• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  AdvisorRecalculationRequiredHandler.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/stack
  /impl/CaseEvidenceStack.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/stack
  /impl/CaseEvidenceStackConst.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/stack
  /impl/CaseEvidenceStackDAO.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/stack
  /impl/CaseEvidenceStackDAOImpl.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/stack
  /impl/CaseEvidenceStackData.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/stack
  /impl/CaseEvidenceStackDataDAO.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/stack
  /impl/CaseEvidenceStackDataDAOImpl.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/stack
  /impl/CaseEvidenceStackDataImpl.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/stack
  /impl/CaseEvidenceStackImpl.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/facade
  /impl/EvidenceFlow.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowAdviceItemCaseLinkEventListener.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowAdviceItemEventListener.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowReload.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowReloadDAO.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowReloadDAOImpl.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowReloadImpl.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowTransactionCallbackHandler.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowUtility.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowVerificationHandler.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowXMLBuilder.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowXMLBuilde rImpl.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  EvidenceFlowXMLConst.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  JDOMCaseEvidenceStack.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  JDOMEvidenceFlowXMLBuilder.java
• ..EJBServer/components/EvidenceFlow/
  source/curam/evidence/evidenceflow/impl/
  Module.java

The following client pages and their associated properties have been deprecated:

• ..webclient/components/core/Integrated
  Case/Default/DefaultIntegratedCase/
  Evidence/DefaultIC_flow.uim
• ..webclient/components/core/Integrated
  Case/Default/DefaultProductDelivery/
  ProductEvidence/DefaultICProduct_flow.uim
• ..webclient/components/core/Evidence
  Infrastructure/Evidence_flow.uim
• ..webclient/components/core/Evidence
  Infrastructure/Evidence_flowLinks.vim
• ..webclient/components/core/Evidence
  Infrastructure/Evidence_flowView.vim
• ..webclient/components/Intake/Application
  /ApplicationEvidence/ApplicationEvidence
  _flow.uim
• ..webclient/components/Intake/Application
  /ApplicationEvidence/ApplicationEvidence
  _flowLinks.vim
• ..webclient/components/Intake/Application
  /ApplicationEvidence/ApplicationEvidence
  _flowView.vim
• ..webclient/components/CPM/ServiceDelivery/
  Evidence/ServiceDelivery_evidence
  Flow.uim
• ..webclient/components/CommonIntake/Delivery/
  ApplicationCase/ApplicationCase_evidenceFlow.uim
• ..webclient/components/ISProduct/Home/
  IC_evidenceFlow.uim
• ..webclient/components/HCR/Insurance
  Affordability/HCRDefaultIC_flow.uim
• ..webclient/components/HCR/Insurance
  Affordability/HCREvidence_flowLinks.uim

The mapping of the evidence flow indicator for Application Cases has been removed from the following UIM pages, and the associated properties deprecated:

• ..webclient/components/CommonIntake/
  Admin/CommonIntake_applicationCaseAdminHome.uim
• ..webclient/components/CommonIntake/
  Admin/CommonIntake_createApplicationCaseAdmin.uim
• ..webclient/components/CommonIntake/
  Admin/CommonIntake_editApplicationCaseAdmin.uim

Links to Evidence Flow pages have been removed from the following application configuration files, and the associated properties for those entries marked as deprecated:

• ..EJBServer/components/AssessmentPlanning
  /tab/OutcomePlan.nav
• ..EJBServer/components/CPM/tab/
  CPMAppView/PDServiceDelivery.nav
• ..EJBServer/components/CommonIntake/
  tab/CommonIntakeApplicationCase.nav
• ..EJBServer/components/Intake/tab/
  Application.nav
• ..EJBServer/components/PFMAppViews/
  tab/CaseEvidence/CaseEvidence.nav
• ..EJBServer/components/PFMAppViews/
  tab/DefaultIntegratedCase/DefaultIntegratedCase.tab
• ..EJBServer/components/PFMAppViews/
  tab/DefaultIntegratedCase/DefaultIntegratedCase.nav
• ..EJBServer/components/PFMAppViews/
  tab/DefaultIntegratedCase/DefaultProductDelivery.nav
• ..EJBServer/components/HCR/tab/HCRCase
  /HCRChildrenHealthInsurancePlan.nav
• ..EJBServer/components/HCR/tab/HCRCase/
  HCREmergencyMedicaidHome.nav
• ..EJBServer/components/HCR/tab/HCRCase/
  HCREmployerSponsoredInsurace.nav
• ..EJBServer/components/HCR/tab/HCRCase/
  HCRExemptionPDHome.nav
• ..EJBServer/components/HCR/tab/HCRCase/
  HCRInsuranceAssistanceHome.nav
• ..EJBServer/components/HCR/tab/HCRIntegrated
  CaseHome/HCRIntegratedCase.nav
• ..EJBServer/components/HCR/tab/HCRCase/
  HCRStateBasicHealthPlanPDHome.nav
• ..EJBServer/components/HCR/tab/HCRCase/
  HCRUnassistedQualifiedHealthPlanPDHome.nav
• ..EJBServer/components/HCR/tab/HCRCase/
  StreamlinedMedicaidHome.nav
• ..EJBServer/components/ISProduct/tab/
  CGISSCREOLEApplication.nav
• ..EJBServer/components/ISProduct/tab/
  CREOLEIntegratedCaseHome.nav
• ..EJBServer/components/ISProduct/tab/
  IntegratedCaseHome.nav

The following message files have been deprecated:

• ..EJBServer/components/EvidenceFlow/
  message/GenCaseEvidenceStack.xml
• ..EJBServer/components/EvidenceFlow/
  message/GenEvidenceFlowConfig.xml
• ..EJBServer/components/EvidenceFlow/
  message/GenEvidenceFlowDisplay.xml

The following ShortNames and adapters properties files have been deprecated:

• ..EJBServer/components/EvidenceFlow/properties/ShortNames.properties
• ..EJBServer/components/EvidenceFlow/properties/adapters.properties

The following event handler configuration file has been marked as deprecated:

• ..EJBServer/components/EvidenceFlow/events/handler_config.xml

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

WorkItem:159372 - Deprecate Superseded Non-Identical Evidence Mapping

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

..EJBServer/components/EvidenceBroker/model/
Packages/PresentationLayer/EvidenceBroker
Admin/EvidenceBrokerAdmin_cat.efx

• Deprecated the process listNonIdenticalAttributeConfig()

..EJBServer/components/EvidenceBroker/model/
Packages/Reference Model/ServiceLayer/Administration/
EvidenceBrokerConfig/EvidenceBrokerConfig_cat.efx

• Deprecated the process listNonIdenticalAttributeConfig()

..EJBServer/components/EvidenceBroker/source/
curam/evidencebroker/facade/impl/
EvidenceBrokerAdmin.java

• Deprecated the process listNonIdenticalAttributeConfig()

..EJBServer/components/EvidenceBroker/source/
curam/evidencebroker/sl/impl/
EvidenceBrokerConfigAdmin.java

• Deprecated the process listNonIdenticalAttributeConfig()

The following client page and its associated properties have been deprecated:

• ..webclient/components/EvidenceBroker/
  Administration/SharedEvidenceConfigAdmin/
  EvidenceBroker_listNonIdenticalAttributesConfig.uim

References to non-identical evidence mapping pages have been removed from the following application configuration files, and the associated properties for those entries marked as deprecated:

• ..EJBServer/components/PFMAppViews/
  tab/AdminAppView/ADMINAPPSection.sec
• ..EJBServer/components/PFMAppViews/
  tab/AdminAppView/ADMINAPPSectionShortcuts.ssp
• ..EJBServer/components/PFMAppViews/
  tab/EvidenceBroker/NonIdenticalEvidence
  AttributeMapping.tab

The following traditional (pre Merative SPM 6.0) page hierarchy configuration file has been updated to remove reference to the non-identical evidence mapping page:

• ..webclient/components/EvidenceBroker/
  Hierarchy/EvidenceBrokerAdminGroup.xml

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

COMMON

WorkItem:159371 - Deprecate Referrals (Legacy) functionality

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

The following efx files are now deprecated:

• ..EJBServer/components/core/model/
  Packages/Case Manager/Maintain Case Referral_cat.efx
• ..EJBServer/components/core/model/
  Packages/Case Manager/Maintain Case Referral Assistant
  _cat.efx

The following APIs have been deprecated:

..EJBServer/components/core/source/curam/core/facade/impl/Case.java

• Deprecated the process createReferral()
• Deprecated the process modifyReferral()
• Deprecated the process readReferral()

The following java classes have been deprecated in their entirety:

• ..EJBServer/components/core/source/curam/
  core/impl/MaintainCaseReferral.java
• ..EJBServer/components/core/source/curam/
  core/impl/MaintainCaseReferralAssistant.java

The following workflow has been deprecated:

• ..EJBServer/components/core/workflow/
  CASEREFERRALNOTIFICATION_v1.xml

The following message files have been deprecated:

• ..EJBServer/components/core/message/
  BpoMaintainCaseReferral.xml
• ..EJBServer/components/core/message/
  BpoMaintainCaseReferralAssistant.xml
• ..EJBServer/components/core/message/
  BpoMaintainProductDelivery.xml

The following environment properties files contain deprecated properties:

..EJBServer/components/core/properties/Environment.xml

• Inside the section 'Application - Workflow ticket settings', the variable curam.workflow.gencasereferralticket is marked as deprecated, and its
  default value is now set to 'NO'

The following client pages and their associated properties have been deprecated:

• ..webclient/components/core/Case/Events/
  Referral/Case_createReferral.uim
• ..webclient/components/core/Case/Events/
  Referral/Case_createReferralView.vim
• ..webclient/components/core/Case/Events/
  Referral/Case_modifyReferralFromList.uim
• ..webclient/components/core/Case/Events/
  Referral/Case_modifyReferralFromView.uim
• ..webclient/components/core/Case/Events/
  Referral/Case_modifyReferralView.vim
• ..webclient/components/core/Case/Events/
  Referral/Case_viewReferral.uim
• ..webclient/components/core/Case/Events/
  Referral/Case_viewReferralView.vim
• ..webclient/components/core/Case/Events/
  Referral/Case_viewReferralViewOnly.uim
• ..webclient/components/core/Integrated
  Case/Core/Event/Referral/IntegratedCase
  _createReferral.uim
• ..webclient/components/core/Integrated
  Case/Core/Event/Referral/IntegratedCase_
  modifyReferralFromList.uim
• ..webclient/components/core/Integrated
  Case/Core/Event/Referral/IntegratedCase_
  modifyReferralFromView.uim
• ..webclient/components/core/Integrated
  Case/Core/Event/Referral/IntegratedCase_
  modifyReferralView.vim
• ..webclient/components/core/Integrated
  Case/Core/Event/Referral/IntegratedCase_
  viewReferral.uim

The following UIM / VIM pages have been updated to remove references to referrals functionality and the associated properties deprecated:

• ..webclient/components/core/Integrated
  Case/Default/DefaultProductDelivery/Event
  /DefaultICProduct_eventCalendar1.uim
• ..webclient/components/core/Integrated
  Case/Default/DefaultProductDelivery/Event
  /DefaultICProduct_listEvent.uim
• ..webclient/components/core/PaymentCorrection/
  Contact/Event/PaymentCorrection_calendar.uim
• ..webclient/components/core/PaymentCorrection/
  Contact/Event/PaymentCorrection_listEvent.uim
• ..webclient/components/core/Reassessment Products/Benefit Overpayment/Calendar/BenefitSampleOverpayment_calendar1.uim
• ..webclient/components/core/Reassessment Products/Benefit Overpayment/Events/BenefitSampleOverpayment_listEvent.uim
• ..webclient/components/ServicePlans/Service Plan Delivery/Events/ServicePlanDelivery_eventCalendar.uim
• ..webclient/components/ServicePlans/Service Plan Delivery/Events/ServicePlanDelivery_listEvent.uim
• ..webclient/components/core/Integrated
  Case/Default/DefaultIntegratedCase/Event/
  DefaultIC_eventCalendar.uim
• ..webclient/components/core/Integrated
  Case/Default/DefaultIntegratedCase/Event/
  DefaultIC_listEvent.uim
• ..webclient/components/core/Issue Delivery/
  Event/IssueDelivery_eventCalendar1.uim
• ..webclient/components/core/Issue Delivery/
  Event/IssueDelivery_listEvent.uim

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

Common Intake

WorkItem:156705 - Introduce multi-select to Application Search

How to Upgrade:

ApplicationSearch_TabDetails4.uim should be used instead of ApplicationSearch_TabDetails2.uim

Itemised List of Changes:

ApplicationSearch_TabDetails2.uim

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

Cúram Modules

Social Enterprise Collaboration

SOCIAL ENTERPRISE FOLDER

WorkItem:159365 - Deprecate the Social Enterprise Folder (SEF) case

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

..EJBServer/components/SocialEnterpriseCollaboration/
model/Packages/SEF/Application/SocialEnterpriseFolder/
SocialEnterpriseFolder_cat.efx

• Deprecated the process calculateAge()
• Deprecated the process cancelCaseRelationship()
• Deprecated the process close()
• Deprecated the process createCaseRelationship()
• Deprecated the process createCaseSupervisor()
• Deprecated the process createIntegratedCase()
• Deprecated the process createNote()
• Deprecated the process createSocialEnterpriseFolder()
• Deprecated the process getAddressLine1()
• Deprecated the process getCalendar()
• Deprecated the process getUserType()
• Deprecated the process listCalendarEvents()
• Deprecated the process listCalendarMeetings()
• Deprecated the process listCaseRelationship()
• Deprecated the process listMySocialEnterpriseFolders()
• Deprecated the process listNote()
• Deprecated the process listStatusHistory()
• Deprecated the process listUserRoles()
• Deprecated the process modify()
• Deprecated the process modifyCaseRelationship()
• Deprecated the process read
• Deprecated the process readCitizenContextDetails()
• Deprecated the process readCitizenContextTree()
• Deprecated the process readSEFAdminDetails()
• Deprecated the process readSEFCreatePageLabels()
• Deprecated the process readSEFRelationship()
• Deprecated the process readSEFTypesAndContextDetails()
• Deprecated the process readSocialEnterpriseFolderDetails()
• Deprecated the process reopen()
• Deprecated the process resolveFolderCaseType()
• Deprecated the process resolveFolderClientType()
• Deprecated the process searchSEFCases()

../EJBServer/components/SocialEnterpriseCollaboration/
model/Packages/SEF/Application/SocialEnterprise
Communication/SocialEnterpriseFolder
Communication_cat.efx

• Deprecated the process listCommunication()
• Deprecated the process readEmailCommunication()
• Deprecated the process readRecordedCommunication()

..EJBServer/components/SocialEnterpriseCollaboration/
model/Packages/SEF/Application/SocialEnterprise
FolderIncident/SocialEnterpriseFolderIncident_cat.efx

• Deprecated the process addIncidentConcern()
• Deprecated the process addIncidentFile()
• Deprecated the process addIncidentFileAttachment()
• Deprecated the process addWitness()
• Deprecated the process changeIncidentReporter()
• Deprecated the process closeIncident()
• Deprecated the process closeIncidentWithInformationals()
• Deprecated the process createIncident()
• Deprecated the process createIncidentAndWitnesses()
• Deprecated the process createIncidentAndWitnessesWithInformationals()
• Deprecated the process createIncidentParticipant()
• Deprecated the process createIncidentWithInformationals()
• Deprecated the process deleteIncident()
• Deprecated the process listClientsForIncident()
• Deprecated the process listClientsForIncidentReporter()
• Deprecated the process listClientsParticipantsMDTMembersForSocialEnterpriseFolder()
• Deprecated the process listClientsParticipantsMDTMembersRelatedToIncident()
• Deprecated the process listIncident()
• Deprecated the process listIncidentConcern()
• Deprecated the process listIncidentConcernNoDuplicates()
• Deprecated the process listIncidentFile()
• Deprecated the process listMDTMembersAffectedByIncident()
• Deprecated the process listNonCurrentWitnessClientsParticipantsMDTMembersRelatedToIncident()
• Deprecated the process listUnaffectedM embersForIncident()
• Deprecated the process listWitness()
• Deprecated the process modifyIncident()
• Deprecated the process modifyIncidentFile()
• Deprecated the process modifyIncidentFileAttachment()
• Deprecated the process modifyIncidentReporter()
• Deprecated the process modifyIncidentWithInformationals()
• Deprecated the process modifyWitness()
• Deprecated the process removeAffectedClient()
• Deprecated the process removeIncidentFile()
• Deprecated the process removeWitness()
• Deprecated the process viewIncident()
• Deprecated the process viewIncidentFile()
• Deprecated the process viewIncidentReporter()
• Deprecated the process viewWitness()

..EJBServer/components/SocialEnterpriseCollaboration/
model/Packages/SEF/Administration_cat.efx

• Deprecated the process cancelSEFAdminDetails()
• Deprecated the process createSEFAdminDetails()
• Deprecated the process listSEFAdminDetails()
• Deprecated the process modifySEFAdminDetails()
• Deprecated the process readDetailsForSEF()
• Deprecated the process viewSEFAdminDetails()

The structs related to Social Enterprise Folder stand-alone cases have been deprecated in the following model files:

• ..EJBServer/components/SocialEnterpriseCollaboration/model/
  Packages/SEF/Application/SocialEnterpriseCommunication/
  SocialEnterpriseFolderCommunication_cat.efx
• ..EJBServer/components/SocialEnterpriseCollaboration/model/
  Packages/SEF/Application/SocialEnterpriseFolderIncident/
  SocialEnterpriseFolderIncident_cat.efx
• ..EJBServer/components/SocialEnterpriseCollaboration/model/
  Packages/SEF/ Administration_cat.efx
• ..EJBServer/components/SocialEnterpriseCollaboration/model/
  Packages/SEF/ Application/SocialEnterpriseFolder_cat.efx

Social Enterprise Folder stand-alone case related operations have been deprecated from the following java classes:

..EJBServer/components/SocialEnterpriseCollaboration/source/
curam/sec/sef/application/facade/impl/SocialEnterpriseFolder.java

• Deprecated the process calculateAge()
• Deprecated the process cancelCaseRelationship()
• Deprecated the process close()
• Deprecated the process createCaseRelationship()
• Deprecated the process createCaseSupervisor()
• Deprecated the process createIntegratedCase()
• Deprecated the process createNote()
• Deprecated the process createSocialEnterpriseFolder()
• Deprecated the process getAddressLine1()
• Deprecated the process getCalendar()
• Deprecated the process getUserType()
• Deprecated the process listCalendarEvents()
• Deprecated the process listCalendarMeetings()
• Deprecated the process listCaseRelationship()
• Deprecated the process listMySocialEnterpriseFolders()
• Deprecated the process listNote()
• Deprecated the process listStatusHistory()
• Deprecated the process listUserRoles()
• Deprecated the process modify()
• Deprecated the process modifyCaseRelationship()
• Deprecated the process read
• Deprecated the process readCitizenContextDetails()
• Deprecated the process readCitizenContextTree()
• Deprecated the process readSEFAdminDetails()
• Deprecated the process readSEFCreatePageLabels()
• Deprecated the process readSEFRelationship()
• Deprecated the process readSEFTypesAndContextDetails()
• Deprecated the process readSocialEnterpriseFolderDetails()
• Deprecated the process reopen()
• Deprecated the process resolveFolderCaseType()
• Deprecated the process resolveFolderClientType()
• Deprecated the process searchSEFCases()

..EJBServer/components/SocialEnterpriseCollaboration/source/
curam/sec/sef/application/facade/impl/SocialEnterprise
FolderCommunication.java

• Deprecated the process listCommunication()
• Deprecated the process readEmailCommunication()
• Deprecated the process readRecordedCommunication()

..EJBServer/components/SocialEnterpriseCollaboration/source/
curam/sec/mdt/facade/impl/MDTExternal.java

• Deprecated the process viewIncident()

..EJBServer/components/SocialEnterpriseCollaboration/source/
curam/sec/sef/application/facade/impl/SocialEnterpriseFolder
Incident.java

• Deprecated the process addIncidentConcern()
• Deprecated the process addIncidentFile()
• Deprecated the process addIncidentFileAttachment()
• Deprecated the process addWitness()
• Deprecated the process changeIncidentReporter()
• Deprecated the process closeIncident()
• Deprecated the process closeIncidentWithInformationals()
• Deprecated the process createIncident()
• Deprecated the process createIncidentAndWitnesses()
• Deprecated the process createIncidentAndWitnessesWithInformationals()
• Deprecated the process createIncidentParticipant()
• Deprecated the process createIncidentWithInformationals()
• Deprecated the process deleteIncident()
• Deprecated the process listClientsForIncident()
• Deprecated the process listClientsForIncidentReporter()
• Deprecated the process listClientsParticipantsMDTMembersForSocialEnterpriseFolder()
• Deprecated the process listClientsParticipantsMDTMembersRelatedToIncident()
• Deprecated the process listIncident()
• Deprecated the process listIncidentConcern()
• Deprecated the process listIncidentConcernNoDuplicates()
• Deprecated the process listIncidentFile()
• Deprecated the process listMDTMembersAffectedByIncident()
• Deprecated the process listNonCurrentWitnessClientsParticipantsMDTMembersRelatedToIncident()
• Deprecated the process listUnaffectedMembersForIncident()
• Deprecated the process listWitness()
• Deprecated the process modifyIncident()
• Deprecated the process modifyIncidentFile()
• Deprecated the process modifyIncidentFileAttachment()
• Deprecated the process modifyIncidentReporter()
• Deprecated the process modifyIncidentWithInformationals()
• Deprecated the process modifyWitness()
• Deprecated the process removeAffectedClient()
• Deprecated the process removeIncidentFile()
• Deprecated the process removeWitness()
• Deprecated the process viewIncident()
• Deprecated the process viewIncidentFile()
• Deprecated the process viewIncidentReporter()
• Deprecated the process viewWitness()

..EJBServer/components/SocialEnterpriseCollaboration/source/
curam/sec/sef/admin/facade/impl/SocialEnterprise
FolderAdministration.java

• Deprecated the process cancelSEFAdminDetails()
• Deprecated the process createSEFAdminDetails()
• Deprecated the process listSEFAdminDetails()
• Deprecated the process modifySEFAdminDetails()
• Deprecated the process readDetailsForSEF()
• Deprecated the process viewSEFAdminDetails()

..EJBServer/components/SocialEnterpriseCollaboration/source/
curam/sec/tab/impl/SocialEnterpriseFolderMenuLoader.java

The following UIM / VIM pages and their associated properties have been deprecated:

• ..webclient/components/SECCommon/SEF/
  Application/Incident/SocialEnterpriseFolder
  _cancelIncident.uim
• ..webclient/components/SECCommon/SEF/
  Application/Incident/SocialEnterpriseFolder
  _changeIncidentReporter.uim
• ..webclient/components/SECCommon/SEF/
  Application/Incident/SocialEnterpriseFolder
  _closeIncident.uim
• ..webclient/components/SECCommon/SEF/
  Application/Incident/SocialEnterpriseFolder
  _modifyIncidentFileFromList.uim
• ..webclient/components/SECCommon/SEF/
  Application/Incident/SocialEnterpriseFolder
  _modifyIncidentFromList.uim
• ..webclient/components/SECCommon/SEF/
  Application/Incident/SocialEnterpriseFolder
  _modifyIncidentFromView.uim
• ..webclient/components/SECCommon/SEF/
  Application/Incident/SocialEnterpriseFolder
  _removeIncidentConcern.uim
• ..webclient/components/SECCommon/SEF/
  Application/Incident/SocialEnterpriseFolder
  _removeIncidentFile.uim
• ..webclient/components/SECCommon/SEF/
  Application/Incident/SocialEnterpriseFolder
  _removeWitness.uim
• ..webclient/components/SECCommon/SEF/
  Application/Incident/SocialEnterpriseFolder
  _viewWitness.uim
• ..webclient/components/SocialEnterprise
  Collaboration/SEF/Administration/Administration
  CaseColaboration_create.vim
• ..webclient/components/SocialEnterprise
  Collaboration/SEF/Administration/SocialEnterprise
  FolderAdministration_cancelSEFType.uim

• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Administration/SocialEnterpriseFolderAdministration
  _createSEFType.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Administration/SocialEnterpriseFolderAdministration
  _listSEFTypes.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Administration/SocialEnterpriseFolderAdministration
  _modifySEFTypeFromList.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Administration/SocialEnterpriseFolderAdministration
  _modifySEFTypeFromView.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Administration/SocialEnterpriseFolderAdministration
  _modifySEFTypeView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Administration/SocialEnterpriseFolderAdministration
  _viewLocalizableText.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Administration/SocialEnterpriseFolderAdministration
  _viewSEFType.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_close.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_create.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_createClient.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_createClient
  FromClientView.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_enhancedCreate.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_listStatusHistory.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_listUserRoles.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_modify.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_new.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_reopen.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_searchCaseAddMember.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_searchPerson.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_searchPerson
  AddMember.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/SocialEnterpriseFolder_selectPersonType.uim

• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/AddCases/SocialEnterpriseFolder
  _addCaseMultipleClients.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Add Cases/SocialEnterpriseFolder
  _listCaseAddCaseMultipleClients.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Add Cases/SocialEnterpriseFolder
  _resolveAddCaseClients.uim

• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Assessment/SocialEnterpriseFolder
  _listAssessment.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Attachment/Case_viewAttachmentModal.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Attachment/SocialEnterpriseFolder
  _createAttachment.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Attachment/SocialEnterpriseFolder
  _listAttachment.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Attachment/SocialEnterpriseFolder
  _modifyAttachmentView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Attachment/SocialEnterpriseFolder
  _viewAttachment.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Calendar/SocialEnterpriseFolder
  _eventCalendar.uim
• ..webclient/components/SocialEnterpris eCollaboration/
  SEF/Application/Calendar/SocialEnterpriseFolder
  _listEvent.uim

• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Calendar/SocialEnterpriseFolder
  _resolveCalendar.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Calendar/Meetings/Meeting
  _inviteAttendeeView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Calendar/Meetings/Meeting
  _modifyMeetingFromUserCalendar.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Calendar/Meetings/Meeting
  _viewMeeting.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Calendar/Meetings/Meeting
  _viewMeetingFromUserCalendar.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Case/SocialEnterpriseFolder
  _listCurrentCases.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Case/SocialEnterpriseFolder
  _listRemovedCases.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Case/User Roles/SocialEnterpriseFolder
  _modifyCaseOwner.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Case/User Roles/SocialEnterpriseFolder
  _modifyCaseOwnerView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Case/User Roles/SocialEnterpriseFolder
  _modifyCaseSupervisor.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Case/User Roles/SocialEnterpriseFolder
  _modifyCaseSupervisorView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Case TransactionLog/View/SocialEnterprise
  Folder_viewAllTransactions.uim

• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Client/SocialEnterpriseFolder
  _listCurrentClients.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Client/SocialEnterpriseFolder
  _listRemovedClients.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Communication/SocialEnterpriseFolder
  _createEmailCommunication.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Communication/SocialEnterpriseFolder
  _createMSWordCommunication.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Communication/SocialEnterpriseFolder
  _createProFormaCommunication.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Communication/SocialEnterpriseFolder
  _getCorrespondentView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Communication/SocialEnterpriseFolder
  _listCommunication.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Communication/SocialEnterpriseFolder
  _recordCommunication.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Communication/SocialEnterpriseFolder
  _viewCommunicationView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Communication/SocialEnterpriseFolder
  _viewMSWordCommunication.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Hierarchy/SocialEnterpriseFolderGroup.xml
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Home/SocialEnterpriseFolder_home.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _addAffectedClient.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _addIncidentConcern.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _cancelIncidentFile.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _createIncident.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _createIncidentFile.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _createWitness.uim

• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _listIncident.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _listIncidentFile.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _listWitness.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _modifyIncidentFileFromView.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _modifyIncidentFileView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _modifyIncidentReporter.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _modifyIncidentView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _modifyWitness.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _viewIncident.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _viewIncidentDiscussion.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _viewIncidentFile.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _viewIncidentFileFromList.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _viewIncidentFileView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Incident/SocialEnterpriseFolder
  _viewMDTSensitivityDetails.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Interaction/SocialEnterpriseFolder
  _listInteraction.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/List/SocialEnterpriseFolder
  _listByOwner.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Note/Case_viewNoteModal.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Note/SocialEnterpriseFolder_listCaseNote.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Note/SocialEnterpriseFolder_listNote.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Note/SocialEnterpriseFolder_listNoteView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/PersonDetails/SocialEnterpriseFolder
  _personDetails.uim

• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Related Social Enterprise Folder/SocialEnterpriseFolder_cancelCaseRelationship.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Related Social Enterprise Folder/SocialEnterprise
  Folder_cancelCaseRelationshipView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Related Social Enterprise Folder/SocialEnterpriseFolder
  _createCaseRelationship.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Related Social Enterprise Folder/SocialEnterpriseFolder
  _listRelatedSEF.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Related Social Enterprise Folder/SocialEnterpriseFolder
  _modifyCaseRelationshipFromList.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Related Social Enterprise Folder/SocialEnterpriseFolder
  _modifyCaseRelationshipFromView.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Related Social Enterprise
  Folder/SocialEnterpriseFolder_modifyCase
  RelationshipView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Related Social Enterprise Folder/SocialEnterpriseFolder
  _viewCaseRelationship.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Related Social Enterprise Folder/SocialEnterpriseFolder_viewCaseRelationshipView.vim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/Related Social Enterprise Folder/Search/SocialEnterpriseFolder_searchCasePopup.uim
• ..webclient/components/SocialEnterpriseCollaboration/
  SEF/Application/User Roles/SocialEnterpriseFolder
  _listUserRoleView.vim

Entries relating to Social Enterprise Folder stand-alone cases have been removed from the following application configuration files, and the associated properties for removed entries marked as deprecated:

• ..EJBServer/components/SocialEnterpriseCollaboration/
  tab/AdminAppView/ADMINAPPSection.sec
• ..EJBServer/components/SocialEnterpriseCollaboration/
  tab/DefaultAppView/DefaultAppSection.sec
• ..EJBServer/components/SocialEnterpriseCollaboration/
  tab/MDTWorkspace/MDTEAPPWorkspaceSection.sec
• ..EJBServer/components/SocialEnterpriseCollaboration/
  tab/PlannerAppView/PlannerAppWorkspaceSection.sec
• ..EJBServer/components/SocialEnterpriseCollaboration/
  tab/MDTWorkspace/MDTSocialEnterpriseFolderMenu.mnu
• ..EJBServer/components/SocialEnterpriseCollaboration/
  tab/SocialEnterpriseFolder.mnu
• ..EJBServer/components/SocialEnterpriseCollaboration/
  tab/SEFMyCases.tab
• ..EJBServer/components/SocialEnterpriseCollaboration/
  tab/SocialEnterpriseCollaboration.tab
• ..EJBServer/components/SocialEnterpriseCollaboration/
  tab/SocialEnterpriseCollaboration.nav
• ..EJBServer/components/SocialEnterpriseCollaboration/
  tab/SocialEnterpriseFolder.nav
• ..EJBServer/components/PFMAppViews/
  tab/AdminAppView/ADMINAPPSectionShortcuts.ssp
• ..EJBServer/components/PFMAppViews/
  tab/DefaultAppView/DefaultAppSectionShortcuts.ssp

Messages related to Social Enterprise Folder stand-alone cases have been deprecated in the following message files:

• ..EJBServer/components/SocialEnterpriseCollaboration
  /message/BPOIncident.xml
• ..EJBServer/components/SocialEnterpriseCollaboration
  /message/BPOIncidentConcern.xml
• ..EJBServer/components/SocialEnterpriseCollaboration
  /message/BPOIncidentLink.xml
• ..EJBServer/components/SocialEnterpriseCollaboration
  /message/BPOSocialEnterpriseFolder.xml
• ..EJBServer/components/SocialEnterpriseCollaboration
  /message/BPOSocialEnterpriseFolderAdministration.xml
• ..EJBServer/components/SocialEnterpriseCollaboration
  /message/BPOSocialEnterpriseFolderCaseRelationship.xml
• ..EJBServer/components/SocialEnterpriseCollaboration/
  message/BPOWitness.xml
• ..EJBServer/components/SocialEnterpriseCollaboration/
  message/SEFCreateLabels.xml

For entries in the following DMX files related to Social Enterprise Folder stand-alone cases, a deprecation comment has been added:

• ..EJBServer/components/SocialEnterpriseCollaboration/
  data/initial/PageConfig.dmx
• ..EJBServer/components/SocialEnterpriseCollaboration/
  data/initial/QuickLink.dmx
• ..EJBServer/components/SocialEnterpriseCollaboration/
  data/initial/QuickLinkApplicationLink.dmx
• ..EJBServer/components/SocialEnterpriseCollaboration/
  data/initial/WebAddress.dmx

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

Provider Management

MISCELLANEOUS

WorkItem:159267 - Deprecate CPM Taxonomy

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

../EJBServer/components/CPM/model/Packages/
Facade/Taxonomy/Related Concept/RelatedConcept.efx

• Deprecated the process MaintainRelatedConcept.createRelatedConcept()
• Deprecated the process MaintainRelatedConcept.listRelatedConcept()
• Deprecated the process MaintainRelatedConcept.modifyRelatedConcept()
• Deprecated the process MaintainRelatedConcept.previewRelatedConcept()
• Deprecated the process MaintainRelatedConcept.previewTaxonomyTerms()
• Deprecated the process MaintainRelatedConcept.readWizardMenu()
• Deprecated the process MaintainRelatedConcept.removeRelatedConcept()
• Deprecated the process MaintainRelatedConcept.removeTaxonomyTerm()
• Deprecated the process MaintainRelatedConcept.removeTaxonomyTermFromRelatedConcept()
• Deprecated the process MaintainRelatedConcept.searchAddTaxonomyTermsToRelatedConcept()
• Deprecated the process MaintainRelatedConcept.viewRelatedConcept()
• Deprecated the process MaintainRelatedConceptElement.createRelatedConceptElement
• Deprecated the process MaintainRelatedConceptElement.listRelatedConceptElements
• Deprecated the process MaintainRelatedConceptElement.modifyRelatedConceptElement
• Deprecated the process MaintainRelatedConceptElement.previewInEditTerms
• Deprecated the process MaintainRelatedConceptElement.previewRelatedConceptElement
• Deprecated the process MaintainRelatedConceptElement.readWizardMenu
• Deprecated the process MaintainRelatedConceptElement.removeInEditTerm
• Deprecated the process MaintainRelatedConceptElement.removeInEditTermFromRelatedConceptElement
• Deprecated the process MaintainRelatedConceptElement.removeRelatedConceptElement
• Deprecated the process MaintainRelatedConceptElement.searchAddInEditTermsToRelatedConceptElement
• Deprecated the process MaintainRelatedConceptElement.viewRelatedConceptElement

..EJBServer/components/CPM/model/Packages/
Facade/Taxonomy/Taxonomy Version/TaxonomyVersion.efx

• Deprecated the process MaintainTaxonomyImportLog.getPageNumber()
• Deprecated the process MaintainTaxonomyImportLog.listImportLogsForDeletedTerms()
• Deprecated the process MaintainTaxonomyImportLog.listImportLogsForModifiedTerms()
• Deprecated the process MaintainTaxonomyImportLog.listImportLogsForNewTerms()
• Deprecated the process MaintainTaxonomyImportLog.listImportLogsForNotImportedTerms()
• Deprecated the process MaintainTaxonomyImportLog.listImportLogsForReplacedTerms()
• Deprecated the process MaintainTaxonomyImportLog.viewTaxonomyImportLog
• Deprecated the process MaintainTaxonomyVersion.addTaxonomyReviewAttributes()
• Deprecated the process MaintainTaxonomyVersion.createTaxonomyVersion()
• Deprecated the process MaintainTaxonomyVersion.importTaxonomy()
• Deprecated the process MaintainTaxonomyVersion.importTaxonomyTranslation()
• Deprecated the process MaintainTaxonomyVersion.listImportTaxonomyInformational()
• Deprecated the process MaintainTaxonomyVersion.listImportTranslationInformations()
• Deprecated the process MaintainTaxonomyVersion.listPublishTaxonomyInformational()
• Deprecated the process MaintainTaxonomyVersion.listTaxonomyVersion()
• Deprecated the process MaintainTaxonomyVersion.listTaxonomyVersionDataForTaxonomyVersion()
• Deprecated the process MaintainTaxonomyVersion.listUpdateReviewAttributes()
• Deprecated the process MaintainTaxonomyVersion.publishInEditTaxonomyTerms()
• Deprecated the process MaintainTaxonomyVersionpublishTaxonomyVersion()
• Deprecated the process Ma intainTaxonomyVersionremoveTaxonomyVersion()
• Deprecated the process MaintainTaxonomyVersion.updateTaxonomy()
• Deprecated the process MaintainTaxonomyVersionupdateTaxonomyVersion()
• Deprecated the process MaintainTaxonomyVersion.viewPublishedTaxonomyVersionDetails()
• Deprecated the process MaintainTaxonomyVersion.viewTaxonomyImportStats()
• Deprecated the process MaintainTaxonomyVersion.viewTaxonomyVersionDetails()

..EJBServer/components/CPM/model/Packages/Facade/
Taxonomy/Taxonomy Term/Taxonomy Term.efx

• Deprecated the process MaintainTaxonomyInEditData.addRelatedConcept
• Deprecated the process MaintainTaxonomyInEditData.addRelatedTerm
• Deprecated the process MaintainTaxonomyInEditData.addUseReference
• Deprecated the process MaintainTaxonomyInEditData.createTaxonomyTerm
• Deprecated the process MaintainTaxonomyInEditData.getInitialPageNumber
• Deprecated the process MaintainTaxonomyInEditData.getPageNumber
• Deprecated the process MaintainTaxonomyInEditData.listDeletedTermsOnTaxonomyUpdate
• Deprecated the process MaintainTaxonomyInEditData.listInEditTaxonomyTerms
• Deprecated the process MaintainTaxonomyInEditData.listModifiedTermsOnTaxonomyUpdate
• Deprecated the process MaintainTaxonomyInEditData.listRelatedConceptElement
• Deprecated the process MaintainTaxonomyInEditData.listRelatedConceptForInEditTerm
• Deprecated the process MaintainTaxonomyInEditData.listRelatedTermsForInEditTerm
• Deprecated the process MaintainTaxonomyInEditData.listReplacedTermsOnTaxonomyUpdate
• Deprecated the process MaintainTaxonomyInEditData.listUseReferencesForInEditTerm
• Deprecated the process MaintainTaxonomyInEditData.previewPublishedTerm
• Deprecated the process MaintainTaxonomyInEditData.previewRelatedConcepts
• Deprecated the process MaintainTaxonomyInEditData.previewRelatedConceptsForPublishedTerm
• Deprecated the process MaintainTaxonomyInEditData.previewRelatedTerms
• Deprecated the process MaintainTaxonomyInEditData.previewTaxonomyTerm
• Deprecated the process MaintainTaxonomyInEditData.previewUpdatedTerm
• Deprecated the process MaintainTaxonomyInEditData.previewUseReferences
• Deprecated the process MaintainTaxonomyInEditData.publishInEditTaxonomyTerm
• Deprecated the process MaintainTaxonomyInEditData.readWizardMenu
• Deprecated the process MaintainTaxonomyInEditData.removeRelatedConcept
• Deprecated the process MaintainTaxonomyInEditData.removeRelatedTerm
• Deprecated the process MaintainTaxonomyInEditData.removeTaxonomyInEditTerm
• Deprecated the process MaintainTaxonomyInEditData.removeUseReference
• Deprecated the process MaintainTaxonomyInEditData.reviewDeletedTerms
• Deprecated the process MaintainTaxonomyInEditData.reviewModifiedTerm
• Deprecated the process MaintainTaxonomyInEditData.reviewReplacedTerm
• Deprecated the process MaintainTaxonomyInEditData.searchInEditTaxonomyTerms
• Deprecated the process MaintainTaxonomyInEditData.storeRelatedConcepts
• Deprecated the process MaintainTaxonomyInEditData.storeRelatedTerm
• Deprecated the process MaintainTaxonomyInEditData.storeUseReference
• Deprecated the process MaintainTaxonomyInEditData.updateInEditTaxonomyTerm
• Deprecated the process MaintainTaxonomyInEditData.viewInEditTaxonomyTerm
• Deprecated the process MaintainTaxonomyInEditData.viewReplacementTermDetails
• Deprecated the process MaintainTaxonomyInEditData.viewTaxonomyTermModifications
• Deprecated the process MaintainTaxonomyTerm.addRelatedConceptsToTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.addRelatedTermToTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.addUseReferenceToTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.createTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.listAssociatedTerms()
• Deprecated the process MaintainTaxonomyTerm.listRelatedConceptsForTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.listRelatedTermsForTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.listTaxonomyTerms()
• Deprecated the process MaintainTaxonomyTerm.listTaxonomyTermS tatus()
• Deprecated the process MaintainTaxonomyTerm.listUpdatedTaxonomyTerms()
• Deprecated the process MaintainTaxonomyTerm.listUseReferencesForTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.previewAndSelectRelatedConceptForTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.previewRelatedConcepts()
• Deprecated the process MaintainTaxonomyTerm.previewRelatedTerms()
• Deprecated the process MaintainTaxonomyTerm.previewTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.previewUseReferences()
• Deprecated the process MaintainTaxonomyTerm.readTaxonomyTermDetailsForUpdate()
• Deprecated the process MaintainTaxonomyTerm.readWizardMenu()
• Deprecated the process MaintainTaxonomyTerm.removeRelatedConceptFromTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.removeRelatedTermFromTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.removeTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.removeUseReferenceFromTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.searchTaxonomyTerms()
• Deprecated the process MaintainTaxonomyTerm.storeRelatedConcepts()
• Deprecated the process MaintainTaxonomyTerm.storeRelatedTerm()
• Deprecated the process MaintainTaxonomyTerm.storeUseReference()
• Deprecated the process MaintainTaxonomyTerm.updateTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTerm.viewTaxonomyTerm()
• Deprecated the process MaintainTaxonomyTranslation.addRelatedConceptTranslation()
• Deprecated the process MaintainTaxonomyTranslation.addTaxonomyTranslation()
• Deprecated the process MaintainTaxonomyTranslation.getTaxonomyTranslationDetails()
• Deprecated the process MaintainTaxonomyTranslation.listRelatedConceptTranslations()
• Deprecated the process MaintainTaxonomyTranslation.listTaxonomyTranslations()
• Deprecated the process MaintainTaxonomyTranslation.modifyRelatedConceptTranslation()
• Deprecated the process MaintainTaxonomyTranslation.modifyTaxonomyTranslation()

..EJBServer/components/CPM/model/Packages/Facade/Service Delivery/Referral/Referral.efx

• Deprecated the process Referral.searchReferralServices()
• Deprecated the process Referral.listReferralServicesByTerm()

The following java classes have been completely deprecated:

• ..EJBServer/components/CPM/source/curam/cpm/facade/
  impl/MaintainRelatedConcept.java
• ..EJBServer/components/CPM/source/curam/cpm/facade/
  impl/MaintainRelatedConceptElement.java
• ..EJBServer/components/CPM/source/curam/cpm/facade/
  impl/MaintainTaxonomyImportLog.java
• ..EJBServer/components/CPM/source/curam/cpm/facade/
  impl/MaintainTaxonomyInEditData.java
• ..EJBServer/components/CPM/source/curam/cpm/facade/
  impl/MaintainTaxonomyTerm.java
• ..EJBServer/components/CPM/source/curam/cpm/facade/
  impl/MaintainTaxonomyTranslation.java
• ..EJBServer/components/CPM/source/curam/cpm/facade/
  impl/MaintainTaxonomyVersion.java
• ..EJBServer/components/CPM/source/curam/cpm/facade/
  impl/POTaxonomyIndexing.java
• ..EJBServer/components/CPM/source/curam/cpm/facade/
  impl/POTaxonomyIndexingHelper.java
• ..EJBServer/components/CPM/source/curam/cpm/facade/
  impl/POTaxonomyIndexingHelperImpl.java
• ..EJBServer/components/CPM/source/curam/cpm/sl/
  impl/BrowseTaxonomy.java
• ..EJBServer/components/CPM/source/curam/cpm/sl/
  impl/BrowseTaxonomyVersion.java
• ..EJBServer/components/CPM/source/curam/cpm/sl/
  impl/ImportTaxonomyData.java
• ..EJBServer/components/CPM/source/curam/cpm/sl/
  impl/PublishTaxonomyData.java
• ..EJBServer/components/CPM/source/curam/cpm/sl/
  impl/TaxonomyDatabaseSearchExtractor.java
• ..EJBServer/components/CPM/source/curam/cpm/
  workflowprocesses/taxonomy/impl/TaxonomyWorkFlow
  Allocation.java
• All classes inside the packages - curam.taxonomy

Taxonomy related methods/variables have been deprecated in the following classes:

..EJBServer/components/CPM/source/curam/
cpm/facade/impl/Referral.java

• Deprecated the process searchReferralServices()
• Deprecated the process listReferralServicesByTerm()

..EJBServer/components/CPM/source/curam/
provider/impl/ProviderServiceCenterDAO.java

• Deprecated the process searchByProviderOffering()

..EJBServer/components/CPM/source/curam/
provider/impl/ProviderServiceCenterDAOImpl.java

• Deprecated the process searchByProviderOffering()

..EJBServer/components/CPM/source/curam/
providerservice/impl/ProviderOfferingDAO.java

• Deprecated the process searchPODetailsByPOID()

..EJBServer/components/CPM/source/curam/
providerservice/impl/ProviderOfferingDAOImpl.java

• Deprecated the process searchPODetailsByPOID()

..EJBServer/components/CPM/source/curam/
cpm/workflowprocesses/impl/WorkflowAllocationFunction.java

• Deprecated the process taxonomyUpdateTaskAllocationStrategy()

..EJBServer/components/CPM/source/curam/
cpm/impl/Module.java

• Deprecated the process bindTaxonomySearchEvents()

..EJBServer/components/CPM/source/curam/
cpm/impl/CPMConstants.java

• Deprecated the constant kResourceManagerUserName
• Deprecated the constant kFacilityManagerUserName
• Deprecated the constant kTaxonomySearchChunkProcessor
• Deprecated the constant kTaxonomySearchStatusChecker
• Deprecated the constant kTaxonomySearchChunker

The following entities are now deprecated:

• ExtSysClassification
• ExtSysClassifnElement
• ExtSysClassifnTermLink
• POTaxonomyInEditIndex
• POTaxonomyIndexLink
• RelatedConcept
• RelatedConceptElement
• RelatedConceptNameLink
• RelatedTermLink
• TaxonomyGSSSynch
• TaxonomyInEditData
• TaxonomyTerm
• TaxonomyTermNameLink
• TaxonomyTermOldCode
• TaxonomyTermRelatedConcept
• TaxonomyVersionData
• TaxonomyVersion
• UseReference
• UseReferenceNameLink

The following application configuration files have either being deprecated or references to Taxonomy removed (in the .sec files) and the associated properties deprecated:

• ..EJBServer/components/CPM/tab/CPMAppView/Taxonomy.tab
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyInEditTermView.tab
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyPublishedTermInEditView.tab
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyTermSearch.tab
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyTermView.tab
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyVersionPublishedView.tab
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyVersionInEditView.tab
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyReviewItemsList.tab
• ..EJBServer/components/CPM/tab/CPMAppView/ListTaxonomy.tab
• ..EJBServer/components/CPM/tab/CPMAppView/Taxonomy.nav
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyInEditTermView.nav
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyPublishedTermInEditView.nav
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyReviewItemsList.nav
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyTermSearch.nav
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyTermView.nav
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyVersionInEditView.nav
• ..EJBServer/components/CPM/tab/CPMAppView/TaxonomyVersionPublishedView.nav
• ..EJBServer/components/CPM/tab/ADMINAPPSectionShortcuts.ssp
• ..EJBServer/components/CPM/tab/ADMINAPPSection.sec
• ..EJBServer/components/CPM/tab/CPMRMAPPWorkspaceSection.sec
• ..EJBServer/components/CPM/tab/CPMRMSAPPWorkspaceSection.sec

The following message files have been deprecated:

• ..EJBServer/components/CPM/message/TaxonomyTerm.xml
• ..EJBServer/components/CPM/message/TaxonomyTermIndex.xml
• ..EJBServer/components/CPM/message/TaxonomyVersion.xml
• ..EJBServer/components/CPM/message/RelatedConcept.xml

The following code tables files have been deprecated:

• ..EJBServer/components/CPM/codetable/CT_TaxonomyDBProcess.ctx
• ..EJBServer/components/CPM/code table/CT_TaxonomyFacet.ctx
• ..EJBServer/components/CPM/codetable/CT_TaxonomyIndexStatus.ctx
• ..EJBServer/components/CPM/codetable/CT_TaxonomySearchOptions.ctx
• ..EJBServer/components/CPM/codetable/CT_TaxonomyTermSearchType.ctx
• ..EJBServer/components/CPM/codetable/CT_TaxonomyTermStatus.ctx
• ..EJBServer/components/CPM/codetable/CT_TaxonomyVersionStatus.ctx
• ..EJBServer/components/CPM/codetable/CT_TaxonomyTermImportType.ctx

The following environment variables have been deprecated:

..EJBServer/components/CPM/Taxonomy/properties/Environment.xml

• Inside the section 'CPM - TAXONOMY', the variable curam.taxonomy is marked as deprecated.
• Inside the section 'CPM - TAXONOMY', the variable curam.taxonomy.version is marked as deprecated.
• Inside the section 'CPM - TAXONOMY', the variable curam.batch.publishtaxonomyversion.chunksize is marked as deprecated.
• Inside the section 'CPM - TAXONOMY', the variable curam.batch.publishtaxonomyversion.dontrunstream is marked as deprecated.
• Inside the section 'CPM - TAXONOMY', the variable curam.batch.publishtaxonomyversion.chunkkeywaitinterval is marked as deprecated.
• Inside the section 'CPM - TAXONOMY', the variable curam.batch.publishtaxonomyversion.unprocessedchunkwaitinterval is marked as deprecated.
• Inside the section 'CPM - TAXONOMY', the variable curam.batch.publishtaxonomyversion.processunprocessedchunk is marked as deprecated.

The following workflow file has been deprecated

• ..EJBServer/components/CPM/workflow/TAXONOMYTERMUPDATEWORKFLOW_v1.xml

All of the UIM / VIM files in the following folder and subfolders and their associated properties have been marked as deprecated:

• ..webclient/components/CPM/Taxonomy

References to Taxonomy are removed from the following files and the associated properties have been marked as deprecated:

• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_viewProviderServiceOffering.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_viewProviderServiceOfferingForFacilityManager.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_listProviderServiceOffering.uim
• ..webclient/components/CPM/ServiceDelivery/ServiceSearch/
  ProviderManagement_service.uim
• ..webclient/components/CPM/Referral/ReferralSearch/
  ProviderManagement_referral.uim
• ..webclient/components/CPM/ServiceDelivery/
  CreateServiceDeliveryWizard/CreateServiceDeliveryWizard
  _service1.uim
• ..webclient/components/CPM/Provider/
  ProviderService/ProviderManagement_viewProviderSOIndexes.uim

The following workflow file has been deprecated

• ..EJBServer/components/CPM/workflow/TAXONOMYTERMUPDATEWORKFLOW_v1.xml

All of the UIM / VIM files in the following folder and subfolders and their associated properties have been marked as deprecated:

• ..webclient/components/CPM/Taxonomy

References to Taxonomy are removed from the following files and the associated properties have been marked as deprecated:

• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_viewProviderServiceOffering.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_viewProviderServiceOfferingForFacilityManager.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_listProviderServiceOffering.uim
• ..webclient/components/CPM/ServiceDelivery/ServiceSearch/
  ProviderManagement_service.uim
• ..webclient/components/CPM/Referral/ReferralSearch/
  ProviderManagement_referral.uim
• ..webclient/components/CPM/ServiceDelivery/CreateServiceDelivery
  Wizard/CreateServiceDeliveryWizard_service1.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_viewProviderSOIndexes.uim

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

WorkItem:159364 - Deprecate CPM Performance Monitoring

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

..EJBServer/components/CPM/model/Packages/Facade/Performance Measure/MaintainPerformanceMeasure_cat.efx

• Deprecated the process PerformanceMeasure.addPerformancesMeasureForProvider()
• Deprecated the process PerformanceMeasure.addPerformancesMeasureForProviderOffering()
• Deprecated the process PerformanceMeasure.listPerformanceMeasureForProvider()
• Deprecated the process PerformanceMeasure.listPerformanceMeasuresForProviderOffering()
• Deprecated the process PerformanceMeasure.listPerformanceMeasureTypes()
• Deprecated the process PerformanceMeasure.readPerformanceMeasureLinkDetails()
• Deprecated the process PerformanceMeasure.removePerformanceMeasure()
• Deprecated the process PerformanceMeasure.viewInformationalForCustomPerformanceMeasure()
• Deprecated the process MaintainContractPerformanceMeasure.addContractPerformanceMeasureToService()
• Deprecated the process MaintainContractPerformanceMeasure.addPerformanceMeasureToContract()
• Deprecated the process MaintainContractPerformanceMeasure.deleteContractPerformanceMeasure()
• Deprecated the process MaintainContractPerformanceMeasure.listContractPerformanceMeaures()
• Deprecated the process MaintainContractPerformanceMeasure.listContractServicePerformanceMeaures()
• Deprecated the process MaintainContractPerformanceMeasure.searchPerformanceMeasure()
• Deprecated the process MaintainContractPerformanceMeasure.updateContractPerformanceMeasure()
• Deprecated the process MaintainContractPerformanceMeasure.updateContractPerformanceMeasureOfService()
• Deprecated the process MaintainContractPerformanceMeasure.viewActualContractPerformanceMeasure()
• Deprecated the process MaintainContractPerformanceMeasure.viewActualContractPMForService()
• Deprecated the process MaintainContractPerformanceMeasure.viewContractPerformanceMeasure()
• Deprecated the process MaintainContractPerformanceMeasure.viewServiceContractPerformanceMeasure()
• Deprecated the process MaintainPerformanceMeasure.createPerformanceMeasure()
• Deprecated the process MaintainPerformanceMeasure.deletePerformanceMeasure()
• Deprecated the process MaintainPerformanceMeasure.listPerformanceMeasure()
• Deprecated the process MaintainPerformanceMeasure.updatePerformanceMeasure()
• Deprecated the process MaintainPerformanceMeasure.viewPerformanceMeasure()
• Deprecated the process MaintainSOPerformanceMeasure.addEvaluationCriteria()
• Deprecated the process MaintainSOPerformanceMeasure.addPerformanceMeasureToServiceOffering()
• Deprecated the process MaintainSOPerformanceMeasure.addScoreOutcome()
• Deprecated the process MaintainSOPerformanceMeasure.createSOPerformanceMeasure()
• Deprecated the process MaintainSOPerformanceMeasure.deleteEvaluationCriteria()
• Deprecated the process MaintainSOPerformanceMeasure.deleteScoreOutcome()
• Deprecated the process MaintainSOPerformanceMeasure.deleteServiceOfferingPerformanceMeasure()
• Deprecated the process MaintainSOPerformanceMeasure.listEvaluationCriteriaForPerformanceMeasure()
• Deprecated the process MaintainSOPerformanceMeasure.listScoreOutcome()
• Deprecated the process MaintainSOPerformanceMeasure.listServiceOfferingPerformanceMeasure()
• Deprecated the process MaintainSOPerformanceMeasure.modifyScoreOutcome()
• Deprecated the process MaintainSOPerformanceMeasure.viewScoreOutcome()
• Deprecated the process MaintainSOPerformanceMeasure.viewServiceOfferingPerformanceMeasure()

..EJBServer/components/CPM/source/ curam/cpm/facade/impl/PerformanceMeasure.java

• Deprecated the process addPerformancesMeasureForProvider()
• Deprecated the process addPerformancesMeasureForProviderOffering()
• Deprecated the process listPerformanceMeasureForProvider()
• Deprecated the process listPerformanceMeasuresForProviderOffering()
• Deprecated the process listPerformanceMeasureTypes()
• Deprecated the process readPerformanceMeasureLinkDetails()
• Deprecated the process removePerformanceMeasure()

..EJBServer/components/CPM/source/curam/
cpm/facade/impl/MaintainContractPerformanceMeasure.java

• Deprecated the process addContractPerformanceMeasureToService()
• Deprecated the process addPerformanceMeasureToContract()
• Deprecated the process deleteContractPerformanceMeasure()
• Deprecated the process listContractPerformanceMeaures()
• Deprecated the process listContractServicePerformanceMeaures()
• Deprecated the process searchPerformanceMeasure()
• Deprecated the process updateContractPerformanceMeasure()
• Deprecated the process updateContractPerformanceMeasureOfService()
• Deprecated the process viewActualContractPerformanceMeasure()
• Deprecated the process viewActualContractPMForService()
• Deprecated the process viewContractPerformanceMeasure()
• Deprecated the process viewServiceContractPerformanceMeasure()

..EJBServer/components/CPM/source/curam/
cpm/facade/impl/MaintainPerformanceMeasure.java

• Deprecated the process createPerformanceMeasure()
• Deprecated the process deletePerformanceMeasure()
• Deprecated the process listPerformanceMeasure()
• Deprecated the process updatePerformanceMeasure()
• Deprecated the process viewPerformanceMeasure()

..EJBServer/components/CPM/source/curam/
cpm/facade/impl/MaintainSOPerformanceMeasure.java

• Deprecated the process addEvaluationCriteria()
• Deprecated the process addPerformanceMeasureToServiceOffering()
• Deprecated the process addScoreOutcome()
• Deprecated the process createSOPerformanceMeasure()
• Deprecated the process deleteEvaluationCriteria()
• Deprecated the process deleteScoreOutcome()
• Deprecated the process deleteServiceOfferingPerformanceMeasure()
• Deprecated the process listEvaluationCriteriaForPerformanceMeasure()
• Deprecated the process listScoreOutcome()
• Deprecated the process listServiceOfferingPerformanceMeasure()
• Deprecated the process modifyScoreOutcome()
• Deprecated the process viewScoreOutcome()
• Deprecated the process viewServiceOfferingPerformanceMeasure()

The following java classes have been deprecated:

• ContractPerformanceMeasure.java
• ContractPerformanceMeasureAccessor.java
• ContractPerformanceMeasureDAO.java
• ContractPerformanceMeasureDAOImpl.java
• ContractPerformanceMeasureImpl.java
• PerformanceMeasure.java
• PerformanceMeasureAccessor.java
• PerformanceMeasureDAO.java
• PerformanceMeasureDAOImpl.java
• PerformanceMeasureImpl.java
• PerformanceMeasureLink.java
• PerformanceMeasureLinkAccessor.java
• PerformanceMeasureLinkDAO.java
• PerformanceMeasureLinkDAOImpl.java
• PerformanceMeasureLinkImpl.java
• PerformanceMeasureServiceEvaluationCriteria.java
• PerformanceMeasureServiceEvaluationCriteriaAccessor.java
• PerformanceMeasureServiceEvaluationCriteriaDAO.java
• PerformanceMeasureServiceEvaluationCriteriaDAOImpl.java
• PerformanceMeasureServiceEvaluationCriteriaImpl.java
• RetrieveAllContractPerformanceMeasures.java
• RetrieveAllContractPerformanceMeasuresImpl.java
• RetrieveAllPerformanceMeasuresForProvider.java
• RetrieveAllPerformanceMeasuresForProviderImpl.java
• RetrieveAllPerformanceMeasuresForProviderOffering.java
• RetrieveAllPerformanceMeasuresForProviderOfferingImpl.java
• RetrievePerformanceMeasure.java
• RetrievePerformanceMeasureForContract.java
• RetrievePerformanceMeasureForContractImpl.java
• RetrievePerformanceMeasureForProvider.java
• RetrievePerformanceMeasureForProviderImpl.java
• RetrievePerformanceMeasureForProviderOffering.java
• RetrievePerformanceMeasureForProviderOfferingImpl.java
• ScoreOutcome.jav a
• ScoreOutcomeAccessor.java
• ScoreOutcomeDAO.java
• ScoreOutcomeDAOImpl.java
• ScoreOutcomeImpl.java
• ServiceOfferingPerformanceMeasureLink.java
• ServiceOfferingPerformanceMeasureLinkAccessor.java
• ServiceOfferingPerformanceMeasureLinkDAO.java
• ServiceOfferingPerformanceMeasureLinkDAOImpl.java
• ServiceOfferingPerformanceMeasureLinkImpl.java

Performance Measure related operations have been deprecated in the following classes:

..EJBServer/components/CPM/source/curam/
servicedeliveryevaluation/impl/ServiceDeliveryEvaluationImpl.java

• Deprecated the process calculateOutcomeForServiceDeliveryEvaluation()

..EJBServer/components/CPM/source/curam/
servicedeliveryevaluation/impl/ServiceDeliveryEvaluationOutcome.java

• Deprecated the process setSOPerformanceMeasure()

..EJBServer/components/CPM/source/curam/
servicedeliveryevaluation/impl/ServiceDeliveryEvaluation
OutcomeAccessor.java

• Deprecated the process getSOPerformanceMeasure()

..EJBServer/components/CPM/source/curam/
servicedeliveryevaluation/impl/ServiceDeliveryEvaluation
OutcomeImpl.java
* Deprecated the process getSOPerformanceMeasure()

• Deprecated the process setSOPerformanceMeasure()

..EJBServer/components/CPM/source/curam/
serviceoffering/impl/SOEvaluationCriterionDAO.java

• Deprecated the process searchUnaddedSOEvaluationCriteria()

..EJBServer/components/CPM/source/curam/
serviceoffering/impl/SOEvaluationCriterionDAOImpl.java

• Deprecated the process searchUnaddedSOEvaluationCriteria()

..EJBServer/components/CPM/source/curam/cpm/impl/Module.java

• Deprecated the process bindTaxonomySearchEvents()

The following entities are now deprecated:

• ContractPerformanceMeasure
• PerformanceMeasure
• PerformanceMeasureLink
• ScoreOutcome
• SOPerformanceMeasureLink
• SOPerformMsrEvalCrtLnk

Links to Performance Measure pages have been removed from the following application configuration files, and the associated properties for those entries marked as deprecated:

• ADMINAPPSection.sec
• ADMINAPPSectionShortcuts.ssp
• CPMRMSupervisorProviderHome.nav
• ListPerformanceMeasures.tab
• ProviderHome.nav
• ProviderHomeView.nav
• ProviderHomeView.tab
• ProviderHome.tab
• ServiceOffering.nav
• ServiceOfferingTraining.nav

The following message files have been deprecated:

• ..EJBServer/components/CPM/message/PerformanceMeasure.xml
• ..EJBServer/components/CPM/message/ContractPerformanceMeasure.xml
• ..EJBServer/components/CPM/message/BusinessObjectTypeName.xml

The following code tables files have been deprecated:

• ..EJBServer/components/CPM/codetable/CT_PerformanceMeasureApplicable.ctx
• ..EJBServer/components/CPM/codetable/CT_PerformanceMeasureOutput.ctx
• ..EJBServer/components/CPM/codetable/CT_PerformanceMeasureResourceType.ctx
• ..EJBServer/components/CPM/codetable/CT_PerformanceMeasureTypeHierarchy.ctx

The following UIM / VIM pages and their associated properties have been marked as deprecated:

• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_addEvaluationCriteriaToSO
  PerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_addScoreOutcome.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_addSOPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_createFlatRateContract
  PerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_createPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_createServiceContract
  PerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_createSOPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_createUtilizationContract
  PerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_deleteEvaluationCriteriaFromSO
  PerformanceMeasure.uim
• ..webclient/components/CPM/Perfor manceMeasure/
  ProviderManagement_deletePerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_deleteScoreOutcome.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_deleteSOPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_listPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_listSOPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_modifyContractPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_modifyScoreOutcome.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_removeContractPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_searchContractPerformanceMeasurePopup.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_updatePerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_viewActualContractPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_viewActualServiceContractPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_viewPerformanceMeasure.uim
• ..webclient/components/CPM/PerformanceMeasure/
  ProviderManagement_viewSOPerformanceMeasure.uim
• ..webclient/components/CPM/Provider/PerformanceMeasure/
  ProviderManagement_addProviderPerformanceMeasure.uim
• ..webclient/components/CPM/Provider/PerformanceMeasure/
  ProviderManagement_confirmRemovePerformanceMeasure.uim
• ..webclient/components/CPM/Provider/PerformanceMeasure/
  ProviderManagement_listProviderPerformanceMeasures.uim
• ..webclient/components/CPM/Provider/PerformanceMeasure/
  ProviderManagement_viewPerformanceMeasureInfoMessages.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_addPOPerformanceMeasure.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_listPOPerformanceMeasures.uim
• ..webclient/components/CPM/ServiceEvaluationCriterion/
  ProviderManagement_listEvaluationCriterionAndPerformance
  MeasuresForAdmin.uim
• ..webclient/components/CPM/ServiceEvaluationCriterion/
  ProviderManagement_listPerformanceMeasuresForAdmin.uim

Links to Performance Measure pages have been removed from the following files and the associated properties marked as deprecated:

• ..webclient/components/CPM/Provider/Contracts/Provider
  Utilization/ProviderManagement_viewUtilizationContractForProvider.uim
• ..webclient/components/CPM/Provider/Contracts/Provider Flat
  Rate/ProviderManagement_listAttachmentForProviderFlatRateContract.uim
• ..webclient/components/CPM/Provider/Contracts/Provider Flat
  Rate/ProviderManagement_listContractsForProvider.uim
• ..webclient/components/CPM/Provider/Contracts/Provider Flat
  Rate/ProviderManagement_resolveNewContractPMForProvider.uim
• ..webclient/components/CPM/Provider/Contracts/Provider Flat
  Rate/ProviderManagement_viewAmendedContract.uim
• ..webclient/components/CPM/Provider/Contracts/Provider Flat
  Rate/ProviderManagement_viewAmendedContractAttachment.uim
• ..webclient/components/CPM/Provider/Contracts/Provider Flat
  Rate/ProviderManagement_viewFlatRateContractForProvider.uim
• ..webclient/components/CPM/Provider/Contracts/Provider Flat
  Rate/ProviderManagement_viewFlatRateContractPMForProvider.uim
• ..webclient/components/CPM/Provider/Contracts/Provider Flat
  Rate/ProviderManagement_viewFlatRateContractServicesForProvider.uim
• ..webclient/components/CPM/Provider/Contracts/Provider
  Utilization/ProviderManagement_listAttachmentForProviderUtilizationContract.uim
• ..webclient/components/CPM/Provider/Contracts/Provider
  Utilization/ProviderManagement_listUtilization
  PerformanceMeasureForAmendHistory.uim
• ..webclient/components/CPM/Provider/Contracts/Provider
  Utilization/ProviderManagement_listUtilizationProvider
  OfferingsForAmendHistory.uim
• ..webclient/components/CPM/Provider/Contracts/Provider
  Utilization/ProviderManagement_viewUtilizationContractForProvider.uim
• ..webclient/components/CPM/Provider/Contracts/Provider
  Utilization/ProviderManagement_viewUtilization
  ContractPerformanceMeasureForProvider.uim
• ..webclient/components/CPM/Provider/Contracts/Provider
  Utilization/ProviderManagement_viewUtilization
  ContractProviderOfferingForAmendHistory.uim
• ..webclient/components/CPM/Provider/Contracts/Provider
  Utilization/ProviderManagement_viewUtilization
  ContractProviderOfferings.uim
• ..webclient/components/CPM/Provider/Contracts/Utilization/
  Provider/ProviderManagement_viewUtilizationContract
  AmendmentHistoryForProvider.uim
• ..webclient/components/CPM/Provider/Contracts/Utilization/
  Provider/ProviderManagement_viewUtilization
  ContractProviderOfferingForProvider.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_listPOPlaceLimits.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_listProviderServiceOffering.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_listProviderServiceRate.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_viewProviderServiceOffering.uim
• ..webclient/components/CPM/Provider/ProviderService/
  ProviderManagement_viewProviderSOIndexes.uim

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

Financial Management

WorkItem:159370 - Deprecate the Over / Under Payment Graphical View

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

../EJBServer/components/core/model/Packages/
Presentation Layer/Product Delivery_cat.efx

• Deprecated the process getReassessmentResultsChart()

../EJBServer/components/core/source/curam/
core/facade/impl/ProductDelivery.java

• Deprecated the process getReassessmentResultsChart()

The following UIM pages and their associated properties have been deprecated:

• ../webclient/components/core/Product Delivery/Over And Under Payments/Benefit/Statement/ProductDelivery_viewBenefit
  StatementGraphicalDetails.uim
• ../webclient/components/core/Product Delivery/Over And Under Payments/Benefit/Statement/ProductDelivery_viewSingle
  ComponentBenefitGraphicalDetails.uim

The following UIM pages have been updated to remove reference to the graphical view:

• ../webclient/components/core/Product Delivery/Over And Under Payments/Benefit/ProductDelivery_listBenefitOverUnder
  PaymentBreakdown.uim
• ../webclient/components/core/Product Delivery/Over And Under Payments/Benefit/Statement/ProductDelivery_viewAllComponents
  BenefitStatement.uim
• ../webclient/components/core/Product Delivery/Over And Under Payments/Benefit/Statement/ProductDelivery_viewSingle
  ComponentBenefitStatement.uim
• ../webclient/components/core/Product Delivery/Over And Under Payments/Benefit/Statement/ProductDelivery_viewSingle
  ComponentBenefitStatementNoBreakdown.uim

The following BIRT reports have been deprecated:

• ..BIContent/components/core/CaseFinancial/
  AllComponentsGraphicalBenefitStatement.rptdesign
• ..BIContent/components/core/CaseFinancial/
  SingleComponentGraphicalBenefitStatement.rptdesign

The references to the above reports in the following DMX file have been marked as deprecated:

• ..EJBServer/components/core/data/initial/
  BIREPORTCONFIGURATION.dmx

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

Solutions

Income Support

MEDICAL ASSISTANCE

WorkItem:161693 - Deprecate HCR Intake Reports

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies you have on any of the deprecated APIs or artifacts as the feature may be removed in a future release.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

The following java classes have been deprecated:

../EJBServer/components/HCR/source/curam/
dashboard/impl/DashboardConst.java

The following client pages and their associated properties have been deprecated:

• ../webclient/components/HCR/Dashboard/
  HCRIntakeReports.uim
• ../webclient/components/HCR/Dashboard/
  HCRIntakeReportWarningPage.uim

The following application configuration file and its associated properties has been deprecated:

• ../EJBServer/components/HCR/tab/ApplicationViews/Admin/HCRIntakeReportsTab.tab

Links to HCR Intake Reports pages have been removed from the following application configuration files, and the associated properties for those entries marked as deprecated:

• ../EJBServer/components/HCR/tab/ApplicationViews/
  Admin/ADMINAPPSection.sec
• ../EJBServer/components/HCR/tab/ApplicationViews/
  Admin/ADMINAPPSectionShortcuts.ssp
• ../EJBServer/components/HCR/tab/ApplicationViews/
  Admin/HCRIntakeReportsTab.tab
• ../EJBServer/components/HCR/tab/ApplicationViews/
  Admin/ADMINAPPSection.sec

The following css files have been deprecated:

• ../webclient/components/HCR/css/ExecDashboard.css

The following BIRT reports and their corresponding property files have been deprecated:

• ../BIContent/components/hcr/executive/HCRApplicationsReceived.rptdesign
• ../BIContent/components/hcr/executive/HCRApprovedPrograms.rptdesign
• ../BIContent/components/hcr/executive/HCRIncomingApplications.rptdesign
• ../BIContent/components/hcr/executive/HCRInterventionRequired.rptdesign

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

Dynamic Evidence

WorkItem:115678 (was previously CDP-1458) - Case evidence export mishandles "0" Date / DateTime values

Dynamic Evidence reporting feature is serializing zero date values incorrectly. Evidence date attributes with zero date values are currently serialized with the date element value set to "0001-01-01" in the generated xml report, i.e. <dateAttribute>0001-01-01</dateAttribute>. Empty evidence dates should be serialized without any value, i.e. <dateAttribute/>.

Integrated Case Management

WorkItem:123357 (was previously SPMP-15534) - Evidence shared from Person to case, is accepted but not activated on the case, modifying this evidence prior to activation will not share this modification back to Person

An issue exists at present with evidence that is shared from Person level to case(s). If the evidence shared from Person evidence to a case is not activated on the case, and that shared evidence is modified within that case prior to activation, the updated evidence is not shared back to Person evidence.

For example; if address evidence is configured for sharing from Person to an Integrated Case with auto-activate disabled and auto-accept enabled. On capturing a new address for a client at Person level, the address is shared to the Integrated Case and automatically accepted onto the In-Edit evidence list on that case. If a case worker modified the In-Edit address within the Integrated Case and activates this change, this address update is not shared back to Person evidence.

To work around this issue, customers have two options.

• Case workers should activate incoming evidence that has been accepted on to the case from Person evidence
• Customers can configure the evidence sharing between the Person evidence to other cases with both auto-activate and auto-accept enabled

Application Development Environment

WorkItem:37987 (was previously TEC-18014) - CDA Assessment Decision Matrix application timeout error

When an administrator is configuring a CDA assessment in Outcome Management, the Decision Matrix displays a wizard to assist the user for creating the matrix. The wizard throws a timeout error, which prevents it from being used. The workaround available is to click OK when the application timeout error appears, select the Cancel button on the wizard and then use the Questions, Outcome and Options button to create the matrix.

Provider Management

WorkItem:103350 (was previously CPM-2415) - Incorrect underpayment amount created when multiple service invoice line items reassessed due to change in service rate

When there are multiple service invoice line items created and paid for a provider using a fixed amount service rate and payment option of 'pay fixed amount', if the service rate that was used to determine the payment amount is retrospectively modified, e.g. to a higher rate, underpayments are not being generated for all of the affected service invoice line items.

Universal Access

WorkItem:152523 - Error while configuring an Application Case with Application Authorization and Integrated Case

An error message is displayed when an application case is configured in administration with application strategy as 'Application' and an integrated case. The error is not displayed while configuring an application case with outcome plan. It is displayed only while configuring an application case with integrated case.

Outcome Management

WorkItem:114547 (was previously CC-1100) - Sysadmin property 'curam.outcomeplanning.referralForAgreementDays' is not working as expected

Outcome Management provides the ability to create agreements where the client(s) can agree in writing to adhere to the activities (services, referrals and actions) that form part of the agreement. A system property exists to filter out referral type activities during the agreement creation process based on a number of days from when the referral was created. This property is currently not being considered when creating an agreement. To work around this issue, the user can view the start date of the referral on the create agreement wizard to determine whether the referral should form part of the agreement.

WorkItem:115188 (was previously CC-930) - Incorrect Activity Responsibility setting when a plan is automatically created by the system.

In certain scenarios, an activity will have an incorrect responsibility setting, in that the responsibility will be set to ‘system’ instead of the appropriate user. The issue occurs for a specific set-up where:

• ‘Enable Automatic Population of Outcome Plans’ system property is set to true; and
• Outcome Plan is created automatically from referral processing; and
• An action which is configured to be automatically added, has been configured so that the responsibility is assigned to a user.

To work around this issue, the responsibility for the actions that are automatically added should be set to 'Any User', so that the planner user can edit the responsibility field when the action is added to the plan and change the responsibility from 'System' to the appropriate user.

WorkItem:148405 - Outcome Plan Activity Workspace does not refresh and display the newly created Action

When a new action is created from outcome plan activity workspace, the created action is not displayed on the workspace as the workspace does not get refreshed automatically. The workaround available is to refresh the workspace manually to see the action.

Evidence Broker

PO06452, WorkItem:172498 - Identifications evidence not brokering from the Person record to Incoming Evidence list of the Insurance Affordability Integrated Case when In-Edit version of SSN Details already exists on the Integrated Case

An issue exists with the non-identical evidence flow. When an Identifications evidence is modified at the Person level, and the target case already had and in-Edit and Active version of SSN Details evidence. The newly updated Identifications information does not broker over to the target case.

Identity Intelligence

WorkItem:179932 - UMFData.owner index is too large to support multibyte expansion

The UMFData database table has an index on the owner field. This index is currently too large to support multibyte expansion on DB2 in a z/OS environment and will not get created.

This is only an issue when running against DB2 for z/OS, where multibyte expansion is enabled.

Solutions

Income Support

WorkItem:67450 (was previously HCR-8548) - Add/Remove: When the primary applicant is deleted on the Application Case, a product delivery case cannot be created for the remaining household members.

When a household member who is designated as the Primary Applicant (and hence Primary Client) is deleted from the Application Case by deleting the corresponding Application Details evidence, the case participant role for the member is not changed to 'Other'. On authorization the IC is created with the deleted member as a Member. The evidences for the deleted member are brokered over to the ongoing IC. This is an issue and the eligibility determination on the IC fails and PD cases are not created.

Notices

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