The following maintenance will be carried out for ZLOSS.
■ Release Date and Time
April 1, 2025 (Tuesday) 12:00 - 13:00 JST
※There will be no service interruptions due to the release.
■ Version Information
ZLOSS Version 4.1.25
■ Impact Range
- Applicant-side reservation screen
- Resume phase date reflecting reservation date and time
- Holidays screen
■ Fixes
- Fixed an issue where the date registered in the linked calendar and the phase date reflected in PORTERS would be misaligned if the applicant's browser and segment setting timezone did not match. (Changed to set the phase date based on the interpretation of the timezone set in the segment used for the reservation.)
▽Supplement:
This fix is particularly for reservations targeting overseas applicants or involving overseas bases. There were cases where inappropriate dates were registered as phase dates in PORTERS. This fix addresses that issue. - Fixed an issue where non-holiday anniversaries were included in the holiday setting list.
▽Supplement:
ZLOSS can be set to prevent reservations on holidays. Due to the use of Google's API for holiday determination, some days that were not originally holidays were treated as holidays. (Examples in Japan: Setsubun 2/3, Hinamatsuri 3/3, Mother's Day 5/11, Tanabata 7/7, Shichi-Go-San 11/15, Christmas 12/25)
※After the fix, the holiday list data will be refreshed in all PORTERS environments. This will forcibly delete non-holiday anniversaries, so please be aware. - Fixed an issue where, under the condition of calendar linkage, the interview setting management of the segment setting was a "Porters User". In the interview reservation screen via the relevant segment, there were cases where extra slots were blocked.
▽Supplement:
For example, even if an interview schedule registered via ZLOSS was deleted from the linked calendar due to reasons such as cancellation, the relevant time slot would still be blocked and marked as unavailable when accessing the interview reservation screen thereafter. This fix addresses that issue. - Fixed an issue where multiple reservations could be made from a one-time URL depending on the timing and procedure of the operation.