As below, we will perform maintenance associated with the ZLOSS update.
■ Release Work Schedule
Tuesday, April 7, 2026 12:00 - 12:30 JST
*Work time may vary slightly.
■ Impact During Work Time
No service suspension will occur due to the release.
■ Impact Range
- Phases > "Phases" screen
- Sending reminder emails (change of the date field used as the starting point)
- Email customization > When sending a reminder email > "Reminder setting"
■ Update Details
① Addition of the 【Field to store interview reservation date/time】 Field
On the Phase Settings screen, a new option titled “Field to store interview reservation date/time” will be added to “When the candidate books an interview schedule.”
Previously, the interview appointment date and time were always registered in the Phase Date by default.
With this change, it will now be possible to select, from a dropdown list, a field (Date Time type: yyyy/mm/dd hh:mm) in which to store the interview appointment date and time.
By default, the Phase Date will continue to be used, and if no changes are made, the behavior will remain the same as before.
If the “Field to store interview reservation date/time” is changed to a field other than the Phase Date, the Phase Date will instead be populated with the date and time when the interview appointment was created.
When making this change, if there are upcoming interviews scheduled in the near future, a warning message will be displayed to alert the user.
② Reminder Emails and Reminder Setting Notice Text
If a field other than the Phase Date is set as the “Field to store interview reservation date/time” in section ①, reminder emails will be sent based on the date and time stored in that selected date/time field.
If no changes are made, reminder emails will continue to be calculated based on the Phase Date, as before.
In addition, on the Email Customization > “When Sending Reminder Emails” screen, the red warning text shown in the “Reminder Settings” section at the bottom of the page will be revised so that it reflects the name of the PORTERS field configured in section ①.