【Scheduled】 2026/11/19 PORTERS 9.5.0 Release Notes

*This page was machine-translated from Japanese and may contain inaccuracies.

We will be performing maintenance in conjunction with a PORTERS release.
Details of the maintenance and the changes are as follows.

■ Release Work Schedule

2026/11/19 (Thu)　6:00 – 9:00　Japan Standard Time

※Times are shown in 24-hour format.
※The maintenance work time may vary.

■ Impact During Work Hours

The service remains available during the above time frame.

■ New Features

Input Restriction Feature (Error Check) for Date/Time and Number/Currency Types
　　・Field types for which conditions can be set
　　・Fields selectable in Related Resource Data Reference
　　・Screens and features where the check works
　　・Notes
 

Input Restrictions (Validation) for Date/Time-type and Number/Currency-type Fields

You will be able to set conditions based on the chronological order of dates or the relative size of numeric values.

For example, for staffing-type business, you can require that the "Contract End Date" field only accept a date earlier than the "Organizational Unit Statutory Limit Date" field, allowing input to be validated for consistency.

Conditions are configured from the Customize screen → "Detail View & Items" → the New/Edit Field screen.

Field Types That Support Conditions

① Date-type / Date-Time-type / Time-type(hereafter referred to collectively as Date/Time-type)

Specify the type of condition (Later/Earlier, After/before) from the dropdown. 

The condition value can be specified using either "fixed" or "From Related Resource".

You can set up to 5 conditions (combined with AND).
For example, to create a condition such as "between Field A and Field B," you would set two conditions: "Later than the value of Field A" and "Earlier than the value of Field B."

② Number-type / Currency-type (hereafter referred to collectively as Number/Currency-type)

For the existing Max/Min value settings, you can now also set "From Related Resource".

Fields Available for "From Related Resource"

The fields available for "From Related Resource" must meet all of the following conditions.

•  A field on the same resource, or a field on a parent resource (a higher-level resource linked via a System-type or LinkType* field)
•  The same field type as the field on which the input restriction is being set

* What is a LinkType field?

This includes fields such as Contact-type fields that can be created via "Related Resource Integration Settings" when creating a field through Customize, as well as the linking fields between resources (Office.P_Client, Employment.P_Resume, Employment.P_Sales, etc.) introduced with the new resources released early to some environments in PORTERS 8.4.0 and PORTERS 9.2.0.

Screens and Features Where the Check Applies

The input restriction check applies on the following screens and features.
For some features, the check applies only in a limited way.
If a condition is not met, an error message is displayed using a method appropriate to the feature.

1. New/Edit Screen
2. List View (Quick-Field-Edit)
3. Phase Update via Individual Mail Send *Excludes sending from Matching (checks the Phase date + Conditional-Required and the fields shown by this feature) 
4. Process Creation for Individual Mail Send from Matching (checks only the "Fixed" for the Phase date)
5. Import (checks only the "Fixed" for Number-type)
6. Bulk Update ("Fixed" only)
7. Bulk Mail Send (checks only the "Fixed" for the Phase date)

* Does not apply to the API or individual apps.

1. New/Edit Screen

When you move focus out of a field, or when you click the Save button, an error message is displayed in red below any field that violates a condition.

• An error is also displayed if you edit a field used in a condition and it causes the condition to be violated, not just the field on which the condition was set.
• On the Edit screen, clicking a Reference-type field allows you to change the value of the higher-level field it references, and in that case as well, the check applies to both "fields with the input restriction set" and "fields used in the condition."
• If a condition referencing related resource data is violated, the error message shows the name of the field used in the condition in parentheses.

2. List View (Quick-Field-Edit)

In Quick-Field-Edit on the List View, an error is displayed if you edit either the "field with the input restriction" or the "field used in the condition" to a value that falls outside the condition.

Example: A Date-type field is set with the condition "later than the Hire Date."

〇 If you enter a date in the "Date-type" field that does not meet the condition

〇 If you enter a date in "Hire Date" that falls outside the condition set on the "Date-type" field

3. Phase Update via Individual Mail Send

For Individual Mail Send (excluding Individual Mail Send from Matching), the check applies to the following fields.

• Phase date: The check applies whether the Phase date itself has an input restriction set, or the Phase date is used as a condition in another Date-Time-type field's input restriction.
• Fields subject to Conditional-Required

4. Process Creation for Individual Mail Send from Matching

To avoid performance degradation, Individual Mail Send from Matching uses the same specification as Bulk Mail Send.

5. Import

To avoid performance degradation, Import uses the following specification.

〇 Input restrictions on Date/Time-type fields
　These are not checked at all (regardless of whether "Fixed" or "From Related Resource" is used)

〇 Max/Min value for Number/Currency-type fields
　・ If "Fixed" is set, the check is performed as before.
　・ If "From Related Resource" is set, the check is performed using 9,999,999,999 / -9,999,999,999 (the system's Max/Min values) as the limit.

6. Bulk Update

To avoid performance degradation, Bulk Update uses the following specification.

〇 If "Fixed" is set
　The check applies when you enter a value on the Bulk Update screen.

〇 If "From Related Resource" is set
　・ Date/Time-type fields are not checked.
　・ As with Import, Number/Currency-type fields are checked using 9,999,999,999 / -9,999,999,999 (the system's maximum/minimum values) as the limit.

7. Bulk Mail Send

To avoid performance degradation, on the Bulk Mail Send screen, Phase Update / Process Creation checks only the Phase date, using the following specification.

〇 If "Fixed" is set
　The check applies when you enter a value on the Phase Update / Process Creation screen.

〇 If "From Related Resource" is set
　The check is not performed.

* Default values are also not checked when creating a Process.

Notes

In some cases, the error message "Please specify a date on or after 2026/10/01 10:00" is displayed, and the error does not disappear even when "2026/10/01 10:00" is entered.

■Cause
Date-Time-type fields display time only down to the "minute" on screens and in messages, but internally hold data down to the "second."

　Example: The data is held as "2026/10/01 10:00:30," but it is displayed as "2026/10/01 10:00" on screens and in messages.

For this data, the error message "Please specify a date on or after 2026/10/01 10:00" is displayed, but in fact you need to enter a date on or after 2026/10/01 10:00:30.

■Solution
In such cases, enter a time one minute later than the time shown in the message.
　 Example: 2026/10/01 10:01

■ Bug Fixes

• Fixed an issue where the maximum number of characters set for a URL-type field was not applied on the Merge screen.
• Fixed an issue where, in the Sales resource, hiding a required System-type field through customization made it impossible to save records.

■ Version Information

PORTERS 9.5.0