February 2024 Escalation Release - 20.11.67.2 (February 14)
The 20.11.67.2 release is expected for the following date:
On-premise - February 14, 2024
Cloud - February 15, 2024
New Features
There are no new features in this release.
Resolved Issues
Reference | Area | Release Note |
---|---|---|
EFIN-114333 EFIN-113836 EFIN-113466 | Installer Created Duplicate Windows Services Which Prevented Dynamic Leave Requests from Being Processed | This issue only impact customers who are using Dynamic Workflow Leave Requests. When the following releases were installed: 20.11.66 and 20.11.67, duplicate Windows services were created with the same name. Some of these created services are attached to different profiles and some of them are not attached to any profile. Windows services names should not be duplicated because this will sometimes prevent the system from identifying the correct service to use. When multiple profiles use the same Windows services, the same services need to be attached to all profiles, instead of different services with same name. Because multiple services with the same name were attached to different profiles, Dynamic Leave Request workflows were not always routing to workflow successfully. In this release, the 20.11 installer was corrected so they will not create duplicate Windows services. This will prevent the issue going forward but some clean up is required. Cloud customers: PowerSchool has removed duplicate Windows services and will install the 20.11.67.2 release. On-Premise customers: PowerSchool will assist you with removing the duplicate Windows services. This must be completed prior to installing the 20.11.67.2 release. If you experienced this issue and do not have a Support case yet, please create one so that we can assist you. All districts (both Cloud and on-premise) who experienced the issue with Dynamic Leave Requests need to restart each failed leave request. The following steps need to be performed:
|
EFIN-114096 | Integration: SmartFind Express (SFE) Restricted the Creation of Duplicate Vacancy Records in PowerSchool ERP | In Human Resources, on the Attendance, Substitute Information page, previously, when Vacancy data in an active state was sent from SFE to PowerSchool ERP or eFinancePlus, it would display as a Pending record. After it was updated, it added a new record in the system, which led to duplication of the record. Now when the vacancy data is sent from SFE, it updates the existing record if one exists. It does not create duplicate vacancy records. |
Federal Reporting
There are no federal reporting issues in this release.
State Reporting
This release includes updates and resolved issues for the following states: