Document Information
More support for:
Merative Social Program Management
Software version:
7.0.6
Operating system(s):
Linux, Windows
Modified date:
21 March 2019
Merative ™ Social Program Management 7.0.6.0 Refresh Pack
Merative ™ Social Program Management is now Cúram ™ by Merative™
Release Notes
Abstract
Merative Social Program Management 7.0.6.0 Refresh Pack Release Notes
Content
Introduction
System Requirements
Download
Installation
Improvements, Resolved Issues and Third Party Updates
Known Issues
Notices
Merative Social Program Management 7.0.6.0 is a Refresh Pack.
Welcome to the Merative Social Program Management 7.0.6.0 Refresh Pack release. Read this document to find important installation information, and to learn about product improvements and resolved issues in this release.
This 7.0.6.0 Refresh Pack release includes new Universal Access functionality. For detailed information about these new features, see the What's new in Version 7.0.6.0 topic in the product documentation.
For more information about version 7.0.6.0 Refresh Pack, see the full product documentation in documentation.
For the latest version of the release notes, see https://curam-spm-devops.github.io/wh-support-docs/spm/release-notes.
A CSV file is attached at the end of this document, which summarizes these release notes.
For information about the supported software and hardware for this release, see the Merative Social Program Management Prerequisites.
Prior to running the installer please ensure all files in your Merative Social Program Management installation are writable.
The installation steps are as follows:
Additional installation instructions can be found in the Development Environment Installation Guide.
Upgrading
If you are upgrading from a previous version, the Merative Social Program Management Upgrade Helper contains documentation and tooling to help you to upgrade your Merative Social Program Management application codebase and database to work with your new version of Merative Social Program Management. The Merative Social Program Management Upgrade Guide describes a recommended process for performing application and database upgrades. The Upgrade Helper contains tools to assist you with implementing the upgrade, including tooling to produce a schedule of required migrations for your upgrade, tooling to provide information about database schema changes and tooling to generate initial SQL scripts for applying changes to your database.
To download the appropriate version of the Merative Social Program Management Upgrade Helper, see the download instructions at https://www.merative.com/support/spm.
Improvements, Resolved Issues and Third Party Updates
Third Party Updates
Cúram Enterprise Framework
Cúram Modules
Solutions
WorkItem:241548 - Browser Support Update
The following browser versions have been updated and certified for this release:
Case Worker Application Browser Support
Universal Access Application Browser Support
WorkItem:241552 - Upgrade Adobe Flash Player to the latest version
The version of the Adobe Flash Player that has been certified to be used by the Social Program Management (SPM) application has been updated to 32.
WorkItem:243946 - Update Browser Plugins JRE levels used in Microsoft Word Integration
The following JRE level for Word Integration is supported for this release:
WorkItem:243952 - Tablet Accessibility Support - Certify Apple VoiceOver with Chrome 72 on iOS 12.1.4
The certified version of Apple VoiceOver has been updated to iOS 12.1.4. This has been certified against Chrome 72.
Technical Services
Integrated Case Management
Administration Suite
Application Development Environment
Business Services
PO07832, WorkItem:232364 - Import Workflow Process Version modal fails to close when the Overwrite Existing Workflow Process checkbox is selected
Issue Description:
When the Overwrite Existing Workflow Process checkbox is ticked in the Import Workflow Process Version modal and the user clicks the Import button, the modal fails to close properly.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
This issue was resolved by updating the related UIM page.
Technical:
The issue was resolved by updating the Javascript ACTION, closeDialogRefresh, on the following UIM page to pass an argument rather than an event:
Eligibility & Entitlement
Evidence Management
Participant Management
PO07970, WorkItem:238973 - Some fields are misaligned while editing an integrated case note
Issue Description:
When editing an integrated case note, some fields are misaligned in the Edit Note modal.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
This issue has been resolved by adjusting the field widths in the underlying VIM. The fix will apply to all pages using that VIM page.
Technical:
The VIM page that was updated is Case_modifyNoteView1.vim.
PO07102, WorkItem:194618 - IndexOutOfBounds exception thrown inside CaseReassessment
Issue Description:
An issue occurs during the reassessment of CREOLE based cases whereby an IndexOutOfBounds exception is thrown when accessing the list of decisions belonging to a period that is no longer covered by the case start and end dates, primarily because the period of certification is moved back or forward in such a way that there is no overlap between the new certification period and the old certification period. The issue manifests itself on a subsequent reassessment of the case, when the case is made ineligible, for example.
User Interface Impact: No
Steps to Reproduce:
Prerequisite:
Scenario (Generic)
Resolution:
The logic for retrieving the decisions associated with each reassessment period has been updated to handle business scenarios where a period is being included that is no longer covered by a current (up-to-date) decision. In this instance, the previous decisions that would have been included for that period are included.
PO08067, WorkItem:242057 - Excess overpayments displayed in the overpayment header from previous periods
Issue Description:
An incorrect reassessment amount is calculated when a gap exists between two eligible periods that have been paid. When the first eligible period is reassessed to give an overpayment and a subsequent reassessment occurs at the start of the second eligible period, another overpayment is created for that (later) period. It is this later overpayment that contains an incorrect overall amount.
User Interface Impact: No
Steps to Reproduce:
Resolution:
One of the key aspects of the reassessment engine when a change of circumstance occurs retrospectively is the determination of the set of dates over which the case must be reassessed. The next key consideration is the processing of these dates in pairs so that the actual financial line items covering those periods are successfully determined. These dates essentially make up the detail that can be found in the 'Actuals' column on the reassessment statement. There was a defect in the handling of those dates as pairs for a period which directly preceded an ineligible period. This resulted in the period being considered twice. The logic has been updated to prevent this from happening and the reassessment amount is now calculated correctly for the above scenario.
PO08020, WorkItem:240550 - Update with Incoming wizard throws an error with incorrect evidence date '01/01/0001' shown
Issue Description:
Updating with Incoming correction was incorrectly using the incoming evidence's effective date to verify the integrity of the expected timeline for all evidence in a timeline. However for the first record in a timeline where no effective date is populated, it should instead use the period start date. This resulted in an incorrect validation message occurring using the null effective date in the message.
User Interface Impact: No
Steps to Reproduce:
Resolution:
The validation has been updated to use either period start date or effective date as appropriate when validating the integrity of the expected timeline. If an effective date exists on the evidence it will be used. If no effective date exists on the evidence, in the scenario of initial record in a succession, the evidence period start date will be used instead. This results in the error message no longer occurring in this scenario and the correction can be performed.
PO08056, WorkItem:241879 - Adding new evidence from the External System category in an integrated case’s evidence dashboard results in an un-handled server exception
Issue Description:
When a user tries to add an evidence using the 'New Evidence' dialog from the Evidence tab of an integrated case, they are able to select an evidence displayed under the External System category even though it is configured as read-only. When the user tries to save this evidence, an un-handled server exception is thrown and the Evidence dashboard is no longer accessible. The 'New Evidence' dialog should filter out read-only evidences under the External System category so they are not available for selection, similar to other evidence type categories.
User Interface Impact: No
Prerequisites:
Steps to Reproduce:
Resolution:
The evidences under the External System category are no longer available for selection in the 'New Evidence' dialog when they are configured as read-only, and are now filtered in the API that populates the 'New Evidence' dialog.
PO08109, WorkItem:243150 - Modals become unresponsive when the Add Evidence and Transfer Evidence menu options are invoked
Issue Description:
There was an issue using the Add Evidence and Transfer Evidence menu options on the Evidence Dashboard. Once these menu options were launched, it caused a responsiveness problem across modals. These specific actions could be launched a second time in the same browser session but not a third time. Other actions would no longer launch. List pages continued to work and display data, and modals could be launched if the application was refreshed, but the lack of responsiveness affected caseworkers managing evidence.
User Interface Impact: Yes
Steps to Reproduce:
Scenario 1
1. Login as a caseworker.
2. Register a new Person.
3. Create an integrated case for the Person.
4. Open the Evidence tab.
5. Go to the actions menu and click on 'New Evidence'.
6. Add new evidence of type Address.
7. Repeat a second time; add another evidence record of type Address.
8. Issue: On the third time of adding a new evidence record, the modal doesn't open.
Scenario 2
1. Login as a caseworker.
2. Register a new Person.
3. Create an integrated case for the Person.
4. Open the Evidence tab.
5. Go to the actions menu and click on 'New Evidence'.
6. Add new evidence of type Address.
7. Issue: Now attempt to launch the Validate Changes modal from the menu option. The modal doesn't open.
Resolution:
This issue has been resolved by adding a new listener to submit the form when the page is loaded.
Technical:
The following javascript files have been updated to include a new listener to submit the form when the page is loaded.
PO07938, WorkItem:238135 - Context Panel is not updated automatically after editing Person address evidence
Issue Description:
When a caseworker updates a Person's address evidence and changes the address that should be considered as the Preferred address, the Context Panel is not automatically updated to display the new Preferred address.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has been resolved by automatically refreshing the context panel associated with the Person and ProspectPerson tabs when evidence is added.
Technical:
The following entries have been added to both the Person and ProspectPerson tab files:
PO07435, WorkItem:209842 - Scroll bar overlapping time field in the New Recurring Organization Activity screen
Issue Description:
The vertical scroll bar on the 'New Recurring Organization Activity' modal overlaps with the time field in the modal.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
This issue has been resolved and the user is now able to see the time field and its value without any overlapping of the vertical scroll bar.
Client Development Environment
Server Development Environment
PO07914, WorkItem:237058 - Description of the ScanMilestoneDeliveryEndDate batch job is incorrect in the Knowledge Center
Issue Description:
The ScanMilestoneDeliveryEndDate batch job was incorrectly described in the Knowledge Center.
The previous documentation text said that the batch job "Searches the system for all milestone deliveries which have a status of 'Not Started' and where the earliest start date has passed", which was incorrect. The batch job instead looks for milestone deliveries where the status is not 'Completed' and the earliest 'Expected End Date' has passed.
User Interface Impact: No
Steps to Reproduce: N/A
Resolution:
The description text of the ScanMilestoneDeliveryEndDate batch job has been updated to state that it searches the system for all milestone deliveries where the status is not 'Completed' and where the earliest 'Expected End Date' has been reached. It now also mentions that the batch job raises an event to notify the case owner of all milestone deliveries where the status is not 'Completed' and where the earliest 'Expected End Date' has been reached. Find more information at: https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation
Accessibility
Look & Feel
Miscellaneous
PO07428, WorkItem:208140 - Text area moves unexpectedly on mouse over
Issue Description:
The text area input field across the application moves slightly when the user hovers over the text area or tabs to this text area.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
This issue has been resolved by updating the CSS styling on this text area.
PO07719, WorkItem:226453 - Menu separators on are not visible in Internet Explorer 11
Issue Description:
The menu separators that display on an actions menu are not visible in Internet Explorer 11.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
This issue has been resolved by updating the relevant CSS styling.
PO08100, PO08101, WorkItem:243601 - When printing inline pages containing tables, if the print preview includes a page break, the table header(s) are not being displayed on the top of the second page
Issue Description:
There was an issue printing an inline page containing a table which spanned beyond one page in length. The headers of the table which were displayed on the first page were not displayed at the start of the second page.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has been resolved by ensuring a table heading will be repeated at the top of the next page when a page break occurs within the content of the table.
PO08099, WorkItem:243602 - Overlapping first row when printing an Assessment Questionnaire
Issue Description:
There was an issue printing an Assessment Questionnaire which had enough questions to span onto a second page. The first row (question) on the second page overlapped the header on the second page. This could be seen on both the Google Chrome and Internet Explorer browsers.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has since been resolved by ensuring question rows break correctly between pages when printing.
PO07956, WorkItem:243603 - When printing expanded evidence the details displayed are truncated
Issue Description:
When using the page level Print icon to print a list of evidence details, certain information was missing. When the evidence was expanded to display the full details, only the header information was printed. No information from the evidence details page was printed.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has been resolved by adding specific styling for evidence pages when they are printed. This ensures all the visible evidence information is printed correctly.
PO07752, WorkItem:228026 - JAWS consistency issue when selecting the Month in the Calendar
Issue Description:
The JAWS screen reader announces the month list from the Date Selector component in an inconsistent manner.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has been resolved by making JAWS read the month list consistently by the order that it will be displayed on the list. The Month field was redesigned to address the accessibility issue. Now, the user can search for specific options by typing the first letter(s) of a matching option when the drop-down menu is opened.
WorkItem:239512 - Tablet Accessibility: When using screen reader drop-down list does not close when navigating away
Issue Description:
A user using a screen reader in the mobile (tablet) environment might unintentionally navigate from the drop-down selection list without closing it and it can remain open on the page.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
The drop-down accessibility in the mobile environment has been improved so that the user is now informed by the screen reader that they have reached the beginning or end of the choices in the list and instructed to either close the list or return to it.
Technical:
Two new localizable properties have been introduced to inform the user if they have reached the end of the selection list in a drop-down:
These properties are localized in the same way as other entries in CDEJResources.properties.
PO08042, WorkItem:241183 - JAWS screen reader instruction to 'Press tab to activate the modal' on a modal window is causing confusion
Issue Description:
When opening a modal dialog in the application, the JAWS screen reader reads out the text 'Press tab to activate the modal' after the modal link has been clicked. This results in the second field of the modal being in focus.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This has been resolved by removing the message 'Press tab to activate the modal' so that the user isn't prompted to press the tab key, thereby resulting in the focus remaining on the first field of the modal.
PO08044, WorkItem:241236 - JAWS screen reader reads frame titles as 'undefined'
Issue Description:
Some user interface frame titles in the application are read as 'undefined' by the JAWS 2018 screen reader.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
This issue has been resolved by updating the JavaScript code concerning the title of the content panel in screens that contain in-page navigation links.
PO07292, WorkItem:202569 - Unable to set 12 hour time format in the Calendar view
Issue Description:
When the CalendarConfig DAY_VIEW_TIME_FORMAT is set to 12, the time displayed is in 24 hour format. The time should be displayed in the Calendar in 12 hour format hh:mm with either AM or PM.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
This issue has been resolved and the time now displays in the Calendar in 12 hour format hh:mm with either AM or PM.
Technical:
Sample CalendarConfig.xml code:
<CALENDAR TYPE="User">
<DESCRIPTION_LOCATION>Activity_resolveViewStandardUserActivityPage.do</DESCRIPTION_LOCATION>
<CREATE_LOCATION>Activity_resolveCreateUserActivityPage.do</CREATE_LOCATION>
<DAY_VIEW_TIME_FORMAT>12</DAY_VIEW_TIME_FORMAT>
</CALENDAR>
PO07861, WorkItem:234386 - Special characters such as quotes and the ampersand (&) are escaped in Announcement messages
Issue Description:
Announcements allow the agency to set an application-wide message that can be displayed on an application home page for a set period.
When an Announcement contains text which has special characters, single-quotes ('), double-quotes (") or an ampersand (&), for example, they are shown as escaped when rendered in the browser. That is, they appear as \’, \”, and \u0026, respectively.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
Special characters entered for an Announcement are no longer escaped when viewing the Announcement message on an application home page. That is, the message appears as it was entered on the 'New Announcement' dialog.
PO07750, WorkItem:238882 - Additional ellipses are being shown in the Open Task actions menu
Issue Description:
Additional ellipses are being shown in the Open Task actions menu in the user's inbox.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
This issue is now resolved and the user sees three ellipses as expected for the menu items.
PO07986, WorkItem:239756 - The pop-up that displays information about a holiday renders the label Holiday over multiple lines
Issue Description:
In the Administration Workspace, when adding a New Location Holiday the label and holiday name entered are word-wrapped onto separate lines.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has been resolved and the label Holiday and the name of the holiday are now aligned.
PO07665, WorkItem:215828 - File not found error while accessing CaseWorkerCustomHome page
Issue Description:
The image file 'digit/themes/tundra/images/validationInputBg.gif' is referenced but cannot be found resulting in a File not found error in the server logs while accessing the CaseworkerCustomHome page.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has been resolved by removing the dependency on the stylesheet referencing the file 'digit/themes/tundra/images/validationInputBg.gif'.
Technical:
The issue can also be seen in the Application Server logs while accessing the CaseworkerCustomHome page. For example, the following error is seen in WebSphere's stdout, stderr, and ffdc logs:
SRVE0190E: File not found: /CDEJ/jscript/dojotk/dijit/themes/tundra/images/validationInputBg.gif
PO08009, WorkItem:235065 - Support for special characters viewed through the Notes History page
Issue Description:
Case Notes are typically created in the application as a result of using the Rich Text Editor. Therefore the manipulation of the data in the Case Notes functionality, for both the storage and the viewing of such notes, is tailored for use with that editor in that the data is expected to be in the format specific to data entry through the Rich Text Editor. An issue arose for a customer who used an alternative mechanism to input a case note. A custom screen contained a text input field which was designated as a standard Comments field at the screen level, but on the server side was stored as a Note. When the text entered via the Comments field and stored as a Note contained a special character such as '&' or '$', it was not stored in the format that was compatible with the manipulation of Case Notes data. This meant it was not displayed correctly when reading back from the database and viewed through the Notes History page.
User Interface Impact: No
Steps to Reproduce:
Note: As the scenario which resulted in this issue did not follow the expected usage of Case Notes infrastructure, there are no examples of this issue in the out-of-the-box Platform application. To reproduce the issue:
Resolution:
This issue has now been resolved and the Notes History page correctly displays comments which include special characters such as '&' or '$'.
Technical:
WorkItem 240981 introduced the Jsoup library into the Social Program Management application. This library enables improved handling of HTML documents and strings. This ticket updated the Notes History Renderer code to make use of these new classes. Data entered as Notes but without using the Rich Text Editor is now in a format that is compatible with being displayed on the Note History screens.
PO08059, WorkItem:241886 - Clarify in the Communication Guide what special characters cannot be used to populate Microsoft Word Templates
Issue Description:
The File Edit widget feature has a limitation as to the special characters that can be used to populate Microsoft Word Templates. Documentation stated that the data content that is passed to the template to populate the variables is limited to only alphanumeric characters.
User Interface Impact: No
Steps to Reproduce: N/A
Resolution:
The documentation has been updated to list the characters that are not permitted. Find more information at: https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation
Calendaring/Scheduling
Task Management
PO07755, WorkItem:228286 - Usernames with numeric characters causing unhandled server exception in a meeting invite
Issue Description:
When a user with one or more numeric characters in their username is added to a meeting invite, an unhandled server exception occurs.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has been resolved by allowing users to have usernames which contain numeric characters.
PO01124, WorkItem:238956 - Unexpected error on the 'My Tasks', 'Available Tasks', 'Recent Notifications' and 'Work Queues' Pods
Issue Description:
An error is displayed on the Available Task, My Tasks, Recent Notifications and Work Queues Pods when special characters such as []{} are inserted in the subject field.
User Interface Impact: No
Steps to Reproduce the My Tasks Pod issue:
Steps to Reproduce the Available Tasks Pod issue:
Steps to reproduce 'Recent Notifications' Pod issue:
Steps to Reproduce 'Work Queues' Pod issue:
Resolution:
This issue has been resolved and tasks, recent notifications and work queues with special characters such as []{} in the subject now appear in the appropriate Pods on the home page without any errors.
Outcome Management
Universal Access
Intelligent Evidence Gathering
PO07743, WorkItem:227821 - New Referral wizard pages contain a number of formatting issues
Issue Description:
When creating a new referral within an outcome plan, pages in the New Referral wizard contained a number of formatting issues.
User Interface Impact: Yes
Steps to Reproduce:
The Referred By Me, Warning Days, and Phone number area code input fields are too narrow to display the appropriate length of input text. Additionally, the Address field labels are too narrow to display the label text.
Resolution:
The formatting issues were resolved by updating the layout of the relevant UIM pages and CSS styling.
PO07747, WorkItem:227931 - Highlight Differences and Clear Differences buttons incorrectly close Compare modal when comparing two assessments
Issue Description:
When running a comparison between two selected assessments from the Compare Modal page, when either the Highlight Differences or Clear Differences button was clicked, the modal unexpectedly closed down. Some other issues found on this page were that:
User Interface Impact: No
Steps to Reproduce:
Resolution:
Now, when a comparison is run for two assessments, the Highlight Difference and Clear Differences buttons no longer close the modal. The result page does not highlight differences automatically. When the Highlight Differences button is clicked by the user, the differences in the comparison results are now highlighted. Also the Clear Differences button has also been fixed, removing any highlighted rows effected. The Close button is now working as expected, closing the modal on the first attempt even after the Reset button has been used.
PO07940, WorkItem:238220 - Validation error on an Outcome Plan's Record Scheduled Attendance or Record Absence Period modal results in the Client dropdown list becoming empty
Issue Description:
Within an Outcome Plan, the drop-down for the Client field gets cleared when any validation is thrown on the Record Scheduled Attendance and Record Absence Period modals.
User Interface Impact: No
Steps to Reproduce:
Resolution:
The participant values in the Client drop-down fields are now retained when a validation error occurs on the Record Scheduled Attendance and Record Absence Period modals that are initiated from within an Outcome Plan.
Technical:
Custom Javascript controls what gets displayed in the participants drop-down on both the Record Scheduled Attendance and Record Absence Period modals. This was getting reset when validations were thrown, as the respective pages reload. This issue has been resolved by updating the Javascript method calls to the ONLOAD events to the following UIM pages:
PO08021, WorkItem:241404 - Unable to withdraw the current user's application
Issue Description:
Users are unable to withdraw their own previously submitted applications through the Citizen Portal.
User Interface Impact: No
Steps to Reproduce:
Resolution:
The withdraw application functionality has been updated to remove a validation that was preventing a user from withdrawing their own submitted applications.
WorkItem:244981 - Universal Access Responsive Web Application: When using a codetable hierarchy question in a List, the code is displayed instead of its value.
Issue Description:
When using a codetable hierarchy question in a List, the code is displayed instead of its value. This only affects users of the Universal Access Responsive Web Application.
User Interface Impact: No
Steps to Reproduce:
Resolution:
When using a codetable hierarchy question in a List, the value is now correctly displayed.
WorkItem:244982 - Universal Access Responsive Web Application: Issue with trailing zeros not displaying in field amounts
Issue Description:
Zeros at the end of decimal numbers are not displayed after navigating back to the page. This only affects users of the Universal Access Responsive Web Application.
User Interface Impact: No
Steps to Reproduce:
Resolution:
Trailing zeros are now correctly displayed.
WorkItem:244983 - Universal Access Responsive Web Application: IEG menus are showing incorrect values when the codetable domain name is duplicated.
Issue Description:
Menus are showing incorrect values when the codetable domain name is duplicated. This only affects users of the Universal Access Responsive Web Application.
User Interface Impact: No
Steps to Reproduce:
Resolution:
IEG menus are now showing the correct values when the code table domain name is duplicated.
WorkItem:245044 - Universal Access Responsive Web Application: Concurrent access to list on a page throwing Exception
Issue Description:
When an IEG script is running for two different users at the same time and a page that contained a list was accessed simultaneously, an error may result with no way to recover except to restart the JVM. This only affects users of the Universal Access Responsive Web Application.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue is now resolved and multiple users can complete forms at the same time as expected.
WorkItem:245242 - Universal Access Responsive Web Application: Unsupported field schema error on read-only array questions
Issue Description:
When accessing an IEG script containing a read-only array question a parser error is thrown. This only affects users of the Universal Access Responsive Web Application.
User Interface Impact: No
Steps to Reproduce:
Resolution:
Read-only array questions are now displayed correctly.
WorkItem:245243 - Universal Access Responsive Web Application: Unable to distinguish between multiple household members
Issue Description:
When adding multiple house members in Universal Access is it not clear which person you are entering details for. This only affects users of the Universal Access Responsive Web Application.
User Interface Impact: No
Steps to Reproduce:
Resolution:
Adding a household member and their details was enhanced to make it clearer who still needs to be added. On the household page, the current household members and their ages are now listed. Household members are displayed in the order in which they were added. While you are adding details for a household member, their name and age are displayed.
WorkItem:245244 - Universal Access Responsive Web Application: Codetable Hierarchy support
Issue Description:
Codetable hierarchies are not supported in the Universal Access Responsive Web Application.
User Interface Impact: No
Steps to Reproduce:
Resolution:
You can now use two-level code-table hierarchies in questions. Any question where the data type is a code table is displayed as two separate questions in vertically aligned drop-down menus. The first question menu corresponds to the root code table in the hierarchy, and displays the label that is specified for the question. The second question menu corresponds to the second-level code table in the hierarchy, and displays a label that corresponds to the code table display name. The second menu is disabled until a selection is made in the first menu. Summary pages display both questions. Displaying a code-table hierarchy value in a list, or the codetable-hierarchy-layout options, are not supported.
WorkItem:245245 - Universal Access Responsive Web Application: Argument substitution in message text fails when the placeholder type is ‘%1d’.
Issue Description:
Date values are not substituted correctly in the message text when the placeholder type is "%1d". This only affects users of the Universal Access Responsive Web Application.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This has now been resolved and date values are substituted correctly.
WorkItem:245246 - Universal Access Responsive Web Application: Issue with the Next and Save & Exit buttons on summary pages
Issue Description:
It is not possible to navigate to the next page by using the ‘Next’ or ‘Save & Exit’ buttons if an attribute has been defined using a custom domain definition derived from IEG_INT32. This only affects users of the Universal Access Responsive Web Application.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has now been resolved and columns with type Integer are converted to type String for lists in summary pages.
PO07565, WorkItem:216550 - Mandatory fields are accepting blank spaces in an IEG script
Issue Description:
The IEG scripts with name and address fields allow a single blank space character to be entered into a mandatory field which was accepted as a valid character.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has been resolved by adding a new domain-specific condition to check if the mandatory field contains a single blank space. Please note that if there is a custom validation in place this change will take precedence over it.
PO08084, WorkItem:242529 - IEG conditional question responses are not cleared and drop-down field is displayed with the previous value
Issue Description:
In an IEG script, drop-down fields within a conditional cluster retain a previously selected value after they are hidden by closing their parent conditional cluster.
This issue can be seen when running an IEG script through the internal Merative Social Program Management application. It occurs when a user navigates back to an IEG script page displaying a drop-down which stores a previously selected value.
User Interface Impact: No
Health Care Reform Steps to Reproduce:
Prerequisite for Non Healthcare Reform Customers: If you are a customer who does not use the Healthcare Reform Solution, but have configured Intelligent Evidence Gathering scripts as an Intake mechanism, you can reproduce this scenario by configuring a valid Intelligent Evidence Gathering script and adding the following to a 'question-page' display element.
Non Healthcare Reform Steps to Reproduce:
Resolution:
This issue has been resolved by ensuring the value of a drop-down within a conditional cluster is cleared each time it is hidden as a result of a user action.
Income Support
Child Welfare
Child Welfare SDM
PO07833, WorkItem:232547 - Not all Tax Filers are displayed for selection on Tax Dependent Information page when a household has a tax dependent and married couple who change their 'filing jointly' response to 'No' after completing Tax Dependent Information
Issue Description:
Not all Tax Filers are displayed for selection at the bottom of the Tax Dependent Information page when the household has a tax dependent (e.g. child) and a married couple who change their 'filing jointly' response from 'Yes' to 'No'. The expected behaviour is both Mother and Father should be available for selection there.
User Interface Impact: No
Steps to Reproduce:
Resolution:
Both relevant tax filers are now appearing for selection when the Child Dependent question on tax income is asked.
Technical:
There is a custom function - updateSpouseInformation() in CustomFunctionUpdateFilingTogetherInformation.java. It sets filing jointly status for spouses when 'Yes' or 'No' is selected on the Married Couple Filing Status page. This condition has been fixed to allow the correct selection for this scenario.
PO08065, WorkItem:241938 - Reports section is incorrectly displayed when the Business Intelligence and Analytics for Income Support component is not installed
Issue Description:
The Reports section in the Income Support application was incorrectly displayed when the Income Support component was installed without the Business Intelligence and Analytics for Income Support component.
User Interface Impact: No
Steps to Reproduce:
Resolution:
The Reports section no longer displays in the Income Support application when the Income Support component is installed without the Business Intelligence and Analytics for Income Support component.
Technical:
The reported problem has been resolved by removing the reference to IS Reports from the following application file:
and creating a new application file referencing the IS Reports section in the IncomeSupportBI component
PO07710, WorkItem:226280 - Address Evidence Preferred indicator not set on the integrated case and application case
Issue Description:
When an Insurance Affordability application was submitted, the preferred address attribute was not set correctly in 'Private Address' evidence.
User Interface Impact: No
Steps to Reproduce:
Resolution:
The preferred address attribute wasn't set during the evidence mapping. The preferred address attribute is now set correctly.
PO07923, WorkItem:237723 - CCV does not load from context panel list view for child welfare Investigation, Ongoing and Adoption cases
Issue Description:
The Citizen Context Viewer (CCV) is not opening in the Context Panel list view for the Investigation, Ongoing and Adoption Child Welfare cases.
User Interface Impact: No
Steps to Reproduce:
Resolution:
This issue has been fixed and the CCV now launches in the Context Panel list view for the Investigation, Ongoing and Adoption Child Welfare cases.
WorkItem:238971 - Incorrect Visit Type displayed when modifying Medical Visit information
Issue Description:
When a Medical Visit is edited for a Person, Developmental Assessment always displays as the Visit Type regardless of the Visit Type that was saved initially.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
This issue is now resolved and the Visit Type previously saved is displayed when the caseworker selects to edit the Medical Visit.
Techical:
The following page has been updated so that the Visit Type is taken from the DISPLAY phase bean rather than being treated like it was on a create page and being attached to the ACTION phase bean:
PO08033, WorkItem:240897 - SDM Screening Assessment Questions Missing
Issue Description:
The screening assessment script for a Structured Decision Making (SDM) Child Welfare caseworker is missing the question labels for questions 1, 3, 5, 6, 7, 8 & 12.
User Interface Impact: Yes
Steps to Reproduce:
Resolution:
The missing question labels have now been configured correctly for the screening assessment script.
CSV Release Notes
This CSV file summarizes the individual release notes documented above in the "Improvements, Resolved Issues and Third Party Updates" section. The individual release notes documented above will be maintained and will reflect the latest version of the release notes from eGA onwards. However, the content of this CSV file is valid on eGA date, but is not maintained after that.
Document Information
More support for:
Merative Social Program Management
Software version:
7.0.6
Operating system(s):
Linux, Windows
Modified date:
21 March 2019