Skip to main content
Skip table of contents

April 29, 2022 Release

Resolved Issues

These changes have been released in the following software version(s) unless otherwise noted in the release note:

  • Version 19.4
  • Version 20.11

The following issues have been resolved:

Reference

Area

Release Note

EFIN-63038TX TEAM End Date before Start Date

Customers reported that the Texas TEAM load had several instances of the end date of ED40 or ED45 records being before the start date for certain records. This has been corrected.

EFIN-69320TX TEAM - Load of Substitute Zero Day Reason Code corrected

The Texas TEAM Load creates a code for reporting zero days automatically. Instead of a 'C ’, It was loading an ‘A' for substitutes, though there were no days to report. This is a correction for the Exit reason code.

EFIN-71612TX Unique ID Does not Require a Paycode 

Added a prompt to the Texas Unique ID program to allow customers to include names of employees who do not have a payrate as part of the file created and to request a unique staff identifier for the respective employees. Previously, if there was no payrate for an employee record, those records would not be included in the file, which caused a problem for some districts.

EFIN-81325TX TEAM - Translate 08 Position to 05 on Load in RP25

The Texas TEAM Load process translates a 08 TRS position to a 05 position. The Hours Upload is used to import docking information for the translated position. When the employee had a pay dock,  the days were not reduced because it looked for an 08 RP20 record instead of 05 RP20 records. This has been corrected, so it translates for the Hours Import the same way it does for the load.

EFIN-82702TX PEIMS - Class Roster 305 Record Load issue

While running the Texas PEIMS Load and including an XML format file, subsequent records were not being loaded for the 305 records if they had an invalid State Staff ID. This has been corrected.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.