Release 116 Notes

Improved Export-Client-to-PrismHR Handling of Multiple GeoCodes and Added Auto-Fill of Latitude/Longitude

Previously when a Client Master record was exported to PrismHR with a zip code that had multiple GeoCodes, the first GeoCode found in the list of GeoCodes for that zip code was exported. Now, when there are multiple GeoCodes matching the same zip code, the following validation occurs to determine a GeoCode exact match (if possible):

• Validation Step 1: City, County, and State are checked for an exact match.

  • If an exact match is found, the GeoCode is exported.

  • If an exact match is not found, the system moves to Validation Step 2.

• Validation Step 2: City and State are checked for an exact match.

  • If an exact match is found, the GeoCode is exported.

  • If an exact match is not found, the system moves to the next validation step.

• Validation Step 3: Instances of multiple GeoCodes still remaining OR no GeoCode found are processed.

  • If multiple GeoCodes remain after Validation Steps 1 and 2, the system will export the first GeoCode found in the list of GeoCodes.

  • If no GeoCode is found after Validation Steps 1 and 2, the export fails. The Client Master Export Status field is set to Failed Validation and GeoCode validation error details are included in the Client Master Export Log field using the following format: "Create PrismHR Client failed, error='Unable to locate PrismHR geoCode for ZipCode'{0}'".

Additionally, if an exact GeoCode match is exported, the Latitude and Longitude values for the GeoCode are also now exported to PrismHR.

Note: The zip code is represented by the Postal Code field on the Client Master record.

Improved PrismHR API User Import Handling of Records with Invalid or Missing Email Addresses

PrismHR API User import records containing invalid or missing email addresses will now be set to a Status of Requires Attention in the Import Queue when the email validation fails. Email validation error details are included in the log data using the following format:

"User '<username>' invalid or missing email address <invalid email>, queue record set to Requires Attention".

See Initial Import Queue management or Ongoing Import Queue Management.

Added New Condition to EmployeeStateTaxChange Email Template

A "Contains" condition statement in the EmployeeStateTaxChange email template looked for 'FilingStatus' in the trigger condition string while a "Contains" condition statement in the EmployeeFedTaxChange email template looked for 'FedFilingStatus' in the trigger condition string. Since both conditions contained 'FilingStatus' in the string, the EmployeeStateTaxChange email template alert triggered twice. Now, a new condition expression C9 (Fed) has been added to the EmployeeStateTaxChange email template with a "Not" statement so that the EmployeeStateTaxChange alert is only triggered when the "Contains" condition statement does not contain 'Fed'.

Updated Visual Identifiers of Metadata on Lookup

Improvements were made to help users identify at-a-glance whether a lookup record has a metadata dataform associated with its lookup group and whether associated metadata has been configured for a specific lookup:

• The column heading on the Lookups Dashboard (System Admin > Lookups) has been changed from Has Metadata to Uses Metadata.

  

• Possible values in the Uses Metadata column are:

  • No

  • Yes (Not Created)

  • Yes

See Lookups with Metadata.

Updated the PrismHR SSO Link Functionality to Prevent ClientSpace "Change Password" Prompt

Previously, when Change Password Next Login was set on the User record and the user was a PrismHR-to-ClientSpace SSO user, the Change Password window in ClientSpace displayed at login. An "SSO" value has been added to the Authentication Type lookup group (located in the Administrator Settings fieldset of the User Details form). When Authentication Type is set to SSO (on a user record where the user is otherwise properly configured for PrismHR-to-ClientSpace single sign on) the following behavior is now activated:

• The Password Never Expires checkbox on the user record is checked and becomes Read Only.

• If the SSO user attempts to login via the ClientSpace login page, the following message displays:

  "This user is not configured for login here, please contact your ClientSpace Administrator."

See Implementing SSO from PrismHR to ClientSpace

PrismHR API Version Upgrade

The PrismHR API Service References have been updated to v1.28 to allow compatibility with future development projects. No functionality has changed. The update affects all PrismHR import processes (initial, ongoing, event).

Improved _HE_ValidateIncidents Messages for Private Tasks

Previously when a user marked a case Complete and the _HE_ValidateIncidents business rule method triggered, if there were incomplete private tasks, the message only indicated that there were open tasks associated with the case. Now, when there are incomplete private tasks associated with the case, the following message displays: 

"There are associated tasks that are not complete that may be Private. The users assigned to these tasks must complete them before resolving the case".

If there are incomplete private tasks associated with the case AND the user marking the case Complete is a Global Administrator, the following additional information is appended to the end of message above: 

"If private, please contact the following users

- (<FirstName> <LastName>)"

See Business Rule Methods.

Updated the stored procedure of the Export Client to PrismHR dataform link to exclude inactive Contract Types.

Updated the peo_gen_Benefit_Plan_s_typeahead stored procedure to improve loading time of the Benefit Plan field lookup values located on the Offered Benefits Plan dataform.