Question
An error occurred when importing a yml file from the HENNGE Email DLP management screen. Please provide details of the error.
Answer
1) Syntax error
If the message "Syntax Error" appears on the console, it means that the import file cannot be read because the format is incorrect. Please export the current yml file using the "Export" function, and try modifying the import file based on the exported yml file format.
(Reference)
About exporting HENNGE Email DLP settings
Creating HENNGE Email DLP import data (YAML file)
2) Error report
If an error report is displayed, please refer to the table below for details. Correct the errors listed in the report and try importing the file again. If the cause of the error is unclear, please contact HENNGE Customer Success Guide.
| Field Name | Description |
| location |
Location where the error occurred |
| violation | Reason for the error. Refer to "3) Error List" for details. |
| actual_value | Setting value in the yaml file |
| snippet | Excerpt of where the error occurred |
Example of an error report: Temporary hold time entered for approval request action
==========================================================
[1]
location: $.rule_groups[0].rules[0].action.type
violation: chkattrfield
actual_value: request_approval
snippet:
--------------------------------------------------------------
5 | - priority: 100
6 | name: test approval
7 | action:
> 8 | type: request_approval
^
9 | attribute:
10 | auto_release: true
11 | duration: 10m
12 |
--------------------------------------------------------------
==========================================================
3) Error List
■ General ※Occurs across all YAML files
| required | Input is missing in a required field |
| ieversion | There is an error in the version notation. Do not change the value "version: 1" |
| min | Does not meet the minimum value that can be set. Please review the number |
| max | Exceeds the maximum value that can be set. Please review the number |
| unique | Duplicate found. Please review the value |
■Address Group
Creating a YAML File (Address Group Definition)
| name_reserved_by_system | "All" cannot be used in the address group name. Please change it to a different name. |
| email_or_domain |
There is an error in the address format. Please enter in the format of Email Address, Domain, or Subdomain. |
| not_asterisk |
"*" (wildcard) cannot be used. Please enter in the format of Email Address, Domain, or Subdomain. Example: sample@test.com, @test.com, .test.com |
| duplicate_address_in_address_group | There is a duplicate address in one address group. Please review the list. |
| duplicate_address_group_name | There are duplicate address group names. Please change it to a different name. |
| upstream_group_ambiguous | There are duplicate synchronized address group names. Even if the group IDs are different, synchronization is not possible if the display names are the same. Please check the groupware settings and change the names to something else. |
| upstream_group_not_found |
The group name specified as the synchronization target does not exist. Please check the list or the group name on the groupware settings. |
■Rule Group
YAML File Columns (Rule Group Definition)
| eq | Incorrect setting value. Please check for any errors in the setting value |
| msgsz | Message size should be specified between 1 and 2147483647 (2097152KB) |
| chkattrfield |
There are parameters that cannot be used in the specified action, or there may be missing parameters. Please review the Help Center article "Creating a YAML File (Rule Group)" for reference |
| notiftype | Incorrect setting value for "Notification". Please review the Help Center article "Creating a YAML File (Rule Group)" for reference |
| checkAttachmentOption | Incorrect setting value for "Attachment Files". Please review the Help Center article "Creating a YAML File (Rule Group)" for reference |
| chktargetfield |
Incorrect setting value for "Target". Please review the Help Center article "Creating a YAML File (Rule Group)" for reference |
| chkpredfield | Incorrect setting value for "Condition". Please review the Help Center article "Creating a YAML File (Rule Group)" for reference |
| chkpatfield | Incorrect setting value for "Pattern". Please review the Help Center article "Creating a YAML File (Rule Group)" for reference |
| chkcntfield | Incorrect setting value for "Frequency". Please review the Help Center article "Creating a YAML File (Rule Group)" for reference |
| unknown_address_group_name | The address group specified in the "Pattern" does not exist. Please check the address group |
■FILTER
YAML File Columns (FILTER Definition)
| unknown_address_group_name | The specified address group name does not exist. Please check if the target address group exists or if there are any errors in the group name |
| unknown_rule_group_name | The specified rule group name does not exist. Please check if the target rule group exists or if there are any errors in the group name |
■Encryption Type
Column of YAML file (Encryption Type Definition)
| encryption_cfg_name_reserved | The encryption type name "Don't Encrypt" cannot be used. Please change to a different name |
| valid_encryption_type | There is an error in the setting value of "Password Type". Please review referring to the Help Center article "Creating a YAML file (Encryption Type)" |
| valid_random_password_per_encryption_type | An invalid value is set for "Fixed Password". Please review referring to the Help Center article "Creating a YAML file (Encryption Type)" |
| valid_fixed_password_format_per_encryption_type | An invalid value is set for "Random Password". Please review referring to the Help Center article "Creating a YAML file (Encryption Type)" |
| not_required_notify_recipient_type_never | When specifying "Fixed Password", you cannot set "Notify Recipients" |
| not_required_notification_template_id_for_encrypt_type | When specifying "Fixed Password", you cannot specify a notification template ID in "Notify Recipients" |
| valid_filename_encoding | There is an error in the setting value of "File Name Encoding". Please review referring to the Help Center article "Creating a YAML file (Encryption Type)" |
| valid_filename | There is an error in the setting value of "ZIP File Name". Please review referring to the Help Center article "Creating a YAML file (Encryption Type)" |
| notify_template_not_exist | There is an error in the notification template ID being referenced while specifying "Notify" and "Notify Recipients". Please review referring to the Help Center article "Creating a YAML file (Encryption Type)" |
| valid_extension | There is an error in the setting value of "Non-encrypted File Extension". Please review referring to the Help Center article "Creating a YAML file (Encryption Type)" |
■Encryption Policy
Column of YAML file (Encryption Policy Definition)
| unknown_address_group_name | The specified address group name does not exist. Please confirm whether the target address group exists or if there is no error in the group name |
| unknown_encryption_config_name | The specified encryption type name does not exist. Please confirm whether the target encryption type exists or if there is no error in the type name |
■Secure Download Config
Columns in the YAML File (Secure Download Type)
| not_use_msg_body_or_pdf | Both use message body and PDF options are false. Please only set one of them to true. |
| use_msg_body_and_pdf | Both use message body and PDF options are true. Please only set one of them to true. |
| msg_body_option_not_configured | The message body option is not configured when use message body is set to true. |
| pdf_option_not_configured | The PDF option is not configured when use PDF is set to true. |
| use_pdf_but_msg_body_option_configured | Use PDF is set to true but the message body option is configured. |
| use_msg_body_but_pdf_option_configured | Use message body is set to true but the PDF option is configured. |
| language_is_not_supported | The PDF language specified is not supported. |
■Secure Download Policy
Columns in YAML files (Secure Download Policy)
| unknown_secure_transfer_config_name | he specified Secure Transfer Type name does not exist. Please check if the Secure Transfer Type exists or if the type name is correct. |
| unknown_address_group_name | The specified address group name does not exist. Please check if the address group exists or if the group name is correct. |
| valid_config_name |
The specified Secure Transfer Type name is invalid.
|
| valid_config_id |
The specified Secure Transfer Type ID is invalid.
|