penelope case management software Penelope v4.8.2.0 Release Notes EDGE athena software
Table of contents About this release... 3 What is an Edge Release?... 3 What is a Long Term Release?... 3 Technology upgrades... 4 Penelope enhancements... 6 DSS... 6 Australian Post Codes... 8 Billing - Credit Card module... 9 Billing EDI and CMS... 9 Events... 9 General... 10 NDIS... 10 Reports... 10 System Administration... 11 Legal notice... 13
About this release Athena Software is pleased to announce the release of Penelope v4.8.2.0 EDGE. Please review previous release notes if upgrading from a version prior to Version 4.1. Crucial information regarding upgrade details specific to each version are included in the applicable version s release notes. A reverse-chronological library of Penelope release notes can be found on our help site at: penelopehelp.com/category/whats-new/release-notes. This upgrade contains important security measures designed to keep your system safe. We consistently monitor and update the security of Penelope to ensure your data is protected. It is always important to stay up-to-date with the most recent version of Penelope to ensure you are using the most secure version of the software. What is an Edge Release? This is a supported version of Penelope that has both security updates as well as other features or functionality enhancements. This is helpful for organizations that want to take advantage of all the latest features added in Penelope or stay up to date with any third-party synchronizations (for example, DSS or NDIS). What is a Long Term Release? This is a supported version of Penelope that has security updates during its lifecycle but no other features or functionality enhancements. This is helpful for organizations that want to deliberately plan how they roll out new functionality according to their own timescale as opposed to when Penelope updates are available. 3 Athena Software
Technology upgrades Risk mitigation and information security management never rests! Our recent ISO 27001 certification for Information Security Management is a proud testament to our commitment to protecting the privacy, availability and resiliency of your data. In combination with Penelope security enhancements and SaaS data security services, upgrading the underlying infrastructure components allows us to continue to provide the highest levels of security for your data on an ongoing basis moving forward. Component Description Next steps and supporting documentation Type of action required Install req. Config req. License key req. Process review SSL Penelope will now only operate using SSL encryption (i.e. Penelope must be accessed using the https:// version of your URL instead of the http:// version). If a user navigates to an http URL an error page will be displayed indicating they have used an unsupported protocol and will provide the appropriate URL. If you are a SaaS client, we have you covered! Any changes to your URL will be communicated to you by the Technical Support team at the time of upgrade. If you are a self-hosted client, you will need to purchase a SSL certificate from a Certificate Authority (typically obtained through your web hosting provider). Documentation Set up SSL in Resin x penelopehelp.files.wordpress.com/2016/08/set_up_s sl_in_resin.pdf Postgresql The most recent version of Postgresql (9.6.2) provides greatly improved security, performance and stability - supporting faster response times under heavier usage loads. This upgrade should not impact any of the reports or import/export routines you may have in place and you can continue to use Postgres 9.2 if you prefer. Resin Upgrading to the most recent version of the application web server (4.0.51) will help improve the system s overall performance, stability and security. This upgrade will also importantly ensure readiness for the upcoming Client Connect portal. If you are a SaaS client, we have you covered and will take care of all infrastructure upgrades for you! If you are a self-hosted client, you will need to upgrade Postgresql, Resin, and Java. Documentation Penelope installation components Penelope Upgrade Guide penelopehelp.com/2016/05/05/penelope-installationcomponents penelopehelp.com/2017/06/26/penelope-upgradeguide x x
Component Description Next steps and supporting documentation Type of action required Install req. Config req. License key req. Process review Discontinuation of Java 6 The use of Java 6 on servers running Penelope will no longer be supported. Java 7 Update 79 CPU will now be the minimum version supported for use with Penelope. Penelope Installation Guide penelopehelp.com/2012/09/18/installationinstructions-windows-2008 x 5 Athena Software
Penelope enhancements The following list represents enhancements to existing Penelope features. In most cases, little or no action is required on your part beyond reviewing the updated help materials (if applicable). DSS Primary Information System setting now available in the DSS Setup section Unidentified Counts field updated to match DSS requirements DSS Cases will only submit after all DSS Case Member information If Penelope is the Primary Information System, the following fields are not needed for submission and are therefore hidden or excluded: The Is Using Pseudonym and Consent to Providing Details fields on the Individual Profile will be hidden. The First Name, Last Name, Addr 1 and Addr 2 fields are not included in the Client Submission The Search Client First option cannot be enabled. DSS has provided clarification on the way unidentified counts should be submitted; namely, they should only be submitted for Group-based programming. As a result, for new Service Files and Service Events created after upgrading to v4.8.2.0, you will no longer see the Non-identified Count field (though you will continue to find this field for Groups and Group Events). There are scripts available to help you update your existing Service File and Service Event records. For more information about these scripts, see the Upgrading to v4.8.2.0: Additional information for DSS clients topic. Additionally, for Groups and Group Events, negative unidentified counts will no longer be possible. -> DSS Individuals will not be submitted until added to a DSS based service file and the DSS Case Member fields are all completed. DSS Configuration Guide penelopehelp.com/2015/06/24/dss-configuration-guide/ Upgrading to v4.8.2.0: Additional information for DSS clients penelopehelp.com/2017/09/22/upgrading-to-v4-8-2-0- dss/ Upgrading to v4.8.2.0: Additional information for DSS clients penelopehelp.com/2017/09/22/upgrading-to-v4-8-2-0- dss/ DSS Submission Process Guide penelopehelp.com/2017/09/21/dss-submission-process/
Additional DSS Individual fields on DSS Case Member screen -> DSS Cases will not be submitted until all members on the DSS based service file have their DSS Case Member information completed. When recording or updating information for DSS Case Members, all of the fields submitted to DSS for the Individual, including those found on the Individual Profile. When entered, the information for the DSS Individual will update the IIndividual Profile and mark the DSS Individual for submission. Record or update DSS Case-level data from a Service File or Group Individuals will be prevented from being added to a DSS based Continuous Group more than once Additional validation for common error conditions for DSS Individual record DSS Outlet list will only show outlets setup for the Case Service Both Pre- and Post-service assessments are available to be completed per Event To prevent Individuals from having duplicate DSS Cases for a Group, users will not be able to add the same Individual to a DSS-based continuous Group more than once. Validation now includes: Invalid characters for First Name and Last NAme Missing values for the following address fields: Suburb, State and Post Code Approximate gross income requirement if Income Frequency is completed Month & year of first arrival between DOB and current date Requirements based on Partnership approach and Activity and/or Service Specific requirements When setting the Outlet at the Service File/Group, or Event levels, the list of available Outlets will only include those available for the Case Service. You can now complete and submit both a Pre-service and Post-service SCORE assessment for each Service or Group Event (for both Group/Community Assessments and Client Assessments). Complete a DSS Score Assessment for a Service File or Group Event penelopehelp.com/2015/06/25/how-to-record-or-updatea-clients-dss-information-on-a-service-file-or-group/ penelopehelp.com/2017/09/21/complete-a-dss-scoreassessment/ Partnership approach is now a Case Service specific setting to The In Partnership Approach field is now available to be set on a per-case Service level. Additionally, at the System DSS Configuration Guide 7 Athena Software
allow for configuring at a DSS Activity level. Support for expanded Activity Requirements and adding Service Type Requirements Mark All for Submission link hidden from Error tab Administration level you can choose a default setting when creating new Case Services. The following fields are now available in Penelope to capture additional information available in the current technical specifications (and additional CHSP and NDAP based data): DSS Individual: o Has Carer (yes/no checkbox) o DVA Card Status (drop down) o Accommodation Type (drop down) DSS Case Member (Service file): o Exit Case (drop down) DSS Session (Event): o Total Cost (whole number) o Time (whole number) o Quantity (whole number) o Extra Items (multi-select) o Topic (drop down) The Mark All For Submission link will not appear to users on the Error tab of the DSS Submission List if they do not have "Allow Mark not For Submission" on in their Security Class. penelopehelp.com/2015/06/24/dss-configuration-guide/ Upgrading to v4.8.2.0: Additional information for DSS clients penelopehelp.com/2017/09/22/upgrading-to-v4-8-2-0- dss/ Record or update DSS Client-level data from the Individual Profile Record or update DSS Case-level data from a Service File or Group Record or update DSS Session-level data from a Service Event or Group Event Penelope End User Security Configuration Guide penelopehelp.com/2015/06/25/how-to-record-or-updatea-clients-dss-information-on-their-individual-profile/ penelopehelp.com/2015/06/25/how-to-record-or-updatea-clients-dss-information-on-a-service-file-or-group/ penelopehelp.com/2015/06/30/how-to-record-or-updatea-clients-dss-information-in-a-service-event/ penelopehelp.com/2012/09/18/security-settings-inpenelope-tutorial/ Australian Post Codes 8 Athena Software
Update of AU postal Codes For Agencies that have purchased a copy of the Australia Post's Post Code list, a script can be ran on their database to insert/update the suburb/post code tables to match the most recent list provided by Australia Post. The script matches the quarterly updates provided by Australia Post. Note: Proof of purchase from Australia Post is required. penelopehelp.com/2017/08/01/australian-post-codes/ Billing - Credit Card module Processing refunds for historic credit card gateways Penelope now stores Gateway Account credentials for previous Credit Card gateways. If you need to switch gateways or is provided with a new account by a gateway, you can continue to process refunds from the prior gateway. Note: Data storage for merchant accounts is limited to the merchant account currently configured on upgrade to 4.8.2.0 or added after upgrading to 4.8.2.0. Credit Card Module Configuration Guide Billing EDI and CMS EDI Version on the 837 Detail page displays the version the file was generated for The EDI Version field on the 837 Detail tab will now display the EDI Version the EDI 837 was generated for (i.e. 005010X222A1 vs. 004010X098A1). EDI 837P Configuration Guide penelopehelp.com/2017/03/22/configure-the-credit-cardmodule/ penelopehelp.com/2016/10/24/configure-penelope-foruse-with-edi-837p Events 9 Athena Software
Reassigning large volumes of events When using Rapid Scheduling, unexpected errors will no longer occur when reassigning a large volume of events where conflicts were not indicated. Reassign multiple events to another worker penelopehelp.com/2016/06/06/reassign-multiple-eventsto-another-worker General Improved error messages Removal of the reload page and login popup page Owl icon links to worker homepage athenasoftware.net on login page links to corporate website The wording of error messages throughout Penelope have been improved to provided clearer directions to resolve the issue(s). When logging into Penelope, the login page will automatically load. A new pop-up window and reload tab will no longer be required. A user can now navigate to the homepage by clicking on the Penelope logo (owl icon) in the left sidebar. A user can now navigate to the Athena Software corporate website by clicking athenasoftware.net located at the bottom of the login page in Penelope. n/a n/a n/a n/a NDIS Wrapping of error messages for NDIS file lines Error messages now wrap to display the complete message on NDIS Files with error line items. Reports 10 Athena Software
Unit Coverage Use Report This new report displays an individual's policy coverage information including unit limits, used coverage, remaining coverage and itemized details, when selected, as of today for policies added within a specified time period. Complete Reports Guide penelopehelp.com/2012/09/18/reports-guide System Administration Ability to return to the Penelope login page from the System Cannot Start Up page The System Cannot Start Up page now includes a Try again button that will attempt to redirect users back to their Penelope login page. Ensure users can log in through SSO When a user logs in through SSO, Penelope de-crypts the user's UID from their Identity Provider. Authentication Configuration Guide penelopehelp.com/2016/01/22/authentication-guide-2/ System fields moved to the resin.properties file Require 'disable field truncation' set to true Version based incremental upgrades A variety of system fields have been moved to the resin.properties file to increase stability. These fields include: Penelope External URL Attachments directory Disabling field truncation is now on by default. The full contents of fields will be saved to the stdout.log files instead of being truncated at a set length when a record is saved. When upgrading from older versions, if an error occurs during an upgrade, the process will stop at the last successful complete version. An error message in the stdout.log indicates External Communications Configuration Guide penelopehelp.com/2014/01/16/how-to-set-up-smsemail-communication-in-version-4/ Authentication Configuration Guide penelopehelp.com/2016/01/22/authentication-guide-2/ Configure File Attachments for the first time penelopehelp.com/2012/09/18/attachments-tutorial/ 11 Athena Software
the version that Penelope can be started with while the issue encountered upgrading to the latest version is resolved. Add stderr to log cycling configuration Avoidance of search engine crawlers Expanded logging in the stdout.log file The stderr.log file will now roll over at the start of each day to create separate files to prevent the stderr.log file from becoming too large. Penelope will no longer be searchable via google and other search engines. If desired, a setting in the resin.properties file has been introduced to allow for search-ability. Rich text fields (i.e. Notes, Documents, etc. with rich text fields) are now shown in the stdout.log file. 12 Athena Software
Legal notice 2017 Athena Software. All rights reserved. The information in this document is provided "AS IS" and without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This information could contain technical inaccuracies or typographical errors. Changes may be made periodically to the information herein without notice. This document may contain links or references to products, materials or web sites that are provided by independent third parties either directly or through frames. The availability of such third-party material does not constitute any form of recommendation, endorsement or publication of such third-party material by us. Any concerns that you have about the third-party material should be directed to the relevant third party. iphone, ipad, and Safari are trademarks of Apple Inc. Chrome, Google and Gmail are trademarks of Google Inc. Active Directory, Excel, Internet Explorer, Microsoft, Microsoft Edge, and Office 365 are trademarks of Microsoft Corporation. Firefox and Mozilla are trademarks of The Mozilla Foundation. Other company and product names mentioned herein may be trademarks of their respective companies.