KSML Evaluation Report
📊 Summary
- Errors: 261
- Warnings: 250
- Suggestions: 117
- Solids: 721
Error Pattern Summary
261 errors total. Fix the largest repeated pattern first, then rerun evaluation.
| Count | Pattern | Explanation | Action |
|---|---|---|---|
| 59 | Constant object missing root reference (KSML-CONSTANT-002) | Constant object 'gender_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md, apply the smallest fix, then rerun evaluation. |
| 182 | Incomplete constant value record (KSML-CONSTANT-008) | Constant value 'MALE' in constant object 'gender_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Check agents/ERROR-FIX.md, apply the smallest fix, then rerun evaluation. |
| 3 | Missing referenced object (KSML-REFERENCE-003) | Field 'city_by_ip' in 'user_account' references target object 'cityByIp' which does not exist in the model. | Check agents/ERROR-FIX.md, apply the smallest fix, then rerun evaluation. |
| 15 | Boolean field naming (KSML-NAMING-BOOLEAN-001) | Boolean field 'time_slot.is_peak_hour' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_peak_hour="false" -> peak_hour="false". Also update all model references that use 'is_peak_hour'. | Check agents/ERROR-FIX.md, apply the smallest fix, then rerun evaluation. |
| 2 | reserved-keyword (KSML-KEYWORD-002) | KSML XML naming error at merchant.xml:81: element <user_role_assignment> defines an XML attribute named 'user', which conflicts with reserved keywords in: SQL. Rename the attribute in the KSML XML itself and keep its current value; for example, change user="..." to user_id="...". Also update any <_value> attributes or other model references that use the old field name. | Rename the target to a descriptive two-word snake_case name using the concrete example in the error. |
❌ Errors (Must Fix)
| Rule ID | Target | Source | Error Message | Action |
|---|---|---|---|---|
KSML-CONSTANT-002 | gender_type.platform | merchant.xml:1293 | Constant object 'gender_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | gender_type.merchant | merchant.xml:1304 | Constant value 'MALE' in constant object 'gender_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | gender_type.merchant | merchant.xml:1305 | Constant value 'FEMALE' in constant object 'gender_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | gender_type.merchant | merchant.xml:1306 | Constant value 'OTHER' in constant object 'gender_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | shipment_status_type.platform | merchant.xml:1309 | Constant object 'shipment_status_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | shipment_status_type.merchant | merchant.xml:1320 | Constant value 'PENDING' in constant object 'shipment_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | shipment_status_type.merchant | merchant.xml:1321 | Constant value 'ASSIGNED' in constant object 'shipment_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | shipment_status_type.merchant | merchant.xml:1322 | Constant value 'IN_TRANSIT' in constant object 'shipment_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | shipment_status_type.merchant | merchant.xml:1323 | Constant value 'DELIVERED' in constant object 'shipment_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | shipment_status_type.merchant | merchant.xml:1324 | Constant value 'CANCELED' in constant object 'shipment_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | event_type.platform | merchant.xml:1327 | Constant object 'event_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | event_type.merchant | merchant.xml:1338 | Constant value 'PICKUP' in constant object 'event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | event_type.merchant | merchant.xml:1339 | Constant value 'LEFT_WAREHOUSE' in constant object 'event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | event_type.merchant | merchant.xml:1340 | Constant value 'ARRIVED_DESTINATION' in constant object 'event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | event_type.merchant | merchant.xml:1341 | Constant value 'EXCEPTION' in constant object 'event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | movement_type.platform | merchant.xml:1344 | Constant object 'movement_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | movement_type.merchant | merchant.xml:1355 | Constant value 'RECEIVE' in constant object 'movement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | movement_type.merchant | merchant.xml:1356 | Constant value 'ISSUE' in constant object 'movement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | movement_type.merchant | merchant.xml:1357 | Constant value 'TRANSFER' in constant object 'movement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | movement_type.merchant | merchant.xml:1358 | Constant value 'ADJUSTMENT' in constant object 'movement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | vehicle_type.platform | merchant.xml:1361 | Constant object 'vehicle_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | vehicle_type.merchant | merchant.xml:1372 | Constant value 'VAN' in constant object 'vehicle_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | vehicle_type.merchant | merchant.xml:1373 | Constant value 'TRUCK_HEAVY' in constant object 'vehicle_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | vehicle_type.merchant | merchant.xml:1374 | Constant value 'LIGHT_TRUCK' in constant object 'vehicle_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | service_status_type.platform | merchant.xml:1377 | Constant object 'service_status_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | service_status_type.merchant | merchant.xml:1388 | Constant value 'SCHEDULED' in constant object 'service_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | service_status_type.merchant | merchant.xml:1389 | Constant value 'IN_PROGRESS' in constant object 'service_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | service_status_type.merchant | merchant.xml:1390 | Constant value 'COMPLETED' in constant object 'service_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | service_status_type.merchant | merchant.xml:1391 | Constant value 'CANCELLED' in constant object 'service_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | team_member_role.platform | merchant.xml:1394 | Constant object 'team_member_role' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | team_member_role.merchant | merchant.xml:1405 | Constant value 'TEAM_LEAD' in constant object 'team_member_role' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | team_member_role.merchant | merchant.xml:1406 | Constant value 'MOVER' in constant object 'team_member_role' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | team_member_role.merchant | merchant.xml:1407 | Constant value 'PACKER' in constant object 'team_member_role' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | work_order_status.platform | merchant.xml:1410 | Constant object 'work_order_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | work_order_status.merchant | merchant.xml:1421 | Constant value 'NEW' in constant object 'work_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | work_order_status.merchant | merchant.xml:1422 | Constant value 'PENDING' in constant object 'work_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | work_order_status.merchant | merchant.xml:1423 | Constant value 'CLOSED' in constant object 'work_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | priority_type.platform | merchant.xml:1426 | Constant object 'priority_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | priority_type.merchant | merchant.xml:1437 | Constant value 'HIGH' in constant object 'priority_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | priority_type.merchant | merchant.xml:1438 | Constant value 'MEDIUM' in constant object 'priority_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | priority_type.merchant | merchant.xml:1439 | Constant value 'LOW' in constant object 'priority_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | task_status.platform | merchant.xml:1442 | Constant object 'task_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | task_status.merchant | merchant.xml:1453 | Constant value 'TO_DO' in constant object 'task_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | task_status.merchant | merchant.xml:1454 | Constant value 'IN_PROGRESS' in constant object 'task_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | task_status.merchant | merchant.xml:1455 | Constant value 'DONE' in constant object 'task_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | salary_grade.platform | merchant.xml:1458 | Constant object 'salary_grade' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | salary_grade.merchant | merchant.xml:1469 | Constant value 'GRADE_1' in constant object 'salary_grade' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | salary_grade.merchant | merchant.xml:1470 | Constant value 'GRADE_2' in constant object 'salary_grade' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | salary_grade.merchant | merchant.xml:1471 | Constant value 'GRADE_3' in constant object 'salary_grade' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | employment_type.platform | merchant.xml:1474 | Constant object 'employment_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | employment_type.merchant | merchant.xml:1485 | Constant value 'FULL_TIME' in constant object 'employment_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | employment_type.merchant | merchant.xml:1486 | Constant value 'PART_TIME' in constant object 'employment_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | employment_type.merchant | merchant.xml:1487 | Constant value 'CONTRACT' in constant object 'employment_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | employment_status.platform | merchant.xml:1490 | Constant object 'employment_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | employment_status.merchant | merchant.xml:1501 | Constant value 'ACTIVE' in constant object 'employment_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | employment_status.merchant | merchant.xml:1502 | Constant value 'INACTIVE' in constant object 'employment_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | timesheet_status.platform | merchant.xml:1505 | Constant object 'timesheet_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | timesheet_status.merchant | merchant.xml:1516 | Constant value 'DRAFT' in constant object 'timesheet_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | timesheet_status.merchant | merchant.xml:1517 | Constant value 'PENDING_APPROVAL' in constant object 'timesheet_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | timesheet_status.merchant | merchant.xml:1518 | Constant value 'APPROVED' in constant object 'timesheet_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | payroll_status.platform | merchant.xml:1521 | Constant object 'payroll_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | payroll_status.merchant | merchant.xml:1532 | Constant value 'PENDING' in constant object 'payroll_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | payroll_status.merchant | merchant.xml:1533 | Constant value 'PROCESSED' in constant object 'payroll_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | payroll_status.merchant | merchant.xml:1534 | Constant value 'PAID' in constant object 'payroll_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | payroll_item_type.platform | merchant.xml:1537 | Constant object 'payroll_item_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | payroll_item_type.merchant | merchant.xml:1548 | Constant value 'BASE_SALARY' in constant object 'payroll_item_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | payroll_item_type.merchant | merchant.xml:1549 | Constant value 'BONUS' in constant object 'payroll_item_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | payroll_item_type.merchant | merchant.xml:1550 | Constant value 'TAX_DEDUCTION' in constant object 'payroll_item_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | rule_type.platform | merchant.xml:1553 | Constant object 'rule_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | rule_type.merchant | merchant.xml:1564 | Constant value 'FIXED_AMOUNT' in constant object 'rule_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | rule_type.merchant | merchant.xml:1565 | Constant value 'PERCENTAGE' in constant object 'rule_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | bonus_status.platform | merchant.xml:1568 | Constant object 'bonus_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | bonus_status.merchant | merchant.xml:1579 | Constant value 'PENDING' in constant object 'bonus_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | bonus_status.merchant | merchant.xml:1580 | Constant value 'ISSUED' in constant object 'bonus_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | leave_type.platform | merchant.xml:1583 | Constant object 'leave_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | leave_type.merchant | merchant.xml:1594 | Constant value 'ANNUAL_LEAVE' in constant object 'leave_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | leave_type.merchant | merchant.xml:1595 | Constant value 'SICK_LEAVE' in constant object 'leave_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | leave_type.merchant | merchant.xml:1596 | Constant value 'PERSONAL_LEAVE' in constant object 'leave_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | leave_status.platform | merchant.xml:1599 | Constant object 'leave_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | leave_status.merchant | merchant.xml:1610 | Constant value 'PENDING_APPROVAL' in constant object 'leave_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | leave_status.merchant | merchant.xml:1611 | Constant value 'APPROVED' in constant object 'leave_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | leave_status.merchant | merchant.xml:1612 | Constant value 'REJECTED' in constant object 'leave_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | training_status.platform | merchant.xml:1615 | Constant object 'training_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | training_status.merchant | merchant.xml:1626 | Constant value 'NOT_STARTED' in constant object 'training_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | training_status.merchant | merchant.xml:1627 | Constant value 'IN_PROGRESS' in constant object 'training_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | training_status.merchant | merchant.xml:1628 | Constant value 'COMPLETED' in constant object 'training_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | customer_type.platform | merchant.xml:1631 | Constant object 'customer_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | customer_type.merchant | merchant.xml:1642 | Constant value 'PRIVATE' in constant object 'customer_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | customer_type.merchant | merchant.xml:1643 | Constant value 'CORPORATE' in constant object 'customer_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | industry_type.platform | merchant.xml:1646 | Constant object 'industry_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | industry_type.merchant | merchant.xml:1657 | Constant value 'LOGISTICS' in constant object 'industry_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | industry_type.merchant | merchant.xml:1658 | Constant value 'TECH' in constant object 'industry_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | industry_type.merchant | merchant.xml:1659 | Constant value 'MANUFACTURING' in constant object 'industry_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | payment_method.platform | merchant.xml:1662 | Constant object 'payment_method' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | payment_method.merchant | merchant.xml:1673 | Constant value 'BANK_TRANSFER' in constant object 'payment_method' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | payment_method.merchant | merchant.xml:1674 | Constant value 'CREDIT_CARD' in constant object 'payment_method' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | payment_method.merchant | merchant.xml:1675 | Constant value 'CASH' in constant object 'payment_method' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | billing_cycle.platform | merchant.xml:1678 | Constant object 'billing_cycle' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | billing_cycle.merchant | merchant.xml:1689 | Constant value 'MONTHLY' in constant object 'billing_cycle' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | billing_cycle.merchant | merchant.xml:1690 | Constant value 'QUARTERLY' in constant object 'billing_cycle' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | billing_cycle.merchant | merchant.xml:1691 | Constant value 'ONE_TIME' in constant object 'billing_cycle' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | history_event_type.platform | merchant.xml:1694 | Constant object 'history_event_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | history_event_type.merchant | merchant.xml:1705 | Constant value 'SERVICE_COMPLETED' in constant object 'history_event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | history_event_type.merchant | merchant.xml:1706 | Constant value 'COMPLAINT' in constant object 'history_event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | history_event_type.merchant | merchant.xml:1707 | Constant value 'CONTRACT_RENEWED' in constant object 'history_event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | contract_type.platform | merchant.xml:1710 | Constant object 'contract_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | contract_type.merchant | merchant.xml:1721 | Constant value 'FRAMEWORK' in constant object 'contract_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | contract_type.merchant | merchant.xml:1722 | Constant value 'SINGLE_SERVICE' in constant object 'contract_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | contract_status.platform | merchant.xml:1725 | Constant object 'contract_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | contract_status.merchant | merchant.xml:1736 | Constant value 'DRAFT' in constant object 'contract_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | contract_status.merchant | merchant.xml:1737 | Constant value 'ACTIVE' in constant object 'contract_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | contract_status.merchant | merchant.xml:1738 | Constant value 'EXPIRED' in constant object 'contract_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | document_type.platform | merchant.xml:1741 | Constant object 'document_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | document_type.merchant | merchant.xml:1752 | Constant value 'CONTRACT' in constant object 'document_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | document_type.merchant | merchant.xml:1753 | Constant value 'INVOICE' in constant object 'document_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | document_type.merchant | merchant.xml:1754 | Constant value 'RECEIPT' in constant object 'document_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | ticket_status.platform | merchant.xml:1757 | Constant object 'ticket_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | ticket_status.merchant | merchant.xml:1768 | Constant value 'OPEN' in constant object 'ticket_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | ticket_status.merchant | merchant.xml:1769 | Constant value 'IN_PROCESS' in constant object 'ticket_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | ticket_status.merchant | merchant.xml:1770 | Constant value 'RESOLVED' in constant object 'ticket_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | unit_of_measure.platform | merchant.xml:1773 | Constant object 'unit_of_measure' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | unit_of_measure.merchant | merchant.xml:1784 | Constant value 'UNIT' in constant object 'unit_of_measure' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | unit_of_measure.merchant | merchant.xml:1785 | Constant value 'HOUR' in constant object 'unit_of_measure' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | unit_of_measure.merchant | merchant.xml:1786 | Constant value 'CUBIC_METER' in constant object 'unit_of_measure' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | unit_of_measure.merchant | merchant.xml:1787 | Constant value 'KILOGRAM' in constant object 'unit_of_measure' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | currency_type.platform | merchant.xml:1790 | Constant object 'currency_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | currency_type.merchant | merchant.xml:1801 | Constant value 'EUR' in constant object 'currency_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | currency_type.merchant | merchant.xml:1802 | Constant value 'USD' in constant object 'currency_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | currency_type.merchant | merchant.xml:1803 | Constant value 'GBP' in constant object 'currency_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | target_audience_type.platform | merchant.xml:1806 | Constant object 'target_audience_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | target_audience_type.merchant | merchant.xml:1817 | Constant value 'NEW_CUSTOMERS' in constant object 'target_audience_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | target_audience_type.merchant | merchant.xml:1818 | Constant value 'EXISTING_CUSTOMERS' in constant object 'target_audience_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | discount_type.platform | merchant.xml:1821 | Constant object 'discount_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | discount_type.merchant | merchant.xml:1832 | Constant value 'AMOUNT_OFF' in constant object 'discount_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | discount_type.merchant | merchant.xml:1833 | Constant value 'PERCENT_OFF' in constant object 'discount_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | discount_type.merchant | merchant.xml:1834 | Constant value 'FREE_SERVICE' in constant object 'discount_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | lead_source.platform | merchant.xml:1837 | Constant object 'lead_source' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | lead_source.merchant | merchant.xml:1848 | Constant value 'WEBSITE' in constant object 'lead_source' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | lead_source.merchant | merchant.xml:1849 | Constant value 'PHONE_CALL' in constant object 'lead_source' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | lead_source.merchant | merchant.xml:1850 | Constant value 'REFERRAL' in constant object 'lead_source' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | lead_status.platform | merchant.xml:1853 | Constant object 'lead_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | lead_status.merchant | merchant.xml:1864 | Constant value 'NEW' in constant object 'lead_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | lead_status.merchant | merchant.xml:1865 | Constant value 'CONTACTING' in constant object 'lead_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | lead_status.merchant | merchant.xml:1866 | Constant value 'QUALIFIED' in constant object 'lead_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | lead_status.merchant | merchant.xml:1867 | Constant value 'CONVERTED' in constant object 'lead_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | lead_activity_type.platform | merchant.xml:1870 | Constant object 'lead_activity_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | lead_activity_type.merchant | merchant.xml:1881 | Constant value 'CALL' in constant object 'lead_activity_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | lead_activity_type.merchant | merchant.xml:1882 | Constant value 'EMAIL' in constant object 'lead_activity_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | lead_activity_type.merchant | merchant.xml:1883 | Constant value 'MEETING' in constant object 'lead_activity_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | quotation_status.platform | merchant.xml:1886 | Constant object 'quotation_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | quotation_status.merchant | merchant.xml:1897 | Constant value 'DRAFT' in constant object 'quotation_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | quotation_status.merchant | merchant.xml:1898 | Constant value 'SENT' in constant object 'quotation_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | quotation_status.merchant | merchant.xml:1899 | Constant value 'ACCEPTED' in constant object 'quotation_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | quotation_status.merchant | merchant.xml:1900 | Constant value 'REJECTED' in constant object 'quotation_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | sales_order_status.platform | merchant.xml:1903 | Constant object 'sales_order_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | sales_order_status.merchant | merchant.xml:1914 | Constant value 'CONFIRMED' in constant object 'sales_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | sales_order_status.merchant | merchant.xml:1915 | Constant value 'FULFILLING' in constant object 'sales_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | sales_order_status.merchant | merchant.xml:1916 | Constant value 'CLOSED' in constant object 'sales_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | account_type.platform | merchant.xml:1919 | Constant object 'account_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | account_type.merchant | merchant.xml:1930 | Constant value 'ASSET' in constant object 'account_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | account_type.merchant | merchant.xml:1931 | Constant value 'LIABILITY' in constant object 'account_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | account_type.merchant | merchant.xml:1932 | Constant value 'REVENUE' in constant object 'account_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | account_type.merchant | merchant.xml:1933 | Constant value 'EXPENSE' in constant object 'account_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | journal_status.platform | merchant.xml:1936 | Constant object 'journal_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | journal_status.merchant | merchant.xml:1947 | Constant value 'DRAFT' in constant object 'journal_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | journal_status.merchant | merchant.xml:1948 | Constant value 'POSTED' in constant object 'journal_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | payment_status.platform | merchant.xml:1951 | Constant object 'payment_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | payment_status.merchant | merchant.xml:1962 | Constant value 'PENDING' in constant object 'payment_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | payment_status.merchant | merchant.xml:1963 | Constant value 'PAID' in constant object 'payment_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | payment_status.merchant | merchant.xml:1964 | Constant value 'REFUNDED' in constant object 'payment_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | invoice_status.platform | merchant.xml:1967 | Constant object 'invoice_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | invoice_status.merchant | merchant.xml:1978 | Constant value 'DRAFT' in constant object 'invoice_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | invoice_status.merchant | merchant.xml:1979 | Constant value 'ISSUED' in constant object 'invoice_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | invoice_status.merchant | merchant.xml:1980 | Constant value 'SETTLED' in constant object 'invoice_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | invoice_status.merchant | merchant.xml:1981 | Constant value 'OVERDUE' in constant object 'invoice_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | vat_rate.platform | merchant.xml:1984 | Constant object 'vat_rate' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | vat_rate.merchant | merchant.xml:1995 | Constant value 'VAT_24' in constant object 'vat_rate' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | vat_rate.merchant | merchant.xml:1996 | Constant value 'VAT_14' in constant object 'vat_rate' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | vat_rate.merchant | merchant.xml:1997 | Constant value 'VAT_10' in constant object 'vat_rate' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | vat_rate.merchant | merchant.xml:1998 | Constant value 'VAT_0' in constant object 'vat_rate' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | expense_status.platform | merchant.xml:2001 | Constant object 'expense_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | expense_status.merchant | merchant.xml:2012 | Constant value 'DRAFT' in constant object 'expense_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | expense_status.merchant | merchant.xml:2013 | Constant value 'PENDING_APPROVAL' in constant object 'expense_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | expense_status.merchant | merchant.xml:2014 | Constant value 'APPROVED' in constant object 'expense_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | expense_status.merchant | merchant.xml:2015 | Constant value 'REIMBURSED' in constant object 'expense_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | expense_category.platform | merchant.xml:2018 | Constant object 'expense_category' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | expense_category.merchant | merchant.xml:2029 | Constant value 'TRAVEL' in constant object 'expense_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | expense_category.merchant | merchant.xml:2030 | Constant value 'MEALS' in constant object 'expense_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | expense_category.merchant | merchant.xml:2031 | Constant value 'OFFICE_SUPPLIES' in constant object 'expense_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | statement_type.platform | merchant.xml:2034 | Constant object 'statement_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | statement_type.merchant | merchant.xml:2045 | Constant value 'BALANCE_SHEET' in constant object 'statement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | statement_type.merchant | merchant.xml:2046 | Constant value 'INCOME_STATEMENT' in constant object 'statement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | statement_type.merchant | merchant.xml:2047 | Constant value 'CASH_FLOW' in constant object 'statement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | statement_status.platform | merchant.xml:2050 | Constant object 'statement_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | statement_status.merchant | merchant.xml:2061 | Constant value 'GENERATING' in constant object 'statement_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | statement_status.merchant | merchant.xml:2062 | Constant value 'COMPLETED' in constant object 'statement_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | statement_status.merchant | merchant.xml:2063 | Constant value 'ARCHIVED' in constant object 'statement_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | budget_category.platform | merchant.xml:2066 | Constant object 'budget_category' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | budget_category.merchant | merchant.xml:2077 | Constant value 'OPERATIONAL' in constant object 'budget_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | budget_category.merchant | merchant.xml:2078 | Constant value 'CAPITAL' in constant object 'budget_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | budget_category.merchant | merchant.xml:2079 | Constant value 'MARKETING' in constant object 'budget_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | budget_status.platform | merchant.xml:2082 | Constant object 'budget_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | budget_status.merchant | merchant.xml:2093 | Constant value 'DRAFT' in constant object 'budget_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | budget_status.merchant | merchant.xml:2094 | Constant value 'APPROVED' in constant object 'budget_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | budget_status.merchant | merchant.xml:2095 | Constant value 'CLOSED' in constant object 'budget_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | depreciation_method.platform | merchant.xml:2098 | Constant object 'depreciation_method' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | depreciation_method.merchant | merchant.xml:2109 | Constant value 'STRAIGHT_LINE' in constant object 'depreciation_method' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | depreciation_method.merchant | merchant.xml:2110 | Constant value 'DOUBLE_DECLINING' in constant object 'depreciation_method' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | maintenance_type.platform | merchant.xml:2113 | Constant object 'maintenance_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | maintenance_type.merchant | merchant.xml:2124 | Constant value 'PREVENTIVE' in constant object 'maintenance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | maintenance_type.merchant | merchant.xml:2125 | Constant value 'CORRECTIVE' in constant object 'maintenance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | maintenance_type.merchant | merchant.xml:2126 | Constant value 'OVERHAUL' in constant object 'maintenance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | maintenance_status.platform | merchant.xml:2129 | Constant object 'maintenance_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | maintenance_status.merchant | merchant.xml:2140 | Constant value 'PENDING' in constant object 'maintenance_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | maintenance_status.merchant | merchant.xml:2141 | Constant value 'IN_PROGRESS' in constant object 'maintenance_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | maintenance_status.merchant | merchant.xml:2142 | Constant value 'COMPLETED' in constant object 'maintenance_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | policy_type.platform | merchant.xml:2145 | Constant object 'policy_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | policy_type.merchant | merchant.xml:2156 | Constant value 'PROPERTY' in constant object 'policy_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | policy_type.merchant | merchant.xml:2157 | Constant value 'VEHICLE' in constant object 'policy_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | policy_type.merchant | merchant.xml:2158 | Constant value 'LIABILITY' in constant object 'policy_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | compliance_type.platform | merchant.xml:2161 | Constant object 'compliance_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | compliance_type.merchant | merchant.xml:2172 | Constant value 'INDUSTRY_STANDARD' in constant object 'compliance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | compliance_type.merchant | merchant.xml:2173 | Constant value 'INTERNAL_POLICY' in constant object 'compliance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | compliance_type.merchant | merchant.xml:2174 | Constant value 'REGULATION' in constant object 'compliance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | action_type.platform | merchant.xml:2177 | Constant object 'action_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | action_type.merchant | merchant.xml:2188 | Constant value 'CREATE' in constant object 'action_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | action_type.merchant | merchant.xml:2189 | Constant value 'UPDATE' in constant object 'action_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | action_type.merchant | merchant.xml:2190 | Constant value 'DELETE' in constant object 'action_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | action_type.merchant | merchant.xml:2191 | Constant value 'LOGIN' in constant object 'action_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | notification_channel.platform | merchant.xml:2194 | Constant object 'notification_channel' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | notification_channel.merchant | merchant.xml:2205 | Constant value 'EMAIL' in constant object 'notification_channel' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | notification_channel.merchant | merchant.xml:2206 | Constant value 'SMS' in constant object 'notification_channel' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | notification_channel.merchant | merchant.xml:2207 | Constant value 'IN_APP' in constant object 'notification_channel' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | auth_method_type.platform | merchant.xml:2210 | Constant object 'auth_method_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | auth_method_type.merchant | merchant.xml:2221 | Constant value 'API_KEY' in constant object 'auth_method_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | auth_method_type.merchant | merchant.xml:2222 | Constant value 'OAUTH2' in constant object 'auth_method_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | auth_method_type.merchant | merchant.xml:2223 | Constant value 'BASIC_AUTH' in constant object 'auth_method_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-002 | customer_status.platform | merchant.xml:2226 | Constant object 'customer_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
KSML-CONSTANT-008 | customer_status.merchant | merchant.xml:2237 | Constant value 'ACTIVE' in constant object 'customer_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | customer_status.merchant | merchant.xml:2238 | Constant value 'INACTIVE' in constant object 'customer_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-CONSTANT-008 | customer_status.merchant | merchant.xml:2239 | Constant value 'BLACKLISTED' in constant object 'customer_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
KSML-REFERENCE-003 | user_account.city_by_ip | merchant.xml:56 | Field 'city_by_ip' in 'user_account' references target object 'cityByIp' which does not exist in the model. | Check agents/ERROR-FIX.md |
KSML-REFERENCE-003 | user_account.remote_ip | merchant.xml:55 | Field 'remote_ip' in 'user_account' references target object 'remoteIp' which does not exist in the model. | Check agents/ERROR-FIX.md |
KSML-REFERENCE-003 | audit_log.remote_ip | merchant.xml:1225 | Field 'remote_ip' in 'audit_log' references target object 'remoteIp' which does not exist in the model. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | time_slot.is_peak_hour | merchant.xml:142 | Boolean field 'time_slot.is_peak_hour' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_peak_hour="false" -> peak_hour="false". Also update all model references that use 'is_peak_hour'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | worked_hour_entry.is_overtime | merchant.xml:415 | Boolean field 'worked_hour_entry.is_overtime' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_overtime="false" -> overtime="false". Also update all model references that use 'is_overtime'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | customer_contact.is_primary | merchant.xml:580 | Boolean field 'customer_contact.is_primary' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_primary="true" -> primary="true". Also update all model references that use 'is_primary'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | product.is_service | merchant.xml:689 | Boolean field 'product.is_service' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_service="true" -> service="true". Also update all model references that use 'is_service'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | product.is_taxable | merchant.xml:689 | Boolean field 'product.is_taxable' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_taxable="true" -> taxable="true". Also update all model references that use 'is_taxable'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | product_service.is_customizable | merchant.xml:701 | Boolean field 'product_service.is_customizable' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_customizable="true" -> customizable="true". Also update all model references that use 'is_customizable'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | price_list.is_default | merchant.xml:725 | Boolean field 'price_list.is_default' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_default="true" -> default="true". Also update all model references that use 'is_default'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | service_configuration_option.is_required | merchant.xml:737 | Boolean field 'service_configuration_option.is_required' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_required="false" -> required="false". Also update all model references that use 'is_required'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | material_item.is_consumable | merchant.xml:771 | Boolean field 'material_item.is_consumable' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_consumable="true" -> consumable="true". Also update all model references that use 'is_consumable'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | discount_code.is_active | merchant.xml:812 | Boolean field 'discount_code.is_active' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_active="true" -> active="true". Also update all model references that use 'is_active'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | account_chart.is_active | merchant.xml:911 | Boolean field 'account_chart.is_active' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_active="true" -> active="true". Also update all model references that use 'is_active'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | bank_account.is_operating_account | merchant.xml:1063 | Boolean field 'bank_account.is_operating_account' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_operating_account="true" -> operating_account="true". Also update all model references that use 'is_operating_account'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | equipment.is_mobile | merchant.xml:1103 | Boolean field 'equipment.is_mobile' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_mobile="true" -> mobile="true". Also update all model references that use 'is_mobile'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | system_automation_hook.is_active | merchant.xml:1279 | Boolean field 'system_automation_hook.is_active' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_active="true" -> active="true". Also update all model references that use 'is_active'. | Check agents/ERROR-FIX.md |
KSML-NAMING-BOOLEAN-001 | external_integration.is_active | merchant.xml:1291 | Boolean field 'external_integration.is_active' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_active="true" -> active="true". Also update all model references that use 'is_active'. | Check agents/ERROR-FIX.md |
KSML-KEYWORD-002 | /root/user_role_assignment/@user | merchant.xml:81 | KSML XML naming error at merchant.xml:81: element <user_role_assignment> defines an XML attribute named 'user', which conflicts with reserved keywords in: SQL. Rename the attribute in the KSML XML itself and keep its current value; for example, change user="..." to user_id="...". Also update any <_value> attributes or other model references that use the old field name. | Edit the KSML XML name using the concrete snake_case example. |
KSML-KEYWORD-002 | /root/audit_log/@user | merchant.xml:1228 | KSML XML naming error at merchant.xml:1228: element <audit_log> defines an XML attribute named 'user', which conflicts with reserved keywords in: SQL. Rename the attribute in the KSML XML itself and keep its current value; for example, change user="..." to user_id="...". Also update any <_value> attributes or other model references that use the old field name. | Edit the KSML XML name using the concrete snake_case example. |
⚠️ Warnings
| Rule ID | Target | Source | Warning Message |
|---|---|---|---|
KSML-OBJECT-002 | merchant._module_key | merchant.xml:17 | Module key 'organizational_structure' on object 'merchant' should be lowercase kebab-case. |
KSML-OBJECT-002 | employee._module_key | merchant.xml:30 | Module key 'employee_management' on object 'employee' should be lowercase kebab-case. |
KSML-OBJECT-002 | user_account._module_key | merchant.xml:47 | Module key 'user_management' on object 'user_account' should be lowercase kebab-case. |
KSML-OBJECT-002 | user_role._module_key | merchant.xml:61 | Module key 'role_management' on object 'user_role' should be lowercase kebab-case. |
KSML-OBJECT-002 | user_role_assignment._module_key | merchant.xml:72 | Module key 'role_assignment' on object 'user_role_assignment' should be lowercase kebab-case. |
KSML-OBJECT-002 | permission_set._module_key | merchant.xml:83 | Module key 'permission_control' on object 'permission_set' should be lowercase kebab-case. |
KSML-OBJECT-002 | role_permission._module_key | merchant.xml:93 | Module key 'permission_control' on object 'role_permission' should be lowercase kebab-case. |
KSML-OBJECT-002 | time_slot._module_key | merchant.xml:132 | Module key 'time_slots' on object 'time_slot' should be lowercase kebab-case. |
KSML-OBJECT-002 | fulfillment_event._module_key | merchant.xml:175 | Module key 'fulfillment_events' on object 'fulfillment_event' should be lowercase kebab-case. |
KSML-OBJECT-002 | delivery_vehicle._module_key | merchant.xml:228 | Module key 'fleet_management' on object 'delivery_vehicle' should be lowercase kebab-case. |
KSML-OBJECT-002 | vehicle_assignment._module_key | merchant.xml:243 | Module key 'fleet_management' on object 'vehicle_assignment' should be lowercase kebab-case. |
KSML-OBJECT-002 | load_plan._module_key | merchant.xml:255 | Module key 'route_planning' on object 'load_plan' should be lowercase kebab-case. |
KSML-OBJECT-002 | load_plan_item._module_key | merchant.xml:269 | Module key 'route_planning' on object 'load_plan_item' should be lowercase kebab-case. |
KSML-OBJECT-002 | service_appointment._module_key | merchant.xml:280 | Module key 'service_scheduling' on object 'service_appointment' should be lowercase kebab-case. |
KSML-OBJECT-002 | service_team._module_key | merchant.xml:296 | Module key 'service_scheduling' on object 'service_team' should be lowercase kebab-case. |
KSML-OBJECT-002 | team_member._module_key | merchant.xml:307 | Module key 'service_scheduling' on object 'team_member' should be lowercase kebab-case. |
KSML-OBJECT-002 | job_assignment._module_key | merchant.xml:318 | Module key 'service_scheduling' on object 'job_assignment' should be lowercase kebab-case. |
KSML-OBJECT-002 | work_order._module_key | merchant.xml:331 | Module key 'work_order_management' on object 'work_order' should be lowercase kebab-case. |
KSML-OBJECT-002 | task._module_key | merchant.xml:347 | Module key 'work_order_management' on object 'task' should be lowercase kebab-case. |
KSML-OBJECT-002 | department._module_key | merchant.xml:361 | Module key 'staff_registry' on object 'department' should be lowercase kebab-case. |
KSML-OBJECT-002 | job_position._module_key | merchant.xml:373 | Module key 'staff_registry' on object 'job_position' should be lowercase kebab-case. |
KSML-OBJECT-002 | employment_record._module_key | merchant.xml:385 | Module key 'staff_registry' on object 'employment_record' should be lowercase kebab-case. |
KSML-OBJECT-002 | worked_hour_entry._module_key | merchant.xml:401 | Module key 'worked_hours' on object 'worked_hour_entry' should be lowercase kebab-case. |
KSML-OBJECT-002 | timesheet._module_key | merchant.xml:417 | Module key 'worked_hours' on object 'timesheet' should be lowercase kebab-case. |
KSML-OBJECT-002 | payroll_calculation._module_key | merchant.xml:431 | Module key 'payroll_calculations' on object 'payroll_calculation' should be lowercase kebab-case. |
KSML-OBJECT-002 | payroll_item._module_key | merchant.xml:447 | Module key 'payroll_calculations' on object 'payroll_item' should be lowercase kebab-case. |
KSML-OBJECT-002 | leave_request._module_key | merchant.xml:483 | Module key 'leave_tracking' on object 'leave_request' should be lowercase kebab-case. |
KSML-OBJECT-002 | leave_balance._module_key | merchant.xml:500 | Module key 'leave_tracking' on object 'leave_balance' should be lowercase kebab-case. |
KSML-OBJECT-002 | training_program._module_key | merchant.xml:514 | Module key 'training_and_development' on object 'training_program' should be lowercase kebab-case. |
KSML-OBJECT-002 | employee_training_enrollment._module_key | merchant.xml:526 | Module key 'training_and_development' on object 'employee_training_enrollment' should be lowercase kebab-case. |
KSML-OBJECT-002 | customer._module_key | merchant.xml:538 | Module key 'private_and_corporate_customers' on object 'customer' should be lowercase kebab-case. |
KSML-OBJECT-002 | corporate_customer._module_key | merchant.xml:555 | Module key 'private_and_corporate_customers' on object 'corporate_customer' should be lowercase kebab-case. |
KSML-OBJECT-002 | customer_contact._module_key | merchant.xml:568 | Module key 'linked_contacts' on object 'customer_contact' should be lowercase kebab-case. |
KSML-OBJECT-002 | billing_info._module_key | merchant.xml:582 | Module key 'billing_info' on object 'billing_info' should be lowercase kebab-case. |
KSML-OBJECT-002 | customer_history_event._module_key | merchant.xml:595 | Module key 'customer_history' on object 'customer_history_event' should be lowercase kebab-case. |
KSML-OBJECT-002 | contract_document._module_key | merchant.xml:625 | Module key 'document_storage' on object 'contract_document' should be lowercase kebab-case. |
KSML-OBJECT-002 | support_ticket._module_key | merchant.xml:638 | Module key 'customer_support' on object 'support_ticket' should be lowercase kebab-case. |
KSML-OBJECT-002 | ticket_reply._module_key | merchant.xml:653 | Module key 'customer_support' on object 'ticket_reply' should be lowercase kebab-case. |
KSML-OBJECT-002 | product_category._module_key | merchant.xml:665 | Module key 'product_configuration' on object 'product_category' should be lowercase kebab-case. |
KSML-OBJECT-002 | product._module_key | merchant.xml:676 | Module key 'product_configuration' on object 'product' should be lowercase kebab-case. |
KSML-OBJECT-002 | product_service._module_key | merchant.xml:691 | Module key 'service_configuration' on object 'product_service' should be lowercase kebab-case. |
KSML-OBJECT-002 | service_configuration_option._module_key | merchant.xml:727 | Module key 'service_configuration' on object 'service_configuration_option' should be lowercase kebab-case. |
KSML-OBJECT-002 | product_bundle._module_key | merchant.xml:739 | Module key 'product_configuration' on object 'product_bundle' should be lowercase kebab-case. |
KSML-OBJECT-002 | bundle_item._module_key | merchant.xml:749 | Module key 'product_configuration' on object 'bundle_item' should be lowercase kebab-case. |
KSML-OBJECT-002 | material_item._module_key | merchant.xml:760 | Module key 'product_configuration' on object 'material_item' should be lowercase kebab-case. |
KSML-OBJECT-002 | discount_code._module_key | merchant.xml:800 | Module key 'discount_codes' on object 'discount_code' should be lowercase kebab-case. |
KSML-OBJECT-002 | lead._module_key | merchant.xml:814 | Module key 'lead_tracking' on object 'lead' should be lowercase kebab-case. |
KSML-OBJECT-002 | lead_activity._module_key | merchant.xml:828 | Module key 'lead_tracking' on object 'lead_activity' should be lowercase kebab-case. |
KSML-OBJECT-002 | conversion_metric._module_key | merchant.xml:841 | Module key 'conversion_metrics' on object 'conversion_metric' should be lowercase kebab-case. |
KSML-OBJECT-002 | quotation._module_key | merchant.xml:855 | Module key 'sales_process' on object 'quotation' should be lowercase kebab-case. |
KSML-OBJECT-002 | quotation_line_item._module_key | merchant.xml:871 | Module key 'sales_process' on object 'quotation_line_item' should be lowercase kebab-case. |
KSML-OBJECT-002 | sales_order._module_key | merchant.xml:884 | Module key 'sales_process' on object 'sales_order' should be lowercase kebab-case. |
KSML-OBJECT-002 | account_chart._module_key | merchant.xml:901 | Module key 'financial_summaries' on object 'account_chart' should be lowercase kebab-case. |
KSML-OBJECT-002 | journal_entry._module_key | merchant.xml:913 | Module key 'financial_summaries' on object 'journal_entry' should be lowercase kebab-case. |
KSML-OBJECT-002 | ledger_transaction._module_key | merchant.xml:926 | Module key 'financial_summaries' on object 'ledger_transaction' should be lowercase kebab-case. |
KSML-OBJECT-002 | financial_statement._module_key | merchant.xml:1024 | Module key 'financial_summaries' on object 'financial_statement' should be lowercase kebab-case. |
KSML-OBJECT-002 | bank_account._module_key | merchant.xml:1052 | Module key 'cash_management' on object 'bank_account' should be lowercase kebab-case. |
KSML-OBJECT-002 | asset_category._module_key | merchant.xml:1065 | Module key 'asset_management' on object 'asset_category' should be lowercase kebab-case. |
KSML-OBJECT-002 | asset._module_key | merchant.xml:1076 | Module key 'asset_management' on object 'asset' should be lowercase kebab-case. |
KSML-OBJECT-002 | maintenance_schedule._module_key | merchant.xml:1145 | Module key 'maintenance_schedules' on object 'maintenance_schedule' should be lowercase kebab-case. |
KSML-OBJECT-002 | maintenance_log._module_key | merchant.xml:1159 | Module key 'maintenance_schedules' on object 'maintenance_log' should be lowercase kebab-case. |
KSML-OBJECT-002 | depreciation_record._module_key | merchant.xml:1173 | Module key 'asset_accounting' on object 'depreciation_record' should be lowercase kebab-case. |
KSML-OBJECT-002 | compliance_document._module_key | merchant.xml:1201 | Module key 'document_storage' on object 'compliance_document' should be lowercase kebab-case. |
KSML-OBJECT-002 | audit_log._module_key | merchant.xml:1215 | Module key 'audit_logs' on object 'audit_log' should be lowercase kebab-case. |
KSML-OBJECT-002 | version_history._module_key | merchant.xml:1230 | Module key 'versioning_and_soft_deletes' on object 'version_history' should be lowercase kebab-case. |
KSML-OBJECT-002 | deleted_record._module_key | merchant.xml:1245 | Module key 'versioning_and_soft_deletes' on object 'deleted_record' should be lowercase kebab-case. |
KSML-OBJECT-002 | system_automation_hook._module_key | merchant.xml:1269 | Module key 'automation_hooks' on object 'system_automation_hook' should be lowercase kebab-case. |
KSML-OBJECT-002 | external_integration._module_key | merchant.xml:1281 | Module key 'api_ready_architecture' on object 'external_integration' should be lowercase kebab-case. |
KSML-OBJECT-002 | gender_type._module_key | merchant.xml:1293 | Module key 'basic_data' on object 'gender_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | shipment_status_type._module_key | merchant.xml:1309 | Module key 'basic_data' on object 'shipment_status_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | event_type._module_key | merchant.xml:1327 | Module key 'basic_data' on object 'event_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | movement_type._module_key | merchant.xml:1344 | Module key 'basic_data' on object 'movement_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | vehicle_type._module_key | merchant.xml:1361 | Module key 'basic_data' on object 'vehicle_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | service_status_type._module_key | merchant.xml:1377 | Module key 'basic_data' on object 'service_status_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | team_member_role._module_key | merchant.xml:1394 | Module key 'basic_data' on object 'team_member_role' should be lowercase kebab-case. |
KSML-OBJECT-002 | work_order_status._module_key | merchant.xml:1410 | Module key 'basic_data' on object 'work_order_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | priority_type._module_key | merchant.xml:1426 | Module key 'basic_data' on object 'priority_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | task_status._module_key | merchant.xml:1442 | Module key 'basic_data' on object 'task_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | salary_grade._module_key | merchant.xml:1458 | Module key 'basic_data' on object 'salary_grade' should be lowercase kebab-case. |
KSML-OBJECT-002 | employment_type._module_key | merchant.xml:1474 | Module key 'basic_data' on object 'employment_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | employment_status._module_key | merchant.xml:1490 | Module key 'basic_data' on object 'employment_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | timesheet_status._module_key | merchant.xml:1505 | Module key 'basic_data' on object 'timesheet_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | payroll_status._module_key | merchant.xml:1521 | Module key 'basic_data' on object 'payroll_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | payroll_item_type._module_key | merchant.xml:1537 | Module key 'basic_data' on object 'payroll_item_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | rule_type._module_key | merchant.xml:1553 | Module key 'basic_data' on object 'rule_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | bonus_status._module_key | merchant.xml:1568 | Module key 'basic_data' on object 'bonus_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | leave_type._module_key | merchant.xml:1583 | Module key 'basic_data' on object 'leave_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | leave_status._module_key | merchant.xml:1599 | Module key 'basic_data' on object 'leave_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | training_status._module_key | merchant.xml:1615 | Module key 'basic_data' on object 'training_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | customer_type._module_key | merchant.xml:1631 | Module key 'basic_data' on object 'customer_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | industry_type._module_key | merchant.xml:1646 | Module key 'basic_data' on object 'industry_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | payment_method._module_key | merchant.xml:1662 | Module key 'basic_data' on object 'payment_method' should be lowercase kebab-case. |
KSML-OBJECT-002 | billing_cycle._module_key | merchant.xml:1678 | Module key 'basic_data' on object 'billing_cycle' should be lowercase kebab-case. |
KSML-OBJECT-002 | history_event_type._module_key | merchant.xml:1694 | Module key 'basic_data' on object 'history_event_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | contract_type._module_key | merchant.xml:1710 | Module key 'basic_data' on object 'contract_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | contract_status._module_key | merchant.xml:1725 | Module key 'basic_data' on object 'contract_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | document_type._module_key | merchant.xml:1741 | Module key 'basic_data' on object 'document_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | ticket_status._module_key | merchant.xml:1757 | Module key 'basic_data' on object 'ticket_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | unit_of_measure._module_key | merchant.xml:1773 | Module key 'basic_data' on object 'unit_of_measure' should be lowercase kebab-case. |
KSML-OBJECT-002 | currency_type._module_key | merchant.xml:1790 | Module key 'basic_data' on object 'currency_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | target_audience_type._module_key | merchant.xml:1806 | Module key 'basic_data' on object 'target_audience_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | discount_type._module_key | merchant.xml:1821 | Module key 'basic_data' on object 'discount_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | lead_source._module_key | merchant.xml:1837 | Module key 'basic_data' on object 'lead_source' should be lowercase kebab-case. |
KSML-OBJECT-002 | lead_status._module_key | merchant.xml:1853 | Module key 'basic_data' on object 'lead_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | lead_activity_type._module_key | merchant.xml:1870 | Module key 'basic_data' on object 'lead_activity_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | quotation_status._module_key | merchant.xml:1886 | Module key 'basic_data' on object 'quotation_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | sales_order_status._module_key | merchant.xml:1903 | Module key 'basic_data' on object 'sales_order_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | account_type._module_key | merchant.xml:1919 | Module key 'basic_data' on object 'account_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | journal_status._module_key | merchant.xml:1936 | Module key 'basic_data' on object 'journal_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | payment_status._module_key | merchant.xml:1951 | Module key 'basic_data' on object 'payment_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | invoice_status._module_key | merchant.xml:1967 | Module key 'basic_data' on object 'invoice_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | vat_rate._module_key | merchant.xml:1984 | Module key 'basic_data' on object 'vat_rate' should be lowercase kebab-case. |
KSML-OBJECT-002 | expense_status._module_key | merchant.xml:2001 | Module key 'basic_data' on object 'expense_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | expense_category._module_key | merchant.xml:2018 | Module key 'basic_data' on object 'expense_category' should be lowercase kebab-case. |
KSML-OBJECT-002 | statement_type._module_key | merchant.xml:2034 | Module key 'basic_data' on object 'statement_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | statement_status._module_key | merchant.xml:2050 | Module key 'basic_data' on object 'statement_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | budget_category._module_key | merchant.xml:2066 | Module key 'basic_data' on object 'budget_category' should be lowercase kebab-case. |
KSML-OBJECT-002 | budget_status._module_key | merchant.xml:2082 | Module key 'basic_data' on object 'budget_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | depreciation_method._module_key | merchant.xml:2098 | Module key 'basic_data' on object 'depreciation_method' should be lowercase kebab-case. |
KSML-OBJECT-002 | maintenance_type._module_key | merchant.xml:2113 | Module key 'basic_data' on object 'maintenance_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | maintenance_status._module_key | merchant.xml:2129 | Module key 'basic_data' on object 'maintenance_status' should be lowercase kebab-case. |
KSML-OBJECT-002 | policy_type._module_key | merchant.xml:2145 | Module key 'basic_data' on object 'policy_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | compliance_type._module_key | merchant.xml:2161 | Module key 'basic_data' on object 'compliance_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | action_type._module_key | merchant.xml:2177 | Module key 'basic_data' on object 'action_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | notification_channel._module_key | merchant.xml:2194 | Module key 'basic_data' on object 'notification_channel' should be lowercase kebab-case. |
KSML-OBJECT-002 | auth_method_type._module_key | merchant.xml:2210 | Module key 'basic_data' on object 'auth_method_type' should be lowercase kebab-case. |
KSML-OBJECT-002 | customer_status._module_key | merchant.xml:2226 | Module key 'basic_data' on object 'customer_status' should be lowercase kebab-case. |
KSML-CONSTANT-005 | gender_type.id | merchant.xml:1293 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | shipment_status_type.id | merchant.xml:1309 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | event_type.id | merchant.xml:1327 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | movement_type.id | merchant.xml:1344 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | vehicle_type.id | merchant.xml:1361 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | service_status_type.id | merchant.xml:1377 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | team_member_role.id | merchant.xml:1394 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | work_order_status.id | merchant.xml:1410 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | priority_type.id | merchant.xml:1426 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | task_status.id | merchant.xml:1442 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | salary_grade.id | merchant.xml:1458 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | employment_type.id | merchant.xml:1474 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | employment_status.id | merchant.xml:1490 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | timesheet_status.id | merchant.xml:1505 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | payroll_status.id | merchant.xml:1521 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | payroll_item_type.id | merchant.xml:1537 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | rule_type.id | merchant.xml:1553 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | bonus_status.id | merchant.xml:1568 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | leave_type.id | merchant.xml:1583 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | leave_status.id | merchant.xml:1599 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | training_status.id | merchant.xml:1615 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | customer_type.id | merchant.xml:1631 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | industry_type.id | merchant.xml:1646 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | payment_method.id | merchant.xml:1662 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | billing_cycle.id | merchant.xml:1678 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | history_event_type.id | merchant.xml:1694 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | contract_type.id | merchant.xml:1710 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | contract_status.id | merchant.xml:1725 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | document_type.id | merchant.xml:1741 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | ticket_status.id | merchant.xml:1757 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | unit_of_measure.id | merchant.xml:1773 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | currency_type.id | merchant.xml:1790 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | target_audience_type.id | merchant.xml:1806 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | discount_type.id | merchant.xml:1821 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | lead_source.id | merchant.xml:1837 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | lead_status.id | merchant.xml:1853 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | lead_activity_type.id | merchant.xml:1870 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | quotation_status.id | merchant.xml:1886 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | sales_order_status.id | merchant.xml:1903 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | account_type.id | merchant.xml:1919 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | journal_status.id | merchant.xml:1936 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | payment_status.id | merchant.xml:1951 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | invoice_status.id | merchant.xml:1967 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | vat_rate.id | merchant.xml:1984 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | expense_status.id | merchant.xml:2001 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | expense_category.id | merchant.xml:2018 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | statement_type.id | merchant.xml:2034 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | statement_status.id | merchant.xml:2050 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | budget_category.id | merchant.xml:2066 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | budget_status.id | merchant.xml:2082 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | depreciation_method.id | merchant.xml:2098 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | maintenance_type.id | merchant.xml:2113 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | maintenance_status.id | merchant.xml:2129 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | policy_type.id | merchant.xml:2145 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | compliance_type.id | merchant.xml:2161 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | action_type.id | merchant.xml:2177 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | notification_channel.id | merchant.xml:2194 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | auth_method_type.id | merchant.xml:2210 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-CONSTANT-005 | customer_status.id | merchant.xml:2226 | Constant value IDs should preferably start from 1001 and increment sequentially. |
KSML-BUSINESS-002 | external_integration.api_endpoint | merchant.xml:1286 | Field 'api_endpoint' in business object 'external_integration' should preferably use a rich concrete typical value instead of generic string(). |
KSML-REFERENCE-005 | product.category | merchant.xml:682 | Field 'category' in 'product' represents a finite set and should preferably reference a constant object. |
KSML-MODULE-004 | gender_type | merchant.xml:1293 | Constant object 'gender_type' is referenced by exactly one business object ('employee'), but its _module_key ('basic_data') does not match the business object's _module_key ('employee_management'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | shipment_status_type | merchant.xml:1309 | Constant object 'shipment_status_type' is referenced by exactly one business object ('shipment'), but its _module_key ('basic_data') does not match the business object's _module_key ('moves'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | event_type | merchant.xml:1327 | Constant object 'event_type' is referenced by exactly one business object ('fulfillment_event'), but its _module_key ('basic_data') does not match the business object's _module_key ('fulfillment_events'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | movement_type | merchant.xml:1344 | Constant object 'movement_type' is referenced by exactly one business object ('stock_movement'), but its _module_key ('basic_data') does not match the business object's _module_key ('inventory'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | service_status_type | merchant.xml:1377 | Constant object 'service_status_type' is referenced by exactly one business object ('service_appointment'), but its _module_key ('basic_data') does not match the business object's _module_key ('service_scheduling'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | team_member_role | merchant.xml:1394 | Constant object 'team_member_role' is referenced by exactly one business object ('team_member'), but its _module_key ('basic_data') does not match the business object's _module_key ('service_scheduling'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | work_order_status | merchant.xml:1410 | Constant object 'work_order_status' is referenced by exactly one business object ('work_order'), but its _module_key ('basic_data') does not match the business object's _module_key ('work_order_management'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | task_status | merchant.xml:1442 | Constant object 'task_status' is referenced by exactly one business object ('task'), but its _module_key ('basic_data') does not match the business object's _module_key ('work_order_management'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | employment_type | merchant.xml:1474 | Constant object 'employment_type' is referenced by exactly one business object ('employment_record'), but its _module_key ('basic_data') does not match the business object's _module_key ('staff_registry'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | employment_status | merchant.xml:1490 | Constant object 'employment_status' is referenced by exactly one business object ('employment_record'), but its _module_key ('basic_data') does not match the business object's _module_key ('staff_registry'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | timesheet_status | merchant.xml:1505 | Constant object 'timesheet_status' is referenced by exactly one business object ('timesheet'), but its _module_key ('basic_data') does not match the business object's _module_key ('worked_hours'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | payroll_status | merchant.xml:1521 | Constant object 'payroll_status' is referenced by exactly one business object ('payroll_calculation'), but its _module_key ('basic_data') does not match the business object's _module_key ('payroll_calculations'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | payroll_item_type | merchant.xml:1537 | Constant object 'payroll_item_type' is referenced by exactly one business object ('payroll_item'), but its _module_key ('basic_data') does not match the business object's _module_key ('payroll_calculations'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | rule_type | merchant.xml:1553 | Constant object 'rule_type' is referenced by exactly one business object ('bonus_scheme'), but its _module_key ('basic_data') does not match the business object's _module_key ('bonuses'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | bonus_status | merchant.xml:1568 | Constant object 'bonus_status' is referenced by exactly one business object ('employee_bonus'), but its _module_key ('basic_data') does not match the business object's _module_key ('bonuses'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | leave_status | merchant.xml:1599 | Constant object 'leave_status' is referenced by exactly one business object ('leave_request'), but its _module_key ('basic_data') does not match the business object's _module_key ('leave_tracking'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | training_status | merchant.xml:1615 | Constant object 'training_status' is referenced by exactly one business object ('employee_training_enrollment'), but its _module_key ('basic_data') does not match the business object's _module_key ('training_and_development'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | customer_type | merchant.xml:1631 | Constant object 'customer_type' is referenced by exactly one business object ('customer'), but its _module_key ('basic_data') does not match the business object's _module_key ('private_and_corporate_customers'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | industry_type | merchant.xml:1646 | Constant object 'industry_type' is referenced by exactly one business object ('corporate_customer'), but its _module_key ('basic_data') does not match the business object's _module_key ('private_and_corporate_customers'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | billing_cycle | merchant.xml:1678 | Constant object 'billing_cycle' is referenced by exactly one business object ('billing_info'), but its _module_key ('basic_data') does not match the business object's _module_key ('billing_info'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | history_event_type | merchant.xml:1694 | Constant object 'history_event_type' is referenced by exactly one business object ('customer_history_event'), but its _module_key ('basic_data') does not match the business object's _module_key ('customer_history'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | contract_type | merchant.xml:1710 | Constant object 'contract_type' is referenced by exactly one business object ('service_contract'), but its _module_key ('basic_data') does not match the business object's _module_key ('contracts'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | contract_status | merchant.xml:1725 | Constant object 'contract_status' is referenced by exactly one business object ('service_contract'), but its _module_key ('basic_data') does not match the business object's _module_key ('contracts'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | document_type | merchant.xml:1741 | Constant object 'document_type' is referenced by exactly one business object ('contract_document'), but its _module_key ('basic_data') does not match the business object's _module_key ('document_storage'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | ticket_status | merchant.xml:1757 | Constant object 'ticket_status' is referenced by exactly one business object ('support_ticket'), but its _module_key ('basic_data') does not match the business object's _module_key ('customer_support'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | target_audience_type | merchant.xml:1806 | Constant object 'target_audience_type' is referenced by exactly one business object ('sales_campaign'), but its _module_key ('basic_data') does not match the business object's _module_key ('campaigns'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | discount_type | merchant.xml:1821 | Constant object 'discount_type' is referenced by exactly one business object ('discount_code'), but its _module_key ('basic_data') does not match the business object's _module_key ('discount_codes'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | lead_status | merchant.xml:1853 | Constant object 'lead_status' is referenced by exactly one business object ('lead'), but its _module_key ('basic_data') does not match the business object's _module_key ('lead_tracking'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | lead_activity_type | merchant.xml:1870 | Constant object 'lead_activity_type' is referenced by exactly one business object ('lead_activity'), but its _module_key ('basic_data') does not match the business object's _module_key ('lead_tracking'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | quotation_status | merchant.xml:1886 | Constant object 'quotation_status' is referenced by exactly one business object ('quotation'), but its _module_key ('basic_data') does not match the business object's _module_key ('sales_process'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | sales_order_status | merchant.xml:1903 | Constant object 'sales_order_status' is referenced by exactly one business object ('sales_order'), but its _module_key ('basic_data') does not match the business object's _module_key ('sales_process'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | account_type | merchant.xml:1919 | Constant object 'account_type' is referenced by exactly one business object ('account_chart'), but its _module_key ('basic_data') does not match the business object's _module_key ('financial_summaries'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | journal_status | merchant.xml:1936 | Constant object 'journal_status' is referenced by exactly one business object ('journal_entry'), but its _module_key ('basic_data') does not match the business object's _module_key ('financial_summaries'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | payment_status | merchant.xml:1951 | Constant object 'payment_status' is referenced by exactly one business object ('payment'), but its _module_key ('basic_data') does not match the business object's _module_key ('payments'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | invoice_status | merchant.xml:1967 | Constant object 'invoice_status' is referenced by exactly one business object ('invoice'), but its _module_key ('basic_data') does not match the business object's _module_key ('invoices'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | vat_rate | merchant.xml:1984 | Constant object 'vat_rate' is referenced by exactly one business object ('invoice_line_item'), but its _module_key ('basic_data') does not match the business object's _module_key ('invoices'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | expense_status | merchant.xml:2001 | Constant object 'expense_status' is referenced by exactly one business object ('expense_report'), but its _module_key ('basic_data') does not match the business object's _module_key ('expenses'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | expense_category | merchant.xml:2018 | Constant object 'expense_category' is referenced by exactly one business object ('expense_item'), but its _module_key ('basic_data') does not match the business object's _module_key ('expenses'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | statement_type | merchant.xml:2034 | Constant object 'statement_type' is referenced by exactly one business object ('financial_statement'), but its _module_key ('basic_data') does not match the business object's _module_key ('financial_summaries'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | statement_status | merchant.xml:2050 | Constant object 'statement_status' is referenced by exactly one business object ('financial_statement'), but its _module_key ('basic_data') does not match the business object's _module_key ('financial_summaries'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | budget_category | merchant.xml:2066 | Constant object 'budget_category' is referenced by exactly one business object ('budget'), but its _module_key ('basic_data') does not match the business object's _module_key ('budgeting'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | budget_status | merchant.xml:2082 | Constant object 'budget_status' is referenced by exactly one business object ('budget'), but its _module_key ('basic_data') does not match the business object's _module_key ('budgeting'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | depreciation_method | merchant.xml:2098 | Constant object 'depreciation_method' is referenced by exactly one business object ('asset_category'), but its _module_key ('basic_data') does not match the business object's _module_key ('asset_management'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | maintenance_status | merchant.xml:2129 | Constant object 'maintenance_status' is referenced by exactly one business object ('maintenance_schedule'), but its _module_key ('basic_data') does not match the business object's _module_key ('maintenance_schedules'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | policy_type | merchant.xml:2145 | Constant object 'policy_type' is referenced by exactly one business object ('insurance_policy'), but its _module_key ('basic_data') does not match the business object's _module_key ('insurance'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | compliance_type | merchant.xml:2161 | Constant object 'compliance_type' is referenced by exactly one business object ('compliance_document'), but its _module_key ('basic_data') does not match the business object's _module_key ('document_storage'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | action_type | merchant.xml:2177 | Constant object 'action_type' is referenced by exactly one business object ('audit_log'), but its _module_key ('basic_data') does not match the business object's _module_key ('audit_logs'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | notification_channel | merchant.xml:2194 | Constant object 'notification_channel' is referenced by exactly one business object ('notification_template'), but its _module_key ('basic_data') does not match the business object's _module_key ('notifications'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | auth_method_type | merchant.xml:2210 | Constant object 'auth_method_type' is referenced by exactly one business object ('external_integration'), but its _module_key ('basic_data') does not match the business object's _module_key ('api_ready_architecture'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-MODULE-004 | customer_status | merchant.xml:2226 | Constant object 'customer_status' is referenced by exactly one business object ('customer'), but its _module_key ('basic_data') does not match the business object's _module_key ('private_and_corporate_customers'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
KSML-TENANCY-001 | external_integration | merchant.xml:1281 | Almost all business objects (95/96) contain tenant/merchant fields. Ensure that tenancy is explicitly required, rather than just copied from examples. |
KSML-PRIVACY-001-WARN | employee.mobile_phone | merchant.xml:45 | Contact identifier on person-like subject. Add mobile_phone to _audit_mask_fields (e.g., <employee _audit_mask_fields="mobile_phone">). |
KSML-PRIVACY-001-WARN | employee.email | merchant.xml:45 | Contact identifier on person-like subject. Add email to _audit_mask_fields (e.g., <employee _audit_mask_fields="email">). |
KSML-PRIVACY-001-WARN | customer.mobile_phone | merchant.xml:553 | Contact identifier on person-like subject. Add mobile_phone to _audit_mask_fields (e.g., <customer _audit_mask_fields="mobile_phone">). |
KSML-PRIVACY-001-WARN | customer.email | merchant.xml:553 | Contact identifier on person-like subject. Add email to _audit_mask_fields (e.g., <customer _audit_mask_fields="email">). |
KSML-PRIVACY-001-WARN | customer.billing_address | merchant.xml:553 | Location data on person-like subject. Add billing_address to _audit_mask_fields (e.g., <customer _audit_mask_fields="billing_address">). |
KSML-PRIVACY-001-WARN | customer.shipping_address | merchant.xml:553 | Location data on person-like subject. Add shipping_address to _audit_mask_fields (e.g., <customer _audit_mask_fields="shipping_address">). |
KSML-PRIVACY-001-WARN | corporate_customer.tax_id | merchant.xml:566 | Government identifier field. Add tax_id to _audit_mask_fields (e.g., <corporate_customer _audit_mask_fields="tax_id">). |
KSML-PRIVACY-001-WARN | customer_contact.contact_email | merchant.xml:580 | Contact identifier on person-like subject. Add contact_email to _audit_mask_fields (e.g., <customer_contact _audit_mask_fields="contact_email">). |
KSML-PRIVACY-001-WARN | bank_account.account_name | merchant.xml:1063 | Personal attribute on high-risk privacy subject. Add account_name to _audit_mask_fields (e.g., <bank_account _audit_mask_fields="account_name">). |
KSML-PRIVACY-001-WARN | bank_account.bank_name | merchant.xml:1063 | Personal attribute on high-risk privacy subject. Add bank_name to _audit_mask_fields (e.g., <bank_account _audit_mask_fields="bank_name">). |
KSML-PRIVACY-001-WARN | bank_account.account_number | merchant.xml:1063 | Financial data on high-risk privacy subject. Add account_number to _audit_mask_fields (e.g., <bank_account _audit_mask_fields="account_number">). |
💡 Suggestions
| Rule ID | Target | Source | Suggestion |
|---|---|---|---|
KSML-LOG-007 | maintenance_log | merchant.xml:1159 | Object 'maintenance_log' has a name ending with '_log' but is not marked as a logging object. Consider adding _log="true" if this object represents append-only log entries. |
KSML-LOG-007 | audit_log | merchant.xml:1215 | Object 'audit_log' has a name ending with '_log' but is not marked as a logging object. Consider adding _log="true" if this object represents append-only log entries. |
KSML-UI-002 | gender_type | merchant.xml:1293 | Constant object 'gender_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | shipment_status_type | merchant.xml:1309 | Status-like constant 'shipment_status_type' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | shipment_status_type | merchant.xml:1309 | Constant object 'shipment_status_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | shipment_status_type | merchant.xml:1309 | Status-like constant 'shipment_status_type' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | event_type | merchant.xml:1327 | Constant object 'event_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | movement_type | merchant.xml:1344 | Constant object 'movement_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | vehicle_type | merchant.xml:1361 | Constant object 'vehicle_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | service_status_type | merchant.xml:1377 | Status-like constant 'service_status_type' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | service_status_type | merchant.xml:1377 | Constant object 'service_status_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | service_status_type | merchant.xml:1377 | Status-like constant 'service_status_type' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | team_member_role | merchant.xml:1394 | Constant object 'team_member_role' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | work_order_status | merchant.xml:1410 | Status-like constant 'work_order_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | work_order_status | merchant.xml:1410 | Constant object 'work_order_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | work_order_status | merchant.xml:1410 | Status-like constant 'work_order_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | priority_type | merchant.xml:1426 | Constant object 'priority_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | task_status | merchant.xml:1442 | Status-like constant 'task_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | task_status | merchant.xml:1442 | Constant object 'task_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | task_status | merchant.xml:1442 | Status-like constant 'task_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | salary_grade | merchant.xml:1458 | Constant object 'salary_grade' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | employment_type | merchant.xml:1474 | Constant object 'employment_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | employment_status | merchant.xml:1490 | Status-like constant 'employment_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | employment_status | merchant.xml:1490 | Constant object 'employment_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | employment_status | merchant.xml:1490 | Status-like constant 'employment_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-001 | timesheet_status | merchant.xml:1505 | Status-like constant 'timesheet_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | timesheet_status | merchant.xml:1505 | Constant object 'timesheet_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | timesheet_status | merchant.xml:1505 | Status-like constant 'timesheet_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-001 | payroll_status | merchant.xml:1521 | Status-like constant 'payroll_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | payroll_status | merchant.xml:1521 | Constant object 'payroll_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | payroll_status | merchant.xml:1521 | Status-like constant 'payroll_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | payroll_item_type | merchant.xml:1537 | Constant object 'payroll_item_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | rule_type | merchant.xml:1553 | Constant object 'rule_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | bonus_status | merchant.xml:1568 | Status-like constant 'bonus_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | bonus_status | merchant.xml:1568 | Constant object 'bonus_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | bonus_status | merchant.xml:1568 | Status-like constant 'bonus_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | leave_type | merchant.xml:1583 | Constant object 'leave_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | leave_status | merchant.xml:1599 | Status-like constant 'leave_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | leave_status | merchant.xml:1599 | Constant object 'leave_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | leave_status | merchant.xml:1599 | Status-like constant 'leave_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-001 | training_status | merchant.xml:1615 | Status-like constant 'training_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | training_status | merchant.xml:1615 | Constant object 'training_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | training_status | merchant.xml:1615 | Status-like constant 'training_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | customer_type | merchant.xml:1631 | Constant object 'customer_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | industry_type | merchant.xml:1646 | Constant object 'industry_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | payment_method | merchant.xml:1662 | Constant object 'payment_method' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | billing_cycle | merchant.xml:1678 | Constant object 'billing_cycle' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | history_event_type | merchant.xml:1694 | Constant object 'history_event_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | contract_type | merchant.xml:1710 | Constant object 'contract_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | contract_status | merchant.xml:1725 | Status-like constant 'contract_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | contract_status | merchant.xml:1725 | Constant object 'contract_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | contract_status | merchant.xml:1725 | Status-like constant 'contract_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | document_type | merchant.xml:1741 | Constant object 'document_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | ticket_status | merchant.xml:1757 | Status-like constant 'ticket_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | ticket_status | merchant.xml:1757 | Constant object 'ticket_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | ticket_status | merchant.xml:1757 | Status-like constant 'ticket_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | unit_of_measure | merchant.xml:1773 | Constant object 'unit_of_measure' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | currency_type | merchant.xml:1790 | Constant object 'currency_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | target_audience_type | merchant.xml:1806 | Constant object 'target_audience_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | discount_type | merchant.xml:1821 | Constant object 'discount_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | lead_source | merchant.xml:1837 | Constant object 'lead_source' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | lead_status | merchant.xml:1853 | Status-like constant 'lead_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | lead_status | merchant.xml:1853 | Constant object 'lead_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | lead_status | merchant.xml:1853 | Status-like constant 'lead_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | lead_activity_type | merchant.xml:1870 | Constant object 'lead_activity_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | quotation_status | merchant.xml:1886 | Status-like constant 'quotation_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | quotation_status | merchant.xml:1886 | Constant object 'quotation_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | quotation_status | merchant.xml:1886 | Status-like constant 'quotation_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-001 | sales_order_status | merchant.xml:1903 | Status-like constant 'sales_order_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | sales_order_status | merchant.xml:1903 | Constant object 'sales_order_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | sales_order_status | merchant.xml:1903 | Status-like constant 'sales_order_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | account_type | merchant.xml:1919 | Constant object 'account_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | journal_status | merchant.xml:1936 | Status-like constant 'journal_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | journal_status | merchant.xml:1936 | Constant object 'journal_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | journal_status | merchant.xml:1936 | Status-like constant 'journal_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-001 | payment_status | merchant.xml:1951 | Status-like constant 'payment_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | payment_status | merchant.xml:1951 | Constant object 'payment_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | payment_status | merchant.xml:1951 | Status-like constant 'payment_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-001 | invoice_status | merchant.xml:1967 | Status-like constant 'invoice_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | invoice_status | merchant.xml:1967 | Constant object 'invoice_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | invoice_status | merchant.xml:1967 | Status-like constant 'invoice_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | vat_rate | merchant.xml:1984 | Constant object 'vat_rate' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | expense_status | merchant.xml:2001 | Status-like constant 'expense_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | expense_status | merchant.xml:2001 | Constant object 'expense_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | expense_status | merchant.xml:2001 | Status-like constant 'expense_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | expense_category | merchant.xml:2018 | Constant object 'expense_category' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | statement_type | merchant.xml:2034 | Constant object 'statement_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | statement_status | merchant.xml:2050 | Status-like constant 'statement_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | statement_status | merchant.xml:2050 | Constant object 'statement_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | statement_status | merchant.xml:2050 | Status-like constant 'statement_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | budget_category | merchant.xml:2066 | Constant object 'budget_category' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | budget_status | merchant.xml:2082 | Status-like constant 'budget_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | budget_status | merchant.xml:2082 | Constant object 'budget_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | budget_status | merchant.xml:2082 | Status-like constant 'budget_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | depreciation_method | merchant.xml:2098 | Constant object 'depreciation_method' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | maintenance_type | merchant.xml:2113 | Constant object 'maintenance_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | maintenance_status | merchant.xml:2129 | Status-like constant 'maintenance_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | maintenance_status | merchant.xml:2129 | Constant object 'maintenance_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | maintenance_status | merchant.xml:2129 | Status-like constant 'maintenance_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-UI-002 | policy_type | merchant.xml:2145 | Constant object 'policy_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | compliance_type | merchant.xml:2161 | Constant object 'compliance_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | action_type | merchant.xml:2177 | Constant object 'action_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | notification_channel | merchant.xml:2194 | Constant object 'notification_channel' can add display_order="number()" for stable UI sorting. |
KSML-UI-002 | auth_method_type | merchant.xml:2210 | Constant object 'auth_method_type' can add display_order="number()" for stable UI sorting. |
KSML-UI-001 | customer_status | merchant.xml:2226 | Status-like constant 'customer_status' can add color="string()" to declare visual badge colors for values. |
KSML-UI-002 | customer_status | merchant.xml:2226 | Constant object 'customer_status' can add display_order="number()" for stable UI sorting. |
KSML-UI-003 | customer_status | merchant.xml:2226 | Status-like constant 'customer_status' can add progress="number()" to visualize completion progress percentage (0-100). |
KSML-PRIVACY-001-SUG | employee.name | merchant.xml:45 | Personal attribute on person-like subject. Add name to _audit_mask_fields (e.g., <employee _audit_mask_fields="name">). |
KSML-PRIVACY-001-SUG | employee.gender | merchant.xml:45 | Personal attribute on person-like subject. Add gender to _audit_mask_fields (e.g., <employee _audit_mask_fields="gender">). |
KSML-PRIVACY-001-SUG | employee.birth_date | merchant.xml:45 | Personal attribute on person-like subject. Add birth_date to _audit_mask_fields (e.g., <employee _audit_mask_fields="birth_date">). |
KSML-PRIVACY-001-SUG | user_account.display_name | merchant.xml:59 | Personal attribute field. Add display_name to _audit_mask_fields (e.g., <user_account _audit_mask_fields="display_name">). |
KSML-PRIVACY-001-SUG | job_position.salary_grade | merchant.xml:383 | Financial data field. Add salary_grade to _audit_mask_fields (e.g., <job_position _audit_mask_fields="salary_grade">). |
KSML-PRIVACY-001-SUG | payroll_calculation.gross_salary | merchant.xml:445 | Financial data field. Add gross_salary to _audit_mask_fields (e.g., <payroll_calculation _audit_mask_fields="gross_salary">). |
KSML-PRIVACY-001-SUG | customer.name | merchant.xml:553 | Personal attribute on person-like subject. Add name to _audit_mask_fields (e.g., <customer _audit_mask_fields="name">). |
KSML-PRIVACY-001-SUG | customer_contact.contact_name | merchant.xml:580 | Personal attribute on person-like subject. Add contact_name to _audit_mask_fields (e.g., <customer_contact _audit_mask_fields="contact_name">). |
KSML-PRIVACY-001-SUG | billing_info.account_number | merchant.xml:593 | Financial data field. Add account_number to _audit_mask_fields (e.g., <billing_info _audit_mask_fields="account_number">). |
KSML-PRIVACY-001-SUG | lead.contact_email | merchant.xml:826 | Contact identifier field. Add contact_email to _audit_mask_fields (e.g., <lead _audit_mask_fields="contact_email">). |
Privacy Findings
These are model-level risk findings and jurisdiction-specific review references, not a compliance certificate. Field names do not establish legal applicability. Confirm processing purposes, legal bases, retention, individual rights, cross-border transfers and operational evidence separately. Masking alone is not compliance. Regional repetitions do not add to the Summary counts. Official references reviewed on 2026-10-13; check current law and commencement dates before deployment.
Mainland China — PIPL (Personal Information Protection Law)
PIPL (LAW). Confirm the processing falls within PIPL scope, including its territorial rules. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | PIPL Art. 28: financial accounts; verify whether this field contains account information rather than an ordinary business amount |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | PIPL Art. 28: financial accounts; verify whether this field contains account information rather than an ordinary business amount |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | PIPL Art. 28: financial accounts; verify whether this field contains account information rather than an ordinary business amount |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | PIPL Art. 28: financial accounts; verify whether this field contains account information rather than an ordinary business amount |
Hong Kong — PDPO (Personal Data (Privacy) Ordinance)
PDPO (LAW). Review the applicable data-user duties and six data protection principles. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
European Union / EEA — GDPR (General Data Protection Regulation)
GDPR (LAW). Confirm GDPR territorial scope and the lawful basis for the actual processing. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
United Kingdom — UK GDPR / Data Protection Act 2018 (UK General Data Protection Regulation and Data Protection Act 2018)
UK GDPR / Data Protection Act 2018 (LAW). Apply the UK framework separately; check applicable Data (Use and Access) Act 2025 amendments. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
Switzerland — FADP (Federal Act on Data Protection)
FADP (LAW). Confirm the revised federal law applies; check any additional sector or cantonal requirements. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
United States - California — CCPA, as amended by CPRA (California Consumer Privacy Act, as amended by the California Privacy Rights Act)
CCPA, as amended by CPRA (LAW). Confirm covered-business criteria and exemptions. CPRA amends CCPA; this is not a nationwide US law. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | CCPA/CPRA: verify whether location is precise geolocation; do not infer precision from the field name |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | CCPA/CPRA: verify whether location is precise geolocation; do not infer precision from the field name |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
Canada — PIPEDA (Personal Information Protection and Electronic Documents Act)
PIPEDA (LAW). Confirm commercial-activity scope and whether a provincial or sector law applies instead or additionally. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
Brazil — LGPD (Lei Geral de Protecao de Dados Pessoais (General Personal Data Protection Law))
LGPD (LAW). Confirm LGPD applicability and the processing basis; field names do not establish either. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
Australia — Privacy Act 1988 / Australian Privacy Principles (Privacy Act 1988 and Australian Privacy Principles)
Privacy Act 1988 / Australian Privacy Principles (LAW). Confirm APP-entity coverage and exemptions; not every organisation is covered. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
India — DPDP Act 2023 / Rules 2025 (Digital Personal Data Protection Act 2023 and Digital Personal Data Protection Rules 2025)
DPDP Act 2023 / Rules 2025 (LAW). Confirm digital-personal-data scope and the commencement date of each provision; implementation is phased. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
Japan — APPI (Act on the Protection of Personal Information)
APPI (LAW). Confirm APPI coverage and the relevant handling and third-party provision requirements. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
South Korea — PIPA (Personal Information Protection Act)
PIPA (LAW). Confirm PIPA coverage and the current Korean statutory text and applicable amendments. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
Singapore — PDPA (Personal Data Protection Act)
PDPA (LAW). Confirm organisational coverage, exceptions and which obligations are in force. Official reference
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|---|---|---|---|---|
| Suggestion | employee.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.gender | Personal attribute on person-like subject. | Add to _audit_mask_fields="gender". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | employee.birth_date | Personal attribute on person-like subject. | Add to _audit_mask_fields="birth_date". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | employee.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | user_account.display_name | Personal attribute field. | Add to _audit_mask_fields="display_name". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | job_position.salary_grade | Financial data field. | Add to _audit_mask_fields="salary_grade". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | payroll_calculation.gross_salary | Financial data field. | Add to _audit_mask_fields="gross_salary". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer.name | Personal attribute on person-like subject. | Add to _audit_mask_fields="name". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.mobile_phone | Contact identifier on person-like subject. | Add to _audit_mask_fields="mobile_phone". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.email | Contact identifier on person-like subject. | Add to _audit_mask_fields="email". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.billing_address | Location data on person-like subject. | Add to _audit_mask_fields="billing_address". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer.shipping_address | Location data on person-like subject. | Add to _audit_mask_fields="shipping_address". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | corporate_customer.tax_id | Government identifier field. | Add to _audit_mask_fields="tax_id". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | customer_contact.contact_name | Personal attribute on person-like subject. | Add to _audit_mask_fields="contact_name". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | customer_contact.contact_email | Contact identifier on person-like subject. | Add to _audit_mask_fields="contact_email". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | billing_info.account_number | Financial data field. | Add to _audit_mask_fields="account_number". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | lead.contact_email | Contact identifier field. | Add to _audit_mask_fields="contact_email". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="account_name". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.bank_name | Personal attribute on high-risk privacy subject. | Add to _audit_mask_fields="bank_name". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | bank_account.account_number | Financial data on high-risk privacy subject. | Add to _audit_mask_fields="account_number". | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
✅ Solids
| Rule ID | Target | Source | Message |
|---|---|---|---|
KSML-UPLOAD-001 | `` | — | The upload contains 1 files. |
KSML-UPLOAD-005 | `` | merchant.xml:2 | Resolved entrypoint: merchant.xml |
KSML-XML-002 | `` | merchant.xml:2 | The XML document merchant.xml was parsed successfully. |
KSML-ROOT-003 | `` | merchant.xml:2 | Root name 'crm-erp-service' is well-formed. |
KSML-ROOT-008 | `` | merchant.xml:2 | External JSON business fields use the default camelCase profile. |
KSML-OBJECT-001 | platform | merchant.xml:8 | Object 'platform' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | merchant | merchant.xml:17 | Object 'merchant' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | employee | merchant.xml:30 | Object 'employee' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | user_account | merchant.xml:47 | Object 'user_account' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | user_role | merchant.xml:61 | Object 'user_role' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | user_role_assignment | merchant.xml:72 | Object 'user_role_assignment' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | permission_set | merchant.xml:83 | Object 'permission_set' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | role_permission | merchant.xml:93 | Object 'role_permission' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | address | merchant.xml:103 | Object 'address' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | route | merchant.xml:119 | Object 'route' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | time_slot | merchant.xml:132 | Object 'time_slot' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | shipment | merchant.xml:144 | Object 'shipment' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | shipment_item | merchant.xml:162 | Object 'shipment_item' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | fulfillment_event | merchant.xml:175 | Object 'fulfillment_event' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | warehouse | merchant.xml:189 | Object 'warehouse' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | inventory_level | merchant.xml:200 | Object 'inventory_level' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | stock_movement | merchant.xml:213 | Object 'stock_movement' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | delivery_vehicle | merchant.xml:228 | Object 'delivery_vehicle' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | vehicle_assignment | merchant.xml:243 | Object 'vehicle_assignment' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | load_plan | merchant.xml:255 | Object 'load_plan' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | load_plan_item | merchant.xml:269 | Object 'load_plan_item' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | service_appointment | merchant.xml:280 | Object 'service_appointment' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | service_team | merchant.xml:296 | Object 'service_team' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | team_member | merchant.xml:307 | Object 'team_member' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | job_assignment | merchant.xml:318 | Object 'job_assignment' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | work_order | merchant.xml:331 | Object 'work_order' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | task | merchant.xml:347 | Object 'task' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | department | merchant.xml:361 | Object 'department' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | job_position | merchant.xml:373 | Object 'job_position' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | employment_record | merchant.xml:385 | Object 'employment_record' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | worked_hour_entry | merchant.xml:401 | Object 'worked_hour_entry' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | timesheet | merchant.xml:417 | Object 'timesheet' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | payroll_calculation | merchant.xml:431 | Object 'payroll_calculation' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | payroll_item | merchant.xml:447 | Object 'payroll_item' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | bonus_scheme | merchant.xml:459 | Object 'bonus_scheme' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | employee_bonus | merchant.xml:470 | Object 'employee_bonus' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | leave_request | merchant.xml:483 | Object 'leave_request' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | leave_balance | merchant.xml:500 | Object 'leave_balance' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | training_program | merchant.xml:514 | Object 'training_program' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | employee_training_enrollment | merchant.xml:526 | Object 'employee_training_enrollment' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | customer | merchant.xml:538 | Object 'customer' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | corporate_customer | merchant.xml:555 | Object 'corporate_customer' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | customer_contact | merchant.xml:568 | Object 'customer_contact' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | billing_info | merchant.xml:582 | Object 'billing_info' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | customer_history_event | merchant.xml:595 | Object 'customer_history_event' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | service_contract | merchant.xml:608 | Object 'service_contract' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | contract_document | merchant.xml:625 | Object 'contract_document' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | support_ticket | merchant.xml:638 | Object 'support_ticket' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | ticket_reply | merchant.xml:653 | Object 'ticket_reply' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | product_category | merchant.xml:665 | Object 'product_category' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | product | merchant.xml:676 | Object 'product' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | product_service | merchant.xml:691 | Object 'product_service' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | product_pricing | merchant.xml:703 | Object 'product_pricing' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | price_list | merchant.xml:717 | Object 'price_list' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | service_configuration_option | merchant.xml:727 | Object 'service_configuration_option' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | product_bundle | merchant.xml:739 | Object 'product_bundle' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | bundle_item | merchant.xml:749 | Object 'bundle_item' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | material_item | merchant.xml:760 | Object 'material_item' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | material_inventory | merchant.xml:773 | Object 'material_inventory' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | sales_campaign | merchant.xml:785 | Object 'sales_campaign' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | discount_code | merchant.xml:800 | Object 'discount_code' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | lead | merchant.xml:814 | Object 'lead' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | lead_activity | merchant.xml:828 | Object 'lead_activity' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | conversion_metric | merchant.xml:841 | Object 'conversion_metric' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | quotation | merchant.xml:855 | Object 'quotation' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | quotation_line_item | merchant.xml:871 | Object 'quotation_line_item' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | sales_order | merchant.xml:884 | Object 'sales_order' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | account_chart | merchant.xml:901 | Object 'account_chart' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | journal_entry | merchant.xml:913 | Object 'journal_entry' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | ledger_transaction | merchant.xml:926 | Object 'ledger_transaction' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | payment | merchant.xml:938 | Object 'payment' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | invoice | merchant.xml:952 | Object 'invoice' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | invoice_line_item | merchant.xml:969 | Object 'invoice_line_item' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | expense_report | merchant.xml:983 | Object 'expense_report' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | expense_item | merchant.xml:998 | Object 'expense_item' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | vat_rate_config | merchant.xml:1012 | Object 'vat_rate_config' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | financial_statement | merchant.xml:1024 | Object 'financial_statement' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | budget | merchant.xml:1038 | Object 'budget' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | bank_account | merchant.xml:1052 | Object 'bank_account' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | asset_category | merchant.xml:1065 | Object 'asset_category' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | asset | merchant.xml:1076 | Object 'asset' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | equipment | merchant.xml:1093 | Object 'equipment' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | vehicle | merchant.xml:1105 | Object 'vehicle' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | consumable | merchant.xml:1120 | Object 'consumable' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | consumable_stock | merchant.xml:1132 | Object 'consumable_stock' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | maintenance_schedule | merchant.xml:1145 | Object 'maintenance_schedule' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | maintenance_log | merchant.xml:1159 | Object 'maintenance_log' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | depreciation_record | merchant.xml:1173 | Object 'depreciation_record' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | insurance_policy | merchant.xml:1186 | Object 'insurance_policy' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | compliance_document | merchant.xml:1201 | Object 'compliance_document' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | audit_log | merchant.xml:1215 | Object 'audit_log' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | version_history | merchant.xml:1230 | Object 'version_history' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | deleted_record | merchant.xml:1245 | Object 'deleted_record' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | notification_template | merchant.xml:1257 | Object 'notification_template' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | system_automation_hook | merchant.xml:1269 | Object 'system_automation_hook' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | external_integration | merchant.xml:1281 | Object 'external_integration' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | gender_type | merchant.xml:1293 | Object 'gender_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | shipment_status_type | merchant.xml:1309 | Object 'shipment_status_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | event_type | merchant.xml:1327 | Object 'event_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | movement_type | merchant.xml:1344 | Object 'movement_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | vehicle_type | merchant.xml:1361 | Object 'vehicle_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | service_status_type | merchant.xml:1377 | Object 'service_status_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | team_member_role | merchant.xml:1394 | Object 'team_member_role' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | work_order_status | merchant.xml:1410 | Object 'work_order_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | priority_type | merchant.xml:1426 | Object 'priority_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | task_status | merchant.xml:1442 | Object 'task_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | salary_grade | merchant.xml:1458 | Object 'salary_grade' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | employment_type | merchant.xml:1474 | Object 'employment_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | employment_status | merchant.xml:1490 | Object 'employment_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | timesheet_status | merchant.xml:1505 | Object 'timesheet_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | payroll_status | merchant.xml:1521 | Object 'payroll_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | payroll_item_type | merchant.xml:1537 | Object 'payroll_item_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | rule_type | merchant.xml:1553 | Object 'rule_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | bonus_status | merchant.xml:1568 | Object 'bonus_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | leave_type | merchant.xml:1583 | Object 'leave_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | leave_status | merchant.xml:1599 | Object 'leave_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | training_status | merchant.xml:1615 | Object 'training_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | customer_type | merchant.xml:1631 | Object 'customer_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | industry_type | merchant.xml:1646 | Object 'industry_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | payment_method | merchant.xml:1662 | Object 'payment_method' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | billing_cycle | merchant.xml:1678 | Object 'billing_cycle' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | history_event_type | merchant.xml:1694 | Object 'history_event_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | contract_type | merchant.xml:1710 | Object 'contract_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | contract_status | merchant.xml:1725 | Object 'contract_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | document_type | merchant.xml:1741 | Object 'document_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | ticket_status | merchant.xml:1757 | Object 'ticket_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | unit_of_measure | merchant.xml:1773 | Object 'unit_of_measure' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | currency_type | merchant.xml:1790 | Object 'currency_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | target_audience_type | merchant.xml:1806 | Object 'target_audience_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | discount_type | merchant.xml:1821 | Object 'discount_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | lead_source | merchant.xml:1837 | Object 'lead_source' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | lead_status | merchant.xml:1853 | Object 'lead_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | lead_activity_type | merchant.xml:1870 | Object 'lead_activity_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | quotation_status | merchant.xml:1886 | Object 'quotation_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | sales_order_status | merchant.xml:1903 | Object 'sales_order_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | account_type | merchant.xml:1919 | Object 'account_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | journal_status | merchant.xml:1936 | Object 'journal_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | payment_status | merchant.xml:1951 | Object 'payment_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | invoice_status | merchant.xml:1967 | Object 'invoice_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | vat_rate | merchant.xml:1984 | Object 'vat_rate' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | expense_status | merchant.xml:2001 | Object 'expense_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | expense_category | merchant.xml:2018 | Object 'expense_category' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | statement_type | merchant.xml:2034 | Object 'statement_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | statement_status | merchant.xml:2050 | Object 'statement_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | budget_category | merchant.xml:2066 | Object 'budget_category' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | budget_status | merchant.xml:2082 | Object 'budget_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | depreciation_method | merchant.xml:2098 | Object 'depreciation_method' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | maintenance_type | merchant.xml:2113 | Object 'maintenance_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | maintenance_status | merchant.xml:2129 | Object 'maintenance_status' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | policy_type | merchant.xml:2145 | Object 'policy_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | compliance_type | merchant.xml:2161 | Object 'compliance_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | action_type | merchant.xml:2177 | Object 'action_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | notification_channel | merchant.xml:2194 | Object 'notification_channel' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | auth_method_type | merchant.xml:2210 | Object 'auth_method_type' defines display name, module, and module key metadata. |
KSML-OBJECT-001 | customer_status | merchant.xml:2226 | Object 'customer_status' defines display name, module, and module key metadata. |
KSML-CONSTANT-007 | gender_type.id | merchant.xml:1297 | Constant object 'gender_type' correctly defines id="id()". |
KSML-CONSTANT-001 | gender_type | merchant.xml:1293 | Constant object 'gender_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | gender_type | merchant.xml:1293 | Constant object 'gender_type' has 3 constant value records. |
KSML-CONSTANT-007 | shipment_status_type.id | merchant.xml:1313 | Constant object 'shipment_status_type' correctly defines id="id()". |
KSML-CONSTANT-001 | shipment_status_type | merchant.xml:1309 | Constant object 'shipment_status_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | shipment_status_type | merchant.xml:1309 | Constant object 'shipment_status_type' has 5 constant value records. |
KSML-CONSTANT-007 | event_type.id | merchant.xml:1331 | Constant object 'event_type' correctly defines id="id()". |
KSML-CONSTANT-001 | event_type | merchant.xml:1327 | Constant object 'event_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | event_type | merchant.xml:1327 | Constant object 'event_type' has 4 constant value records. |
KSML-CONSTANT-007 | movement_type.id | merchant.xml:1348 | Constant object 'movement_type' correctly defines id="id()". |
KSML-CONSTANT-001 | movement_type | merchant.xml:1344 | Constant object 'movement_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | movement_type | merchant.xml:1344 | Constant object 'movement_type' has 4 constant value records. |
KSML-CONSTANT-007 | vehicle_type.id | merchant.xml:1365 | Constant object 'vehicle_type' correctly defines id="id()". |
KSML-CONSTANT-001 | vehicle_type | merchant.xml:1361 | Constant object 'vehicle_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | vehicle_type | merchant.xml:1361 | Constant object 'vehicle_type' has 3 constant value records. |
KSML-CONSTANT-007 | service_status_type.id | merchant.xml:1381 | Constant object 'service_status_type' correctly defines id="id()". |
KSML-CONSTANT-001 | service_status_type | merchant.xml:1377 | Constant object 'service_status_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | service_status_type | merchant.xml:1377 | Constant object 'service_status_type' has 4 constant value records. |
KSML-CONSTANT-007 | team_member_role.id | merchant.xml:1398 | Constant object 'team_member_role' correctly defines id="id()". |
KSML-CONSTANT-001 | team_member_role | merchant.xml:1394 | Constant object 'team_member_role' has correctly defined constant properties. |
KSML-CONSTANT-004 | team_member_role | merchant.xml:1394 | Constant object 'team_member_role' has 3 constant value records. |
KSML-CONSTANT-007 | work_order_status.id | merchant.xml:1414 | Constant object 'work_order_status' correctly defines id="id()". |
KSML-CONSTANT-001 | work_order_status | merchant.xml:1410 | Constant object 'work_order_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | work_order_status | merchant.xml:1410 | Constant object 'work_order_status' has 3 constant value records. |
KSML-CONSTANT-007 | priority_type.id | merchant.xml:1430 | Constant object 'priority_type' correctly defines id="id()". |
KSML-CONSTANT-001 | priority_type | merchant.xml:1426 | Constant object 'priority_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | priority_type | merchant.xml:1426 | Constant object 'priority_type' has 3 constant value records. |
KSML-CONSTANT-007 | task_status.id | merchant.xml:1446 | Constant object 'task_status' correctly defines id="id()". |
KSML-CONSTANT-001 | task_status | merchant.xml:1442 | Constant object 'task_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | task_status | merchant.xml:1442 | Constant object 'task_status' has 3 constant value records. |
KSML-CONSTANT-007 | salary_grade.id | merchant.xml:1462 | Constant object 'salary_grade' correctly defines id="id()". |
KSML-CONSTANT-001 | salary_grade | merchant.xml:1458 | Constant object 'salary_grade' has correctly defined constant properties. |
KSML-CONSTANT-004 | salary_grade | merchant.xml:1458 | Constant object 'salary_grade' has 3 constant value records. |
KSML-CONSTANT-007 | employment_type.id | merchant.xml:1478 | Constant object 'employment_type' correctly defines id="id()". |
KSML-CONSTANT-001 | employment_type | merchant.xml:1474 | Constant object 'employment_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | employment_type | merchant.xml:1474 | Constant object 'employment_type' has 3 constant value records. |
KSML-CONSTANT-007 | employment_status.id | merchant.xml:1494 | Constant object 'employment_status' correctly defines id="id()". |
KSML-CONSTANT-001 | employment_status | merchant.xml:1490 | Constant object 'employment_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | employment_status | merchant.xml:1490 | Constant object 'employment_status' has 2 constant value records. |
KSML-CONSTANT-007 | timesheet_status.id | merchant.xml:1509 | Constant object 'timesheet_status' correctly defines id="id()". |
KSML-CONSTANT-001 | timesheet_status | merchant.xml:1505 | Constant object 'timesheet_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | timesheet_status | merchant.xml:1505 | Constant object 'timesheet_status' has 3 constant value records. |
KSML-CONSTANT-007 | payroll_status.id | merchant.xml:1525 | Constant object 'payroll_status' correctly defines id="id()". |
KSML-CONSTANT-001 | payroll_status | merchant.xml:1521 | Constant object 'payroll_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | payroll_status | merchant.xml:1521 | Constant object 'payroll_status' has 3 constant value records. |
KSML-CONSTANT-007 | payroll_item_type.id | merchant.xml:1541 | Constant object 'payroll_item_type' correctly defines id="id()". |
KSML-CONSTANT-001 | payroll_item_type | merchant.xml:1537 | Constant object 'payroll_item_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | payroll_item_type | merchant.xml:1537 | Constant object 'payroll_item_type' has 3 constant value records. |
KSML-CONSTANT-007 | rule_type.id | merchant.xml:1557 | Constant object 'rule_type' correctly defines id="id()". |
KSML-CONSTANT-001 | rule_type | merchant.xml:1553 | Constant object 'rule_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | rule_type | merchant.xml:1553 | Constant object 'rule_type' has 2 constant value records. |
KSML-CONSTANT-007 | bonus_status.id | merchant.xml:1572 | Constant object 'bonus_status' correctly defines id="id()". |
KSML-CONSTANT-001 | bonus_status | merchant.xml:1568 | Constant object 'bonus_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | bonus_status | merchant.xml:1568 | Constant object 'bonus_status' has 2 constant value records. |
KSML-CONSTANT-007 | leave_type.id | merchant.xml:1587 | Constant object 'leave_type' correctly defines id="id()". |
KSML-CONSTANT-001 | leave_type | merchant.xml:1583 | Constant object 'leave_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | leave_type | merchant.xml:1583 | Constant object 'leave_type' has 3 constant value records. |
KSML-CONSTANT-007 | leave_status.id | merchant.xml:1603 | Constant object 'leave_status' correctly defines id="id()". |
KSML-CONSTANT-001 | leave_status | merchant.xml:1599 | Constant object 'leave_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | leave_status | merchant.xml:1599 | Constant object 'leave_status' has 3 constant value records. |
KSML-CONSTANT-007 | training_status.id | merchant.xml:1619 | Constant object 'training_status' correctly defines id="id()". |
KSML-CONSTANT-001 | training_status | merchant.xml:1615 | Constant object 'training_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | training_status | merchant.xml:1615 | Constant object 'training_status' has 3 constant value records. |
KSML-CONSTANT-007 | customer_type.id | merchant.xml:1635 | Constant object 'customer_type' correctly defines id="id()". |
KSML-CONSTANT-001 | customer_type | merchant.xml:1631 | Constant object 'customer_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | customer_type | merchant.xml:1631 | Constant object 'customer_type' has 2 constant value records. |
KSML-CONSTANT-007 | industry_type.id | merchant.xml:1650 | Constant object 'industry_type' correctly defines id="id()". |
KSML-CONSTANT-001 | industry_type | merchant.xml:1646 | Constant object 'industry_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | industry_type | merchant.xml:1646 | Constant object 'industry_type' has 3 constant value records. |
KSML-CONSTANT-007 | payment_method.id | merchant.xml:1666 | Constant object 'payment_method' correctly defines id="id()". |
KSML-CONSTANT-001 | payment_method | merchant.xml:1662 | Constant object 'payment_method' has correctly defined constant properties. |
KSML-CONSTANT-004 | payment_method | merchant.xml:1662 | Constant object 'payment_method' has 3 constant value records. |
KSML-CONSTANT-007 | billing_cycle.id | merchant.xml:1682 | Constant object 'billing_cycle' correctly defines id="id()". |
KSML-CONSTANT-001 | billing_cycle | merchant.xml:1678 | Constant object 'billing_cycle' has correctly defined constant properties. |
KSML-CONSTANT-004 | billing_cycle | merchant.xml:1678 | Constant object 'billing_cycle' has 3 constant value records. |
KSML-CONSTANT-007 | history_event_type.id | merchant.xml:1698 | Constant object 'history_event_type' correctly defines id="id()". |
KSML-CONSTANT-001 | history_event_type | merchant.xml:1694 | Constant object 'history_event_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | history_event_type | merchant.xml:1694 | Constant object 'history_event_type' has 3 constant value records. |
KSML-CONSTANT-007 | contract_type.id | merchant.xml:1714 | Constant object 'contract_type' correctly defines id="id()". |
KSML-CONSTANT-001 | contract_type | merchant.xml:1710 | Constant object 'contract_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | contract_type | merchant.xml:1710 | Constant object 'contract_type' has 2 constant value records. |
KSML-CONSTANT-007 | contract_status.id | merchant.xml:1729 | Constant object 'contract_status' correctly defines id="id()". |
KSML-CONSTANT-001 | contract_status | merchant.xml:1725 | Constant object 'contract_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | contract_status | merchant.xml:1725 | Constant object 'contract_status' has 3 constant value records. |
KSML-CONSTANT-007 | document_type.id | merchant.xml:1745 | Constant object 'document_type' correctly defines id="id()". |
KSML-CONSTANT-001 | document_type | merchant.xml:1741 | Constant object 'document_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | document_type | merchant.xml:1741 | Constant object 'document_type' has 3 constant value records. |
KSML-CONSTANT-007 | ticket_status.id | merchant.xml:1761 | Constant object 'ticket_status' correctly defines id="id()". |
KSML-CONSTANT-001 | ticket_status | merchant.xml:1757 | Constant object 'ticket_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | ticket_status | merchant.xml:1757 | Constant object 'ticket_status' has 3 constant value records. |
KSML-CONSTANT-007 | unit_of_measure.id | merchant.xml:1777 | Constant object 'unit_of_measure' correctly defines id="id()". |
KSML-CONSTANT-001 | unit_of_measure | merchant.xml:1773 | Constant object 'unit_of_measure' has correctly defined constant properties. |
KSML-CONSTANT-004 | unit_of_measure | merchant.xml:1773 | Constant object 'unit_of_measure' has 4 constant value records. |
KSML-CONSTANT-007 | currency_type.id | merchant.xml:1794 | Constant object 'currency_type' correctly defines id="id()". |
KSML-CONSTANT-001 | currency_type | merchant.xml:1790 | Constant object 'currency_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | currency_type | merchant.xml:1790 | Constant object 'currency_type' has 3 constant value records. |
KSML-CONSTANT-007 | target_audience_type.id | merchant.xml:1810 | Constant object 'target_audience_type' correctly defines id="id()". |
KSML-CONSTANT-001 | target_audience_type | merchant.xml:1806 | Constant object 'target_audience_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | target_audience_type | merchant.xml:1806 | Constant object 'target_audience_type' has 2 constant value records. |
KSML-CONSTANT-007 | discount_type.id | merchant.xml:1825 | Constant object 'discount_type' correctly defines id="id()". |
KSML-CONSTANT-001 | discount_type | merchant.xml:1821 | Constant object 'discount_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | discount_type | merchant.xml:1821 | Constant object 'discount_type' has 3 constant value records. |
KSML-CONSTANT-007 | lead_source.id | merchant.xml:1841 | Constant object 'lead_source' correctly defines id="id()". |
KSML-CONSTANT-001 | lead_source | merchant.xml:1837 | Constant object 'lead_source' has correctly defined constant properties. |
KSML-CONSTANT-004 | lead_source | merchant.xml:1837 | Constant object 'lead_source' has 3 constant value records. |
KSML-CONSTANT-007 | lead_status.id | merchant.xml:1857 | Constant object 'lead_status' correctly defines id="id()". |
KSML-CONSTANT-001 | lead_status | merchant.xml:1853 | Constant object 'lead_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | lead_status | merchant.xml:1853 | Constant object 'lead_status' has 4 constant value records. |
KSML-CONSTANT-007 | lead_activity_type.id | merchant.xml:1874 | Constant object 'lead_activity_type' correctly defines id="id()". |
KSML-CONSTANT-001 | lead_activity_type | merchant.xml:1870 | Constant object 'lead_activity_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | lead_activity_type | merchant.xml:1870 | Constant object 'lead_activity_type' has 3 constant value records. |
KSML-CONSTANT-007 | quotation_status.id | merchant.xml:1890 | Constant object 'quotation_status' correctly defines id="id()". |
KSML-CONSTANT-001 | quotation_status | merchant.xml:1886 | Constant object 'quotation_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | quotation_status | merchant.xml:1886 | Constant object 'quotation_status' has 4 constant value records. |
KSML-CONSTANT-007 | sales_order_status.id | merchant.xml:1907 | Constant object 'sales_order_status' correctly defines id="id()". |
KSML-CONSTANT-001 | sales_order_status | merchant.xml:1903 | Constant object 'sales_order_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | sales_order_status | merchant.xml:1903 | Constant object 'sales_order_status' has 3 constant value records. |
KSML-CONSTANT-007 | account_type.id | merchant.xml:1923 | Constant object 'account_type' correctly defines id="id()". |
KSML-CONSTANT-001 | account_type | merchant.xml:1919 | Constant object 'account_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | account_type | merchant.xml:1919 | Constant object 'account_type' has 4 constant value records. |
KSML-CONSTANT-007 | journal_status.id | merchant.xml:1940 | Constant object 'journal_status' correctly defines id="id()". |
KSML-CONSTANT-001 | journal_status | merchant.xml:1936 | Constant object 'journal_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | journal_status | merchant.xml:1936 | Constant object 'journal_status' has 2 constant value records. |
KSML-CONSTANT-007 | payment_status.id | merchant.xml:1955 | Constant object 'payment_status' correctly defines id="id()". |
KSML-CONSTANT-001 | payment_status | merchant.xml:1951 | Constant object 'payment_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | payment_status | merchant.xml:1951 | Constant object 'payment_status' has 3 constant value records. |
KSML-CONSTANT-007 | invoice_status.id | merchant.xml:1971 | Constant object 'invoice_status' correctly defines id="id()". |
KSML-CONSTANT-001 | invoice_status | merchant.xml:1967 | Constant object 'invoice_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | invoice_status | merchant.xml:1967 | Constant object 'invoice_status' has 4 constant value records. |
KSML-CONSTANT-007 | vat_rate.id | merchant.xml:1988 | Constant object 'vat_rate' correctly defines id="id()". |
KSML-CONSTANT-001 | vat_rate | merchant.xml:1984 | Constant object 'vat_rate' has correctly defined constant properties. |
KSML-CONSTANT-004 | vat_rate | merchant.xml:1984 | Constant object 'vat_rate' has 4 constant value records. |
KSML-CONSTANT-007 | expense_status.id | merchant.xml:2005 | Constant object 'expense_status' correctly defines id="id()". |
KSML-CONSTANT-001 | expense_status | merchant.xml:2001 | Constant object 'expense_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | expense_status | merchant.xml:2001 | Constant object 'expense_status' has 4 constant value records. |
KSML-CONSTANT-007 | expense_category.id | merchant.xml:2022 | Constant object 'expense_category' correctly defines id="id()". |
KSML-CONSTANT-001 | expense_category | merchant.xml:2018 | Constant object 'expense_category' has correctly defined constant properties. |
KSML-CONSTANT-004 | expense_category | merchant.xml:2018 | Constant object 'expense_category' has 3 constant value records. |
KSML-CONSTANT-007 | statement_type.id | merchant.xml:2038 | Constant object 'statement_type' correctly defines id="id()". |
KSML-CONSTANT-001 | statement_type | merchant.xml:2034 | Constant object 'statement_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | statement_type | merchant.xml:2034 | Constant object 'statement_type' has 3 constant value records. |
KSML-CONSTANT-007 | statement_status.id | merchant.xml:2054 | Constant object 'statement_status' correctly defines id="id()". |
KSML-CONSTANT-001 | statement_status | merchant.xml:2050 | Constant object 'statement_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | statement_status | merchant.xml:2050 | Constant object 'statement_status' has 3 constant value records. |
KSML-CONSTANT-007 | budget_category.id | merchant.xml:2070 | Constant object 'budget_category' correctly defines id="id()". |
KSML-CONSTANT-001 | budget_category | merchant.xml:2066 | Constant object 'budget_category' has correctly defined constant properties. |
KSML-CONSTANT-004 | budget_category | merchant.xml:2066 | Constant object 'budget_category' has 3 constant value records. |
KSML-CONSTANT-007 | budget_status.id | merchant.xml:2086 | Constant object 'budget_status' correctly defines id="id()". |
KSML-CONSTANT-001 | budget_status | merchant.xml:2082 | Constant object 'budget_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | budget_status | merchant.xml:2082 | Constant object 'budget_status' has 3 constant value records. |
KSML-CONSTANT-007 | depreciation_method.id | merchant.xml:2102 | Constant object 'depreciation_method' correctly defines id="id()". |
KSML-CONSTANT-001 | depreciation_method | merchant.xml:2098 | Constant object 'depreciation_method' has correctly defined constant properties. |
KSML-CONSTANT-004 | depreciation_method | merchant.xml:2098 | Constant object 'depreciation_method' has 2 constant value records. |
KSML-CONSTANT-007 | maintenance_type.id | merchant.xml:2117 | Constant object 'maintenance_type' correctly defines id="id()". |
KSML-CONSTANT-001 | maintenance_type | merchant.xml:2113 | Constant object 'maintenance_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | maintenance_type | merchant.xml:2113 | Constant object 'maintenance_type' has 3 constant value records. |
KSML-CONSTANT-007 | maintenance_status.id | merchant.xml:2133 | Constant object 'maintenance_status' correctly defines id="id()". |
KSML-CONSTANT-001 | maintenance_status | merchant.xml:2129 | Constant object 'maintenance_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | maintenance_status | merchant.xml:2129 | Constant object 'maintenance_status' has 3 constant value records. |
KSML-CONSTANT-007 | policy_type.id | merchant.xml:2149 | Constant object 'policy_type' correctly defines id="id()". |
KSML-CONSTANT-001 | policy_type | merchant.xml:2145 | Constant object 'policy_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | policy_type | merchant.xml:2145 | Constant object 'policy_type' has 3 constant value records. |
KSML-CONSTANT-007 | compliance_type.id | merchant.xml:2165 | Constant object 'compliance_type' correctly defines id="id()". |
KSML-CONSTANT-001 | compliance_type | merchant.xml:2161 | Constant object 'compliance_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | compliance_type | merchant.xml:2161 | Constant object 'compliance_type' has 3 constant value records. |
KSML-CONSTANT-007 | action_type.id | merchant.xml:2181 | Constant object 'action_type' correctly defines id="id()". |
KSML-CONSTANT-001 | action_type | merchant.xml:2177 | Constant object 'action_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | action_type | merchant.xml:2177 | Constant object 'action_type' has 4 constant value records. |
KSML-CONSTANT-007 | notification_channel.id | merchant.xml:2198 | Constant object 'notification_channel' correctly defines id="id()". |
KSML-CONSTANT-001 | notification_channel | merchant.xml:2194 | Constant object 'notification_channel' has correctly defined constant properties. |
KSML-CONSTANT-004 | notification_channel | merchant.xml:2194 | Constant object 'notification_channel' has 3 constant value records. |
KSML-CONSTANT-007 | auth_method_type.id | merchant.xml:2214 | Constant object 'auth_method_type' correctly defines id="id()". |
KSML-CONSTANT-001 | auth_method_type | merchant.xml:2210 | Constant object 'auth_method_type' has correctly defined constant properties. |
KSML-CONSTANT-004 | auth_method_type | merchant.xml:2210 | Constant object 'auth_method_type' has 3 constant value records. |
KSML-CONSTANT-007 | customer_status.id | merchant.xml:2230 | Constant object 'customer_status' correctly defines id="id()". |
KSML-CONSTANT-001 | customer_status | merchant.xml:2226 | Constant object 'customer_status' has correctly defined constant properties. |
KSML-CONSTANT-004 | customer_status | merchant.xml:2226 | Constant object 'customer_status' has 3 constant value records. |
KSML-REFERENCE-003 | merchant.platform | merchant.xml:25 | Reference 'platform' in 'merchant' successfully resolves to target object 'platform'. |
KSML-REFERENCE-003 | employee.gender | merchant.xml:36 | Reference 'gender' in 'employee' successfully resolves to target object 'gender_type'. |
KSML-REFERENCE-003 | employee.merchant | merchant.xml:42 | Reference 'merchant' in 'employee' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | user_account.employee | merchant.xml:53 | Reference 'employee' in 'user_account' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | user_account.merchant | merchant.xml:57 | Reference 'merchant' in 'user_account' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | user_role.merchant | merchant.xml:68 | Reference 'merchant' in 'user_role' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | user_role_assignment.assigned_by | merchant.xml:78 | Reference 'assigned_by' in 'user_role_assignment' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | user_role_assignment.merchant | merchant.xml:79 | Reference 'merchant' in 'user_role_assignment' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | user_role_assignment.role | merchant.xml:77 | Reference 'role' in 'user_role_assignment' successfully resolves to target object 'user_role'. |
KSML-REFERENCE-003 | user_role_assignment.user | merchant.xml:76 | Reference 'user' in 'user_role_assignment' successfully resolves to target object 'user_account'. |
KSML-REFERENCE-003 | permission_set.merchant | merchant.xml:89 | Reference 'merchant' in 'permission_set' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | role_permission.merchant | merchant.xml:99 | Reference 'merchant' in 'role_permission' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | role_permission.permission | merchant.xml:98 | Reference 'permission' in 'role_permission' successfully resolves to target object 'permission_set'. |
KSML-REFERENCE-003 | role_permission.user_role | merchant.xml:97 | Reference 'user_role' in 'role_permission' successfully resolves to target object 'user_role'. |
KSML-REFERENCE-003 | address.merchant | merchant.xml:115 | Reference 'merchant' in 'address' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | route.merchant | merchant.xml:128 | Reference 'merchant' in 'route' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | time_slot.merchant | merchant.xml:140 | Reference 'merchant' in 'time_slot' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | shipment.customer | merchant.xml:149 | Reference 'customer' in 'shipment' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | shipment.delivery_address | merchant.xml:151 | Reference 'delivery_address' in 'shipment' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | shipment.merchant | merchant.xml:157 | Reference 'merchant' in 'shipment' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | shipment.pickup_address | merchant.xml:150 | Reference 'pickup_address' in 'shipment' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | shipment.route | merchant.xml:152 | Reference 'route' in 'shipment' successfully resolves to target object 'route'. |
KSML-REFERENCE-003 | shipment.status | merchant.xml:155 | Reference 'status' in 'shipment' successfully resolves to target object 'shipment_status_type'. |
KSML-REFERENCE-003 | shipment.time_slot | merchant.xml:153 | Reference 'time_slot' in 'shipment' successfully resolves to target object 'time_slot'. |
KSML-REFERENCE-003 | shipment_item.merchant | merchant.xml:171 | Reference 'merchant' in 'shipment_item' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | shipment_item.product | merchant.xml:167 | Reference 'product' in 'shipment_item' successfully resolves to target object 'product'. |
KSML-REFERENCE-003 | shipment_item.shipment | merchant.xml:166 | Reference 'shipment' in 'shipment_item' successfully resolves to target object 'shipment'. |
KSML-REFERENCE-003 | fulfillment_event.event_type | merchant.xml:180 | Reference 'event_type' in 'fulfillment_event' successfully resolves to target object 'event_type'. |
KSML-REFERENCE-003 | fulfillment_event.location_address | merchant.xml:182 | Reference 'location_address' in 'fulfillment_event' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | fulfillment_event.merchant | merchant.xml:185 | Reference 'merchant' in 'fulfillment_event' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | fulfillment_event.reported_by | merchant.xml:184 | Reference 'reported_by' in 'fulfillment_event' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | fulfillment_event.shipment | merchant.xml:179 | Reference 'shipment' in 'fulfillment_event' successfully resolves to target object 'shipment'. |
KSML-REFERENCE-003 | warehouse.manager | merchant.xml:195 | Reference 'manager' in 'warehouse' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | warehouse.merchant | merchant.xml:196 | Reference 'merchant' in 'warehouse' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | warehouse.warehouse_address | merchant.xml:194 | Reference 'warehouse_address' in 'warehouse' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | inventory_level.merchant | merchant.xml:208 | Reference 'merchant' in 'inventory_level' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | inventory_level.product | merchant.xml:205 | Reference 'product' in 'inventory_level' successfully resolves to target object 'product'. |
KSML-REFERENCE-003 | inventory_level.warehouse | merchant.xml:204 | Reference 'warehouse' in 'inventory_level' successfully resolves to target object 'warehouse'. |
KSML-REFERENCE-003 | stock_movement.merchant | merchant.xml:224 | Reference 'merchant' in 'stock_movement' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | stock_movement.movement_type | merchant.xml:221 | Reference 'movement_type' in 'stock_movement' successfully resolves to target object 'movement_type'. |
KSML-REFERENCE-003 | stock_movement.processed_by | merchant.xml:223 | Reference 'processed_by' in 'stock_movement' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | stock_movement.product | merchant.xml:217 | Reference 'product' in 'stock_movement' successfully resolves to target object 'product'. |
KSML-REFERENCE-003 | stock_movement.source_warehouse | merchant.xml:218 | Reference 'source_warehouse' in 'stock_movement' successfully resolves to target object 'warehouse'. |
KSML-REFERENCE-003 | stock_movement.target_warehouse | merchant.xml:219 | Reference 'target_warehouse' in 'stock_movement' successfully resolves to target object 'warehouse'. |
KSML-REFERENCE-003 | delivery_vehicle.current_location | merchant.xml:237 | Reference 'current_location' in 'delivery_vehicle' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | delivery_vehicle.driver | merchant.xml:236 | Reference 'driver' in 'delivery_vehicle' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | delivery_vehicle.merchant | merchant.xml:238 | Reference 'merchant' in 'delivery_vehicle' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | delivery_vehicle.vehicle_type | merchant.xml:233 | Reference 'vehicle_type' in 'delivery_vehicle' successfully resolves to target object 'vehicle_type'. |
KSML-REFERENCE-003 | vehicle_assignment.assigned_driver | merchant.xml:250 | Reference 'assigned_driver' in 'vehicle_assignment' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | vehicle_assignment.delivery_vehicle | merchant.xml:247 | Reference 'delivery_vehicle' in 'vehicle_assignment' successfully resolves to target object 'delivery_vehicle'. |
KSML-REFERENCE-003 | vehicle_assignment.merchant | merchant.xml:251 | Reference 'merchant' in 'vehicle_assignment' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | vehicle_assignment.shipment | merchant.xml:248 | Reference 'shipment' in 'vehicle_assignment' successfully resolves to target object 'shipment'. |
KSML-REFERENCE-003 | load_plan.merchant | merchant.xml:265 | Reference 'merchant' in 'load_plan' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | load_plan.planner | merchant.xml:262 | Reference 'planner' in 'load_plan' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | load_plan.route | merchant.xml:259 | Reference 'route' in 'load_plan' successfully resolves to target object 'route'. |
KSML-REFERENCE-003 | load_plan.vehicle | merchant.xml:260 | Reference 'vehicle' in 'load_plan' successfully resolves to target object 'delivery_vehicle'. |
KSML-REFERENCE-003 | load_plan_item.load_plan | merchant.xml:273 | Reference 'load_plan' in 'load_plan_item' successfully resolves to target object 'load_plan'. |
KSML-REFERENCE-003 | load_plan_item.merchant | merchant.xml:276 | Reference 'merchant' in 'load_plan_item' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | load_plan_item.shipment | merchant.xml:274 | Reference 'shipment' in 'load_plan_item' successfully resolves to target object 'shipment'. |
KSML-REFERENCE-003 | service_appointment.assigned_team | merchant.xml:289 | Reference 'assigned_team' in 'service_appointment' successfully resolves to target object 'service_team'. |
KSML-REFERENCE-003 | service_appointment.customer | merchant.xml:284 | Reference 'customer' in 'service_appointment' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | service_appointment.merchant | merchant.xml:291 | Reference 'merchant' in 'service_appointment' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | service_appointment.service | merchant.xml:285 | Reference 'service' in 'service_appointment' successfully resolves to target object 'product_service'. |
KSML-REFERENCE-003 | service_appointment.service_address | merchant.xml:288 | Reference 'service_address' in 'service_appointment' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | service_appointment.status | merchant.xml:290 | Reference 'status' in 'service_appointment' successfully resolves to target object 'service_status_type'. |
KSML-REFERENCE-003 | service_appointment.time_slot | merchant.xml:287 | Reference 'time_slot' in 'service_appointment' successfully resolves to target object 'time_slot'. |
KSML-REFERENCE-003 | service_team.base_location | merchant.xml:302 | Reference 'base_location' in 'service_team' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | service_team.merchant | merchant.xml:303 | Reference 'merchant' in 'service_team' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | service_team.team_lead | merchant.xml:301 | Reference 'team_lead' in 'service_team' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | team_member.employee | merchant.xml:312 | Reference 'employee' in 'team_member' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | team_member.merchant | merchant.xml:314 | Reference 'merchant' in 'team_member' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | team_member.role | merchant.xml:313 | Reference 'role' in 'team_member' successfully resolves to target object 'team_member_role'. |
KSML-REFERENCE-003 | team_member.service_team | merchant.xml:311 | Reference 'service_team' in 'team_member' successfully resolves to target object 'service_team'. |
KSML-REFERENCE-003 | job_assignment.assigned_employee | merchant.xml:323 | Reference 'assigned_employee' in 'job_assignment' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | job_assignment.merchant | merchant.xml:327 | Reference 'merchant' in 'job_assignment' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | job_assignment.service_appointment | merchant.xml:322 | Reference 'service_appointment' in 'job_assignment' successfully resolves to target object 'service_appointment'. |
KSML-REFERENCE-003 | work_order.assigned_to | merchant.xml:340 | Reference 'assigned_to' in 'work_order' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | work_order.merchant | merchant.xml:342 | Reference 'merchant' in 'work_order' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | work_order.priority | merchant.xml:339 | Reference 'priority' in 'work_order' successfully resolves to target object 'priority_type'. |
KSML-REFERENCE-003 | work_order.related_service_appointment | merchant.xml:337 | Reference 'related_service_appointment' in 'work_order' successfully resolves to target object 'service_appointment'. |
KSML-REFERENCE-003 | work_order.related_shipment | merchant.xml:336 | Reference 'related_shipment' in 'work_order' successfully resolves to target object 'shipment'. |
KSML-REFERENCE-003 | work_order.status | merchant.xml:338 | Reference 'status' in 'work_order' successfully resolves to target object 'work_order_status'. |
KSML-REFERENCE-003 | task.assigned_to | merchant.xml:353 | Reference 'assigned_to' in 'task' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | task.merchant | merchant.xml:357 | Reference 'merchant' in 'task' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | task.status | merchant.xml:354 | Reference 'status' in 'task' successfully resolves to target object 'task_status'. |
KSML-REFERENCE-003 | task.work_order | merchant.xml:351 | Reference 'work_order' in 'task' successfully resolves to target object 'work_order'. |
KSML-REFERENCE-003 | department.manager | merchant.xml:367 | Reference 'manager' in 'department' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | department.merchant | merchant.xml:369 | Reference 'merchant' in 'department' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | job_position.department | merchant.xml:378 | Reference 'department' in 'job_position' successfully resolves to target object 'department'. |
KSML-REFERENCE-003 | job_position.merchant | merchant.xml:381 | Reference 'merchant' in 'job_position' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | employment_record.department | merchant.xml:390 | Reference 'department' in 'employment_record' successfully resolves to target object 'department'. |
KSML-REFERENCE-003 | employment_record.employee | merchant.xml:389 | Reference 'employee' in 'employment_record' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | employment_record.employment_type | merchant.xml:394 | Reference 'employment_type' in 'employment_record' successfully resolves to target object 'employment_type'. |
KSML-REFERENCE-003 | employment_record.job_position | merchant.xml:391 | Reference 'job_position' in 'employment_record' successfully resolves to target object 'job_position'. |
KSML-REFERENCE-003 | employment_record.merchant | merchant.xml:396 | Reference 'merchant' in 'employment_record' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | employment_record.status | merchant.xml:395 | Reference 'status' in 'employment_record' successfully resolves to target object 'employment_status'. |
KSML-REFERENCE-003 | worked_hour_entry.employee | merchant.xml:405 | Reference 'employee' in 'worked_hour_entry' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | worked_hour_entry.merchant | merchant.xml:413 | Reference 'merchant' in 'worked_hour_entry' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | worked_hour_entry.task_performed | merchant.xml:411 | Reference 'task_performed' in 'worked_hour_entry' successfully resolves to target object 'task'. |
KSML-REFERENCE-003 | timesheet.approved_by | merchant.xml:425 | Reference 'approved_by' in 'timesheet' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | timesheet.employee | merchant.xml:421 | Reference 'employee' in 'timesheet' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | timesheet.merchant | merchant.xml:426 | Reference 'merchant' in 'timesheet' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | timesheet.status | merchant.xml:424 | Reference 'status' in 'timesheet' successfully resolves to target object 'timesheet_status'. |
KSML-REFERENCE-003 | payroll_calculation.employee | merchant.xml:435 | Reference 'employee' in 'payroll_calculation' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | payroll_calculation.merchant | merchant.xml:443 | Reference 'merchant' in 'payroll_calculation' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | payroll_calculation.processed_by | merchant.xml:442 | Reference 'processed_by' in 'payroll_calculation' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | payroll_calculation.status | merchant.xml:441 | Reference 'status' in 'payroll_calculation' successfully resolves to target object 'payroll_status'. |
KSML-REFERENCE-003 | payroll_item.item_type | merchant.xml:452 | Reference 'item_type' in 'payroll_item' successfully resolves to target object 'payroll_item_type'. |
KSML-REFERENCE-003 | payroll_item.merchant | merchant.xml:455 | Reference 'merchant' in 'payroll_item' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | payroll_item.payroll | merchant.xml:451 | Reference 'payroll' in 'payroll_item' successfully resolves to target object 'payroll_calculation'. |
KSML-REFERENCE-003 | bonus_scheme.calculation_rule | merchant.xml:465 | Reference 'calculation_rule' in 'bonus_scheme' successfully resolves to target object 'rule_type'. |
KSML-REFERENCE-003 | bonus_scheme.merchant | merchant.xml:466 | Reference 'merchant' in 'bonus_scheme' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | employee_bonus.bonus_scheme | merchant.xml:475 | Reference 'bonus_scheme' in 'employee_bonus' successfully resolves to target object 'bonus_scheme'. |
KSML-REFERENCE-003 | employee_bonus.employee | merchant.xml:474 | Reference 'employee' in 'employee_bonus' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | employee_bonus.merchant | merchant.xml:479 | Reference 'merchant' in 'employee_bonus' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | employee_bonus.status | merchant.xml:478 | Reference 'status' in 'employee_bonus' successfully resolves to target object 'bonus_status'. |
KSML-REFERENCE-003 | leave_request.approved_by | merchant.xml:494 | Reference 'approved_by' in 'leave_request' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | leave_request.employee | merchant.xml:487 | Reference 'employee' in 'leave_request' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | leave_request.leave_type | merchant.xml:488 | Reference 'leave_type' in 'leave_request' successfully resolves to target object 'leave_type'. |
KSML-REFERENCE-003 | leave_request.merchant | merchant.xml:495 | Reference 'merchant' in 'leave_request' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | leave_request.status | merchant.xml:493 | Reference 'status' in 'leave_request' successfully resolves to target object 'leave_status'. |
KSML-REFERENCE-003 | leave_balance.employee | merchant.xml:504 | Reference 'employee' in 'leave_balance' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | leave_balance.leave_type | merchant.xml:505 | Reference 'leave_type' in 'leave_balance' successfully resolves to target object 'leave_type'. |
KSML-REFERENCE-003 | leave_balance.merchant | merchant.xml:509 | Reference 'merchant' in 'leave_balance' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | training_program.merchant | merchant.xml:522 | Reference 'merchant' in 'training_program' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | training_program.trainer | merchant.xml:521 | Reference 'trainer' in 'training_program' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | employee_training_enrollment.completion_status | merchant.xml:533 | Reference 'completion_status' in 'employee_training_enrollment' successfully resolves to target object 'training_status'. |
KSML-REFERENCE-003 | employee_training_enrollment.employee | merchant.xml:530 | Reference 'employee' in 'employee_training_enrollment' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | employee_training_enrollment.merchant | merchant.xml:534 | Reference 'merchant' in 'employee_training_enrollment' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | employee_training_enrollment.training_program | merchant.xml:531 | Reference 'training_program' in 'employee_training_enrollment' successfully resolves to target object 'training_program'. |
KSML-REFERENCE-003 | customer.billing_address | merchant.xml:546 | Reference 'billing_address' in 'customer' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | customer.customer_type | merchant.xml:542 | Reference 'customer_type' in 'customer' successfully resolves to target object 'customer_type'. |
KSML-REFERENCE-003 | customer.lead_source | merchant.xml:548 | Reference 'lead_source' in 'customer' successfully resolves to target object 'lead_source'. |
KSML-REFERENCE-003 | customer.merchant | merchant.xml:550 | Reference 'merchant' in 'customer' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | customer.shipping_address | merchant.xml:547 | Reference 'shipping_address' in 'customer' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | customer.status | merchant.xml:549 | Reference 'status' in 'customer' successfully resolves to target object 'customer_status'. |
KSML-REFERENCE-003 | corporate_customer.customer | merchant.xml:559 | Reference 'customer' in 'corporate_customer' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | corporate_customer.industry | merchant.xml:562 | Reference 'industry' in 'corporate_customer' successfully resolves to target object 'industry_type'. |
KSML-REFERENCE-003 | corporate_customer.merchant | merchant.xml:564 | Reference 'merchant' in 'corporate_customer' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | customer_contact.customer | merchant.xml:572 | Reference 'customer' in 'customer_contact' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | customer_contact.merchant | merchant.xml:578 | Reference 'merchant' in 'customer_contact' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | billing_info.billing_cycle | merchant.xml:589 | Reference 'billing_cycle' in 'billing_info' successfully resolves to target object 'billing_cycle'. |
KSML-REFERENCE-003 | billing_info.customer | merchant.xml:586 | Reference 'customer' in 'billing_info' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | billing_info.default_billing_address | merchant.xml:590 | Reference 'default_billing_address' in 'billing_info' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | billing_info.merchant | merchant.xml:591 | Reference 'merchant' in 'billing_info' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | billing_info.payment_method | merchant.xml:587 | Reference 'payment_method' in 'billing_info' successfully resolves to target object 'payment_method'. |
KSML-REFERENCE-003 | customer_history_event.customer | merchant.xml:599 | Reference 'customer' in 'customer_history_event' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | customer_history_event.event_type | merchant.xml:600 | Reference 'event_type' in 'customer_history_event' successfully resolves to target object 'history_event_type'. |
KSML-REFERENCE-003 | customer_history_event.merchant | merchant.xml:604 | Reference 'merchant' in 'customer_history_event' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | customer_history_event.related_employee | merchant.xml:603 | Reference 'related_employee' in 'customer_history_event' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | service_contract.contract_type | merchant.xml:614 | Reference 'contract_type' in 'service_contract' successfully resolves to target object 'contract_type'. |
KSML-REFERENCE-003 | service_contract.customer | merchant.xml:612 | Reference 'customer' in 'service_contract' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | service_contract.managed_by | merchant.xml:619 | Reference 'managed_by' in 'service_contract' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | service_contract.merchant | merchant.xml:620 | Reference 'merchant' in 'service_contract' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | service_contract.status | merchant.xml:618 | Reference 'status' in 'service_contract' successfully resolves to target object 'contract_status'. |
KSML-REFERENCE-003 | contract_document.document_type | merchant.xml:630 | Reference 'document_type' in 'contract_document' successfully resolves to target object 'document_type'. |
KSML-REFERENCE-003 | contract_document.merchant | merchant.xml:634 | Reference 'merchant' in 'contract_document' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | contract_document.service_contract | merchant.xml:629 | Reference 'service_contract' in 'contract_document' successfully resolves to target object 'service_contract'. |
KSML-REFERENCE-003 | contract_document.uploaded_by | merchant.xml:633 | Reference 'uploaded_by' in 'contract_document' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | support_ticket.assigned_to | merchant.xml:647 | Reference 'assigned_to' in 'support_ticket' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | support_ticket.customer | merchant.xml:642 | Reference 'customer' in 'support_ticket' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | support_ticket.merchant | merchant.xml:648 | Reference 'merchant' in 'support_ticket' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | support_ticket.priority | merchant.xml:645 | Reference 'priority' in 'support_ticket' successfully resolves to target object 'priority_type'. |
KSML-REFERENCE-003 | support_ticket.status | merchant.xml:646 | Reference 'status' in 'support_ticket' successfully resolves to target object 'ticket_status'. |
KSML-REFERENCE-003 | ticket_reply.merchant | merchant.xml:661 | Reference 'merchant' in 'ticket_reply' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | ticket_reply.replied_by | merchant.xml:658 | Reference 'replied_by' in 'ticket_reply' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | ticket_reply.support_ticket | merchant.xml:657 | Reference 'support_ticket' in 'ticket_reply' successfully resolves to target object 'support_ticket'. |
KSML-REFERENCE-003 | product_category.merchant | merchant.xml:672 | Reference 'merchant' in 'product_category' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | product.category | merchant.xml:682 | Reference 'category' in 'product' successfully resolves to target object 'product_category'. |
KSML-REFERENCE-003 | product.merchant | merchant.xml:686 | Reference 'merchant' in 'product' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | product.unit_of_measure | merchant.xml:683 | Reference 'unit_of_measure' in 'product' successfully resolves to target object 'unit_of_measure'. |
KSML-REFERENCE-003 | product_service.merchant | merchant.xml:699 | Reference 'merchant' in 'product_service' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | product_service.product | merchant.xml:695 | Reference 'product' in 'product_service' successfully resolves to target object 'product'. |
KSML-REFERENCE-003 | product_pricing.currency | merchant.xml:710 | Reference 'currency' in 'product_pricing' successfully resolves to target object 'currency_type'. |
KSML-REFERENCE-003 | product_pricing.merchant | merchant.xml:712 | Reference 'merchant' in 'product_pricing' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | product_pricing.price_list | merchant.xml:708 | Reference 'price_list' in 'product_pricing' successfully resolves to target object 'price_list'. |
KSML-REFERENCE-003 | product_pricing.product | merchant.xml:707 | Reference 'product' in 'product_pricing' successfully resolves to target object 'product'. |
KSML-REFERENCE-003 | price_list.merchant | merchant.xml:723 | Reference 'merchant' in 'price_list' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | service_configuration_option.merchant | merchant.xml:735 | Reference 'merchant' in 'service_configuration_option' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | service_configuration_option.product_service | merchant.xml:731 | Reference 'product_service' in 'service_configuration_option' successfully resolves to target object 'product_service'. |
KSML-REFERENCE-003 | product_bundle.merchant | merchant.xml:745 | Reference 'merchant' in 'product_bundle' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | bundle_item.merchant | merchant.xml:756 | Reference 'merchant' in 'bundle_item' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | bundle_item.product | merchant.xml:754 | Reference 'product' in 'bundle_item' successfully resolves to target object 'product'. |
KSML-REFERENCE-003 | bundle_item.product_bundle | merchant.xml:753 | Reference 'product_bundle' in 'bundle_item' successfully resolves to target object 'product_bundle'. |
KSML-REFERENCE-003 | material_item.merchant | merchant.xml:769 | Reference 'merchant' in 'material_item' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | material_inventory.material | merchant.xml:777 | Reference 'material' in 'material_inventory' successfully resolves to target object 'material_item'. |
KSML-REFERENCE-003 | material_inventory.merchant | merchant.xml:780 | Reference 'merchant' in 'material_inventory' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | material_inventory.warehouse | merchant.xml:778 | Reference 'warehouse' in 'material_inventory' successfully resolves to target object 'warehouse'. |
KSML-REFERENCE-003 | sales_campaign.manager | merchant.xml:794 | Reference 'manager' in 'sales_campaign' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | sales_campaign.merchant | merchant.xml:795 | Reference 'merchant' in 'sales_campaign' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | sales_campaign.target_audience | merchant.xml:793 | Reference 'target_audience' in 'sales_campaign' successfully resolves to target object 'target_audience_type'. |
KSML-REFERENCE-003 | discount_code.campaign | merchant.xml:805 | Reference 'campaign' in 'discount_code' successfully resolves to target object 'sales_campaign'. |
KSML-REFERENCE-003 | discount_code.discount_type | merchant.xml:806 | Reference 'discount_type' in 'discount_code' successfully resolves to target object 'discount_type'. |
KSML-REFERENCE-003 | discount_code.merchant | merchant.xml:810 | Reference 'merchant' in 'discount_code' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | lead.assigned_to | merchant.xml:822 | Reference 'assigned_to' in 'lead' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | lead.merchant | merchant.xml:823 | Reference 'merchant' in 'lead' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | lead.source | merchant.xml:820 | Reference 'source' in 'lead' successfully resolves to target object 'lead_source'. |
KSML-REFERENCE-003 | lead.status | merchant.xml:821 | Reference 'status' in 'lead' successfully resolves to target object 'lead_status'. |
KSML-REFERENCE-003 | lead_activity.activity_type | merchant.xml:833 | Reference 'activity_type' in 'lead_activity' successfully resolves to target object 'lead_activity_type'. |
KSML-REFERENCE-003 | lead_activity.lead | merchant.xml:832 | Reference 'lead' in 'lead_activity' successfully resolves to target object 'lead'. |
KSML-REFERENCE-003 | lead_activity.merchant | merchant.xml:837 | Reference 'merchant' in 'lead_activity' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | lead_activity.performed_by | merchant.xml:836 | Reference 'performed_by' in 'lead_activity' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | conversion_metric.campaign | merchant.xml:845 | Reference 'campaign' in 'conversion_metric' successfully resolves to target object 'sales_campaign'. |
KSML-REFERENCE-003 | conversion_metric.merchant | merchant.xml:851 | Reference 'merchant' in 'conversion_metric' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | quotation.customer | merchant.xml:860 | Reference 'customer' in 'quotation' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | quotation.merchant | merchant.xml:866 | Reference 'merchant' in 'quotation' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | quotation.prepared_by | merchant.xml:861 | Reference 'prepared_by' in 'quotation' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | quotation.status | merchant.xml:865 | Reference 'status' in 'quotation' successfully resolves to target object 'quotation_status'. |
KSML-REFERENCE-003 | quotation_line_item.merchant | merchant.xml:880 | Reference 'merchant' in 'quotation_line_item' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | quotation_line_item.product | merchant.xml:876 | Reference 'product' in 'quotation_line_item' successfully resolves to target object 'product'. |
KSML-REFERENCE-003 | quotation_line_item.quotation | merchant.xml:875 | Reference 'quotation' in 'quotation_line_item' successfully resolves to target object 'quotation'. |
KSML-REFERENCE-003 | sales_order.customer | merchant.xml:889 | Reference 'customer' in 'sales_order' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | sales_order.merchant | merchant.xml:896 | Reference 'merchant' in 'sales_order' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | sales_order.quotation | merchant.xml:890 | Reference 'quotation' in 'sales_order' successfully resolves to target object 'quotation'. |
KSML-REFERENCE-003 | sales_order.sales_rep | merchant.xml:891 | Reference 'sales_rep' in 'sales_order' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | sales_order.status | merchant.xml:895 | Reference 'status' in 'sales_order' successfully resolves to target object 'sales_order_status'. |
KSML-REFERENCE-003 | account_chart.account_type | merchant.xml:907 | Reference 'account_type' in 'account_chart' successfully resolves to target object 'account_type'. |
KSML-REFERENCE-003 | account_chart.merchant | merchant.xml:909 | Reference 'merchant' in 'account_chart' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | journal_entry.merchant | merchant.xml:922 | Reference 'merchant' in 'journal_entry' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | journal_entry.posted_by | merchant.xml:921 | Reference 'posted_by' in 'journal_entry' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | journal_entry.status | merchant.xml:920 | Reference 'status' in 'journal_entry' successfully resolves to target object 'journal_status'. |
KSML-REFERENCE-003 | ledger_transaction.account | merchant.xml:931 | Reference 'account' in 'ledger_transaction' successfully resolves to target object 'account_chart'. |
KSML-REFERENCE-003 | ledger_transaction.journal_entry | merchant.xml:930 | Reference 'journal_entry' in 'ledger_transaction' successfully resolves to target object 'journal_entry'. |
KSML-REFERENCE-003 | ledger_transaction.merchant | merchant.xml:934 | Reference 'merchant' in 'ledger_transaction' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | payment.customer | merchant.xml:942 | Reference 'customer' in 'payment' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | payment.merchant | merchant.xml:948 | Reference 'merchant' in 'payment' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | payment.payment_method | merchant.xml:946 | Reference 'payment_method' in 'payment' successfully resolves to target object 'payment_method'. |
KSML-REFERENCE-003 | payment.status | merchant.xml:947 | Reference 'status' in 'payment' successfully resolves to target object 'payment_status'. |
KSML-REFERENCE-003 | invoice.customer | merchant.xml:956 | Reference 'customer' in 'invoice' successfully resolves to target object 'customer'. |
KSML-REFERENCE-003 | invoice.merchant | merchant.xml:964 | Reference 'merchant' in 'invoice' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | invoice.sales_order | merchant.xml:957 | Reference 'sales_order' in 'invoice' successfully resolves to target object 'sales_order'. |
KSML-REFERENCE-003 | invoice.status | merchant.xml:963 | Reference 'status' in 'invoice' successfully resolves to target object 'invoice_status'. |
KSML-REFERENCE-003 | invoice_line_item.invoice | merchant.xml:973 | Reference 'invoice' in 'invoice_line_item' successfully resolves to target object 'invoice'. |
KSML-REFERENCE-003 | invoice_line_item.merchant | merchant.xml:979 | Reference 'merchant' in 'invoice_line_item' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | invoice_line_item.product | merchant.xml:974 | Reference 'product' in 'invoice_line_item' successfully resolves to target object 'product'. |
KSML-REFERENCE-003 | invoice_line_item.vat_rate | merchant.xml:978 | Reference 'vat_rate' in 'invoice_line_item' successfully resolves to target object 'vat_rate'. |
KSML-REFERENCE-003 | expense_report.approved_by | merchant.xml:992 | Reference 'approved_by' in 'expense_report' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | expense_report.employee | merchant.xml:987 | Reference 'employee' in 'expense_report' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | expense_report.merchant | merchant.xml:993 | Reference 'merchant' in 'expense_report' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | expense_report.status | merchant.xml:991 | Reference 'status' in 'expense_report' successfully resolves to target object 'expense_status'. |
KSML-REFERENCE-003 | expense_item.category | merchant.xml:1004 | Reference 'category' in 'expense_item' successfully resolves to target object 'expense_category'. |
KSML-REFERENCE-003 | expense_item.expense_report | merchant.xml:1002 | Reference 'expense_report' in 'expense_item' successfully resolves to target object 'expense_report'. |
KSML-REFERENCE-003 | expense_item.merchant | merchant.xml:1008 | Reference 'merchant' in 'expense_item' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | expense_item.receipt_attachment | merchant.xml:1007 | Reference 'receipt_attachment' in 'expense_item' successfully resolves to target object 'contract_document'. |
KSML-REFERENCE-003 | vat_rate_config.merchant | merchant.xml:1020 | Reference 'merchant' in 'vat_rate_config' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | financial_statement.merchant | merchant.xml:1034 | Reference 'merchant' in 'financial_statement' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | financial_statement.prepared_by | merchant.xml:1033 | Reference 'prepared_by' in 'financial_statement' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | financial_statement.statement_type | merchant.xml:1028 | Reference 'statement_type' in 'financial_statement' successfully resolves to target object 'statement_type'. |
KSML-REFERENCE-003 | financial_statement.status | merchant.xml:1032 | Reference 'status' in 'financial_statement' successfully resolves to target object 'statement_status'. |
KSML-REFERENCE-003 | budget.budget_category | merchant.xml:1045 | Reference 'budget_category' in 'budget' successfully resolves to target object 'budget_category'. |
KSML-REFERENCE-003 | budget.department | merchant.xml:1042 | Reference 'department' in 'budget' successfully resolves to target object 'department'. |
KSML-REFERENCE-003 | budget.merchant | merchant.xml:1047 | Reference 'merchant' in 'budget' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | budget.status | merchant.xml:1046 | Reference 'status' in 'budget' successfully resolves to target object 'budget_status'. |
KSML-REFERENCE-003 | bank_account.currency | merchant.xml:1059 | Reference 'currency' in 'bank_account' successfully resolves to target object 'currency_type'. |
KSML-REFERENCE-003 | bank_account.merchant | merchant.xml:1061 | Reference 'merchant' in 'bank_account' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | asset_category.depreciation_method | merchant.xml:1070 | Reference 'depreciation_method' in 'asset_category' successfully resolves to target object 'depreciation_method'. |
KSML-REFERENCE-003 | asset_category.merchant | merchant.xml:1072 | Reference 'merchant' in 'asset_category' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | asset.asset_category | merchant.xml:1082 | Reference 'asset_category' in 'asset' successfully resolves to target object 'asset_category'. |
KSML-REFERENCE-003 | asset.assigned_location | merchant.xml:1086 | Reference 'assigned_location' in 'asset' successfully resolves to target object 'address'. |
KSML-REFERENCE-003 | asset.merchant | merchant.xml:1088 | Reference 'merchant' in 'asset' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | asset.responsible_employee | merchant.xml:1087 | Reference 'responsible_employee' in 'asset' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | equipment.asset | merchant.xml:1097 | Reference 'asset' in 'equipment' successfully resolves to target object 'asset'. |
KSML-REFERENCE-003 | equipment.merchant | merchant.xml:1101 | Reference 'merchant' in 'equipment' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | vehicle.asset | merchant.xml:1109 | Reference 'asset' in 'vehicle' successfully resolves to target object 'asset'. |
KSML-REFERENCE-003 | vehicle.merchant | merchant.xml:1115 | Reference 'merchant' in 'vehicle' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | vehicle.vehicle_type | merchant.xml:1114 | Reference 'vehicle_type' in 'vehicle' successfully resolves to target object 'vehicle_type'. |
KSML-REFERENCE-003 | consumable.merchant | merchant.xml:1128 | Reference 'merchant' in 'consumable' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | consumable.unit_of_measure | merchant.xml:1126 | Reference 'unit_of_measure' in 'consumable' successfully resolves to target object 'unit_of_measure'. |
KSML-REFERENCE-003 | consumable_stock.consumable | merchant.xml:1136 | Reference 'consumable' in 'consumable_stock' successfully resolves to target object 'consumable'. |
KSML-REFERENCE-003 | consumable_stock.merchant | merchant.xml:1140 | Reference 'merchant' in 'consumable_stock' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | consumable_stock.warehouse | merchant.xml:1137 | Reference 'warehouse' in 'consumable_stock' successfully resolves to target object 'warehouse'. |
KSML-REFERENCE-003 | maintenance_schedule.asset | merchant.xml:1149 | Reference 'asset' in 'maintenance_schedule' successfully resolves to target object 'asset'. |
KSML-REFERENCE-003 | maintenance_schedule.merchant | merchant.xml:1155 | Reference 'merchant' in 'maintenance_schedule' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | maintenance_schedule.responsible_employee | merchant.xml:1153 | Reference 'responsible_employee' in 'maintenance_schedule' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | maintenance_schedule.schedule_type | merchant.xml:1150 | Reference 'schedule_type' in 'maintenance_schedule' successfully resolves to target object 'maintenance_type'. |
KSML-REFERENCE-003 | maintenance_schedule.status | merchant.xml:1154 | Reference 'status' in 'maintenance_schedule' successfully resolves to target object 'maintenance_status'. |
KSML-REFERENCE-003 | maintenance_log.asset | merchant.xml:1163 | Reference 'asset' in 'maintenance_log' successfully resolves to target object 'asset'. |
KSML-REFERENCE-003 | maintenance_log.maintenance_type | merchant.xml:1165 | Reference 'maintenance_type' in 'maintenance_log' successfully resolves to target object 'maintenance_type'. |
KSML-REFERENCE-003 | maintenance_log.merchant | merchant.xml:1169 | Reference 'merchant' in 'maintenance_log' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | maintenance_log.performed_by | merchant.xml:1167 | Reference 'performed_by' in 'maintenance_log' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | depreciation_record.asset | merchant.xml:1177 | Reference 'asset' in 'depreciation_record' successfully resolves to target object 'asset'. |
KSML-REFERENCE-003 | depreciation_record.merchant | merchant.xml:1182 | Reference 'merchant' in 'depreciation_record' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | insurance_policy.insured_asset | merchant.xml:1192 | Reference 'insured_asset' in 'insurance_policy' successfully resolves to target object 'asset'. |
KSML-REFERENCE-003 | insurance_policy.insured_entity | merchant.xml:1193 | Reference 'insured_entity' in 'insurance_policy' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | insurance_policy.merchant | merchant.xml:1197 | Reference 'merchant' in 'insurance_policy' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | insurance_policy.policy_type | merchant.xml:1191 | Reference 'policy_type' in 'insurance_policy' successfully resolves to target object 'policy_type'. |
KSML-REFERENCE-003 | compliance_document.document_type | merchant.xml:1206 | Reference 'document_type' in 'compliance_document' successfully resolves to target object 'compliance_type'. |
KSML-REFERENCE-003 | compliance_document.merchant | merchant.xml:1211 | Reference 'merchant' in 'compliance_document' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | compliance_document.uploaded_by | merchant.xml:1210 | Reference 'uploaded_by' in 'compliance_document' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | audit_log.action_type | merchant.xml:1221 | Reference 'action_type' in 'audit_log' successfully resolves to target object 'action_type'. |
KSML-REFERENCE-003 | audit_log.merchant | merchant.xml:1226 | Reference 'merchant' in 'audit_log' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | audit_log.user | merchant.xml:1220 | Reference 'user' in 'audit_log' successfully resolves to target object 'user_account'. |
KSML-REFERENCE-003 | version_history.changed_by | merchant.xml:1240 | Reference 'changed_by' in 'version_history' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | version_history.merchant | merchant.xml:1241 | Reference 'merchant' in 'version_history' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | deleted_record.deleted_by | merchant.xml:1252 | Reference 'deleted_by' in 'deleted_record' successfully resolves to target object 'employee'. |
KSML-REFERENCE-003 | deleted_record.merchant | merchant.xml:1253 | Reference 'merchant' in 'deleted_record' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | notification_template.channel | merchant.xml:1262 | Reference 'channel' in 'notification_template' successfully resolves to target object 'notification_channel'. |
KSML-REFERENCE-003 | notification_template.merchant | merchant.xml:1265 | Reference 'merchant' in 'notification_template' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | system_automation_hook.merchant | merchant.xml:1277 | Reference 'merchant' in 'system_automation_hook' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | external_integration.authentication_method | merchant.xml:1287 | Reference 'authentication_method' in 'external_integration' successfully resolves to target object 'auth_method_type'. |
KSML-REFERENCE-003 | external_integration.merchant | merchant.xml:1289 | Reference 'merchant' in 'external_integration' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | gender_type.merchant | merchant.xml:1300 | Reference 'merchant' in 'gender_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | shipment_status_type.merchant | merchant.xml:1316 | Reference 'merchant' in 'shipment_status_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | event_type.merchant | merchant.xml:1334 | Reference 'merchant' in 'event_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | movement_type.merchant | merchant.xml:1351 | Reference 'merchant' in 'movement_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | vehicle_type.merchant | merchant.xml:1368 | Reference 'merchant' in 'vehicle_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | service_status_type.merchant | merchant.xml:1384 | Reference 'merchant' in 'service_status_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | team_member_role.merchant | merchant.xml:1401 | Reference 'merchant' in 'team_member_role' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | work_order_status.merchant | merchant.xml:1417 | Reference 'merchant' in 'work_order_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | priority_type.merchant | merchant.xml:1433 | Reference 'merchant' in 'priority_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | task_status.merchant | merchant.xml:1449 | Reference 'merchant' in 'task_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | salary_grade.merchant | merchant.xml:1465 | Reference 'merchant' in 'salary_grade' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | employment_type.merchant | merchant.xml:1481 | Reference 'merchant' in 'employment_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | employment_status.merchant | merchant.xml:1497 | Reference 'merchant' in 'employment_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | timesheet_status.merchant | merchant.xml:1512 | Reference 'merchant' in 'timesheet_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | payroll_status.merchant | merchant.xml:1528 | Reference 'merchant' in 'payroll_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | payroll_item_type.merchant | merchant.xml:1544 | Reference 'merchant' in 'payroll_item_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | rule_type.merchant | merchant.xml:1560 | Reference 'merchant' in 'rule_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | bonus_status.merchant | merchant.xml:1575 | Reference 'merchant' in 'bonus_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | leave_type.merchant | merchant.xml:1590 | Reference 'merchant' in 'leave_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | leave_status.merchant | merchant.xml:1606 | Reference 'merchant' in 'leave_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | training_status.merchant | merchant.xml:1622 | Reference 'merchant' in 'training_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | customer_type.merchant | merchant.xml:1638 | Reference 'merchant' in 'customer_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | industry_type.merchant | merchant.xml:1653 | Reference 'merchant' in 'industry_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | payment_method.merchant | merchant.xml:1669 | Reference 'merchant' in 'payment_method' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | billing_cycle.merchant | merchant.xml:1685 | Reference 'merchant' in 'billing_cycle' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | history_event_type.merchant | merchant.xml:1701 | Reference 'merchant' in 'history_event_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | contract_type.merchant | merchant.xml:1717 | Reference 'merchant' in 'contract_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | contract_status.merchant | merchant.xml:1732 | Reference 'merchant' in 'contract_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | document_type.merchant | merchant.xml:1748 | Reference 'merchant' in 'document_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | ticket_status.merchant | merchant.xml:1764 | Reference 'merchant' in 'ticket_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | unit_of_measure.merchant | merchant.xml:1780 | Reference 'merchant' in 'unit_of_measure' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | currency_type.merchant | merchant.xml:1797 | Reference 'merchant' in 'currency_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | target_audience_type.merchant | merchant.xml:1813 | Reference 'merchant' in 'target_audience_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | discount_type.merchant | merchant.xml:1828 | Reference 'merchant' in 'discount_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | lead_source.merchant | merchant.xml:1844 | Reference 'merchant' in 'lead_source' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | lead_status.merchant | merchant.xml:1860 | Reference 'merchant' in 'lead_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | lead_activity_type.merchant | merchant.xml:1877 | Reference 'merchant' in 'lead_activity_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | quotation_status.merchant | merchant.xml:1893 | Reference 'merchant' in 'quotation_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | sales_order_status.merchant | merchant.xml:1910 | Reference 'merchant' in 'sales_order_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | account_type.merchant | merchant.xml:1926 | Reference 'merchant' in 'account_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | journal_status.merchant | merchant.xml:1943 | Reference 'merchant' in 'journal_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | payment_status.merchant | merchant.xml:1958 | Reference 'merchant' in 'payment_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | invoice_status.merchant | merchant.xml:1974 | Reference 'merchant' in 'invoice_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | vat_rate.merchant | merchant.xml:1991 | Reference 'merchant' in 'vat_rate' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | expense_status.merchant | merchant.xml:2008 | Reference 'merchant' in 'expense_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | expense_category.merchant | merchant.xml:2025 | Reference 'merchant' in 'expense_category' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | statement_type.merchant | merchant.xml:2041 | Reference 'merchant' in 'statement_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | statement_status.merchant | merchant.xml:2057 | Reference 'merchant' in 'statement_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | budget_category.merchant | merchant.xml:2073 | Reference 'merchant' in 'budget_category' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | budget_status.merchant | merchant.xml:2089 | Reference 'merchant' in 'budget_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | depreciation_method.merchant | merchant.xml:2105 | Reference 'merchant' in 'depreciation_method' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | maintenance_type.merchant | merchant.xml:2120 | Reference 'merchant' in 'maintenance_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | maintenance_status.merchant | merchant.xml:2136 | Reference 'merchant' in 'maintenance_status' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | policy_type.merchant | merchant.xml:2152 | Reference 'merchant' in 'policy_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | compliance_type.merchant | merchant.xml:2168 | Reference 'merchant' in 'compliance_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | action_type.merchant | merchant.xml:2184 | Reference 'merchant' in 'action_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | notification_channel.merchant | merchant.xml:2201 | Reference 'merchant' in 'notification_channel' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | auth_method_type.merchant | merchant.xml:2217 | Reference 'merchant' in 'auth_method_type' successfully resolves to target object 'merchant'. |
KSML-REFERENCE-003 | customer_status.merchant | merchant.xml:2233 | Reference 'merchant' in 'customer_status' successfully resolves to target object 'merchant'. |
KSML-DOMAIN-ROOT-003 | `` | merchant.xml:2 | Exactly one domain root candidate 'platform' was found. |
KSML-STATE-001 | shipment.status | merchant.xml:144 | Object 'shipment' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | service_appointment.status | merchant.xml:280 | Object 'service_appointment' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | work_order.status | merchant.xml:331 | Object 'work_order' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | task.status | merchant.xml:347 | Object 'task' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | employment_record.status | merchant.xml:385 | Object 'employment_record' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | timesheet.status | merchant.xml:417 | Object 'timesheet' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | payroll_calculation.status | merchant.xml:431 | Object 'payroll_calculation' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | employee_bonus.status | merchant.xml:470 | Object 'employee_bonus' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | leave_request.status | merchant.xml:483 | Object 'leave_request' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | employee_training_enrollment.completion_status | merchant.xml:526 | Object 'employee_training_enrollment' is an Aggregate Root candidate with primary state field 'completion_status'. |
KSML-STATE-001 | customer.status | merchant.xml:538 | Object 'customer' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | service_contract.status | merchant.xml:608 | Object 'service_contract' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | support_ticket.status | merchant.xml:638 | Object 'support_ticket' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | lead.status | merchant.xml:814 | Object 'lead' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | quotation.status | merchant.xml:855 | Object 'quotation' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | sales_order.status | merchant.xml:884 | Object 'sales_order' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | journal_entry.status | merchant.xml:913 | Object 'journal_entry' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | payment.status | merchant.xml:938 | Object 'payment' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | invoice.status | merchant.xml:952 | Object 'invoice' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | expense_report.status | merchant.xml:983 | Object 'expense_report' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | financial_statement.status | merchant.xml:1024 | Object 'financial_statement' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | budget.status | merchant.xml:1038 | Object 'budget' is an Aggregate Root candidate with primary state field 'status'. |
KSML-STATE-001 | maintenance_schedule.status | merchant.xml:1145 | Object 'maintenance_schedule' is an Aggregate Root candidate with primary state field 'status'. |
View original Markdown
<!-- ephemeral -->
# KSML Evaluation Report
## 📊 Summary
- **Errors**: 261
- **Warnings**: 250
- **Suggestions**: 117
- **Solids**: 721
## Error Pattern Summary
261 errors total. Fix the largest repeated pattern first, then rerun evaluation.
| Count | Pattern | Explanation | Action |
|-------|---------|-------------|--------|
| 59 | `Constant object missing root reference` (`KSML-CONSTANT-002`) | Constant object 'gender_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md, apply the smallest fix, then rerun evaluation. |
| 182 | `Incomplete constant value record` (`KSML-CONSTANT-008`) | Constant value 'MALE' in constant object 'gender_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Check agents/ERROR-FIX.md, apply the smallest fix, then rerun evaluation. |
| 3 | `Missing referenced object` (`KSML-REFERENCE-003`) | Field 'city_by_ip' in 'user_account' references target object 'cityByIp' which does not exist in the model. | Check agents/ERROR-FIX.md, apply the smallest fix, then rerun evaluation. |
| 15 | `Boolean field naming` (`KSML-NAMING-BOOLEAN-001`) | Boolean field 'time_slot.is_peak_hour' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_peak_hour="false" -> peak_hour="false". Also update all model references that use 'is_peak_hour'. | Check agents/ERROR-FIX.md, apply the smallest fix, then rerun evaluation. |
| 2 | `reserved-keyword` (`KSML-KEYWORD-002`) | KSML XML naming error at merchant.xml:81: element <user_role_assignment> defines an XML attribute named 'user', which conflicts with reserved keywords in: SQL. Rename the attribute in the KSML XML itself and keep its current value; for example, change user="..." to user_id="...". Also update any <_value> attributes or other model references that use the old field name. | Rename the target to a descriptive two-word snake_case name using the concrete example in the error. |
## ❌ Errors (Must Fix)
| Rule ID | Target | Source | Error Message | Action |
|---------|--------|--------|---------------|--------|
| `KSML-CONSTANT-002` | `gender_type.platform` | `merchant.xml:1293` | Constant object 'gender_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `gender_type.merchant` | `merchant.xml:1304` | Constant value 'MALE' in constant object 'gender_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `gender_type.merchant` | `merchant.xml:1305` | Constant value 'FEMALE' in constant object 'gender_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `gender_type.merchant` | `merchant.xml:1306` | Constant value 'OTHER' in constant object 'gender_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `shipment_status_type.platform` | `merchant.xml:1309` | Constant object 'shipment_status_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `shipment_status_type.merchant` | `merchant.xml:1320` | Constant value 'PENDING' in constant object 'shipment_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `shipment_status_type.merchant` | `merchant.xml:1321` | Constant value 'ASSIGNED' in constant object 'shipment_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `shipment_status_type.merchant` | `merchant.xml:1322` | Constant value 'IN_TRANSIT' in constant object 'shipment_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `shipment_status_type.merchant` | `merchant.xml:1323` | Constant value 'DELIVERED' in constant object 'shipment_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `shipment_status_type.merchant` | `merchant.xml:1324` | Constant value 'CANCELED' in constant object 'shipment_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `event_type.platform` | `merchant.xml:1327` | Constant object 'event_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `event_type.merchant` | `merchant.xml:1338` | Constant value 'PICKUP' in constant object 'event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `event_type.merchant` | `merchant.xml:1339` | Constant value 'LEFT_WAREHOUSE' in constant object 'event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `event_type.merchant` | `merchant.xml:1340` | Constant value 'ARRIVED_DESTINATION' in constant object 'event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `event_type.merchant` | `merchant.xml:1341` | Constant value 'EXCEPTION' in constant object 'event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `movement_type.platform` | `merchant.xml:1344` | Constant object 'movement_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `movement_type.merchant` | `merchant.xml:1355` | Constant value 'RECEIVE' in constant object 'movement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `movement_type.merchant` | `merchant.xml:1356` | Constant value 'ISSUE' in constant object 'movement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `movement_type.merchant` | `merchant.xml:1357` | Constant value 'TRANSFER' in constant object 'movement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `movement_type.merchant` | `merchant.xml:1358` | Constant value 'ADJUSTMENT' in constant object 'movement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `vehicle_type.platform` | `merchant.xml:1361` | Constant object 'vehicle_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `vehicle_type.merchant` | `merchant.xml:1372` | Constant value 'VAN' in constant object 'vehicle_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `vehicle_type.merchant` | `merchant.xml:1373` | Constant value 'TRUCK_HEAVY' in constant object 'vehicle_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `vehicle_type.merchant` | `merchant.xml:1374` | Constant value 'LIGHT_TRUCK' in constant object 'vehicle_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `service_status_type.platform` | `merchant.xml:1377` | Constant object 'service_status_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `service_status_type.merchant` | `merchant.xml:1388` | Constant value 'SCHEDULED' in constant object 'service_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `service_status_type.merchant` | `merchant.xml:1389` | Constant value 'IN_PROGRESS' in constant object 'service_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `service_status_type.merchant` | `merchant.xml:1390` | Constant value 'COMPLETED' in constant object 'service_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `service_status_type.merchant` | `merchant.xml:1391` | Constant value 'CANCELLED' in constant object 'service_status_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `team_member_role.platform` | `merchant.xml:1394` | Constant object 'team_member_role' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `team_member_role.merchant` | `merchant.xml:1405` | Constant value 'TEAM_LEAD' in constant object 'team_member_role' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `team_member_role.merchant` | `merchant.xml:1406` | Constant value 'MOVER' in constant object 'team_member_role' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `team_member_role.merchant` | `merchant.xml:1407` | Constant value 'PACKER' in constant object 'team_member_role' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `work_order_status.platform` | `merchant.xml:1410` | Constant object 'work_order_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `work_order_status.merchant` | `merchant.xml:1421` | Constant value 'NEW' in constant object 'work_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `work_order_status.merchant` | `merchant.xml:1422` | Constant value 'PENDING' in constant object 'work_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `work_order_status.merchant` | `merchant.xml:1423` | Constant value 'CLOSED' in constant object 'work_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `priority_type.platform` | `merchant.xml:1426` | Constant object 'priority_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `priority_type.merchant` | `merchant.xml:1437` | Constant value 'HIGH' in constant object 'priority_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `priority_type.merchant` | `merchant.xml:1438` | Constant value 'MEDIUM' in constant object 'priority_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `priority_type.merchant` | `merchant.xml:1439` | Constant value 'LOW' in constant object 'priority_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `task_status.platform` | `merchant.xml:1442` | Constant object 'task_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `task_status.merchant` | `merchant.xml:1453` | Constant value 'TO_DO' in constant object 'task_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `task_status.merchant` | `merchant.xml:1454` | Constant value 'IN_PROGRESS' in constant object 'task_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `task_status.merchant` | `merchant.xml:1455` | Constant value 'DONE' in constant object 'task_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `salary_grade.platform` | `merchant.xml:1458` | Constant object 'salary_grade' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `salary_grade.merchant` | `merchant.xml:1469` | Constant value 'GRADE_1' in constant object 'salary_grade' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `salary_grade.merchant` | `merchant.xml:1470` | Constant value 'GRADE_2' in constant object 'salary_grade' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `salary_grade.merchant` | `merchant.xml:1471` | Constant value 'GRADE_3' in constant object 'salary_grade' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `employment_type.platform` | `merchant.xml:1474` | Constant object 'employment_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `employment_type.merchant` | `merchant.xml:1485` | Constant value 'FULL_TIME' in constant object 'employment_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `employment_type.merchant` | `merchant.xml:1486` | Constant value 'PART_TIME' in constant object 'employment_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `employment_type.merchant` | `merchant.xml:1487` | Constant value 'CONTRACT' in constant object 'employment_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `employment_status.platform` | `merchant.xml:1490` | Constant object 'employment_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `employment_status.merchant` | `merchant.xml:1501` | Constant value 'ACTIVE' in constant object 'employment_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `employment_status.merchant` | `merchant.xml:1502` | Constant value 'INACTIVE' in constant object 'employment_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `timesheet_status.platform` | `merchant.xml:1505` | Constant object 'timesheet_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `timesheet_status.merchant` | `merchant.xml:1516` | Constant value 'DRAFT' in constant object 'timesheet_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `timesheet_status.merchant` | `merchant.xml:1517` | Constant value 'PENDING_APPROVAL' in constant object 'timesheet_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `timesheet_status.merchant` | `merchant.xml:1518` | Constant value 'APPROVED' in constant object 'timesheet_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `payroll_status.platform` | `merchant.xml:1521` | Constant object 'payroll_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `payroll_status.merchant` | `merchant.xml:1532` | Constant value 'PENDING' in constant object 'payroll_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `payroll_status.merchant` | `merchant.xml:1533` | Constant value 'PROCESSED' in constant object 'payroll_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `payroll_status.merchant` | `merchant.xml:1534` | Constant value 'PAID' in constant object 'payroll_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `payroll_item_type.platform` | `merchant.xml:1537` | Constant object 'payroll_item_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `payroll_item_type.merchant` | `merchant.xml:1548` | Constant value 'BASE_SALARY' in constant object 'payroll_item_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `payroll_item_type.merchant` | `merchant.xml:1549` | Constant value 'BONUS' in constant object 'payroll_item_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `payroll_item_type.merchant` | `merchant.xml:1550` | Constant value 'TAX_DEDUCTION' in constant object 'payroll_item_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `rule_type.platform` | `merchant.xml:1553` | Constant object 'rule_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `rule_type.merchant` | `merchant.xml:1564` | Constant value 'FIXED_AMOUNT' in constant object 'rule_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `rule_type.merchant` | `merchant.xml:1565` | Constant value 'PERCENTAGE' in constant object 'rule_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `bonus_status.platform` | `merchant.xml:1568` | Constant object 'bonus_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `bonus_status.merchant` | `merchant.xml:1579` | Constant value 'PENDING' in constant object 'bonus_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `bonus_status.merchant` | `merchant.xml:1580` | Constant value 'ISSUED' in constant object 'bonus_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `leave_type.platform` | `merchant.xml:1583` | Constant object 'leave_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `leave_type.merchant` | `merchant.xml:1594` | Constant value 'ANNUAL_LEAVE' in constant object 'leave_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `leave_type.merchant` | `merchant.xml:1595` | Constant value 'SICK_LEAVE' in constant object 'leave_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `leave_type.merchant` | `merchant.xml:1596` | Constant value 'PERSONAL_LEAVE' in constant object 'leave_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `leave_status.platform` | `merchant.xml:1599` | Constant object 'leave_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `leave_status.merchant` | `merchant.xml:1610` | Constant value 'PENDING_APPROVAL' in constant object 'leave_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `leave_status.merchant` | `merchant.xml:1611` | Constant value 'APPROVED' in constant object 'leave_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `leave_status.merchant` | `merchant.xml:1612` | Constant value 'REJECTED' in constant object 'leave_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `training_status.platform` | `merchant.xml:1615` | Constant object 'training_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `training_status.merchant` | `merchant.xml:1626` | Constant value 'NOT_STARTED' in constant object 'training_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `training_status.merchant` | `merchant.xml:1627` | Constant value 'IN_PROGRESS' in constant object 'training_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `training_status.merchant` | `merchant.xml:1628` | Constant value 'COMPLETED' in constant object 'training_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `customer_type.platform` | `merchant.xml:1631` | Constant object 'customer_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `customer_type.merchant` | `merchant.xml:1642` | Constant value 'PRIVATE' in constant object 'customer_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `customer_type.merchant` | `merchant.xml:1643` | Constant value 'CORPORATE' in constant object 'customer_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `industry_type.platform` | `merchant.xml:1646` | Constant object 'industry_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `industry_type.merchant` | `merchant.xml:1657` | Constant value 'LOGISTICS' in constant object 'industry_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `industry_type.merchant` | `merchant.xml:1658` | Constant value 'TECH' in constant object 'industry_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `industry_type.merchant` | `merchant.xml:1659` | Constant value 'MANUFACTURING' in constant object 'industry_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `payment_method.platform` | `merchant.xml:1662` | Constant object 'payment_method' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `payment_method.merchant` | `merchant.xml:1673` | Constant value 'BANK_TRANSFER' in constant object 'payment_method' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `payment_method.merchant` | `merchant.xml:1674` | Constant value 'CREDIT_CARD' in constant object 'payment_method' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `payment_method.merchant` | `merchant.xml:1675` | Constant value 'CASH' in constant object 'payment_method' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `billing_cycle.platform` | `merchant.xml:1678` | Constant object 'billing_cycle' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `billing_cycle.merchant` | `merchant.xml:1689` | Constant value 'MONTHLY' in constant object 'billing_cycle' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `billing_cycle.merchant` | `merchant.xml:1690` | Constant value 'QUARTERLY' in constant object 'billing_cycle' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `billing_cycle.merchant` | `merchant.xml:1691` | Constant value 'ONE_TIME' in constant object 'billing_cycle' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `history_event_type.platform` | `merchant.xml:1694` | Constant object 'history_event_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `history_event_type.merchant` | `merchant.xml:1705` | Constant value 'SERVICE_COMPLETED' in constant object 'history_event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `history_event_type.merchant` | `merchant.xml:1706` | Constant value 'COMPLAINT' in constant object 'history_event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `history_event_type.merchant` | `merchant.xml:1707` | Constant value 'CONTRACT_RENEWED' in constant object 'history_event_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `contract_type.platform` | `merchant.xml:1710` | Constant object 'contract_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `contract_type.merchant` | `merchant.xml:1721` | Constant value 'FRAMEWORK' in constant object 'contract_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `contract_type.merchant` | `merchant.xml:1722` | Constant value 'SINGLE_SERVICE' in constant object 'contract_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `contract_status.platform` | `merchant.xml:1725` | Constant object 'contract_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `contract_status.merchant` | `merchant.xml:1736` | Constant value 'DRAFT' in constant object 'contract_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `contract_status.merchant` | `merchant.xml:1737` | Constant value 'ACTIVE' in constant object 'contract_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `contract_status.merchant` | `merchant.xml:1738` | Constant value 'EXPIRED' in constant object 'contract_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `document_type.platform` | `merchant.xml:1741` | Constant object 'document_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `document_type.merchant` | `merchant.xml:1752` | Constant value 'CONTRACT' in constant object 'document_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `document_type.merchant` | `merchant.xml:1753` | Constant value 'INVOICE' in constant object 'document_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `document_type.merchant` | `merchant.xml:1754` | Constant value 'RECEIPT' in constant object 'document_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `ticket_status.platform` | `merchant.xml:1757` | Constant object 'ticket_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `ticket_status.merchant` | `merchant.xml:1768` | Constant value 'OPEN' in constant object 'ticket_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `ticket_status.merchant` | `merchant.xml:1769` | Constant value 'IN_PROCESS' in constant object 'ticket_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `ticket_status.merchant` | `merchant.xml:1770` | Constant value 'RESOLVED' in constant object 'ticket_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `unit_of_measure.platform` | `merchant.xml:1773` | Constant object 'unit_of_measure' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `unit_of_measure.merchant` | `merchant.xml:1784` | Constant value 'UNIT' in constant object 'unit_of_measure' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `unit_of_measure.merchant` | `merchant.xml:1785` | Constant value 'HOUR' in constant object 'unit_of_measure' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `unit_of_measure.merchant` | `merchant.xml:1786` | Constant value 'CUBIC_METER' in constant object 'unit_of_measure' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `unit_of_measure.merchant` | `merchant.xml:1787` | Constant value 'KILOGRAM' in constant object 'unit_of_measure' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `currency_type.platform` | `merchant.xml:1790` | Constant object 'currency_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `currency_type.merchant` | `merchant.xml:1801` | Constant value 'EUR' in constant object 'currency_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `currency_type.merchant` | `merchant.xml:1802` | Constant value 'USD' in constant object 'currency_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `currency_type.merchant` | `merchant.xml:1803` | Constant value 'GBP' in constant object 'currency_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `target_audience_type.platform` | `merchant.xml:1806` | Constant object 'target_audience_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `target_audience_type.merchant` | `merchant.xml:1817` | Constant value 'NEW_CUSTOMERS' in constant object 'target_audience_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `target_audience_type.merchant` | `merchant.xml:1818` | Constant value 'EXISTING_CUSTOMERS' in constant object 'target_audience_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `discount_type.platform` | `merchant.xml:1821` | Constant object 'discount_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `discount_type.merchant` | `merchant.xml:1832` | Constant value 'AMOUNT_OFF' in constant object 'discount_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `discount_type.merchant` | `merchant.xml:1833` | Constant value 'PERCENT_OFF' in constant object 'discount_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `discount_type.merchant` | `merchant.xml:1834` | Constant value 'FREE_SERVICE' in constant object 'discount_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `lead_source.platform` | `merchant.xml:1837` | Constant object 'lead_source' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `lead_source.merchant` | `merchant.xml:1848` | Constant value 'WEBSITE' in constant object 'lead_source' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `lead_source.merchant` | `merchant.xml:1849` | Constant value 'PHONE_CALL' in constant object 'lead_source' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `lead_source.merchant` | `merchant.xml:1850` | Constant value 'REFERRAL' in constant object 'lead_source' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `lead_status.platform` | `merchant.xml:1853` | Constant object 'lead_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `lead_status.merchant` | `merchant.xml:1864` | Constant value 'NEW' in constant object 'lead_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `lead_status.merchant` | `merchant.xml:1865` | Constant value 'CONTACTING' in constant object 'lead_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `lead_status.merchant` | `merchant.xml:1866` | Constant value 'QUALIFIED' in constant object 'lead_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `lead_status.merchant` | `merchant.xml:1867` | Constant value 'CONVERTED' in constant object 'lead_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `lead_activity_type.platform` | `merchant.xml:1870` | Constant object 'lead_activity_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `lead_activity_type.merchant` | `merchant.xml:1881` | Constant value 'CALL' in constant object 'lead_activity_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `lead_activity_type.merchant` | `merchant.xml:1882` | Constant value 'EMAIL' in constant object 'lead_activity_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `lead_activity_type.merchant` | `merchant.xml:1883` | Constant value 'MEETING' in constant object 'lead_activity_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `quotation_status.platform` | `merchant.xml:1886` | Constant object 'quotation_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `quotation_status.merchant` | `merchant.xml:1897` | Constant value 'DRAFT' in constant object 'quotation_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `quotation_status.merchant` | `merchant.xml:1898` | Constant value 'SENT' in constant object 'quotation_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `quotation_status.merchant` | `merchant.xml:1899` | Constant value 'ACCEPTED' in constant object 'quotation_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `quotation_status.merchant` | `merchant.xml:1900` | Constant value 'REJECTED' in constant object 'quotation_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `sales_order_status.platform` | `merchant.xml:1903` | Constant object 'sales_order_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `sales_order_status.merchant` | `merchant.xml:1914` | Constant value 'CONFIRMED' in constant object 'sales_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `sales_order_status.merchant` | `merchant.xml:1915` | Constant value 'FULFILLING' in constant object 'sales_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `sales_order_status.merchant` | `merchant.xml:1916` | Constant value 'CLOSED' in constant object 'sales_order_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `account_type.platform` | `merchant.xml:1919` | Constant object 'account_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `account_type.merchant` | `merchant.xml:1930` | Constant value 'ASSET' in constant object 'account_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `account_type.merchant` | `merchant.xml:1931` | Constant value 'LIABILITY' in constant object 'account_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `account_type.merchant` | `merchant.xml:1932` | Constant value 'REVENUE' in constant object 'account_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `account_type.merchant` | `merchant.xml:1933` | Constant value 'EXPENSE' in constant object 'account_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `journal_status.platform` | `merchant.xml:1936` | Constant object 'journal_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `journal_status.merchant` | `merchant.xml:1947` | Constant value 'DRAFT' in constant object 'journal_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `journal_status.merchant` | `merchant.xml:1948` | Constant value 'POSTED' in constant object 'journal_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `payment_status.platform` | `merchant.xml:1951` | Constant object 'payment_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `payment_status.merchant` | `merchant.xml:1962` | Constant value 'PENDING' in constant object 'payment_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `payment_status.merchant` | `merchant.xml:1963` | Constant value 'PAID' in constant object 'payment_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `payment_status.merchant` | `merchant.xml:1964` | Constant value 'REFUNDED' in constant object 'payment_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `invoice_status.platform` | `merchant.xml:1967` | Constant object 'invoice_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `invoice_status.merchant` | `merchant.xml:1978` | Constant value 'DRAFT' in constant object 'invoice_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `invoice_status.merchant` | `merchant.xml:1979` | Constant value 'ISSUED' in constant object 'invoice_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `invoice_status.merchant` | `merchant.xml:1980` | Constant value 'SETTLED' in constant object 'invoice_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `invoice_status.merchant` | `merchant.xml:1981` | Constant value 'OVERDUE' in constant object 'invoice_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `vat_rate.platform` | `merchant.xml:1984` | Constant object 'vat_rate' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `vat_rate.merchant` | `merchant.xml:1995` | Constant value 'VAT_24' in constant object 'vat_rate' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `vat_rate.merchant` | `merchant.xml:1996` | Constant value 'VAT_14' in constant object 'vat_rate' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `vat_rate.merchant` | `merchant.xml:1997` | Constant value 'VAT_10' in constant object 'vat_rate' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `vat_rate.merchant` | `merchant.xml:1998` | Constant value 'VAT_0' in constant object 'vat_rate' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `expense_status.platform` | `merchant.xml:2001` | Constant object 'expense_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `expense_status.merchant` | `merchant.xml:2012` | Constant value 'DRAFT' in constant object 'expense_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `expense_status.merchant` | `merchant.xml:2013` | Constant value 'PENDING_APPROVAL' in constant object 'expense_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `expense_status.merchant` | `merchant.xml:2014` | Constant value 'APPROVED' in constant object 'expense_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `expense_status.merchant` | `merchant.xml:2015` | Constant value 'REIMBURSED' in constant object 'expense_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `expense_category.platform` | `merchant.xml:2018` | Constant object 'expense_category' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `expense_category.merchant` | `merchant.xml:2029` | Constant value 'TRAVEL' in constant object 'expense_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `expense_category.merchant` | `merchant.xml:2030` | Constant value 'MEALS' in constant object 'expense_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `expense_category.merchant` | `merchant.xml:2031` | Constant value 'OFFICE_SUPPLIES' in constant object 'expense_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `statement_type.platform` | `merchant.xml:2034` | Constant object 'statement_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `statement_type.merchant` | `merchant.xml:2045` | Constant value 'BALANCE_SHEET' in constant object 'statement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `statement_type.merchant` | `merchant.xml:2046` | Constant value 'INCOME_STATEMENT' in constant object 'statement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `statement_type.merchant` | `merchant.xml:2047` | Constant value 'CASH_FLOW' in constant object 'statement_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `statement_status.platform` | `merchant.xml:2050` | Constant object 'statement_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `statement_status.merchant` | `merchant.xml:2061` | Constant value 'GENERATING' in constant object 'statement_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `statement_status.merchant` | `merchant.xml:2062` | Constant value 'COMPLETED' in constant object 'statement_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `statement_status.merchant` | `merchant.xml:2063` | Constant value 'ARCHIVED' in constant object 'statement_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `budget_category.platform` | `merchant.xml:2066` | Constant object 'budget_category' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `budget_category.merchant` | `merchant.xml:2077` | Constant value 'OPERATIONAL' in constant object 'budget_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `budget_category.merchant` | `merchant.xml:2078` | Constant value 'CAPITAL' in constant object 'budget_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `budget_category.merchant` | `merchant.xml:2079` | Constant value 'MARKETING' in constant object 'budget_category' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `budget_status.platform` | `merchant.xml:2082` | Constant object 'budget_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `budget_status.merchant` | `merchant.xml:2093` | Constant value 'DRAFT' in constant object 'budget_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `budget_status.merchant` | `merchant.xml:2094` | Constant value 'APPROVED' in constant object 'budget_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `budget_status.merchant` | `merchant.xml:2095` | Constant value 'CLOSED' in constant object 'budget_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `depreciation_method.platform` | `merchant.xml:2098` | Constant object 'depreciation_method' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `depreciation_method.merchant` | `merchant.xml:2109` | Constant value 'STRAIGHT_LINE' in constant object 'depreciation_method' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `depreciation_method.merchant` | `merchant.xml:2110` | Constant value 'DOUBLE_DECLINING' in constant object 'depreciation_method' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `maintenance_type.platform` | `merchant.xml:2113` | Constant object 'maintenance_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `maintenance_type.merchant` | `merchant.xml:2124` | Constant value 'PREVENTIVE' in constant object 'maintenance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `maintenance_type.merchant` | `merchant.xml:2125` | Constant value 'CORRECTIVE' in constant object 'maintenance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `maintenance_type.merchant` | `merchant.xml:2126` | Constant value 'OVERHAUL' in constant object 'maintenance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `maintenance_status.platform` | `merchant.xml:2129` | Constant object 'maintenance_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `maintenance_status.merchant` | `merchant.xml:2140` | Constant value 'PENDING' in constant object 'maintenance_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `maintenance_status.merchant` | `merchant.xml:2141` | Constant value 'IN_PROGRESS' in constant object 'maintenance_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `maintenance_status.merchant` | `merchant.xml:2142` | Constant value 'COMPLETED' in constant object 'maintenance_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `policy_type.platform` | `merchant.xml:2145` | Constant object 'policy_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `policy_type.merchant` | `merchant.xml:2156` | Constant value 'PROPERTY' in constant object 'policy_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `policy_type.merchant` | `merchant.xml:2157` | Constant value 'VEHICLE' in constant object 'policy_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `policy_type.merchant` | `merchant.xml:2158` | Constant value 'LIABILITY' in constant object 'policy_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `compliance_type.platform` | `merchant.xml:2161` | Constant object 'compliance_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `compliance_type.merchant` | `merchant.xml:2172` | Constant value 'INDUSTRY_STANDARD' in constant object 'compliance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `compliance_type.merchant` | `merchant.xml:2173` | Constant value 'INTERNAL_POLICY' in constant object 'compliance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `compliance_type.merchant` | `merchant.xml:2174` | Constant value 'REGULATION' in constant object 'compliance_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `action_type.platform` | `merchant.xml:2177` | Constant object 'action_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `action_type.merchant` | `merchant.xml:2188` | Constant value 'CREATE' in constant object 'action_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `action_type.merchant` | `merchant.xml:2189` | Constant value 'UPDATE' in constant object 'action_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `action_type.merchant` | `merchant.xml:2190` | Constant value 'DELETE' in constant object 'action_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `action_type.merchant` | `merchant.xml:2191` | Constant value 'LOGIN' in constant object 'action_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `notification_channel.platform` | `merchant.xml:2194` | Constant object 'notification_channel' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `notification_channel.merchant` | `merchant.xml:2205` | Constant value 'EMAIL' in constant object 'notification_channel' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `notification_channel.merchant` | `merchant.xml:2206` | Constant value 'SMS' in constant object 'notification_channel' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `notification_channel.merchant` | `merchant.xml:2207` | Constant value 'IN_APP' in constant object 'notification_channel' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `auth_method_type.platform` | `merchant.xml:2210` | Constant object 'auth_method_type' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `auth_method_type.merchant` | `merchant.xml:2221` | Constant value 'API_KEY' in constant object 'auth_method_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `auth_method_type.merchant` | `merchant.xml:2222` | Constant value 'OAUTH2' in constant object 'auth_method_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `auth_method_type.merchant` | `merchant.xml:2223` | Constant value 'BASIC_AUTH' in constant object 'auth_method_type' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-002` | `customer_status.platform` | `merchant.xml:2226` | Constant object 'customer_status' must be associated with the root object. For example, add platform="platform()" to the definition. | Check agents/ERROR-FIX.md |
| `KSML-CONSTANT-008` | `customer_status.merchant` | `merchant.xml:2237` | Constant value 'ACTIVE' in constant object 'customer_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `customer_status.merchant` | `merchant.xml:2238` | Constant value 'INACTIVE' in constant object 'customer_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-CONSTANT-008` | `customer_status.merchant` | `merchant.xml:2239` | Constant value 'BLACKLISTED' in constant object 'customer_status' must explicitly provide field 'merchant'. Every <_value> must provide every declared constant field, including nullable fields. | Add the missing field to the reported <_value>; every constant value must explicitly provide every declared constant field. |
| `KSML-REFERENCE-003` | `user_account.city_by_ip` | `merchant.xml:56` | Field 'city_by_ip' in 'user_account' references target object 'cityByIp' which does not exist in the model. | Check agents/ERROR-FIX.md |
| `KSML-REFERENCE-003` | `user_account.remote_ip` | `merchant.xml:55` | Field 'remote_ip' in 'user_account' references target object 'remoteIp' which does not exist in the model. | Check agents/ERROR-FIX.md |
| `KSML-REFERENCE-003` | `audit_log.remote_ip` | `merchant.xml:1225` | Field 'remote_ip' in 'audit_log' references target object 'remoteIp' which does not exist in the model. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `time_slot.is_peak_hour` | `merchant.xml:142` | Boolean field 'time_slot.is_peak_hour' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_peak_hour="false" -> peak_hour="false". Also update all model references that use 'is_peak_hour'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `worked_hour_entry.is_overtime` | `merchant.xml:415` | Boolean field 'worked_hour_entry.is_overtime' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_overtime="false" -> overtime="false". Also update all model references that use 'is_overtime'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `customer_contact.is_primary` | `merchant.xml:580` | Boolean field 'customer_contact.is_primary' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_primary="true" -> primary="true". Also update all model references that use 'is_primary'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `product.is_service` | `merchant.xml:689` | Boolean field 'product.is_service' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_service="true" -> service="true". Also update all model references that use 'is_service'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `product.is_taxable` | `merchant.xml:689` | Boolean field 'product.is_taxable' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_taxable="true" -> taxable="true". Also update all model references that use 'is_taxable'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `product_service.is_customizable` | `merchant.xml:701` | Boolean field 'product_service.is_customizable' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_customizable="true" -> customizable="true". Also update all model references that use 'is_customizable'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `price_list.is_default` | `merchant.xml:725` | Boolean field 'price_list.is_default' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_default="true" -> default="true". Also update all model references that use 'is_default'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `service_configuration_option.is_required` | `merchant.xml:737` | Boolean field 'service_configuration_option.is_required' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_required="false" -> required="false". Also update all model references that use 'is_required'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `material_item.is_consumable` | `merchant.xml:771` | Boolean field 'material_item.is_consumable' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_consumable="true" -> consumable="true". Also update all model references that use 'is_consumable'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `discount_code.is_active` | `merchant.xml:812` | Boolean field 'discount_code.is_active' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_active="true" -> active="true". Also update all model references that use 'is_active'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `account_chart.is_active` | `merchant.xml:911` | Boolean field 'account_chart.is_active' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_active="true" -> active="true". Also update all model references that use 'is_active'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `bank_account.is_operating_account` | `merchant.xml:1063` | Boolean field 'bank_account.is_operating_account' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_operating_account="true" -> operating_account="true". Also update all model references that use 'is_operating_account'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `equipment.is_mobile` | `merchant.xml:1103` | Boolean field 'equipment.is_mobile' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_mobile="true" -> mobile="true". Also update all model references that use 'is_mobile'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `system_automation_hook.is_active` | `merchant.xml:1279` | Boolean field 'system_automation_hook.is_active' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_active="true" -> active="true". Also update all model references that use 'is_active'. | Check agents/ERROR-FIX.md |
| `KSML-NAMING-BOOLEAN-001` | `external_integration.is_active` | `merchant.xml:1291` | Boolean field 'external_integration.is_active' must not use the 'is_' prefix because it produces redundant generated API names. Rename the field while preserving its original value exactly: is_active="true" -> active="true". Also update all model references that use 'is_active'. | Check agents/ERROR-FIX.md |
| `KSML-KEYWORD-002` | `/root/user_role_assignment/@user` | `merchant.xml:81` | KSML XML naming error at merchant.xml:81: element <user_role_assignment> defines an XML attribute named 'user', which conflicts with reserved keywords in: SQL. Rename the attribute in the KSML XML itself and keep its current value; for example, change user="..." to user_id="...". Also update any <_value> attributes or other model references that use the old field name. | Edit the KSML XML name using the concrete snake_case example. |
| `KSML-KEYWORD-002` | `/root/audit_log/@user` | `merchant.xml:1228` | KSML XML naming error at merchant.xml:1228: element <audit_log> defines an XML attribute named 'user', which conflicts with reserved keywords in: SQL. Rename the attribute in the KSML XML itself and keep its current value; for example, change user="..." to user_id="...". Also update any <_value> attributes or other model references that use the old field name. | Edit the KSML XML name using the concrete snake_case example. |
## ⚠️ Warnings
| Rule ID | Target | Source | Warning Message |
|---------|--------|--------|-----------------|
| `KSML-OBJECT-002` | `merchant._module_key` | `merchant.xml:17` | Module key 'organizational_structure' on object 'merchant' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `employee._module_key` | `merchant.xml:30` | Module key 'employee_management' on object 'employee' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `user_account._module_key` | `merchant.xml:47` | Module key 'user_management' on object 'user_account' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `user_role._module_key` | `merchant.xml:61` | Module key 'role_management' on object 'user_role' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `user_role_assignment._module_key` | `merchant.xml:72` | Module key 'role_assignment' on object 'user_role_assignment' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `permission_set._module_key` | `merchant.xml:83` | Module key 'permission_control' on object 'permission_set' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `role_permission._module_key` | `merchant.xml:93` | Module key 'permission_control' on object 'role_permission' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `time_slot._module_key` | `merchant.xml:132` | Module key 'time_slots' on object 'time_slot' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `fulfillment_event._module_key` | `merchant.xml:175` | Module key 'fulfillment_events' on object 'fulfillment_event' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `delivery_vehicle._module_key` | `merchant.xml:228` | Module key 'fleet_management' on object 'delivery_vehicle' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `vehicle_assignment._module_key` | `merchant.xml:243` | Module key 'fleet_management' on object 'vehicle_assignment' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `load_plan._module_key` | `merchant.xml:255` | Module key 'route_planning' on object 'load_plan' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `load_plan_item._module_key` | `merchant.xml:269` | Module key 'route_planning' on object 'load_plan_item' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `service_appointment._module_key` | `merchant.xml:280` | Module key 'service_scheduling' on object 'service_appointment' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `service_team._module_key` | `merchant.xml:296` | Module key 'service_scheduling' on object 'service_team' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `team_member._module_key` | `merchant.xml:307` | Module key 'service_scheduling' on object 'team_member' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `job_assignment._module_key` | `merchant.xml:318` | Module key 'service_scheduling' on object 'job_assignment' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `work_order._module_key` | `merchant.xml:331` | Module key 'work_order_management' on object 'work_order' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `task._module_key` | `merchant.xml:347` | Module key 'work_order_management' on object 'task' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `department._module_key` | `merchant.xml:361` | Module key 'staff_registry' on object 'department' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `job_position._module_key` | `merchant.xml:373` | Module key 'staff_registry' on object 'job_position' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `employment_record._module_key` | `merchant.xml:385` | Module key 'staff_registry' on object 'employment_record' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `worked_hour_entry._module_key` | `merchant.xml:401` | Module key 'worked_hours' on object 'worked_hour_entry' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `timesheet._module_key` | `merchant.xml:417` | Module key 'worked_hours' on object 'timesheet' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `payroll_calculation._module_key` | `merchant.xml:431` | Module key 'payroll_calculations' on object 'payroll_calculation' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `payroll_item._module_key` | `merchant.xml:447` | Module key 'payroll_calculations' on object 'payroll_item' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `leave_request._module_key` | `merchant.xml:483` | Module key 'leave_tracking' on object 'leave_request' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `leave_balance._module_key` | `merchant.xml:500` | Module key 'leave_tracking' on object 'leave_balance' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `training_program._module_key` | `merchant.xml:514` | Module key 'training_and_development' on object 'training_program' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `employee_training_enrollment._module_key` | `merchant.xml:526` | Module key 'training_and_development' on object 'employee_training_enrollment' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `customer._module_key` | `merchant.xml:538` | Module key 'private_and_corporate_customers' on object 'customer' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `corporate_customer._module_key` | `merchant.xml:555` | Module key 'private_and_corporate_customers' on object 'corporate_customer' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `customer_contact._module_key` | `merchant.xml:568` | Module key 'linked_contacts' on object 'customer_contact' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `billing_info._module_key` | `merchant.xml:582` | Module key 'billing_info' on object 'billing_info' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `customer_history_event._module_key` | `merchant.xml:595` | Module key 'customer_history' on object 'customer_history_event' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `contract_document._module_key` | `merchant.xml:625` | Module key 'document_storage' on object 'contract_document' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `support_ticket._module_key` | `merchant.xml:638` | Module key 'customer_support' on object 'support_ticket' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `ticket_reply._module_key` | `merchant.xml:653` | Module key 'customer_support' on object 'ticket_reply' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `product_category._module_key` | `merchant.xml:665` | Module key 'product_configuration' on object 'product_category' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `product._module_key` | `merchant.xml:676` | Module key 'product_configuration' on object 'product' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `product_service._module_key` | `merchant.xml:691` | Module key 'service_configuration' on object 'product_service' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `service_configuration_option._module_key` | `merchant.xml:727` | Module key 'service_configuration' on object 'service_configuration_option' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `product_bundle._module_key` | `merchant.xml:739` | Module key 'product_configuration' on object 'product_bundle' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `bundle_item._module_key` | `merchant.xml:749` | Module key 'product_configuration' on object 'bundle_item' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `material_item._module_key` | `merchant.xml:760` | Module key 'product_configuration' on object 'material_item' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `discount_code._module_key` | `merchant.xml:800` | Module key 'discount_codes' on object 'discount_code' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `lead._module_key` | `merchant.xml:814` | Module key 'lead_tracking' on object 'lead' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `lead_activity._module_key` | `merchant.xml:828` | Module key 'lead_tracking' on object 'lead_activity' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `conversion_metric._module_key` | `merchant.xml:841` | Module key 'conversion_metrics' on object 'conversion_metric' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `quotation._module_key` | `merchant.xml:855` | Module key 'sales_process' on object 'quotation' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `quotation_line_item._module_key` | `merchant.xml:871` | Module key 'sales_process' on object 'quotation_line_item' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `sales_order._module_key` | `merchant.xml:884` | Module key 'sales_process' on object 'sales_order' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `account_chart._module_key` | `merchant.xml:901` | Module key 'financial_summaries' on object 'account_chart' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `journal_entry._module_key` | `merchant.xml:913` | Module key 'financial_summaries' on object 'journal_entry' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `ledger_transaction._module_key` | `merchant.xml:926` | Module key 'financial_summaries' on object 'ledger_transaction' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `financial_statement._module_key` | `merchant.xml:1024` | Module key 'financial_summaries' on object 'financial_statement' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `bank_account._module_key` | `merchant.xml:1052` | Module key 'cash_management' on object 'bank_account' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `asset_category._module_key` | `merchant.xml:1065` | Module key 'asset_management' on object 'asset_category' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `asset._module_key` | `merchant.xml:1076` | Module key 'asset_management' on object 'asset' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `maintenance_schedule._module_key` | `merchant.xml:1145` | Module key 'maintenance_schedules' on object 'maintenance_schedule' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `maintenance_log._module_key` | `merchant.xml:1159` | Module key 'maintenance_schedules' on object 'maintenance_log' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `depreciation_record._module_key` | `merchant.xml:1173` | Module key 'asset_accounting' on object 'depreciation_record' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `compliance_document._module_key` | `merchant.xml:1201` | Module key 'document_storage' on object 'compliance_document' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `audit_log._module_key` | `merchant.xml:1215` | Module key 'audit_logs' on object 'audit_log' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `version_history._module_key` | `merchant.xml:1230` | Module key 'versioning_and_soft_deletes' on object 'version_history' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `deleted_record._module_key` | `merchant.xml:1245` | Module key 'versioning_and_soft_deletes' on object 'deleted_record' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `system_automation_hook._module_key` | `merchant.xml:1269` | Module key 'automation_hooks' on object 'system_automation_hook' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `external_integration._module_key` | `merchant.xml:1281` | Module key 'api_ready_architecture' on object 'external_integration' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `gender_type._module_key` | `merchant.xml:1293` | Module key 'basic_data' on object 'gender_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `shipment_status_type._module_key` | `merchant.xml:1309` | Module key 'basic_data' on object 'shipment_status_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `event_type._module_key` | `merchant.xml:1327` | Module key 'basic_data' on object 'event_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `movement_type._module_key` | `merchant.xml:1344` | Module key 'basic_data' on object 'movement_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `vehicle_type._module_key` | `merchant.xml:1361` | Module key 'basic_data' on object 'vehicle_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `service_status_type._module_key` | `merchant.xml:1377` | Module key 'basic_data' on object 'service_status_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `team_member_role._module_key` | `merchant.xml:1394` | Module key 'basic_data' on object 'team_member_role' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `work_order_status._module_key` | `merchant.xml:1410` | Module key 'basic_data' on object 'work_order_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `priority_type._module_key` | `merchant.xml:1426` | Module key 'basic_data' on object 'priority_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `task_status._module_key` | `merchant.xml:1442` | Module key 'basic_data' on object 'task_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `salary_grade._module_key` | `merchant.xml:1458` | Module key 'basic_data' on object 'salary_grade' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `employment_type._module_key` | `merchant.xml:1474` | Module key 'basic_data' on object 'employment_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `employment_status._module_key` | `merchant.xml:1490` | Module key 'basic_data' on object 'employment_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `timesheet_status._module_key` | `merchant.xml:1505` | Module key 'basic_data' on object 'timesheet_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `payroll_status._module_key` | `merchant.xml:1521` | Module key 'basic_data' on object 'payroll_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `payroll_item_type._module_key` | `merchant.xml:1537` | Module key 'basic_data' on object 'payroll_item_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `rule_type._module_key` | `merchant.xml:1553` | Module key 'basic_data' on object 'rule_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `bonus_status._module_key` | `merchant.xml:1568` | Module key 'basic_data' on object 'bonus_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `leave_type._module_key` | `merchant.xml:1583` | Module key 'basic_data' on object 'leave_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `leave_status._module_key` | `merchant.xml:1599` | Module key 'basic_data' on object 'leave_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `training_status._module_key` | `merchant.xml:1615` | Module key 'basic_data' on object 'training_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `customer_type._module_key` | `merchant.xml:1631` | Module key 'basic_data' on object 'customer_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `industry_type._module_key` | `merchant.xml:1646` | Module key 'basic_data' on object 'industry_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `payment_method._module_key` | `merchant.xml:1662` | Module key 'basic_data' on object 'payment_method' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `billing_cycle._module_key` | `merchant.xml:1678` | Module key 'basic_data' on object 'billing_cycle' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `history_event_type._module_key` | `merchant.xml:1694` | Module key 'basic_data' on object 'history_event_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `contract_type._module_key` | `merchant.xml:1710` | Module key 'basic_data' on object 'contract_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `contract_status._module_key` | `merchant.xml:1725` | Module key 'basic_data' on object 'contract_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `document_type._module_key` | `merchant.xml:1741` | Module key 'basic_data' on object 'document_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `ticket_status._module_key` | `merchant.xml:1757` | Module key 'basic_data' on object 'ticket_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `unit_of_measure._module_key` | `merchant.xml:1773` | Module key 'basic_data' on object 'unit_of_measure' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `currency_type._module_key` | `merchant.xml:1790` | Module key 'basic_data' on object 'currency_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `target_audience_type._module_key` | `merchant.xml:1806` | Module key 'basic_data' on object 'target_audience_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `discount_type._module_key` | `merchant.xml:1821` | Module key 'basic_data' on object 'discount_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `lead_source._module_key` | `merchant.xml:1837` | Module key 'basic_data' on object 'lead_source' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `lead_status._module_key` | `merchant.xml:1853` | Module key 'basic_data' on object 'lead_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `lead_activity_type._module_key` | `merchant.xml:1870` | Module key 'basic_data' on object 'lead_activity_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `quotation_status._module_key` | `merchant.xml:1886` | Module key 'basic_data' on object 'quotation_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `sales_order_status._module_key` | `merchant.xml:1903` | Module key 'basic_data' on object 'sales_order_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `account_type._module_key` | `merchant.xml:1919` | Module key 'basic_data' on object 'account_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `journal_status._module_key` | `merchant.xml:1936` | Module key 'basic_data' on object 'journal_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `payment_status._module_key` | `merchant.xml:1951` | Module key 'basic_data' on object 'payment_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `invoice_status._module_key` | `merchant.xml:1967` | Module key 'basic_data' on object 'invoice_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `vat_rate._module_key` | `merchant.xml:1984` | Module key 'basic_data' on object 'vat_rate' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `expense_status._module_key` | `merchant.xml:2001` | Module key 'basic_data' on object 'expense_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `expense_category._module_key` | `merchant.xml:2018` | Module key 'basic_data' on object 'expense_category' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `statement_type._module_key` | `merchant.xml:2034` | Module key 'basic_data' on object 'statement_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `statement_status._module_key` | `merchant.xml:2050` | Module key 'basic_data' on object 'statement_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `budget_category._module_key` | `merchant.xml:2066` | Module key 'basic_data' on object 'budget_category' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `budget_status._module_key` | `merchant.xml:2082` | Module key 'basic_data' on object 'budget_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `depreciation_method._module_key` | `merchant.xml:2098` | Module key 'basic_data' on object 'depreciation_method' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `maintenance_type._module_key` | `merchant.xml:2113` | Module key 'basic_data' on object 'maintenance_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `maintenance_status._module_key` | `merchant.xml:2129` | Module key 'basic_data' on object 'maintenance_status' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `policy_type._module_key` | `merchant.xml:2145` | Module key 'basic_data' on object 'policy_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `compliance_type._module_key` | `merchant.xml:2161` | Module key 'basic_data' on object 'compliance_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `action_type._module_key` | `merchant.xml:2177` | Module key 'basic_data' on object 'action_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `notification_channel._module_key` | `merchant.xml:2194` | Module key 'basic_data' on object 'notification_channel' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `auth_method_type._module_key` | `merchant.xml:2210` | Module key 'basic_data' on object 'auth_method_type' should be lowercase kebab-case. |
| `KSML-OBJECT-002` | `customer_status._module_key` | `merchant.xml:2226` | Module key 'basic_data' on object 'customer_status' should be lowercase kebab-case. |
| `KSML-CONSTANT-005` | `gender_type.id` | `merchant.xml:1293` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `shipment_status_type.id` | `merchant.xml:1309` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `event_type.id` | `merchant.xml:1327` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `movement_type.id` | `merchant.xml:1344` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `vehicle_type.id` | `merchant.xml:1361` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `service_status_type.id` | `merchant.xml:1377` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `team_member_role.id` | `merchant.xml:1394` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `work_order_status.id` | `merchant.xml:1410` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `priority_type.id` | `merchant.xml:1426` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `task_status.id` | `merchant.xml:1442` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `salary_grade.id` | `merchant.xml:1458` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `employment_type.id` | `merchant.xml:1474` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `employment_status.id` | `merchant.xml:1490` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `timesheet_status.id` | `merchant.xml:1505` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `payroll_status.id` | `merchant.xml:1521` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `payroll_item_type.id` | `merchant.xml:1537` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `rule_type.id` | `merchant.xml:1553` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `bonus_status.id` | `merchant.xml:1568` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `leave_type.id` | `merchant.xml:1583` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `leave_status.id` | `merchant.xml:1599` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `training_status.id` | `merchant.xml:1615` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `customer_type.id` | `merchant.xml:1631` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `industry_type.id` | `merchant.xml:1646` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `payment_method.id` | `merchant.xml:1662` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `billing_cycle.id` | `merchant.xml:1678` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `history_event_type.id` | `merchant.xml:1694` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `contract_type.id` | `merchant.xml:1710` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `contract_status.id` | `merchant.xml:1725` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `document_type.id` | `merchant.xml:1741` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `ticket_status.id` | `merchant.xml:1757` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `unit_of_measure.id` | `merchant.xml:1773` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `currency_type.id` | `merchant.xml:1790` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `target_audience_type.id` | `merchant.xml:1806` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `discount_type.id` | `merchant.xml:1821` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `lead_source.id` | `merchant.xml:1837` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `lead_status.id` | `merchant.xml:1853` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `lead_activity_type.id` | `merchant.xml:1870` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `quotation_status.id` | `merchant.xml:1886` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `sales_order_status.id` | `merchant.xml:1903` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `account_type.id` | `merchant.xml:1919` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `journal_status.id` | `merchant.xml:1936` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `payment_status.id` | `merchant.xml:1951` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `invoice_status.id` | `merchant.xml:1967` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `vat_rate.id` | `merchant.xml:1984` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `expense_status.id` | `merchant.xml:2001` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `expense_category.id` | `merchant.xml:2018` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `statement_type.id` | `merchant.xml:2034` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `statement_status.id` | `merchant.xml:2050` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `budget_category.id` | `merchant.xml:2066` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `budget_status.id` | `merchant.xml:2082` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `depreciation_method.id` | `merchant.xml:2098` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `maintenance_type.id` | `merchant.xml:2113` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `maintenance_status.id` | `merchant.xml:2129` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `policy_type.id` | `merchant.xml:2145` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `compliance_type.id` | `merchant.xml:2161` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `action_type.id` | `merchant.xml:2177` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `notification_channel.id` | `merchant.xml:2194` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `auth_method_type.id` | `merchant.xml:2210` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-CONSTANT-005` | `customer_status.id` | `merchant.xml:2226` | Constant value IDs should preferably start from 1001 and increment sequentially. |
| `KSML-BUSINESS-002` | `external_integration.api_endpoint` | `merchant.xml:1286` | Field 'api_endpoint' in business object 'external_integration' should preferably use a rich concrete typical value instead of generic string(). |
| `KSML-REFERENCE-005` | `product.category` | `merchant.xml:682` | Field 'category' in 'product' represents a finite set and should preferably reference a constant object. |
| `KSML-MODULE-004` | `gender_type` | `merchant.xml:1293` | Constant object 'gender_type' is referenced by exactly one business object ('employee'), but its _module_key ('basic_data') does not match the business object's _module_key ('employee_management'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `shipment_status_type` | `merchant.xml:1309` | Constant object 'shipment_status_type' is referenced by exactly one business object ('shipment'), but its _module_key ('basic_data') does not match the business object's _module_key ('moves'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `event_type` | `merchant.xml:1327` | Constant object 'event_type' is referenced by exactly one business object ('fulfillment_event'), but its _module_key ('basic_data') does not match the business object's _module_key ('fulfillment_events'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `movement_type` | `merchant.xml:1344` | Constant object 'movement_type' is referenced by exactly one business object ('stock_movement'), but its _module_key ('basic_data') does not match the business object's _module_key ('inventory'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `service_status_type` | `merchant.xml:1377` | Constant object 'service_status_type' is referenced by exactly one business object ('service_appointment'), but its _module_key ('basic_data') does not match the business object's _module_key ('service_scheduling'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `team_member_role` | `merchant.xml:1394` | Constant object 'team_member_role' is referenced by exactly one business object ('team_member'), but its _module_key ('basic_data') does not match the business object's _module_key ('service_scheduling'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `work_order_status` | `merchant.xml:1410` | Constant object 'work_order_status' is referenced by exactly one business object ('work_order'), but its _module_key ('basic_data') does not match the business object's _module_key ('work_order_management'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `task_status` | `merchant.xml:1442` | Constant object 'task_status' is referenced by exactly one business object ('task'), but its _module_key ('basic_data') does not match the business object's _module_key ('work_order_management'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `employment_type` | `merchant.xml:1474` | Constant object 'employment_type' is referenced by exactly one business object ('employment_record'), but its _module_key ('basic_data') does not match the business object's _module_key ('staff_registry'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `employment_status` | `merchant.xml:1490` | Constant object 'employment_status' is referenced by exactly one business object ('employment_record'), but its _module_key ('basic_data') does not match the business object's _module_key ('staff_registry'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `timesheet_status` | `merchant.xml:1505` | Constant object 'timesheet_status' is referenced by exactly one business object ('timesheet'), but its _module_key ('basic_data') does not match the business object's _module_key ('worked_hours'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `payroll_status` | `merchant.xml:1521` | Constant object 'payroll_status' is referenced by exactly one business object ('payroll_calculation'), but its _module_key ('basic_data') does not match the business object's _module_key ('payroll_calculations'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `payroll_item_type` | `merchant.xml:1537` | Constant object 'payroll_item_type' is referenced by exactly one business object ('payroll_item'), but its _module_key ('basic_data') does not match the business object's _module_key ('payroll_calculations'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `rule_type` | `merchant.xml:1553` | Constant object 'rule_type' is referenced by exactly one business object ('bonus_scheme'), but its _module_key ('basic_data') does not match the business object's _module_key ('bonuses'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `bonus_status` | `merchant.xml:1568` | Constant object 'bonus_status' is referenced by exactly one business object ('employee_bonus'), but its _module_key ('basic_data') does not match the business object's _module_key ('bonuses'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `leave_status` | `merchant.xml:1599` | Constant object 'leave_status' is referenced by exactly one business object ('leave_request'), but its _module_key ('basic_data') does not match the business object's _module_key ('leave_tracking'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `training_status` | `merchant.xml:1615` | Constant object 'training_status' is referenced by exactly one business object ('employee_training_enrollment'), but its _module_key ('basic_data') does not match the business object's _module_key ('training_and_development'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `customer_type` | `merchant.xml:1631` | Constant object 'customer_type' is referenced by exactly one business object ('customer'), but its _module_key ('basic_data') does not match the business object's _module_key ('private_and_corporate_customers'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `industry_type` | `merchant.xml:1646` | Constant object 'industry_type' is referenced by exactly one business object ('corporate_customer'), but its _module_key ('basic_data') does not match the business object's _module_key ('private_and_corporate_customers'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `billing_cycle` | `merchant.xml:1678` | Constant object 'billing_cycle' is referenced by exactly one business object ('billing_info'), but its _module_key ('basic_data') does not match the business object's _module_key ('billing_info'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `history_event_type` | `merchant.xml:1694` | Constant object 'history_event_type' is referenced by exactly one business object ('customer_history_event'), but its _module_key ('basic_data') does not match the business object's _module_key ('customer_history'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `contract_type` | `merchant.xml:1710` | Constant object 'contract_type' is referenced by exactly one business object ('service_contract'), but its _module_key ('basic_data') does not match the business object's _module_key ('contracts'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `contract_status` | `merchant.xml:1725` | Constant object 'contract_status' is referenced by exactly one business object ('service_contract'), but its _module_key ('basic_data') does not match the business object's _module_key ('contracts'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `document_type` | `merchant.xml:1741` | Constant object 'document_type' is referenced by exactly one business object ('contract_document'), but its _module_key ('basic_data') does not match the business object's _module_key ('document_storage'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `ticket_status` | `merchant.xml:1757` | Constant object 'ticket_status' is referenced by exactly one business object ('support_ticket'), but its _module_key ('basic_data') does not match the business object's _module_key ('customer_support'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `target_audience_type` | `merchant.xml:1806` | Constant object 'target_audience_type' is referenced by exactly one business object ('sales_campaign'), but its _module_key ('basic_data') does not match the business object's _module_key ('campaigns'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `discount_type` | `merchant.xml:1821` | Constant object 'discount_type' is referenced by exactly one business object ('discount_code'), but its _module_key ('basic_data') does not match the business object's _module_key ('discount_codes'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `lead_status` | `merchant.xml:1853` | Constant object 'lead_status' is referenced by exactly one business object ('lead'), but its _module_key ('basic_data') does not match the business object's _module_key ('lead_tracking'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `lead_activity_type` | `merchant.xml:1870` | Constant object 'lead_activity_type' is referenced by exactly one business object ('lead_activity'), but its _module_key ('basic_data') does not match the business object's _module_key ('lead_tracking'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `quotation_status` | `merchant.xml:1886` | Constant object 'quotation_status' is referenced by exactly one business object ('quotation'), but its _module_key ('basic_data') does not match the business object's _module_key ('sales_process'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `sales_order_status` | `merchant.xml:1903` | Constant object 'sales_order_status' is referenced by exactly one business object ('sales_order'), but its _module_key ('basic_data') does not match the business object's _module_key ('sales_process'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `account_type` | `merchant.xml:1919` | Constant object 'account_type' is referenced by exactly one business object ('account_chart'), but its _module_key ('basic_data') does not match the business object's _module_key ('financial_summaries'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `journal_status` | `merchant.xml:1936` | Constant object 'journal_status' is referenced by exactly one business object ('journal_entry'), but its _module_key ('basic_data') does not match the business object's _module_key ('financial_summaries'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `payment_status` | `merchant.xml:1951` | Constant object 'payment_status' is referenced by exactly one business object ('payment'), but its _module_key ('basic_data') does not match the business object's _module_key ('payments'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `invoice_status` | `merchant.xml:1967` | Constant object 'invoice_status' is referenced by exactly one business object ('invoice'), but its _module_key ('basic_data') does not match the business object's _module_key ('invoices'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `vat_rate` | `merchant.xml:1984` | Constant object 'vat_rate' is referenced by exactly one business object ('invoice_line_item'), but its _module_key ('basic_data') does not match the business object's _module_key ('invoices'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `expense_status` | `merchant.xml:2001` | Constant object 'expense_status' is referenced by exactly one business object ('expense_report'), but its _module_key ('basic_data') does not match the business object's _module_key ('expenses'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `expense_category` | `merchant.xml:2018` | Constant object 'expense_category' is referenced by exactly one business object ('expense_item'), but its _module_key ('basic_data') does not match the business object's _module_key ('expenses'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `statement_type` | `merchant.xml:2034` | Constant object 'statement_type' is referenced by exactly one business object ('financial_statement'), but its _module_key ('basic_data') does not match the business object's _module_key ('financial_summaries'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `statement_status` | `merchant.xml:2050` | Constant object 'statement_status' is referenced by exactly one business object ('financial_statement'), but its _module_key ('basic_data') does not match the business object's _module_key ('financial_summaries'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `budget_category` | `merchant.xml:2066` | Constant object 'budget_category' is referenced by exactly one business object ('budget'), but its _module_key ('basic_data') does not match the business object's _module_key ('budgeting'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `budget_status` | `merchant.xml:2082` | Constant object 'budget_status' is referenced by exactly one business object ('budget'), but its _module_key ('basic_data') does not match the business object's _module_key ('budgeting'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `depreciation_method` | `merchant.xml:2098` | Constant object 'depreciation_method' is referenced by exactly one business object ('asset_category'), but its _module_key ('basic_data') does not match the business object's _module_key ('asset_management'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `maintenance_status` | `merchant.xml:2129` | Constant object 'maintenance_status' is referenced by exactly one business object ('maintenance_schedule'), but its _module_key ('basic_data') does not match the business object's _module_key ('maintenance_schedules'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `policy_type` | `merchant.xml:2145` | Constant object 'policy_type' is referenced by exactly one business object ('insurance_policy'), but its _module_key ('basic_data') does not match the business object's _module_key ('insurance'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `compliance_type` | `merchant.xml:2161` | Constant object 'compliance_type' is referenced by exactly one business object ('compliance_document'), but its _module_key ('basic_data') does not match the business object's _module_key ('document_storage'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `action_type` | `merchant.xml:2177` | Constant object 'action_type' is referenced by exactly one business object ('audit_log'), but its _module_key ('basic_data') does not match the business object's _module_key ('audit_logs'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `notification_channel` | `merchant.xml:2194` | Constant object 'notification_channel' is referenced by exactly one business object ('notification_template'), but its _module_key ('basic_data') does not match the business object's _module_key ('notifications'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `auth_method_type` | `merchant.xml:2210` | Constant object 'auth_method_type' is referenced by exactly one business object ('external_integration'), but its _module_key ('basic_data') does not match the business object's _module_key ('api_ready_architecture'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-MODULE-004` | `customer_status` | `merchant.xml:2226` | Constant object 'customer_status' is referenced by exactly one business object ('customer'), but its _module_key ('basic_data') does not match the business object's _module_key ('private_and_corporate_customers'). The finite set should preferably share the same module key because it is local to that business area rather than shared basic data. |
| `KSML-TENANCY-001` | `external_integration` | `merchant.xml:1281` | Almost all business objects (95/96) contain tenant/merchant fields. Ensure that tenancy is explicitly required, rather than just copied from examples. |
| `KSML-PRIVACY-001-WARN` | `employee.mobile_phone` | `merchant.xml:45` | Contact identifier on person-like subject. Add `mobile_phone` to `_audit_mask_fields` (e.g., `<employee _audit_mask_fields="mobile_phone">`). |
| `KSML-PRIVACY-001-WARN` | `employee.email` | `merchant.xml:45` | Contact identifier on person-like subject. Add `email` to `_audit_mask_fields` (e.g., `<employee _audit_mask_fields="email">`). |
| `KSML-PRIVACY-001-WARN` | `customer.mobile_phone` | `merchant.xml:553` | Contact identifier on person-like subject. Add `mobile_phone` to `_audit_mask_fields` (e.g., `<customer _audit_mask_fields="mobile_phone">`). |
| `KSML-PRIVACY-001-WARN` | `customer.email` | `merchant.xml:553` | Contact identifier on person-like subject. Add `email` to `_audit_mask_fields` (e.g., `<customer _audit_mask_fields="email">`). |
| `KSML-PRIVACY-001-WARN` | `customer.billing_address` | `merchant.xml:553` | Location data on person-like subject. Add `billing_address` to `_audit_mask_fields` (e.g., `<customer _audit_mask_fields="billing_address">`). |
| `KSML-PRIVACY-001-WARN` | `customer.shipping_address` | `merchant.xml:553` | Location data on person-like subject. Add `shipping_address` to `_audit_mask_fields` (e.g., `<customer _audit_mask_fields="shipping_address">`). |
| `KSML-PRIVACY-001-WARN` | `corporate_customer.tax_id` | `merchant.xml:566` | Government identifier field. Add `tax_id` to `_audit_mask_fields` (e.g., `<corporate_customer _audit_mask_fields="tax_id">`). |
| `KSML-PRIVACY-001-WARN` | `customer_contact.contact_email` | `merchant.xml:580` | Contact identifier on person-like subject. Add `contact_email` to `_audit_mask_fields` (e.g., `<customer_contact _audit_mask_fields="contact_email">`). |
| `KSML-PRIVACY-001-WARN` | `bank_account.account_name` | `merchant.xml:1063` | Personal attribute on high-risk privacy subject. Add `account_name` to `_audit_mask_fields` (e.g., `<bank_account _audit_mask_fields="account_name">`). |
| `KSML-PRIVACY-001-WARN` | `bank_account.bank_name` | `merchant.xml:1063` | Personal attribute on high-risk privacy subject. Add `bank_name` to `_audit_mask_fields` (e.g., `<bank_account _audit_mask_fields="bank_name">`). |
| `KSML-PRIVACY-001-WARN` | `bank_account.account_number` | `merchant.xml:1063` | Financial data on high-risk privacy subject. Add `account_number` to `_audit_mask_fields` (e.g., `<bank_account _audit_mask_fields="account_number">`). |
## 💡 Suggestions
| Rule ID | Target | Source | Suggestion |
|---------|--------|--------|------------|
| `KSML-LOG-007` | `maintenance_log` | `merchant.xml:1159` | Object 'maintenance_log' has a name ending with '_log' but is not marked as a logging object. Consider adding _log="true" if this object represents append-only log entries. |
| `KSML-LOG-007` | `audit_log` | `merchant.xml:1215` | Object 'audit_log' has a name ending with '_log' but is not marked as a logging object. Consider adding _log="true" if this object represents append-only log entries. |
| `KSML-UI-002` | `gender_type` | `merchant.xml:1293` | Constant object 'gender_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `shipment_status_type` | `merchant.xml:1309` | Status-like constant 'shipment_status_type' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `shipment_status_type` | `merchant.xml:1309` | Constant object 'shipment_status_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `shipment_status_type` | `merchant.xml:1309` | Status-like constant 'shipment_status_type' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `event_type` | `merchant.xml:1327` | Constant object 'event_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `movement_type` | `merchant.xml:1344` | Constant object 'movement_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `vehicle_type` | `merchant.xml:1361` | Constant object 'vehicle_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `service_status_type` | `merchant.xml:1377` | Status-like constant 'service_status_type' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `service_status_type` | `merchant.xml:1377` | Constant object 'service_status_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `service_status_type` | `merchant.xml:1377` | Status-like constant 'service_status_type' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `team_member_role` | `merchant.xml:1394` | Constant object 'team_member_role' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `work_order_status` | `merchant.xml:1410` | Status-like constant 'work_order_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `work_order_status` | `merchant.xml:1410` | Constant object 'work_order_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `work_order_status` | `merchant.xml:1410` | Status-like constant 'work_order_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `priority_type` | `merchant.xml:1426` | Constant object 'priority_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `task_status` | `merchant.xml:1442` | Status-like constant 'task_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `task_status` | `merchant.xml:1442` | Constant object 'task_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `task_status` | `merchant.xml:1442` | Status-like constant 'task_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `salary_grade` | `merchant.xml:1458` | Constant object 'salary_grade' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `employment_type` | `merchant.xml:1474` | Constant object 'employment_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `employment_status` | `merchant.xml:1490` | Status-like constant 'employment_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `employment_status` | `merchant.xml:1490` | Constant object 'employment_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `employment_status` | `merchant.xml:1490` | Status-like constant 'employment_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-001` | `timesheet_status` | `merchant.xml:1505` | Status-like constant 'timesheet_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `timesheet_status` | `merchant.xml:1505` | Constant object 'timesheet_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `timesheet_status` | `merchant.xml:1505` | Status-like constant 'timesheet_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-001` | `payroll_status` | `merchant.xml:1521` | Status-like constant 'payroll_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `payroll_status` | `merchant.xml:1521` | Constant object 'payroll_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `payroll_status` | `merchant.xml:1521` | Status-like constant 'payroll_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `payroll_item_type` | `merchant.xml:1537` | Constant object 'payroll_item_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `rule_type` | `merchant.xml:1553` | Constant object 'rule_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `bonus_status` | `merchant.xml:1568` | Status-like constant 'bonus_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `bonus_status` | `merchant.xml:1568` | Constant object 'bonus_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `bonus_status` | `merchant.xml:1568` | Status-like constant 'bonus_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `leave_type` | `merchant.xml:1583` | Constant object 'leave_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `leave_status` | `merchant.xml:1599` | Status-like constant 'leave_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `leave_status` | `merchant.xml:1599` | Constant object 'leave_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `leave_status` | `merchant.xml:1599` | Status-like constant 'leave_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-001` | `training_status` | `merchant.xml:1615` | Status-like constant 'training_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `training_status` | `merchant.xml:1615` | Constant object 'training_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `training_status` | `merchant.xml:1615` | Status-like constant 'training_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `customer_type` | `merchant.xml:1631` | Constant object 'customer_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `industry_type` | `merchant.xml:1646` | Constant object 'industry_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `payment_method` | `merchant.xml:1662` | Constant object 'payment_method' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `billing_cycle` | `merchant.xml:1678` | Constant object 'billing_cycle' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `history_event_type` | `merchant.xml:1694` | Constant object 'history_event_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `contract_type` | `merchant.xml:1710` | Constant object 'contract_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `contract_status` | `merchant.xml:1725` | Status-like constant 'contract_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `contract_status` | `merchant.xml:1725` | Constant object 'contract_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `contract_status` | `merchant.xml:1725` | Status-like constant 'contract_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `document_type` | `merchant.xml:1741` | Constant object 'document_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `ticket_status` | `merchant.xml:1757` | Status-like constant 'ticket_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `ticket_status` | `merchant.xml:1757` | Constant object 'ticket_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `ticket_status` | `merchant.xml:1757` | Status-like constant 'ticket_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `unit_of_measure` | `merchant.xml:1773` | Constant object 'unit_of_measure' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `currency_type` | `merchant.xml:1790` | Constant object 'currency_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `target_audience_type` | `merchant.xml:1806` | Constant object 'target_audience_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `discount_type` | `merchant.xml:1821` | Constant object 'discount_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `lead_source` | `merchant.xml:1837` | Constant object 'lead_source' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `lead_status` | `merchant.xml:1853` | Status-like constant 'lead_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `lead_status` | `merchant.xml:1853` | Constant object 'lead_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `lead_status` | `merchant.xml:1853` | Status-like constant 'lead_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `lead_activity_type` | `merchant.xml:1870` | Constant object 'lead_activity_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `quotation_status` | `merchant.xml:1886` | Status-like constant 'quotation_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `quotation_status` | `merchant.xml:1886` | Constant object 'quotation_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `quotation_status` | `merchant.xml:1886` | Status-like constant 'quotation_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-001` | `sales_order_status` | `merchant.xml:1903` | Status-like constant 'sales_order_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `sales_order_status` | `merchant.xml:1903` | Constant object 'sales_order_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `sales_order_status` | `merchant.xml:1903` | Status-like constant 'sales_order_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `account_type` | `merchant.xml:1919` | Constant object 'account_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `journal_status` | `merchant.xml:1936` | Status-like constant 'journal_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `journal_status` | `merchant.xml:1936` | Constant object 'journal_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `journal_status` | `merchant.xml:1936` | Status-like constant 'journal_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-001` | `payment_status` | `merchant.xml:1951` | Status-like constant 'payment_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `payment_status` | `merchant.xml:1951` | Constant object 'payment_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `payment_status` | `merchant.xml:1951` | Status-like constant 'payment_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-001` | `invoice_status` | `merchant.xml:1967` | Status-like constant 'invoice_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `invoice_status` | `merchant.xml:1967` | Constant object 'invoice_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `invoice_status` | `merchant.xml:1967` | Status-like constant 'invoice_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `vat_rate` | `merchant.xml:1984` | Constant object 'vat_rate' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `expense_status` | `merchant.xml:2001` | Status-like constant 'expense_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `expense_status` | `merchant.xml:2001` | Constant object 'expense_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `expense_status` | `merchant.xml:2001` | Status-like constant 'expense_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `expense_category` | `merchant.xml:2018` | Constant object 'expense_category' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `statement_type` | `merchant.xml:2034` | Constant object 'statement_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `statement_status` | `merchant.xml:2050` | Status-like constant 'statement_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `statement_status` | `merchant.xml:2050` | Constant object 'statement_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `statement_status` | `merchant.xml:2050` | Status-like constant 'statement_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `budget_category` | `merchant.xml:2066` | Constant object 'budget_category' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `budget_status` | `merchant.xml:2082` | Status-like constant 'budget_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `budget_status` | `merchant.xml:2082` | Constant object 'budget_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `budget_status` | `merchant.xml:2082` | Status-like constant 'budget_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `depreciation_method` | `merchant.xml:2098` | Constant object 'depreciation_method' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `maintenance_type` | `merchant.xml:2113` | Constant object 'maintenance_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `maintenance_status` | `merchant.xml:2129` | Status-like constant 'maintenance_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `maintenance_status` | `merchant.xml:2129` | Constant object 'maintenance_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `maintenance_status` | `merchant.xml:2129` | Status-like constant 'maintenance_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-UI-002` | `policy_type` | `merchant.xml:2145` | Constant object 'policy_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `compliance_type` | `merchant.xml:2161` | Constant object 'compliance_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `action_type` | `merchant.xml:2177` | Constant object 'action_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `notification_channel` | `merchant.xml:2194` | Constant object 'notification_channel' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-002` | `auth_method_type` | `merchant.xml:2210` | Constant object 'auth_method_type' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-001` | `customer_status` | `merchant.xml:2226` | Status-like constant 'customer_status' can add color="string()" to declare visual badge colors for values. |
| `KSML-UI-002` | `customer_status` | `merchant.xml:2226` | Constant object 'customer_status' can add display_order="number()" for stable UI sorting. |
| `KSML-UI-003` | `customer_status` | `merchant.xml:2226` | Status-like constant 'customer_status' can add progress="number()" to visualize completion progress percentage (0-100). |
| `KSML-PRIVACY-001-SUG` | `employee.name` | `merchant.xml:45` | Personal attribute on person-like subject. Add `name` to `_audit_mask_fields` (e.g., `<employee _audit_mask_fields="name">`). |
| `KSML-PRIVACY-001-SUG` | `employee.gender` | `merchant.xml:45` | Personal attribute on person-like subject. Add `gender` to `_audit_mask_fields` (e.g., `<employee _audit_mask_fields="gender">`). |
| `KSML-PRIVACY-001-SUG` | `employee.birth_date` | `merchant.xml:45` | Personal attribute on person-like subject. Add `birth_date` to `_audit_mask_fields` (e.g., `<employee _audit_mask_fields="birth_date">`). |
| `KSML-PRIVACY-001-SUG` | `user_account.display_name` | `merchant.xml:59` | Personal attribute field. Add `display_name` to `_audit_mask_fields` (e.g., `<user_account _audit_mask_fields="display_name">`). |
| `KSML-PRIVACY-001-SUG` | `job_position.salary_grade` | `merchant.xml:383` | Financial data field. Add `salary_grade` to `_audit_mask_fields` (e.g., `<job_position _audit_mask_fields="salary_grade">`). |
| `KSML-PRIVACY-001-SUG` | `payroll_calculation.gross_salary` | `merchant.xml:445` | Financial data field. Add `gross_salary` to `_audit_mask_fields` (e.g., `<payroll_calculation _audit_mask_fields="gross_salary">`). |
| `KSML-PRIVACY-001-SUG` | `customer.name` | `merchant.xml:553` | Personal attribute on person-like subject. Add `name` to `_audit_mask_fields` (e.g., `<customer _audit_mask_fields="name">`). |
| `KSML-PRIVACY-001-SUG` | `customer_contact.contact_name` | `merchant.xml:580` | Personal attribute on person-like subject. Add `contact_name` to `_audit_mask_fields` (e.g., `<customer_contact _audit_mask_fields="contact_name">`). |
| `KSML-PRIVACY-001-SUG` | `billing_info.account_number` | `merchant.xml:593` | Financial data field. Add `account_number` to `_audit_mask_fields` (e.g., `<billing_info _audit_mask_fields="account_number">`). |
| `KSML-PRIVACY-001-SUG` | `lead.contact_email` | `merchant.xml:826` | Contact identifier field. Add `contact_email` to `_audit_mask_fields` (e.g., `<lead _audit_mask_fields="contact_email">`). |
## Privacy Findings
These are model-level risk findings and jurisdiction-specific review references, not a compliance certificate.
Field names do not establish legal applicability. Confirm processing purposes, legal bases, retention,
individual rights, cross-border transfers and operational evidence separately. Masking alone is not compliance.
Regional repetitions do not add to the Summary counts. Official references reviewed on 2026-10-13;
check current law and commencement dates before deployment.
### Mainland China — PIPL (Personal Information Protection Law)
PIPL (LAW). Confirm the processing falls within PIPL scope, including its territorial rules.
[Official reference](https://www.gov.cn/xinwen/2021-08/20/content_5632486.htm)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | PIPL Art. 28: financial accounts; verify whether this field contains account information rather than an ordinary business amount |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | PIPL Art. 28: financial accounts; verify whether this field contains account information rather than an ordinary business amount |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | PIPL Art. 28: financial accounts; verify whether this field contains account information rather than an ordinary business amount |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | PIPL: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | PIPL Art. 28: financial accounts; verify whether this field contains account information rather than an ordinary business amount |
### Hong Kong — PDPO (Personal Data (Privacy) Ordinance)
PDPO (LAW). Review the applicable data-user duties and six data protection principles.
[Official reference](https://www.pcpd.org.hk/english/data_privacy_law/ordinance_at_a_Glance/ordinance.html)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | PDPO: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### European Union / EEA — GDPR (General Data Protection Regulation)
GDPR (LAW). Confirm GDPR territorial scope and the lawful basis for the actual processing.
[Official reference](https://commission.europa.eu/law/law-topic/data-protection_en)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | GDPR Art. 4: identifier; verify that the field relates to an identifiable natural person |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | GDPR: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### United Kingdom — UK GDPR / Data Protection Act 2018 (UK General Data Protection Regulation and Data Protection Act 2018)
UK GDPR / Data Protection Act 2018 (LAW). Apply the UK framework separately; check applicable Data (Use and Access) Act 2025 amendments.
[Official reference](https://www.gov.uk/guidance/data-use-and-access-act-2025-data-protection-and-privacy-changes)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | UK GDPR / Data Protection Act 2018: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### Switzerland — FADP (Federal Act on Data Protection)
FADP (LAW). Confirm the revised federal law applies; check any additional sector or cantonal requirements.
[Official reference](https://www.edoeb.admin.ch/en/faq-data-protection)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | FADP: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### United States - California — CCPA, as amended by CPRA (California Consumer Privacy Act, as amended by the California Privacy Rights Act)
CCPA, as amended by CPRA (LAW). Confirm covered-business criteria and exemptions. CPRA amends CCPA; this is not a nationwide US law.
[Official reference](https://www.cppa.ca.gov/faq.html)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | CCPA/CPRA: verify whether location is precise geolocation; do not infer precision from the field name |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | CCPA/CPRA: verify whether location is precise geolocation; do not infer precision from the field name |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | CCPA, as amended by CPRA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### Canada — PIPEDA (Personal Information Protection and Electronic Documents Act)
PIPEDA (LAW). Confirm commercial-activity scope and whether a provincial or sector law applies instead or additionally.
[Official reference](https://www.priv.gc.ca/en/privacy-topics/privacy-laws-in-canada/the-personal-information-protection-and-electronic-documents-act-pipeda/pipeda_brief/)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | PIPEDA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### Brazil — LGPD (Lei Geral de Protecao de Dados Pessoais (General Personal Data Protection Law))
LGPD (LAW). Confirm LGPD applicability and the processing basis; field names do not establish either.
[Official reference](https://www.gov.br/anpd/pt-br/acesso-a-informacao/perguntas-frequentes)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | LGPD: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### Australia — Privacy Act 1988 / Australian Privacy Principles (Privacy Act 1988 and Australian Privacy Principles)
Privacy Act 1988 / Australian Privacy Principles (LAW). Confirm APP-entity coverage and exemptions; not every organisation is covered.
[Official reference](https://www.oaic.gov.au/privacy/privacy-legislation/the-privacy-act)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | Privacy Act 1988 / Australian Privacy Principles: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### India — DPDP Act 2023 / Rules 2025 (Digital Personal Data Protection Act 2023 and Digital Personal Data Protection Rules 2025)
DPDP Act 2023 / Rules 2025 (LAW). Confirm digital-personal-data scope and the commencement date of each provision; implementation is phased.
[Official reference](https://www.meity.gov.in/documents/act-and-policies/digital-personal-data-protection-rules-2025-gDOxUjMtQWa)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | DPDP Act 2023 / Rules 2025: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### Japan — APPI (Act on the Protection of Personal Information)
APPI (LAW). Confirm APPI coverage and the relevant handling and third-party provision requirements.
[Official reference](https://www.ppc.go.jp/en/legal/)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | APPI: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### South Korea — PIPA (Personal Information Protection Act)
PIPA (LAW). Confirm PIPA coverage and the current Korean statutory text and applicable amendments.
[Official reference](https://pipc.go.kr/eng/user/lgp/law/lawsRegulations.do)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | PIPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
### Singapore — PDPA (Personal Data Protection Act)
PDPA (LAW). Confirm organisational coverage, exceptions and which obligations are in force.
[Official reference](https://www.pdpc.gov.sg/overview-of-pdpa/the-legislation/personal-data-protection-act/data-protection-obligations)
| Severity | Target | Reason | Recommended Action | Regulatory Basis |
|----------|--------|--------|--------------------|------------------|
| Suggestion | `employee.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.gender` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="gender"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `employee.birth_date` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="birth_date"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `employee.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `user_account.display_name` | Personal attribute field. | Add to `_audit_mask_fields="display_name"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `job_position.salary_grade` | Financial data field. | Add to `_audit_mask_fields="salary_grade"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `payroll_calculation.gross_salary` | Financial data field. | Add to `_audit_mask_fields="gross_salary"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer.name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="name"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.mobile_phone` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="mobile_phone"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="email"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.billing_address` | Location data on person-like subject. | Add to `_audit_mask_fields="billing_address"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer.shipping_address` | Location data on person-like subject. | Add to `_audit_mask_fields="shipping_address"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `corporate_customer.tax_id` | Government identifier field. | Add to `_audit_mask_fields="tax_id"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `customer_contact.contact_name` | Personal attribute on person-like subject. | Add to `_audit_mask_fields="contact_name"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `customer_contact.contact_email` | Contact identifier on person-like subject. | Add to `_audit_mask_fields="contact_email"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `billing_info.account_number` | Financial data field. | Add to `_audit_mask_fields="account_number"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Suggestion | `lead.contact_email` | Contact identifier field. | Add to `_audit_mask_fields="contact_email"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="account_name"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.bank_name` | Personal attribute on high-risk privacy subject. | Add to `_audit_mask_fields="bank_name"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
| Warning | `bank_account.account_number` | Financial data on high-risk privacy subject. | Add to `_audit_mask_fields="account_number"`. | PDPA: review personal-data safeguards and unnecessary exposure in audit logs if the law applies |
## ✅ Solids
| Rule ID | Target | Source | Message |
|---------|--------|--------|---------|
| `KSML-UPLOAD-001` | `` | — | The upload contains 1 files. |
| `KSML-UPLOAD-005` | `` | `merchant.xml:2` | Resolved entrypoint: merchant.xml |
| `KSML-XML-002` | `` | `merchant.xml:2` | The XML document merchant.xml was parsed successfully. |
| `KSML-ROOT-003` | `` | `merchant.xml:2` | Root name 'crm-erp-service' is well-formed. |
| `KSML-ROOT-008` | `` | `merchant.xml:2` | External JSON business fields use the default camelCase profile. |
| `KSML-OBJECT-001` | `platform` | `merchant.xml:8` | Object 'platform' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `merchant` | `merchant.xml:17` | Object 'merchant' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `employee` | `merchant.xml:30` | Object 'employee' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `user_account` | `merchant.xml:47` | Object 'user_account' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `user_role` | `merchant.xml:61` | Object 'user_role' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `user_role_assignment` | `merchant.xml:72` | Object 'user_role_assignment' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `permission_set` | `merchant.xml:83` | Object 'permission_set' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `role_permission` | `merchant.xml:93` | Object 'role_permission' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `address` | `merchant.xml:103` | Object 'address' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `route` | `merchant.xml:119` | Object 'route' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `time_slot` | `merchant.xml:132` | Object 'time_slot' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `shipment` | `merchant.xml:144` | Object 'shipment' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `shipment_item` | `merchant.xml:162` | Object 'shipment_item' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `fulfillment_event` | `merchant.xml:175` | Object 'fulfillment_event' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `warehouse` | `merchant.xml:189` | Object 'warehouse' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `inventory_level` | `merchant.xml:200` | Object 'inventory_level' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `stock_movement` | `merchant.xml:213` | Object 'stock_movement' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `delivery_vehicle` | `merchant.xml:228` | Object 'delivery_vehicle' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `vehicle_assignment` | `merchant.xml:243` | Object 'vehicle_assignment' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `load_plan` | `merchant.xml:255` | Object 'load_plan' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `load_plan_item` | `merchant.xml:269` | Object 'load_plan_item' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `service_appointment` | `merchant.xml:280` | Object 'service_appointment' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `service_team` | `merchant.xml:296` | Object 'service_team' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `team_member` | `merchant.xml:307` | Object 'team_member' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `job_assignment` | `merchant.xml:318` | Object 'job_assignment' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `work_order` | `merchant.xml:331` | Object 'work_order' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `task` | `merchant.xml:347` | Object 'task' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `department` | `merchant.xml:361` | Object 'department' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `job_position` | `merchant.xml:373` | Object 'job_position' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `employment_record` | `merchant.xml:385` | Object 'employment_record' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `worked_hour_entry` | `merchant.xml:401` | Object 'worked_hour_entry' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `timesheet` | `merchant.xml:417` | Object 'timesheet' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `payroll_calculation` | `merchant.xml:431` | Object 'payroll_calculation' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `payroll_item` | `merchant.xml:447` | Object 'payroll_item' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `bonus_scheme` | `merchant.xml:459` | Object 'bonus_scheme' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `employee_bonus` | `merchant.xml:470` | Object 'employee_bonus' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `leave_request` | `merchant.xml:483` | Object 'leave_request' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `leave_balance` | `merchant.xml:500` | Object 'leave_balance' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `training_program` | `merchant.xml:514` | Object 'training_program' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `employee_training_enrollment` | `merchant.xml:526` | Object 'employee_training_enrollment' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `customer` | `merchant.xml:538` | Object 'customer' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `corporate_customer` | `merchant.xml:555` | Object 'corporate_customer' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `customer_contact` | `merchant.xml:568` | Object 'customer_contact' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `billing_info` | `merchant.xml:582` | Object 'billing_info' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `customer_history_event` | `merchant.xml:595` | Object 'customer_history_event' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `service_contract` | `merchant.xml:608` | Object 'service_contract' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `contract_document` | `merchant.xml:625` | Object 'contract_document' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `support_ticket` | `merchant.xml:638` | Object 'support_ticket' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `ticket_reply` | `merchant.xml:653` | Object 'ticket_reply' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `product_category` | `merchant.xml:665` | Object 'product_category' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `product` | `merchant.xml:676` | Object 'product' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `product_service` | `merchant.xml:691` | Object 'product_service' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `product_pricing` | `merchant.xml:703` | Object 'product_pricing' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `price_list` | `merchant.xml:717` | Object 'price_list' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `service_configuration_option` | `merchant.xml:727` | Object 'service_configuration_option' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `product_bundle` | `merchant.xml:739` | Object 'product_bundle' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `bundle_item` | `merchant.xml:749` | Object 'bundle_item' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `material_item` | `merchant.xml:760` | Object 'material_item' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `material_inventory` | `merchant.xml:773` | Object 'material_inventory' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `sales_campaign` | `merchant.xml:785` | Object 'sales_campaign' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `discount_code` | `merchant.xml:800` | Object 'discount_code' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `lead` | `merchant.xml:814` | Object 'lead' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `lead_activity` | `merchant.xml:828` | Object 'lead_activity' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `conversion_metric` | `merchant.xml:841` | Object 'conversion_metric' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `quotation` | `merchant.xml:855` | Object 'quotation' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `quotation_line_item` | `merchant.xml:871` | Object 'quotation_line_item' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `sales_order` | `merchant.xml:884` | Object 'sales_order' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `account_chart` | `merchant.xml:901` | Object 'account_chart' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `journal_entry` | `merchant.xml:913` | Object 'journal_entry' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `ledger_transaction` | `merchant.xml:926` | Object 'ledger_transaction' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `payment` | `merchant.xml:938` | Object 'payment' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `invoice` | `merchant.xml:952` | Object 'invoice' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `invoice_line_item` | `merchant.xml:969` | Object 'invoice_line_item' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `expense_report` | `merchant.xml:983` | Object 'expense_report' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `expense_item` | `merchant.xml:998` | Object 'expense_item' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `vat_rate_config` | `merchant.xml:1012` | Object 'vat_rate_config' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `financial_statement` | `merchant.xml:1024` | Object 'financial_statement' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `budget` | `merchant.xml:1038` | Object 'budget' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `bank_account` | `merchant.xml:1052` | Object 'bank_account' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `asset_category` | `merchant.xml:1065` | Object 'asset_category' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `asset` | `merchant.xml:1076` | Object 'asset' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `equipment` | `merchant.xml:1093` | Object 'equipment' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `vehicle` | `merchant.xml:1105` | Object 'vehicle' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `consumable` | `merchant.xml:1120` | Object 'consumable' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `consumable_stock` | `merchant.xml:1132` | Object 'consumable_stock' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `maintenance_schedule` | `merchant.xml:1145` | Object 'maintenance_schedule' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `maintenance_log` | `merchant.xml:1159` | Object 'maintenance_log' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `depreciation_record` | `merchant.xml:1173` | Object 'depreciation_record' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `insurance_policy` | `merchant.xml:1186` | Object 'insurance_policy' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `compliance_document` | `merchant.xml:1201` | Object 'compliance_document' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `audit_log` | `merchant.xml:1215` | Object 'audit_log' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `version_history` | `merchant.xml:1230` | Object 'version_history' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `deleted_record` | `merchant.xml:1245` | Object 'deleted_record' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `notification_template` | `merchant.xml:1257` | Object 'notification_template' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `system_automation_hook` | `merchant.xml:1269` | Object 'system_automation_hook' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `external_integration` | `merchant.xml:1281` | Object 'external_integration' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `gender_type` | `merchant.xml:1293` | Object 'gender_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `shipment_status_type` | `merchant.xml:1309` | Object 'shipment_status_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `event_type` | `merchant.xml:1327` | Object 'event_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `movement_type` | `merchant.xml:1344` | Object 'movement_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `vehicle_type` | `merchant.xml:1361` | Object 'vehicle_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `service_status_type` | `merchant.xml:1377` | Object 'service_status_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `team_member_role` | `merchant.xml:1394` | Object 'team_member_role' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `work_order_status` | `merchant.xml:1410` | Object 'work_order_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `priority_type` | `merchant.xml:1426` | Object 'priority_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `task_status` | `merchant.xml:1442` | Object 'task_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `salary_grade` | `merchant.xml:1458` | Object 'salary_grade' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `employment_type` | `merchant.xml:1474` | Object 'employment_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `employment_status` | `merchant.xml:1490` | Object 'employment_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `timesheet_status` | `merchant.xml:1505` | Object 'timesheet_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `payroll_status` | `merchant.xml:1521` | Object 'payroll_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `payroll_item_type` | `merchant.xml:1537` | Object 'payroll_item_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `rule_type` | `merchant.xml:1553` | Object 'rule_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `bonus_status` | `merchant.xml:1568` | Object 'bonus_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `leave_type` | `merchant.xml:1583` | Object 'leave_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `leave_status` | `merchant.xml:1599` | Object 'leave_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `training_status` | `merchant.xml:1615` | Object 'training_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `customer_type` | `merchant.xml:1631` | Object 'customer_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `industry_type` | `merchant.xml:1646` | Object 'industry_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `payment_method` | `merchant.xml:1662` | Object 'payment_method' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `billing_cycle` | `merchant.xml:1678` | Object 'billing_cycle' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `history_event_type` | `merchant.xml:1694` | Object 'history_event_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `contract_type` | `merchant.xml:1710` | Object 'contract_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `contract_status` | `merchant.xml:1725` | Object 'contract_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `document_type` | `merchant.xml:1741` | Object 'document_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `ticket_status` | `merchant.xml:1757` | Object 'ticket_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `unit_of_measure` | `merchant.xml:1773` | Object 'unit_of_measure' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `currency_type` | `merchant.xml:1790` | Object 'currency_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `target_audience_type` | `merchant.xml:1806` | Object 'target_audience_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `discount_type` | `merchant.xml:1821` | Object 'discount_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `lead_source` | `merchant.xml:1837` | Object 'lead_source' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `lead_status` | `merchant.xml:1853` | Object 'lead_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `lead_activity_type` | `merchant.xml:1870` | Object 'lead_activity_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `quotation_status` | `merchant.xml:1886` | Object 'quotation_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `sales_order_status` | `merchant.xml:1903` | Object 'sales_order_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `account_type` | `merchant.xml:1919` | Object 'account_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `journal_status` | `merchant.xml:1936` | Object 'journal_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `payment_status` | `merchant.xml:1951` | Object 'payment_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `invoice_status` | `merchant.xml:1967` | Object 'invoice_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `vat_rate` | `merchant.xml:1984` | Object 'vat_rate' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `expense_status` | `merchant.xml:2001` | Object 'expense_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `expense_category` | `merchant.xml:2018` | Object 'expense_category' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `statement_type` | `merchant.xml:2034` | Object 'statement_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `statement_status` | `merchant.xml:2050` | Object 'statement_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `budget_category` | `merchant.xml:2066` | Object 'budget_category' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `budget_status` | `merchant.xml:2082` | Object 'budget_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `depreciation_method` | `merchant.xml:2098` | Object 'depreciation_method' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `maintenance_type` | `merchant.xml:2113` | Object 'maintenance_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `maintenance_status` | `merchant.xml:2129` | Object 'maintenance_status' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `policy_type` | `merchant.xml:2145` | Object 'policy_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `compliance_type` | `merchant.xml:2161` | Object 'compliance_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `action_type` | `merchant.xml:2177` | Object 'action_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `notification_channel` | `merchant.xml:2194` | Object 'notification_channel' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `auth_method_type` | `merchant.xml:2210` | Object 'auth_method_type' defines display name, module, and module key metadata. |
| `KSML-OBJECT-001` | `customer_status` | `merchant.xml:2226` | Object 'customer_status' defines display name, module, and module key metadata. |
| `KSML-CONSTANT-007` | `gender_type.id` | `merchant.xml:1297` | Constant object 'gender_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `gender_type` | `merchant.xml:1293` | Constant object 'gender_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `gender_type` | `merchant.xml:1293` | Constant object 'gender_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `shipment_status_type.id` | `merchant.xml:1313` | Constant object 'shipment_status_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `shipment_status_type` | `merchant.xml:1309` | Constant object 'shipment_status_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `shipment_status_type` | `merchant.xml:1309` | Constant object 'shipment_status_type' has 5 constant value records. |
| `KSML-CONSTANT-007` | `event_type.id` | `merchant.xml:1331` | Constant object 'event_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `event_type` | `merchant.xml:1327` | Constant object 'event_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `event_type` | `merchant.xml:1327` | Constant object 'event_type' has 4 constant value records. |
| `KSML-CONSTANT-007` | `movement_type.id` | `merchant.xml:1348` | Constant object 'movement_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `movement_type` | `merchant.xml:1344` | Constant object 'movement_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `movement_type` | `merchant.xml:1344` | Constant object 'movement_type' has 4 constant value records. |
| `KSML-CONSTANT-007` | `vehicle_type.id` | `merchant.xml:1365` | Constant object 'vehicle_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `vehicle_type` | `merchant.xml:1361` | Constant object 'vehicle_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `vehicle_type` | `merchant.xml:1361` | Constant object 'vehicle_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `service_status_type.id` | `merchant.xml:1381` | Constant object 'service_status_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `service_status_type` | `merchant.xml:1377` | Constant object 'service_status_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `service_status_type` | `merchant.xml:1377` | Constant object 'service_status_type' has 4 constant value records. |
| `KSML-CONSTANT-007` | `team_member_role.id` | `merchant.xml:1398` | Constant object 'team_member_role' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `team_member_role` | `merchant.xml:1394` | Constant object 'team_member_role' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `team_member_role` | `merchant.xml:1394` | Constant object 'team_member_role' has 3 constant value records. |
| `KSML-CONSTANT-007` | `work_order_status.id` | `merchant.xml:1414` | Constant object 'work_order_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `work_order_status` | `merchant.xml:1410` | Constant object 'work_order_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `work_order_status` | `merchant.xml:1410` | Constant object 'work_order_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `priority_type.id` | `merchant.xml:1430` | Constant object 'priority_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `priority_type` | `merchant.xml:1426` | Constant object 'priority_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `priority_type` | `merchant.xml:1426` | Constant object 'priority_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `task_status.id` | `merchant.xml:1446` | Constant object 'task_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `task_status` | `merchant.xml:1442` | Constant object 'task_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `task_status` | `merchant.xml:1442` | Constant object 'task_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `salary_grade.id` | `merchant.xml:1462` | Constant object 'salary_grade' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `salary_grade` | `merchant.xml:1458` | Constant object 'salary_grade' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `salary_grade` | `merchant.xml:1458` | Constant object 'salary_grade' has 3 constant value records. |
| `KSML-CONSTANT-007` | `employment_type.id` | `merchant.xml:1478` | Constant object 'employment_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `employment_type` | `merchant.xml:1474` | Constant object 'employment_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `employment_type` | `merchant.xml:1474` | Constant object 'employment_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `employment_status.id` | `merchant.xml:1494` | Constant object 'employment_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `employment_status` | `merchant.xml:1490` | Constant object 'employment_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `employment_status` | `merchant.xml:1490` | Constant object 'employment_status' has 2 constant value records. |
| `KSML-CONSTANT-007` | `timesheet_status.id` | `merchant.xml:1509` | Constant object 'timesheet_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `timesheet_status` | `merchant.xml:1505` | Constant object 'timesheet_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `timesheet_status` | `merchant.xml:1505` | Constant object 'timesheet_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `payroll_status.id` | `merchant.xml:1525` | Constant object 'payroll_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `payroll_status` | `merchant.xml:1521` | Constant object 'payroll_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `payroll_status` | `merchant.xml:1521` | Constant object 'payroll_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `payroll_item_type.id` | `merchant.xml:1541` | Constant object 'payroll_item_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `payroll_item_type` | `merchant.xml:1537` | Constant object 'payroll_item_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `payroll_item_type` | `merchant.xml:1537` | Constant object 'payroll_item_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `rule_type.id` | `merchant.xml:1557` | Constant object 'rule_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `rule_type` | `merchant.xml:1553` | Constant object 'rule_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `rule_type` | `merchant.xml:1553` | Constant object 'rule_type' has 2 constant value records. |
| `KSML-CONSTANT-007` | `bonus_status.id` | `merchant.xml:1572` | Constant object 'bonus_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `bonus_status` | `merchant.xml:1568` | Constant object 'bonus_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `bonus_status` | `merchant.xml:1568` | Constant object 'bonus_status' has 2 constant value records. |
| `KSML-CONSTANT-007` | `leave_type.id` | `merchant.xml:1587` | Constant object 'leave_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `leave_type` | `merchant.xml:1583` | Constant object 'leave_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `leave_type` | `merchant.xml:1583` | Constant object 'leave_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `leave_status.id` | `merchant.xml:1603` | Constant object 'leave_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `leave_status` | `merchant.xml:1599` | Constant object 'leave_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `leave_status` | `merchant.xml:1599` | Constant object 'leave_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `training_status.id` | `merchant.xml:1619` | Constant object 'training_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `training_status` | `merchant.xml:1615` | Constant object 'training_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `training_status` | `merchant.xml:1615` | Constant object 'training_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `customer_type.id` | `merchant.xml:1635` | Constant object 'customer_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `customer_type` | `merchant.xml:1631` | Constant object 'customer_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `customer_type` | `merchant.xml:1631` | Constant object 'customer_type' has 2 constant value records. |
| `KSML-CONSTANT-007` | `industry_type.id` | `merchant.xml:1650` | Constant object 'industry_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `industry_type` | `merchant.xml:1646` | Constant object 'industry_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `industry_type` | `merchant.xml:1646` | Constant object 'industry_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `payment_method.id` | `merchant.xml:1666` | Constant object 'payment_method' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `payment_method` | `merchant.xml:1662` | Constant object 'payment_method' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `payment_method` | `merchant.xml:1662` | Constant object 'payment_method' has 3 constant value records. |
| `KSML-CONSTANT-007` | `billing_cycle.id` | `merchant.xml:1682` | Constant object 'billing_cycle' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `billing_cycle` | `merchant.xml:1678` | Constant object 'billing_cycle' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `billing_cycle` | `merchant.xml:1678` | Constant object 'billing_cycle' has 3 constant value records. |
| `KSML-CONSTANT-007` | `history_event_type.id` | `merchant.xml:1698` | Constant object 'history_event_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `history_event_type` | `merchant.xml:1694` | Constant object 'history_event_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `history_event_type` | `merchant.xml:1694` | Constant object 'history_event_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `contract_type.id` | `merchant.xml:1714` | Constant object 'contract_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `contract_type` | `merchant.xml:1710` | Constant object 'contract_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `contract_type` | `merchant.xml:1710` | Constant object 'contract_type' has 2 constant value records. |
| `KSML-CONSTANT-007` | `contract_status.id` | `merchant.xml:1729` | Constant object 'contract_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `contract_status` | `merchant.xml:1725` | Constant object 'contract_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `contract_status` | `merchant.xml:1725` | Constant object 'contract_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `document_type.id` | `merchant.xml:1745` | Constant object 'document_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `document_type` | `merchant.xml:1741` | Constant object 'document_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `document_type` | `merchant.xml:1741` | Constant object 'document_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `ticket_status.id` | `merchant.xml:1761` | Constant object 'ticket_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `ticket_status` | `merchant.xml:1757` | Constant object 'ticket_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `ticket_status` | `merchant.xml:1757` | Constant object 'ticket_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `unit_of_measure.id` | `merchant.xml:1777` | Constant object 'unit_of_measure' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `unit_of_measure` | `merchant.xml:1773` | Constant object 'unit_of_measure' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `unit_of_measure` | `merchant.xml:1773` | Constant object 'unit_of_measure' has 4 constant value records. |
| `KSML-CONSTANT-007` | `currency_type.id` | `merchant.xml:1794` | Constant object 'currency_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `currency_type` | `merchant.xml:1790` | Constant object 'currency_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `currency_type` | `merchant.xml:1790` | Constant object 'currency_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `target_audience_type.id` | `merchant.xml:1810` | Constant object 'target_audience_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `target_audience_type` | `merchant.xml:1806` | Constant object 'target_audience_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `target_audience_type` | `merchant.xml:1806` | Constant object 'target_audience_type' has 2 constant value records. |
| `KSML-CONSTANT-007` | `discount_type.id` | `merchant.xml:1825` | Constant object 'discount_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `discount_type` | `merchant.xml:1821` | Constant object 'discount_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `discount_type` | `merchant.xml:1821` | Constant object 'discount_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `lead_source.id` | `merchant.xml:1841` | Constant object 'lead_source' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `lead_source` | `merchant.xml:1837` | Constant object 'lead_source' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `lead_source` | `merchant.xml:1837` | Constant object 'lead_source' has 3 constant value records. |
| `KSML-CONSTANT-007` | `lead_status.id` | `merchant.xml:1857` | Constant object 'lead_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `lead_status` | `merchant.xml:1853` | Constant object 'lead_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `lead_status` | `merchant.xml:1853` | Constant object 'lead_status' has 4 constant value records. |
| `KSML-CONSTANT-007` | `lead_activity_type.id` | `merchant.xml:1874` | Constant object 'lead_activity_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `lead_activity_type` | `merchant.xml:1870` | Constant object 'lead_activity_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `lead_activity_type` | `merchant.xml:1870` | Constant object 'lead_activity_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `quotation_status.id` | `merchant.xml:1890` | Constant object 'quotation_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `quotation_status` | `merchant.xml:1886` | Constant object 'quotation_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `quotation_status` | `merchant.xml:1886` | Constant object 'quotation_status' has 4 constant value records. |
| `KSML-CONSTANT-007` | `sales_order_status.id` | `merchant.xml:1907` | Constant object 'sales_order_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `sales_order_status` | `merchant.xml:1903` | Constant object 'sales_order_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `sales_order_status` | `merchant.xml:1903` | Constant object 'sales_order_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `account_type.id` | `merchant.xml:1923` | Constant object 'account_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `account_type` | `merchant.xml:1919` | Constant object 'account_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `account_type` | `merchant.xml:1919` | Constant object 'account_type' has 4 constant value records. |
| `KSML-CONSTANT-007` | `journal_status.id` | `merchant.xml:1940` | Constant object 'journal_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `journal_status` | `merchant.xml:1936` | Constant object 'journal_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `journal_status` | `merchant.xml:1936` | Constant object 'journal_status' has 2 constant value records. |
| `KSML-CONSTANT-007` | `payment_status.id` | `merchant.xml:1955` | Constant object 'payment_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `payment_status` | `merchant.xml:1951` | Constant object 'payment_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `payment_status` | `merchant.xml:1951` | Constant object 'payment_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `invoice_status.id` | `merchant.xml:1971` | Constant object 'invoice_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `invoice_status` | `merchant.xml:1967` | Constant object 'invoice_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `invoice_status` | `merchant.xml:1967` | Constant object 'invoice_status' has 4 constant value records. |
| `KSML-CONSTANT-007` | `vat_rate.id` | `merchant.xml:1988` | Constant object 'vat_rate' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `vat_rate` | `merchant.xml:1984` | Constant object 'vat_rate' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `vat_rate` | `merchant.xml:1984` | Constant object 'vat_rate' has 4 constant value records. |
| `KSML-CONSTANT-007` | `expense_status.id` | `merchant.xml:2005` | Constant object 'expense_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `expense_status` | `merchant.xml:2001` | Constant object 'expense_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `expense_status` | `merchant.xml:2001` | Constant object 'expense_status' has 4 constant value records. |
| `KSML-CONSTANT-007` | `expense_category.id` | `merchant.xml:2022` | Constant object 'expense_category' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `expense_category` | `merchant.xml:2018` | Constant object 'expense_category' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `expense_category` | `merchant.xml:2018` | Constant object 'expense_category' has 3 constant value records. |
| `KSML-CONSTANT-007` | `statement_type.id` | `merchant.xml:2038` | Constant object 'statement_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `statement_type` | `merchant.xml:2034` | Constant object 'statement_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `statement_type` | `merchant.xml:2034` | Constant object 'statement_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `statement_status.id` | `merchant.xml:2054` | Constant object 'statement_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `statement_status` | `merchant.xml:2050` | Constant object 'statement_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `statement_status` | `merchant.xml:2050` | Constant object 'statement_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `budget_category.id` | `merchant.xml:2070` | Constant object 'budget_category' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `budget_category` | `merchant.xml:2066` | Constant object 'budget_category' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `budget_category` | `merchant.xml:2066` | Constant object 'budget_category' has 3 constant value records. |
| `KSML-CONSTANT-007` | `budget_status.id` | `merchant.xml:2086` | Constant object 'budget_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `budget_status` | `merchant.xml:2082` | Constant object 'budget_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `budget_status` | `merchant.xml:2082` | Constant object 'budget_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `depreciation_method.id` | `merchant.xml:2102` | Constant object 'depreciation_method' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `depreciation_method` | `merchant.xml:2098` | Constant object 'depreciation_method' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `depreciation_method` | `merchant.xml:2098` | Constant object 'depreciation_method' has 2 constant value records. |
| `KSML-CONSTANT-007` | `maintenance_type.id` | `merchant.xml:2117` | Constant object 'maintenance_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `maintenance_type` | `merchant.xml:2113` | Constant object 'maintenance_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `maintenance_type` | `merchant.xml:2113` | Constant object 'maintenance_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `maintenance_status.id` | `merchant.xml:2133` | Constant object 'maintenance_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `maintenance_status` | `merchant.xml:2129` | Constant object 'maintenance_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `maintenance_status` | `merchant.xml:2129` | Constant object 'maintenance_status' has 3 constant value records. |
| `KSML-CONSTANT-007` | `policy_type.id` | `merchant.xml:2149` | Constant object 'policy_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `policy_type` | `merchant.xml:2145` | Constant object 'policy_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `policy_type` | `merchant.xml:2145` | Constant object 'policy_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `compliance_type.id` | `merchant.xml:2165` | Constant object 'compliance_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `compliance_type` | `merchant.xml:2161` | Constant object 'compliance_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `compliance_type` | `merchant.xml:2161` | Constant object 'compliance_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `action_type.id` | `merchant.xml:2181` | Constant object 'action_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `action_type` | `merchant.xml:2177` | Constant object 'action_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `action_type` | `merchant.xml:2177` | Constant object 'action_type' has 4 constant value records. |
| `KSML-CONSTANT-007` | `notification_channel.id` | `merchant.xml:2198` | Constant object 'notification_channel' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `notification_channel` | `merchant.xml:2194` | Constant object 'notification_channel' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `notification_channel` | `merchant.xml:2194` | Constant object 'notification_channel' has 3 constant value records. |
| `KSML-CONSTANT-007` | `auth_method_type.id` | `merchant.xml:2214` | Constant object 'auth_method_type' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `auth_method_type` | `merchant.xml:2210` | Constant object 'auth_method_type' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `auth_method_type` | `merchant.xml:2210` | Constant object 'auth_method_type' has 3 constant value records. |
| `KSML-CONSTANT-007` | `customer_status.id` | `merchant.xml:2230` | Constant object 'customer_status' correctly defines id="id()". |
| `KSML-CONSTANT-001` | `customer_status` | `merchant.xml:2226` | Constant object 'customer_status' has correctly defined constant properties. |
| `KSML-CONSTANT-004` | `customer_status` | `merchant.xml:2226` | Constant object 'customer_status' has 3 constant value records. |
| `KSML-REFERENCE-003` | `merchant.platform` | `merchant.xml:25` | Reference 'platform' in 'merchant' successfully resolves to target object 'platform'. |
| `KSML-REFERENCE-003` | `employee.gender` | `merchant.xml:36` | Reference 'gender' in 'employee' successfully resolves to target object 'gender_type'. |
| `KSML-REFERENCE-003` | `employee.merchant` | `merchant.xml:42` | Reference 'merchant' in 'employee' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `user_account.employee` | `merchant.xml:53` | Reference 'employee' in 'user_account' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `user_account.merchant` | `merchant.xml:57` | Reference 'merchant' in 'user_account' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `user_role.merchant` | `merchant.xml:68` | Reference 'merchant' in 'user_role' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `user_role_assignment.assigned_by` | `merchant.xml:78` | Reference 'assigned_by' in 'user_role_assignment' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `user_role_assignment.merchant` | `merchant.xml:79` | Reference 'merchant' in 'user_role_assignment' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `user_role_assignment.role` | `merchant.xml:77` | Reference 'role' in 'user_role_assignment' successfully resolves to target object 'user_role'. |
| `KSML-REFERENCE-003` | `user_role_assignment.user` | `merchant.xml:76` | Reference 'user' in 'user_role_assignment' successfully resolves to target object 'user_account'. |
| `KSML-REFERENCE-003` | `permission_set.merchant` | `merchant.xml:89` | Reference 'merchant' in 'permission_set' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `role_permission.merchant` | `merchant.xml:99` | Reference 'merchant' in 'role_permission' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `role_permission.permission` | `merchant.xml:98` | Reference 'permission' in 'role_permission' successfully resolves to target object 'permission_set'. |
| `KSML-REFERENCE-003` | `role_permission.user_role` | `merchant.xml:97` | Reference 'user_role' in 'role_permission' successfully resolves to target object 'user_role'. |
| `KSML-REFERENCE-003` | `address.merchant` | `merchant.xml:115` | Reference 'merchant' in 'address' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `route.merchant` | `merchant.xml:128` | Reference 'merchant' in 'route' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `time_slot.merchant` | `merchant.xml:140` | Reference 'merchant' in 'time_slot' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `shipment.customer` | `merchant.xml:149` | Reference 'customer' in 'shipment' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `shipment.delivery_address` | `merchant.xml:151` | Reference 'delivery_address' in 'shipment' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `shipment.merchant` | `merchant.xml:157` | Reference 'merchant' in 'shipment' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `shipment.pickup_address` | `merchant.xml:150` | Reference 'pickup_address' in 'shipment' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `shipment.route` | `merchant.xml:152` | Reference 'route' in 'shipment' successfully resolves to target object 'route'. |
| `KSML-REFERENCE-003` | `shipment.status` | `merchant.xml:155` | Reference 'status' in 'shipment' successfully resolves to target object 'shipment_status_type'. |
| `KSML-REFERENCE-003` | `shipment.time_slot` | `merchant.xml:153` | Reference 'time_slot' in 'shipment' successfully resolves to target object 'time_slot'. |
| `KSML-REFERENCE-003` | `shipment_item.merchant` | `merchant.xml:171` | Reference 'merchant' in 'shipment_item' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `shipment_item.product` | `merchant.xml:167` | Reference 'product' in 'shipment_item' successfully resolves to target object 'product'. |
| `KSML-REFERENCE-003` | `shipment_item.shipment` | `merchant.xml:166` | Reference 'shipment' in 'shipment_item' successfully resolves to target object 'shipment'. |
| `KSML-REFERENCE-003` | `fulfillment_event.event_type` | `merchant.xml:180` | Reference 'event_type' in 'fulfillment_event' successfully resolves to target object 'event_type'. |
| `KSML-REFERENCE-003` | `fulfillment_event.location_address` | `merchant.xml:182` | Reference 'location_address' in 'fulfillment_event' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `fulfillment_event.merchant` | `merchant.xml:185` | Reference 'merchant' in 'fulfillment_event' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `fulfillment_event.reported_by` | `merchant.xml:184` | Reference 'reported_by' in 'fulfillment_event' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `fulfillment_event.shipment` | `merchant.xml:179` | Reference 'shipment' in 'fulfillment_event' successfully resolves to target object 'shipment'. |
| `KSML-REFERENCE-003` | `warehouse.manager` | `merchant.xml:195` | Reference 'manager' in 'warehouse' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `warehouse.merchant` | `merchant.xml:196` | Reference 'merchant' in 'warehouse' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `warehouse.warehouse_address` | `merchant.xml:194` | Reference 'warehouse_address' in 'warehouse' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `inventory_level.merchant` | `merchant.xml:208` | Reference 'merchant' in 'inventory_level' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `inventory_level.product` | `merchant.xml:205` | Reference 'product' in 'inventory_level' successfully resolves to target object 'product'. |
| `KSML-REFERENCE-003` | `inventory_level.warehouse` | `merchant.xml:204` | Reference 'warehouse' in 'inventory_level' successfully resolves to target object 'warehouse'. |
| `KSML-REFERENCE-003` | `stock_movement.merchant` | `merchant.xml:224` | Reference 'merchant' in 'stock_movement' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `stock_movement.movement_type` | `merchant.xml:221` | Reference 'movement_type' in 'stock_movement' successfully resolves to target object 'movement_type'. |
| `KSML-REFERENCE-003` | `stock_movement.processed_by` | `merchant.xml:223` | Reference 'processed_by' in 'stock_movement' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `stock_movement.product` | `merchant.xml:217` | Reference 'product' in 'stock_movement' successfully resolves to target object 'product'. |
| `KSML-REFERENCE-003` | `stock_movement.source_warehouse` | `merchant.xml:218` | Reference 'source_warehouse' in 'stock_movement' successfully resolves to target object 'warehouse'. |
| `KSML-REFERENCE-003` | `stock_movement.target_warehouse` | `merchant.xml:219` | Reference 'target_warehouse' in 'stock_movement' successfully resolves to target object 'warehouse'. |
| `KSML-REFERENCE-003` | `delivery_vehicle.current_location` | `merchant.xml:237` | Reference 'current_location' in 'delivery_vehicle' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `delivery_vehicle.driver` | `merchant.xml:236` | Reference 'driver' in 'delivery_vehicle' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `delivery_vehicle.merchant` | `merchant.xml:238` | Reference 'merchant' in 'delivery_vehicle' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `delivery_vehicle.vehicle_type` | `merchant.xml:233` | Reference 'vehicle_type' in 'delivery_vehicle' successfully resolves to target object 'vehicle_type'. |
| `KSML-REFERENCE-003` | `vehicle_assignment.assigned_driver` | `merchant.xml:250` | Reference 'assigned_driver' in 'vehicle_assignment' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `vehicle_assignment.delivery_vehicle` | `merchant.xml:247` | Reference 'delivery_vehicle' in 'vehicle_assignment' successfully resolves to target object 'delivery_vehicle'. |
| `KSML-REFERENCE-003` | `vehicle_assignment.merchant` | `merchant.xml:251` | Reference 'merchant' in 'vehicle_assignment' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `vehicle_assignment.shipment` | `merchant.xml:248` | Reference 'shipment' in 'vehicle_assignment' successfully resolves to target object 'shipment'. |
| `KSML-REFERENCE-003` | `load_plan.merchant` | `merchant.xml:265` | Reference 'merchant' in 'load_plan' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `load_plan.planner` | `merchant.xml:262` | Reference 'planner' in 'load_plan' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `load_plan.route` | `merchant.xml:259` | Reference 'route' in 'load_plan' successfully resolves to target object 'route'. |
| `KSML-REFERENCE-003` | `load_plan.vehicle` | `merchant.xml:260` | Reference 'vehicle' in 'load_plan' successfully resolves to target object 'delivery_vehicle'. |
| `KSML-REFERENCE-003` | `load_plan_item.load_plan` | `merchant.xml:273` | Reference 'load_plan' in 'load_plan_item' successfully resolves to target object 'load_plan'. |
| `KSML-REFERENCE-003` | `load_plan_item.merchant` | `merchant.xml:276` | Reference 'merchant' in 'load_plan_item' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `load_plan_item.shipment` | `merchant.xml:274` | Reference 'shipment' in 'load_plan_item' successfully resolves to target object 'shipment'. |
| `KSML-REFERENCE-003` | `service_appointment.assigned_team` | `merchant.xml:289` | Reference 'assigned_team' in 'service_appointment' successfully resolves to target object 'service_team'. |
| `KSML-REFERENCE-003` | `service_appointment.customer` | `merchant.xml:284` | Reference 'customer' in 'service_appointment' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `service_appointment.merchant` | `merchant.xml:291` | Reference 'merchant' in 'service_appointment' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `service_appointment.service` | `merchant.xml:285` | Reference 'service' in 'service_appointment' successfully resolves to target object 'product_service'. |
| `KSML-REFERENCE-003` | `service_appointment.service_address` | `merchant.xml:288` | Reference 'service_address' in 'service_appointment' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `service_appointment.status` | `merchant.xml:290` | Reference 'status' in 'service_appointment' successfully resolves to target object 'service_status_type'. |
| `KSML-REFERENCE-003` | `service_appointment.time_slot` | `merchant.xml:287` | Reference 'time_slot' in 'service_appointment' successfully resolves to target object 'time_slot'. |
| `KSML-REFERENCE-003` | `service_team.base_location` | `merchant.xml:302` | Reference 'base_location' in 'service_team' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `service_team.merchant` | `merchant.xml:303` | Reference 'merchant' in 'service_team' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `service_team.team_lead` | `merchant.xml:301` | Reference 'team_lead' in 'service_team' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `team_member.employee` | `merchant.xml:312` | Reference 'employee' in 'team_member' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `team_member.merchant` | `merchant.xml:314` | Reference 'merchant' in 'team_member' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `team_member.role` | `merchant.xml:313` | Reference 'role' in 'team_member' successfully resolves to target object 'team_member_role'. |
| `KSML-REFERENCE-003` | `team_member.service_team` | `merchant.xml:311` | Reference 'service_team' in 'team_member' successfully resolves to target object 'service_team'. |
| `KSML-REFERENCE-003` | `job_assignment.assigned_employee` | `merchant.xml:323` | Reference 'assigned_employee' in 'job_assignment' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `job_assignment.merchant` | `merchant.xml:327` | Reference 'merchant' in 'job_assignment' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `job_assignment.service_appointment` | `merchant.xml:322` | Reference 'service_appointment' in 'job_assignment' successfully resolves to target object 'service_appointment'. |
| `KSML-REFERENCE-003` | `work_order.assigned_to` | `merchant.xml:340` | Reference 'assigned_to' in 'work_order' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `work_order.merchant` | `merchant.xml:342` | Reference 'merchant' in 'work_order' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `work_order.priority` | `merchant.xml:339` | Reference 'priority' in 'work_order' successfully resolves to target object 'priority_type'. |
| `KSML-REFERENCE-003` | `work_order.related_service_appointment` | `merchant.xml:337` | Reference 'related_service_appointment' in 'work_order' successfully resolves to target object 'service_appointment'. |
| `KSML-REFERENCE-003` | `work_order.related_shipment` | `merchant.xml:336` | Reference 'related_shipment' in 'work_order' successfully resolves to target object 'shipment'. |
| `KSML-REFERENCE-003` | `work_order.status` | `merchant.xml:338` | Reference 'status' in 'work_order' successfully resolves to target object 'work_order_status'. |
| `KSML-REFERENCE-003` | `task.assigned_to` | `merchant.xml:353` | Reference 'assigned_to' in 'task' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `task.merchant` | `merchant.xml:357` | Reference 'merchant' in 'task' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `task.status` | `merchant.xml:354` | Reference 'status' in 'task' successfully resolves to target object 'task_status'. |
| `KSML-REFERENCE-003` | `task.work_order` | `merchant.xml:351` | Reference 'work_order' in 'task' successfully resolves to target object 'work_order'. |
| `KSML-REFERENCE-003` | `department.manager` | `merchant.xml:367` | Reference 'manager' in 'department' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `department.merchant` | `merchant.xml:369` | Reference 'merchant' in 'department' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `job_position.department` | `merchant.xml:378` | Reference 'department' in 'job_position' successfully resolves to target object 'department'. |
| `KSML-REFERENCE-003` | `job_position.merchant` | `merchant.xml:381` | Reference 'merchant' in 'job_position' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `employment_record.department` | `merchant.xml:390` | Reference 'department' in 'employment_record' successfully resolves to target object 'department'. |
| `KSML-REFERENCE-003` | `employment_record.employee` | `merchant.xml:389` | Reference 'employee' in 'employment_record' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `employment_record.employment_type` | `merchant.xml:394` | Reference 'employment_type' in 'employment_record' successfully resolves to target object 'employment_type'. |
| `KSML-REFERENCE-003` | `employment_record.job_position` | `merchant.xml:391` | Reference 'job_position' in 'employment_record' successfully resolves to target object 'job_position'. |
| `KSML-REFERENCE-003` | `employment_record.merchant` | `merchant.xml:396` | Reference 'merchant' in 'employment_record' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `employment_record.status` | `merchant.xml:395` | Reference 'status' in 'employment_record' successfully resolves to target object 'employment_status'. |
| `KSML-REFERENCE-003` | `worked_hour_entry.employee` | `merchant.xml:405` | Reference 'employee' in 'worked_hour_entry' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `worked_hour_entry.merchant` | `merchant.xml:413` | Reference 'merchant' in 'worked_hour_entry' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `worked_hour_entry.task_performed` | `merchant.xml:411` | Reference 'task_performed' in 'worked_hour_entry' successfully resolves to target object 'task'. |
| `KSML-REFERENCE-003` | `timesheet.approved_by` | `merchant.xml:425` | Reference 'approved_by' in 'timesheet' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `timesheet.employee` | `merchant.xml:421` | Reference 'employee' in 'timesheet' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `timesheet.merchant` | `merchant.xml:426` | Reference 'merchant' in 'timesheet' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `timesheet.status` | `merchant.xml:424` | Reference 'status' in 'timesheet' successfully resolves to target object 'timesheet_status'. |
| `KSML-REFERENCE-003` | `payroll_calculation.employee` | `merchant.xml:435` | Reference 'employee' in 'payroll_calculation' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `payroll_calculation.merchant` | `merchant.xml:443` | Reference 'merchant' in 'payroll_calculation' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `payroll_calculation.processed_by` | `merchant.xml:442` | Reference 'processed_by' in 'payroll_calculation' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `payroll_calculation.status` | `merchant.xml:441` | Reference 'status' in 'payroll_calculation' successfully resolves to target object 'payroll_status'. |
| `KSML-REFERENCE-003` | `payroll_item.item_type` | `merchant.xml:452` | Reference 'item_type' in 'payroll_item' successfully resolves to target object 'payroll_item_type'. |
| `KSML-REFERENCE-003` | `payroll_item.merchant` | `merchant.xml:455` | Reference 'merchant' in 'payroll_item' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `payroll_item.payroll` | `merchant.xml:451` | Reference 'payroll' in 'payroll_item' successfully resolves to target object 'payroll_calculation'. |
| `KSML-REFERENCE-003` | `bonus_scheme.calculation_rule` | `merchant.xml:465` | Reference 'calculation_rule' in 'bonus_scheme' successfully resolves to target object 'rule_type'. |
| `KSML-REFERENCE-003` | `bonus_scheme.merchant` | `merchant.xml:466` | Reference 'merchant' in 'bonus_scheme' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `employee_bonus.bonus_scheme` | `merchant.xml:475` | Reference 'bonus_scheme' in 'employee_bonus' successfully resolves to target object 'bonus_scheme'. |
| `KSML-REFERENCE-003` | `employee_bonus.employee` | `merchant.xml:474` | Reference 'employee' in 'employee_bonus' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `employee_bonus.merchant` | `merchant.xml:479` | Reference 'merchant' in 'employee_bonus' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `employee_bonus.status` | `merchant.xml:478` | Reference 'status' in 'employee_bonus' successfully resolves to target object 'bonus_status'. |
| `KSML-REFERENCE-003` | `leave_request.approved_by` | `merchant.xml:494` | Reference 'approved_by' in 'leave_request' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `leave_request.employee` | `merchant.xml:487` | Reference 'employee' in 'leave_request' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `leave_request.leave_type` | `merchant.xml:488` | Reference 'leave_type' in 'leave_request' successfully resolves to target object 'leave_type'. |
| `KSML-REFERENCE-003` | `leave_request.merchant` | `merchant.xml:495` | Reference 'merchant' in 'leave_request' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `leave_request.status` | `merchant.xml:493` | Reference 'status' in 'leave_request' successfully resolves to target object 'leave_status'. |
| `KSML-REFERENCE-003` | `leave_balance.employee` | `merchant.xml:504` | Reference 'employee' in 'leave_balance' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `leave_balance.leave_type` | `merchant.xml:505` | Reference 'leave_type' in 'leave_balance' successfully resolves to target object 'leave_type'. |
| `KSML-REFERENCE-003` | `leave_balance.merchant` | `merchant.xml:509` | Reference 'merchant' in 'leave_balance' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `training_program.merchant` | `merchant.xml:522` | Reference 'merchant' in 'training_program' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `training_program.trainer` | `merchant.xml:521` | Reference 'trainer' in 'training_program' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `employee_training_enrollment.completion_status` | `merchant.xml:533` | Reference 'completion_status' in 'employee_training_enrollment' successfully resolves to target object 'training_status'. |
| `KSML-REFERENCE-003` | `employee_training_enrollment.employee` | `merchant.xml:530` | Reference 'employee' in 'employee_training_enrollment' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `employee_training_enrollment.merchant` | `merchant.xml:534` | Reference 'merchant' in 'employee_training_enrollment' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `employee_training_enrollment.training_program` | `merchant.xml:531` | Reference 'training_program' in 'employee_training_enrollment' successfully resolves to target object 'training_program'. |
| `KSML-REFERENCE-003` | `customer.billing_address` | `merchant.xml:546` | Reference 'billing_address' in 'customer' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `customer.customer_type` | `merchant.xml:542` | Reference 'customer_type' in 'customer' successfully resolves to target object 'customer_type'. |
| `KSML-REFERENCE-003` | `customer.lead_source` | `merchant.xml:548` | Reference 'lead_source' in 'customer' successfully resolves to target object 'lead_source'. |
| `KSML-REFERENCE-003` | `customer.merchant` | `merchant.xml:550` | Reference 'merchant' in 'customer' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `customer.shipping_address` | `merchant.xml:547` | Reference 'shipping_address' in 'customer' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `customer.status` | `merchant.xml:549` | Reference 'status' in 'customer' successfully resolves to target object 'customer_status'. |
| `KSML-REFERENCE-003` | `corporate_customer.customer` | `merchant.xml:559` | Reference 'customer' in 'corporate_customer' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `corporate_customer.industry` | `merchant.xml:562` | Reference 'industry' in 'corporate_customer' successfully resolves to target object 'industry_type'. |
| `KSML-REFERENCE-003` | `corporate_customer.merchant` | `merchant.xml:564` | Reference 'merchant' in 'corporate_customer' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `customer_contact.customer` | `merchant.xml:572` | Reference 'customer' in 'customer_contact' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `customer_contact.merchant` | `merchant.xml:578` | Reference 'merchant' in 'customer_contact' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `billing_info.billing_cycle` | `merchant.xml:589` | Reference 'billing_cycle' in 'billing_info' successfully resolves to target object 'billing_cycle'. |
| `KSML-REFERENCE-003` | `billing_info.customer` | `merchant.xml:586` | Reference 'customer' in 'billing_info' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `billing_info.default_billing_address` | `merchant.xml:590` | Reference 'default_billing_address' in 'billing_info' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `billing_info.merchant` | `merchant.xml:591` | Reference 'merchant' in 'billing_info' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `billing_info.payment_method` | `merchant.xml:587` | Reference 'payment_method' in 'billing_info' successfully resolves to target object 'payment_method'. |
| `KSML-REFERENCE-003` | `customer_history_event.customer` | `merchant.xml:599` | Reference 'customer' in 'customer_history_event' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `customer_history_event.event_type` | `merchant.xml:600` | Reference 'event_type' in 'customer_history_event' successfully resolves to target object 'history_event_type'. |
| `KSML-REFERENCE-003` | `customer_history_event.merchant` | `merchant.xml:604` | Reference 'merchant' in 'customer_history_event' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `customer_history_event.related_employee` | `merchant.xml:603` | Reference 'related_employee' in 'customer_history_event' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `service_contract.contract_type` | `merchant.xml:614` | Reference 'contract_type' in 'service_contract' successfully resolves to target object 'contract_type'. |
| `KSML-REFERENCE-003` | `service_contract.customer` | `merchant.xml:612` | Reference 'customer' in 'service_contract' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `service_contract.managed_by` | `merchant.xml:619` | Reference 'managed_by' in 'service_contract' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `service_contract.merchant` | `merchant.xml:620` | Reference 'merchant' in 'service_contract' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `service_contract.status` | `merchant.xml:618` | Reference 'status' in 'service_contract' successfully resolves to target object 'contract_status'. |
| `KSML-REFERENCE-003` | `contract_document.document_type` | `merchant.xml:630` | Reference 'document_type' in 'contract_document' successfully resolves to target object 'document_type'. |
| `KSML-REFERENCE-003` | `contract_document.merchant` | `merchant.xml:634` | Reference 'merchant' in 'contract_document' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `contract_document.service_contract` | `merchant.xml:629` | Reference 'service_contract' in 'contract_document' successfully resolves to target object 'service_contract'. |
| `KSML-REFERENCE-003` | `contract_document.uploaded_by` | `merchant.xml:633` | Reference 'uploaded_by' in 'contract_document' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `support_ticket.assigned_to` | `merchant.xml:647` | Reference 'assigned_to' in 'support_ticket' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `support_ticket.customer` | `merchant.xml:642` | Reference 'customer' in 'support_ticket' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `support_ticket.merchant` | `merchant.xml:648` | Reference 'merchant' in 'support_ticket' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `support_ticket.priority` | `merchant.xml:645` | Reference 'priority' in 'support_ticket' successfully resolves to target object 'priority_type'. |
| `KSML-REFERENCE-003` | `support_ticket.status` | `merchant.xml:646` | Reference 'status' in 'support_ticket' successfully resolves to target object 'ticket_status'. |
| `KSML-REFERENCE-003` | `ticket_reply.merchant` | `merchant.xml:661` | Reference 'merchant' in 'ticket_reply' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `ticket_reply.replied_by` | `merchant.xml:658` | Reference 'replied_by' in 'ticket_reply' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `ticket_reply.support_ticket` | `merchant.xml:657` | Reference 'support_ticket' in 'ticket_reply' successfully resolves to target object 'support_ticket'. |
| `KSML-REFERENCE-003` | `product_category.merchant` | `merchant.xml:672` | Reference 'merchant' in 'product_category' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `product.category` | `merchant.xml:682` | Reference 'category' in 'product' successfully resolves to target object 'product_category'. |
| `KSML-REFERENCE-003` | `product.merchant` | `merchant.xml:686` | Reference 'merchant' in 'product' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `product.unit_of_measure` | `merchant.xml:683` | Reference 'unit_of_measure' in 'product' successfully resolves to target object 'unit_of_measure'. |
| `KSML-REFERENCE-003` | `product_service.merchant` | `merchant.xml:699` | Reference 'merchant' in 'product_service' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `product_service.product` | `merchant.xml:695` | Reference 'product' in 'product_service' successfully resolves to target object 'product'. |
| `KSML-REFERENCE-003` | `product_pricing.currency` | `merchant.xml:710` | Reference 'currency' in 'product_pricing' successfully resolves to target object 'currency_type'. |
| `KSML-REFERENCE-003` | `product_pricing.merchant` | `merchant.xml:712` | Reference 'merchant' in 'product_pricing' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `product_pricing.price_list` | `merchant.xml:708` | Reference 'price_list' in 'product_pricing' successfully resolves to target object 'price_list'. |
| `KSML-REFERENCE-003` | `product_pricing.product` | `merchant.xml:707` | Reference 'product' in 'product_pricing' successfully resolves to target object 'product'. |
| `KSML-REFERENCE-003` | `price_list.merchant` | `merchant.xml:723` | Reference 'merchant' in 'price_list' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `service_configuration_option.merchant` | `merchant.xml:735` | Reference 'merchant' in 'service_configuration_option' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `service_configuration_option.product_service` | `merchant.xml:731` | Reference 'product_service' in 'service_configuration_option' successfully resolves to target object 'product_service'. |
| `KSML-REFERENCE-003` | `product_bundle.merchant` | `merchant.xml:745` | Reference 'merchant' in 'product_bundle' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `bundle_item.merchant` | `merchant.xml:756` | Reference 'merchant' in 'bundle_item' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `bundle_item.product` | `merchant.xml:754` | Reference 'product' in 'bundle_item' successfully resolves to target object 'product'. |
| `KSML-REFERENCE-003` | `bundle_item.product_bundle` | `merchant.xml:753` | Reference 'product_bundle' in 'bundle_item' successfully resolves to target object 'product_bundle'. |
| `KSML-REFERENCE-003` | `material_item.merchant` | `merchant.xml:769` | Reference 'merchant' in 'material_item' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `material_inventory.material` | `merchant.xml:777` | Reference 'material' in 'material_inventory' successfully resolves to target object 'material_item'. |
| `KSML-REFERENCE-003` | `material_inventory.merchant` | `merchant.xml:780` | Reference 'merchant' in 'material_inventory' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `material_inventory.warehouse` | `merchant.xml:778` | Reference 'warehouse' in 'material_inventory' successfully resolves to target object 'warehouse'. |
| `KSML-REFERENCE-003` | `sales_campaign.manager` | `merchant.xml:794` | Reference 'manager' in 'sales_campaign' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `sales_campaign.merchant` | `merchant.xml:795` | Reference 'merchant' in 'sales_campaign' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `sales_campaign.target_audience` | `merchant.xml:793` | Reference 'target_audience' in 'sales_campaign' successfully resolves to target object 'target_audience_type'. |
| `KSML-REFERENCE-003` | `discount_code.campaign` | `merchant.xml:805` | Reference 'campaign' in 'discount_code' successfully resolves to target object 'sales_campaign'. |
| `KSML-REFERENCE-003` | `discount_code.discount_type` | `merchant.xml:806` | Reference 'discount_type' in 'discount_code' successfully resolves to target object 'discount_type'. |
| `KSML-REFERENCE-003` | `discount_code.merchant` | `merchant.xml:810` | Reference 'merchant' in 'discount_code' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `lead.assigned_to` | `merchant.xml:822` | Reference 'assigned_to' in 'lead' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `lead.merchant` | `merchant.xml:823` | Reference 'merchant' in 'lead' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `lead.source` | `merchant.xml:820` | Reference 'source' in 'lead' successfully resolves to target object 'lead_source'. |
| `KSML-REFERENCE-003` | `lead.status` | `merchant.xml:821` | Reference 'status' in 'lead' successfully resolves to target object 'lead_status'. |
| `KSML-REFERENCE-003` | `lead_activity.activity_type` | `merchant.xml:833` | Reference 'activity_type' in 'lead_activity' successfully resolves to target object 'lead_activity_type'. |
| `KSML-REFERENCE-003` | `lead_activity.lead` | `merchant.xml:832` | Reference 'lead' in 'lead_activity' successfully resolves to target object 'lead'. |
| `KSML-REFERENCE-003` | `lead_activity.merchant` | `merchant.xml:837` | Reference 'merchant' in 'lead_activity' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `lead_activity.performed_by` | `merchant.xml:836` | Reference 'performed_by' in 'lead_activity' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `conversion_metric.campaign` | `merchant.xml:845` | Reference 'campaign' in 'conversion_metric' successfully resolves to target object 'sales_campaign'. |
| `KSML-REFERENCE-003` | `conversion_metric.merchant` | `merchant.xml:851` | Reference 'merchant' in 'conversion_metric' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `quotation.customer` | `merchant.xml:860` | Reference 'customer' in 'quotation' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `quotation.merchant` | `merchant.xml:866` | Reference 'merchant' in 'quotation' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `quotation.prepared_by` | `merchant.xml:861` | Reference 'prepared_by' in 'quotation' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `quotation.status` | `merchant.xml:865` | Reference 'status' in 'quotation' successfully resolves to target object 'quotation_status'. |
| `KSML-REFERENCE-003` | `quotation_line_item.merchant` | `merchant.xml:880` | Reference 'merchant' in 'quotation_line_item' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `quotation_line_item.product` | `merchant.xml:876` | Reference 'product' in 'quotation_line_item' successfully resolves to target object 'product'. |
| `KSML-REFERENCE-003` | `quotation_line_item.quotation` | `merchant.xml:875` | Reference 'quotation' in 'quotation_line_item' successfully resolves to target object 'quotation'. |
| `KSML-REFERENCE-003` | `sales_order.customer` | `merchant.xml:889` | Reference 'customer' in 'sales_order' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `sales_order.merchant` | `merchant.xml:896` | Reference 'merchant' in 'sales_order' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `sales_order.quotation` | `merchant.xml:890` | Reference 'quotation' in 'sales_order' successfully resolves to target object 'quotation'. |
| `KSML-REFERENCE-003` | `sales_order.sales_rep` | `merchant.xml:891` | Reference 'sales_rep' in 'sales_order' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `sales_order.status` | `merchant.xml:895` | Reference 'status' in 'sales_order' successfully resolves to target object 'sales_order_status'. |
| `KSML-REFERENCE-003` | `account_chart.account_type` | `merchant.xml:907` | Reference 'account_type' in 'account_chart' successfully resolves to target object 'account_type'. |
| `KSML-REFERENCE-003` | `account_chart.merchant` | `merchant.xml:909` | Reference 'merchant' in 'account_chart' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `journal_entry.merchant` | `merchant.xml:922` | Reference 'merchant' in 'journal_entry' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `journal_entry.posted_by` | `merchant.xml:921` | Reference 'posted_by' in 'journal_entry' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `journal_entry.status` | `merchant.xml:920` | Reference 'status' in 'journal_entry' successfully resolves to target object 'journal_status'. |
| `KSML-REFERENCE-003` | `ledger_transaction.account` | `merchant.xml:931` | Reference 'account' in 'ledger_transaction' successfully resolves to target object 'account_chart'. |
| `KSML-REFERENCE-003` | `ledger_transaction.journal_entry` | `merchant.xml:930` | Reference 'journal_entry' in 'ledger_transaction' successfully resolves to target object 'journal_entry'. |
| `KSML-REFERENCE-003` | `ledger_transaction.merchant` | `merchant.xml:934` | Reference 'merchant' in 'ledger_transaction' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `payment.customer` | `merchant.xml:942` | Reference 'customer' in 'payment' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `payment.merchant` | `merchant.xml:948` | Reference 'merchant' in 'payment' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `payment.payment_method` | `merchant.xml:946` | Reference 'payment_method' in 'payment' successfully resolves to target object 'payment_method'. |
| `KSML-REFERENCE-003` | `payment.status` | `merchant.xml:947` | Reference 'status' in 'payment' successfully resolves to target object 'payment_status'. |
| `KSML-REFERENCE-003` | `invoice.customer` | `merchant.xml:956` | Reference 'customer' in 'invoice' successfully resolves to target object 'customer'. |
| `KSML-REFERENCE-003` | `invoice.merchant` | `merchant.xml:964` | Reference 'merchant' in 'invoice' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `invoice.sales_order` | `merchant.xml:957` | Reference 'sales_order' in 'invoice' successfully resolves to target object 'sales_order'. |
| `KSML-REFERENCE-003` | `invoice.status` | `merchant.xml:963` | Reference 'status' in 'invoice' successfully resolves to target object 'invoice_status'. |
| `KSML-REFERENCE-003` | `invoice_line_item.invoice` | `merchant.xml:973` | Reference 'invoice' in 'invoice_line_item' successfully resolves to target object 'invoice'. |
| `KSML-REFERENCE-003` | `invoice_line_item.merchant` | `merchant.xml:979` | Reference 'merchant' in 'invoice_line_item' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `invoice_line_item.product` | `merchant.xml:974` | Reference 'product' in 'invoice_line_item' successfully resolves to target object 'product'. |
| `KSML-REFERENCE-003` | `invoice_line_item.vat_rate` | `merchant.xml:978` | Reference 'vat_rate' in 'invoice_line_item' successfully resolves to target object 'vat_rate'. |
| `KSML-REFERENCE-003` | `expense_report.approved_by` | `merchant.xml:992` | Reference 'approved_by' in 'expense_report' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `expense_report.employee` | `merchant.xml:987` | Reference 'employee' in 'expense_report' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `expense_report.merchant` | `merchant.xml:993` | Reference 'merchant' in 'expense_report' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `expense_report.status` | `merchant.xml:991` | Reference 'status' in 'expense_report' successfully resolves to target object 'expense_status'. |
| `KSML-REFERENCE-003` | `expense_item.category` | `merchant.xml:1004` | Reference 'category' in 'expense_item' successfully resolves to target object 'expense_category'. |
| `KSML-REFERENCE-003` | `expense_item.expense_report` | `merchant.xml:1002` | Reference 'expense_report' in 'expense_item' successfully resolves to target object 'expense_report'. |
| `KSML-REFERENCE-003` | `expense_item.merchant` | `merchant.xml:1008` | Reference 'merchant' in 'expense_item' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `expense_item.receipt_attachment` | `merchant.xml:1007` | Reference 'receipt_attachment' in 'expense_item' successfully resolves to target object 'contract_document'. |
| `KSML-REFERENCE-003` | `vat_rate_config.merchant` | `merchant.xml:1020` | Reference 'merchant' in 'vat_rate_config' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `financial_statement.merchant` | `merchant.xml:1034` | Reference 'merchant' in 'financial_statement' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `financial_statement.prepared_by` | `merchant.xml:1033` | Reference 'prepared_by' in 'financial_statement' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `financial_statement.statement_type` | `merchant.xml:1028` | Reference 'statement_type' in 'financial_statement' successfully resolves to target object 'statement_type'. |
| `KSML-REFERENCE-003` | `financial_statement.status` | `merchant.xml:1032` | Reference 'status' in 'financial_statement' successfully resolves to target object 'statement_status'. |
| `KSML-REFERENCE-003` | `budget.budget_category` | `merchant.xml:1045` | Reference 'budget_category' in 'budget' successfully resolves to target object 'budget_category'. |
| `KSML-REFERENCE-003` | `budget.department` | `merchant.xml:1042` | Reference 'department' in 'budget' successfully resolves to target object 'department'. |
| `KSML-REFERENCE-003` | `budget.merchant` | `merchant.xml:1047` | Reference 'merchant' in 'budget' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `budget.status` | `merchant.xml:1046` | Reference 'status' in 'budget' successfully resolves to target object 'budget_status'. |
| `KSML-REFERENCE-003` | `bank_account.currency` | `merchant.xml:1059` | Reference 'currency' in 'bank_account' successfully resolves to target object 'currency_type'. |
| `KSML-REFERENCE-003` | `bank_account.merchant` | `merchant.xml:1061` | Reference 'merchant' in 'bank_account' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `asset_category.depreciation_method` | `merchant.xml:1070` | Reference 'depreciation_method' in 'asset_category' successfully resolves to target object 'depreciation_method'. |
| `KSML-REFERENCE-003` | `asset_category.merchant` | `merchant.xml:1072` | Reference 'merchant' in 'asset_category' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `asset.asset_category` | `merchant.xml:1082` | Reference 'asset_category' in 'asset' successfully resolves to target object 'asset_category'. |
| `KSML-REFERENCE-003` | `asset.assigned_location` | `merchant.xml:1086` | Reference 'assigned_location' in 'asset' successfully resolves to target object 'address'. |
| `KSML-REFERENCE-003` | `asset.merchant` | `merchant.xml:1088` | Reference 'merchant' in 'asset' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `asset.responsible_employee` | `merchant.xml:1087` | Reference 'responsible_employee' in 'asset' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `equipment.asset` | `merchant.xml:1097` | Reference 'asset' in 'equipment' successfully resolves to target object 'asset'. |
| `KSML-REFERENCE-003` | `equipment.merchant` | `merchant.xml:1101` | Reference 'merchant' in 'equipment' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `vehicle.asset` | `merchant.xml:1109` | Reference 'asset' in 'vehicle' successfully resolves to target object 'asset'. |
| `KSML-REFERENCE-003` | `vehicle.merchant` | `merchant.xml:1115` | Reference 'merchant' in 'vehicle' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `vehicle.vehicle_type` | `merchant.xml:1114` | Reference 'vehicle_type' in 'vehicle' successfully resolves to target object 'vehicle_type'. |
| `KSML-REFERENCE-003` | `consumable.merchant` | `merchant.xml:1128` | Reference 'merchant' in 'consumable' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `consumable.unit_of_measure` | `merchant.xml:1126` | Reference 'unit_of_measure' in 'consumable' successfully resolves to target object 'unit_of_measure'. |
| `KSML-REFERENCE-003` | `consumable_stock.consumable` | `merchant.xml:1136` | Reference 'consumable' in 'consumable_stock' successfully resolves to target object 'consumable'. |
| `KSML-REFERENCE-003` | `consumable_stock.merchant` | `merchant.xml:1140` | Reference 'merchant' in 'consumable_stock' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `consumable_stock.warehouse` | `merchant.xml:1137` | Reference 'warehouse' in 'consumable_stock' successfully resolves to target object 'warehouse'. |
| `KSML-REFERENCE-003` | `maintenance_schedule.asset` | `merchant.xml:1149` | Reference 'asset' in 'maintenance_schedule' successfully resolves to target object 'asset'. |
| `KSML-REFERENCE-003` | `maintenance_schedule.merchant` | `merchant.xml:1155` | Reference 'merchant' in 'maintenance_schedule' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `maintenance_schedule.responsible_employee` | `merchant.xml:1153` | Reference 'responsible_employee' in 'maintenance_schedule' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `maintenance_schedule.schedule_type` | `merchant.xml:1150` | Reference 'schedule_type' in 'maintenance_schedule' successfully resolves to target object 'maintenance_type'. |
| `KSML-REFERENCE-003` | `maintenance_schedule.status` | `merchant.xml:1154` | Reference 'status' in 'maintenance_schedule' successfully resolves to target object 'maintenance_status'. |
| `KSML-REFERENCE-003` | `maintenance_log.asset` | `merchant.xml:1163` | Reference 'asset' in 'maintenance_log' successfully resolves to target object 'asset'. |
| `KSML-REFERENCE-003` | `maintenance_log.maintenance_type` | `merchant.xml:1165` | Reference 'maintenance_type' in 'maintenance_log' successfully resolves to target object 'maintenance_type'. |
| `KSML-REFERENCE-003` | `maintenance_log.merchant` | `merchant.xml:1169` | Reference 'merchant' in 'maintenance_log' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `maintenance_log.performed_by` | `merchant.xml:1167` | Reference 'performed_by' in 'maintenance_log' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `depreciation_record.asset` | `merchant.xml:1177` | Reference 'asset' in 'depreciation_record' successfully resolves to target object 'asset'. |
| `KSML-REFERENCE-003` | `depreciation_record.merchant` | `merchant.xml:1182` | Reference 'merchant' in 'depreciation_record' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `insurance_policy.insured_asset` | `merchant.xml:1192` | Reference 'insured_asset' in 'insurance_policy' successfully resolves to target object 'asset'. |
| `KSML-REFERENCE-003` | `insurance_policy.insured_entity` | `merchant.xml:1193` | Reference 'insured_entity' in 'insurance_policy' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `insurance_policy.merchant` | `merchant.xml:1197` | Reference 'merchant' in 'insurance_policy' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `insurance_policy.policy_type` | `merchant.xml:1191` | Reference 'policy_type' in 'insurance_policy' successfully resolves to target object 'policy_type'. |
| `KSML-REFERENCE-003` | `compliance_document.document_type` | `merchant.xml:1206` | Reference 'document_type' in 'compliance_document' successfully resolves to target object 'compliance_type'. |
| `KSML-REFERENCE-003` | `compliance_document.merchant` | `merchant.xml:1211` | Reference 'merchant' in 'compliance_document' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `compliance_document.uploaded_by` | `merchant.xml:1210` | Reference 'uploaded_by' in 'compliance_document' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `audit_log.action_type` | `merchant.xml:1221` | Reference 'action_type' in 'audit_log' successfully resolves to target object 'action_type'. |
| `KSML-REFERENCE-003` | `audit_log.merchant` | `merchant.xml:1226` | Reference 'merchant' in 'audit_log' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `audit_log.user` | `merchant.xml:1220` | Reference 'user' in 'audit_log' successfully resolves to target object 'user_account'. |
| `KSML-REFERENCE-003` | `version_history.changed_by` | `merchant.xml:1240` | Reference 'changed_by' in 'version_history' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `version_history.merchant` | `merchant.xml:1241` | Reference 'merchant' in 'version_history' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `deleted_record.deleted_by` | `merchant.xml:1252` | Reference 'deleted_by' in 'deleted_record' successfully resolves to target object 'employee'. |
| `KSML-REFERENCE-003` | `deleted_record.merchant` | `merchant.xml:1253` | Reference 'merchant' in 'deleted_record' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `notification_template.channel` | `merchant.xml:1262` | Reference 'channel' in 'notification_template' successfully resolves to target object 'notification_channel'. |
| `KSML-REFERENCE-003` | `notification_template.merchant` | `merchant.xml:1265` | Reference 'merchant' in 'notification_template' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `system_automation_hook.merchant` | `merchant.xml:1277` | Reference 'merchant' in 'system_automation_hook' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `external_integration.authentication_method` | `merchant.xml:1287` | Reference 'authentication_method' in 'external_integration' successfully resolves to target object 'auth_method_type'. |
| `KSML-REFERENCE-003` | `external_integration.merchant` | `merchant.xml:1289` | Reference 'merchant' in 'external_integration' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `gender_type.merchant` | `merchant.xml:1300` | Reference 'merchant' in 'gender_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `shipment_status_type.merchant` | `merchant.xml:1316` | Reference 'merchant' in 'shipment_status_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `event_type.merchant` | `merchant.xml:1334` | Reference 'merchant' in 'event_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `movement_type.merchant` | `merchant.xml:1351` | Reference 'merchant' in 'movement_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `vehicle_type.merchant` | `merchant.xml:1368` | Reference 'merchant' in 'vehicle_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `service_status_type.merchant` | `merchant.xml:1384` | Reference 'merchant' in 'service_status_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `team_member_role.merchant` | `merchant.xml:1401` | Reference 'merchant' in 'team_member_role' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `work_order_status.merchant` | `merchant.xml:1417` | Reference 'merchant' in 'work_order_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `priority_type.merchant` | `merchant.xml:1433` | Reference 'merchant' in 'priority_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `task_status.merchant` | `merchant.xml:1449` | Reference 'merchant' in 'task_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `salary_grade.merchant` | `merchant.xml:1465` | Reference 'merchant' in 'salary_grade' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `employment_type.merchant` | `merchant.xml:1481` | Reference 'merchant' in 'employment_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `employment_status.merchant` | `merchant.xml:1497` | Reference 'merchant' in 'employment_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `timesheet_status.merchant` | `merchant.xml:1512` | Reference 'merchant' in 'timesheet_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `payroll_status.merchant` | `merchant.xml:1528` | Reference 'merchant' in 'payroll_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `payroll_item_type.merchant` | `merchant.xml:1544` | Reference 'merchant' in 'payroll_item_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `rule_type.merchant` | `merchant.xml:1560` | Reference 'merchant' in 'rule_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `bonus_status.merchant` | `merchant.xml:1575` | Reference 'merchant' in 'bonus_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `leave_type.merchant` | `merchant.xml:1590` | Reference 'merchant' in 'leave_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `leave_status.merchant` | `merchant.xml:1606` | Reference 'merchant' in 'leave_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `training_status.merchant` | `merchant.xml:1622` | Reference 'merchant' in 'training_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `customer_type.merchant` | `merchant.xml:1638` | Reference 'merchant' in 'customer_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `industry_type.merchant` | `merchant.xml:1653` | Reference 'merchant' in 'industry_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `payment_method.merchant` | `merchant.xml:1669` | Reference 'merchant' in 'payment_method' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `billing_cycle.merchant` | `merchant.xml:1685` | Reference 'merchant' in 'billing_cycle' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `history_event_type.merchant` | `merchant.xml:1701` | Reference 'merchant' in 'history_event_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `contract_type.merchant` | `merchant.xml:1717` | Reference 'merchant' in 'contract_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `contract_status.merchant` | `merchant.xml:1732` | Reference 'merchant' in 'contract_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `document_type.merchant` | `merchant.xml:1748` | Reference 'merchant' in 'document_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `ticket_status.merchant` | `merchant.xml:1764` | Reference 'merchant' in 'ticket_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `unit_of_measure.merchant` | `merchant.xml:1780` | Reference 'merchant' in 'unit_of_measure' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `currency_type.merchant` | `merchant.xml:1797` | Reference 'merchant' in 'currency_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `target_audience_type.merchant` | `merchant.xml:1813` | Reference 'merchant' in 'target_audience_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `discount_type.merchant` | `merchant.xml:1828` | Reference 'merchant' in 'discount_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `lead_source.merchant` | `merchant.xml:1844` | Reference 'merchant' in 'lead_source' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `lead_status.merchant` | `merchant.xml:1860` | Reference 'merchant' in 'lead_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `lead_activity_type.merchant` | `merchant.xml:1877` | Reference 'merchant' in 'lead_activity_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `quotation_status.merchant` | `merchant.xml:1893` | Reference 'merchant' in 'quotation_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `sales_order_status.merchant` | `merchant.xml:1910` | Reference 'merchant' in 'sales_order_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `account_type.merchant` | `merchant.xml:1926` | Reference 'merchant' in 'account_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `journal_status.merchant` | `merchant.xml:1943` | Reference 'merchant' in 'journal_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `payment_status.merchant` | `merchant.xml:1958` | Reference 'merchant' in 'payment_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `invoice_status.merchant` | `merchant.xml:1974` | Reference 'merchant' in 'invoice_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `vat_rate.merchant` | `merchant.xml:1991` | Reference 'merchant' in 'vat_rate' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `expense_status.merchant` | `merchant.xml:2008` | Reference 'merchant' in 'expense_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `expense_category.merchant` | `merchant.xml:2025` | Reference 'merchant' in 'expense_category' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `statement_type.merchant` | `merchant.xml:2041` | Reference 'merchant' in 'statement_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `statement_status.merchant` | `merchant.xml:2057` | Reference 'merchant' in 'statement_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `budget_category.merchant` | `merchant.xml:2073` | Reference 'merchant' in 'budget_category' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `budget_status.merchant` | `merchant.xml:2089` | Reference 'merchant' in 'budget_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `depreciation_method.merchant` | `merchant.xml:2105` | Reference 'merchant' in 'depreciation_method' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `maintenance_type.merchant` | `merchant.xml:2120` | Reference 'merchant' in 'maintenance_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `maintenance_status.merchant` | `merchant.xml:2136` | Reference 'merchant' in 'maintenance_status' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `policy_type.merchant` | `merchant.xml:2152` | Reference 'merchant' in 'policy_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `compliance_type.merchant` | `merchant.xml:2168` | Reference 'merchant' in 'compliance_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `action_type.merchant` | `merchant.xml:2184` | Reference 'merchant' in 'action_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `notification_channel.merchant` | `merchant.xml:2201` | Reference 'merchant' in 'notification_channel' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `auth_method_type.merchant` | `merchant.xml:2217` | Reference 'merchant' in 'auth_method_type' successfully resolves to target object 'merchant'. |
| `KSML-REFERENCE-003` | `customer_status.merchant` | `merchant.xml:2233` | Reference 'merchant' in 'customer_status' successfully resolves to target object 'merchant'. |
| `KSML-DOMAIN-ROOT-003` | `` | `merchant.xml:2` | Exactly one domain root candidate 'platform' was found. |
| `KSML-STATE-001` | `shipment.status` | `merchant.xml:144` | Object 'shipment' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `service_appointment.status` | `merchant.xml:280` | Object 'service_appointment' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `work_order.status` | `merchant.xml:331` | Object 'work_order' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `task.status` | `merchant.xml:347` | Object 'task' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `employment_record.status` | `merchant.xml:385` | Object 'employment_record' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `timesheet.status` | `merchant.xml:417` | Object 'timesheet' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `payroll_calculation.status` | `merchant.xml:431` | Object 'payroll_calculation' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `employee_bonus.status` | `merchant.xml:470` | Object 'employee_bonus' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `leave_request.status` | `merchant.xml:483` | Object 'leave_request' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `employee_training_enrollment.completion_status` | `merchant.xml:526` | Object 'employee_training_enrollment' is an Aggregate Root candidate with primary state field 'completion_status'. |
| `KSML-STATE-001` | `customer.status` | `merchant.xml:538` | Object 'customer' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `service_contract.status` | `merchant.xml:608` | Object 'service_contract' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `support_ticket.status` | `merchant.xml:638` | Object 'support_ticket' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `lead.status` | `merchant.xml:814` | Object 'lead' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `quotation.status` | `merchant.xml:855` | Object 'quotation' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `sales_order.status` | `merchant.xml:884` | Object 'sales_order' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `journal_entry.status` | `merchant.xml:913` | Object 'journal_entry' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `payment.status` | `merchant.xml:938` | Object 'payment' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `invoice.status` | `merchant.xml:952` | Object 'invoice' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `expense_report.status` | `merchant.xml:983` | Object 'expense_report' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `financial_statement.status` | `merchant.xml:1024` | Object 'financial_statement' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `budget.status` | `merchant.xml:1038` | Object 'budget' is an Aggregate Root candidate with primary state field 'status'. |
| `KSML-STATE-001` | `maintenance_schedule.status` | `merchant.xml:1145` | Object 'maintenance_schedule' is an Aggregate Root candidate with primary state field 'status'. |