Overview
In PORTERS, you can configure Creating/Editing Items to make input mandatory for each field (with some exceptions).
When such fields are set as required, you cannot save data unless a value is entered. While this helps prevent missing input, it forces mandatory entry in all cases, which may reduce flexibility and make administrators hesitant to apply this setting to certain fields.
If you have such concerns, consider using the feature "Conditional-Required".
The "Conditional-Required" feature allows you to adjust which fields are required based on the current data input status.
This enables more flexible management of input rules and helps reduce missing data and the effort needed for input checks.
*The “required input” control provided by this feature works only on the screens listed below. It does not work when adding or updating data through other methods.
Applicable screens
・ On PORTERS, the resource data "Add New / Edit" screen (including updates to Reference-type fields in the edit screen)
・ List screen ( Quick-Field-Edit )
・ Phase Update during the sending of a single individual email *Excludes emails sent from Matching
・ Sub-list Phase History Add New screen
▽ Examples of “other methods” where this feature does NOT work :
・ Import
・ Bulk update
・ Bulk registration
・ Data updates associated with bulk mail sending
・ Individual mail sending from Matching
・ Data integration from various applications
・ API …etc.
*The fields that can be used in the condition (the aforementioned “input status of the data at that time”) are limited to fields of the Option-type within the same resource. For detailed specifications, please continue reading below to confirm.
*The configuration items and screens mentioned on this page can be accessed only by users with the System Administrator user type. Standard users cannot access them.
▼ Example 1
On the "Job" resource level...
- If the phase is "Draft", you can save even if fields are blank (not required).
- If the phase is "OPEN", you cannot save unless job detail fields have values (required).
▼ Example 2
On the "Process" resource level...
- If the field "End Flag" is checked, the field "NG Reason" must also have a value (required).
Add / Edit / Delete Rules
Rules that define the behavior of this feature are displayed in the customization screen, at the bottom right of the "Detail View & Items" section under the heading "Required fields conditions" (orange frame in the image).
- Add Rule: Click [New] button to access the rule setting screen and add a new rule.
- Edit Rule: Click the pencil button to access the rule setting screen for editing.
- Delete Rule: Click the trash button to delete the rule.
Rule New/Edit Screen & Settings
■ Required Item
Specify the fields that become required when the conditions defined in "Required Condition" are met.
Click the magnifying glass button to select fields.
You can narrow down candidates by entering characters used in the field name in the text box.
Selected fields will be displayed as shown above.
Click the [×] button next to each field to deselect.
■ Required Condition
Specify the conditions under which this rule enforces required input.
You can use the input status of option-type fields in the same resource as conditions. (For example, upper-level fields. Fields from other resources cannot be used as conditions.)
To add a field as a condition, use the [Required Condition] section. Click the magnifying glass button to select fields, or enter characters from the field name in the text box to narrow down candidates.
Below are tips and restrictions regarding specifications:
- The rule is considered satisfied only when all specified fields meet their respective conditions.
(Conditions between fields work as AND)
- For conditions within a field, you can choose from the following evaluation methods:
- Contains Any (OR)
- Contains All (AND)
- Does not contain (not)
- No Value Entered (is null)
- Only Option-type fields in the same resource can be used as conditions.
■ Error Message
On the resource data "New" or "Edit" screen in PORTERS, when the specified rule conditions are met, a red mark will be displayed on the “Required Fields.”
If you click the Save button without entering a value, an error message will appear next to the corresponding field.
In this setting, you can define the message to be displayed. Up to 100 characters can be entered.
(This setting is optional and does not need to be specified.)
- English : This message will be displayed to users whose language setting in PORTERS (User Info > “Default Language”) is set to English.
If not specified, the default message will be shown (e.g., “Value is required.”).
- Japanese : This message will be displayed to users whose language setting in PORTERS (User Info > “Default Language”) is set to Japanese.
If not specified, the default message will be shown (e.g., 「文字を入力してください。」 or 「値を選択してください。」).
*The “required input” control provided by this feature works only on the screens listed below. It does not work when adding or updating data through other methods.
Applicable screens
・ On PORTERS, the resource data "Add New / Edit" screen (including updates to Reference-type fields in the edit screen)
・ List screen ( Quick-Field-Edit )
・ Phase Update during the sending of a single individual email *Excludes emails sent from Matching
・ Sub-list Phase History Add New screen
▽ Examples of “other methods” where this feature does NOT work :
・ Import
・ Bulk update
・ Bulk registration
・ Data updates associated with bulk mail sending
・ Individual mail sending from Matching
・ Data integration from various applications
・ API …etc.
*The fields that can be used in the condition (the aforementioned “input status of the data at that time”) are limited to fields of the Option-type within the same resource.
■ Conditional Requirement Management
- Rule Name: Assign a management name to the rule. Enter in the text box, up to 50 characters.
- Usage: Set to "ON" and save to activate the rule immediately. "OFF" disables it. Click the button to toggle.
FAQ / Tips
*Additional notes will be added based on frequently asked questions and feedback after this feature release.