The following items have been completed in this release:
Sprint Began: 12/1/2018 Sprint Ended: 1/2/2019
Note | ||
---|---|---|
| ||
Mmmmm - Cheese! The cheese icon denotes a change in functionality. So, when we move the cheese and change the way something works, you will know about it. |
ENHANCEMENT
The Email Template system has been enhanced to allow individual users to be selected from the recipient proc and set as either To or CC recipients. Previously this selection was a pre-designated group of To or CC users and did not allow individual custom configuration of recipients.
ENHANCEMENT
The following existing PEO procs have been converted to return discrete recipients:
- peo_clientservicecase_external_emailtemplate_recipient_proc
- peo_clientservicecase_internal_critical_emailtemplate_recipient_proc
- peo_clientservicecase_internal_emailtemplate_recipient_proc
- peo_directdeposit_emailtemplate_recipient_proc
- peo_employee_emailtemplate_recipient_proc
Previously these stored procedures would return the From, To, and CC recipients as a block of email addresses instead of individual recipients.
ENHANCEMENT
Older, infrequently used application variables have been removed from the system and their functionality deprecated. The affected variables are:
ENHANCEMENT
A Direct Deposit Notice Email Template is now available. This template is a base template, which can be customized by each client to alert an employee of a direct deposit change in PrismHR. The template (template code PHRDDNotice) is unpublished and must be published before use.
34704, 34705, 34706, 34707, 34708, 34709 | Remove enterprise libraries | Removed enterprise libraries and replaced with more efficient code to optimize system performance.||||||
35238 | Record count widget issues | Resolved an issue where the magnifying glass icon on Claim and the Workflow Channel Claim link were not working, breaking the "jump to" functionality. | 35850 | Clone active pricing batch issue | Resolved an issue where the pricing batch clone process would only look at the default Legal Entity on the State Master, which was not always correct. If there is not a matching SLE, the system would not clone that state without an error creating confusion about how this should work. The system now properly uses the Contract Type metadata to set the Legal Entity during pricing. | ||
35866 | Entity filter on dataform Subscribers "More" search does not work | The Entity filter on dataform subscribers More filtering has been replaced with a much more useful Department filter, allowing you to filter available dataform subscribers by the default department set on the user record. | |||||
36029 | User Audit Trail: Quick Search LoginID | Resolved a problem with the User Audit Trail Quick Search using the LoginID (user) search parameter. | |||||
36030 | Condition expressions do not recognize underscore (_) values in condition label names | Resolved a problem in which condition expressions would not recognize a condition if the condition label contained an underscore (_) character. | |||||
36031 | Update Two Factor Authentication template | Resolved the Two Factor Authentication process that caused the authorization code to improperly format the validation email sent to the user after an attempted login to a Two Factor Authentication enabled system. | |||||
36043 | Client service case category metadata not saving correctly | Resolved a problem when adding a metadata record after returning to the lookup, and then clicking Open Metadata link. An Add dialog would open instead of opening the metadata record you just created. The system will display the normal "unsaved changes" warning if you close the lookup record without saving; this action orphans the metadata record. You must save the lookup record to maintain the metadata record. | |||||
36072 | Jump icon in Inbox for triggered emails | Resolved an issue where embedded links in notification emails were not being properly linked to the triggering dataform. | |||||
36075 | Initial data on a company ongoing insert of client | Resolved an issue with PrismHR_API_ongoing imports where dataforms associated with newly created client workspaces and created in the same import would fail with the error: "The value (####) in the "ClientNumber" column did not produce a valid lookup for data row ###." This would happen because inserts of workspace related data such as location or employee data would try to process at the same time the client information was processing, and the client workspace had not yet been created. The system will now check to see if client data is processing and if so, utilize the client data when validating the presence of the client. | |||||
36119 | Salesforce API v2.0 Default Value mapping | Resolved an issue in the Salesforce API that would cause Salesforce imports to ignore the Default Value configuration of the import map detail record, and instead insert a blank value. | |||||
36130 | Payroll audit workflow channel triggering Issues | Resolved an issue with workflow triggering when the triggering field being used is a parent form field with hundreds of child form options and the system would only return the first 100 options. The system will now return the first 1000 options. | |||||
36244 | Error when clicking email templates | Removed a deprecated link to the classic email templates admin control panel (System Admin > Advanced). | |||||
36250 | Workflow channel not generating case notification | 36346 | Removed Saved Search | Resolved an issue where email template triggering would not properly fire if the triggering field was an empty checkbox on a dataform that was auto-generated by a workflow channel. | |||
36255 | Import Map Search chiclet being cleared | Resolved an issue when adding or editing import map configurations. If a filter (such as “Show All”) was applied to the import map detail list and a record was edited, then when you returned to the list, the filter was removed. This action required you to reapply the filter each time. The selected filter is now preserved through record adds and edits. | |||||
36283 | Legal Entity form cannot be opened | Resolved an issue where the link to jump to a legal entity form from one of the following system areas produced an error when clicked and did not open the legal entity form:
| |||||
Saved searches were removed from the Surcharges dashboard because this functionality was causing issues when a user would inadvertently save a search, which would later hide records they needed to see. | |||||||
36382 | New field sets added | The following new fields have been added to all installs. All fieldsets are hidden by default:
| |||||
36405 | Checkbox condition criteria | Updated the system to allow 0 (unchecked) or 1 (checked) to be used as valid triggering conditions when using a checkbox to trigger an email template. | |||||
36435 | Dataform security removed on form Name Change through Beta interface | Resolved an issue when changing the dataform name of a secured dataform removes form level security from the dataform. The system will now maintain any dataform level security through a dataform name change. |
Filter by label (Content by label) | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|