Overview
This reference documents the structure of the SYSNOW data table 9outbu_sysnow_service_cases. It is intended to help administrators understand the fields stored by the related application/module. This article describes schema only and does not expose customer or operational record values.
How this table is used
The owning module reads and writes records in this table according to its workflow, permissions, and validation rules. Use the module interface for normal data entry; do not edit production rows directly unless following an approved maintenance procedure.
Field-by-field reference
The following fields were discovered from the database schema. “Significance” is an inferred guide based on the field name and type; verify business rules with the owning module before changing data.
| Field | Data type | Required / key | Significance |
|---|---|---|---|
id |
Number / Boolean bigint unsigned |
Required by schema; key: PRI | Unique identifier used to distinguish this record from other records. |
case_number |
Text / Choice varchar(30) |
Required by schema; key: UNI | Text value used to store this attribute for display, search, or application processing. Confirm the exact business meaning with the owning module. |
module_type |
Text / Choice varchar(30) |
Required by schema; key: MUL | Classification that determines the record kind or behaviour. |
title |
Text / Choice varchar(255) |
Required by schema | Human-readable title shown to users and used to identify the record. |
description |
Text / Choice longtext |
Required by schema | Detailed explanation of the item, its purpose, or the issue being recorded. |
category |
Text / Choice varchar(100) |
Required by schema | Classification used to group, filter, and report on related records. |
account_name |
Text / Choice varchar(190) |
Required by schema | Primary display name used to identify this item in lists and searches. |
contact_name |
Text / Choice varchar(190) |
Required by schema | Primary display name used to identify this item in lists and searches. |
contact_email |
Text / Choice varchar(190) |
Required by schema | Email address used for contact, notifications, or account identification. |
case_type |
Text / Choice varchar(60) |
Required by schema | Classification that determines the record kind or behaviour. |
channel |
Text / Choice varchar(60) |
Required by schema | Text value used to store this attribute for display, search, or application processing. Confirm the exact business meaning with the owning module. |
service_name |
Text / Choice varchar(190) |
Required by schema | Primary display name used to identify this item in lists and searches. |
customer_reference |
Text / Choice varchar(190) |
Required by schema | Text value used to store this attribute for display, search, or application processing. Confirm the exact business meaning with the owning module. |
resolution_notes |
Text / Choice longtext |
Required by schema | Additional context, observations, or handling details. |
priority |
Text / Choice varchar(30) |
Required by schema | Urgency or business importance used to help order work. |
status |
Text / Choice varchar(40) |
Required by schema; key: MUL | Current state of the record; commonly used to track progress or availability. |
assigned_to |
Number / Boolean bigint unsigned |
Required by schema | Person or team responsible for handling this record. |
created_by |
Number / Boolean bigint unsigned |
Required by schema; key: MUL | User or process that originally created the record. |
created_at |
Date / Time datetime |
Required by schema | Timestamp showing when the record was created. |
updated_at |
Date / Time datetime |
Required by schema | Timestamp showing when the record was last updated. |
sys_id |
Text / Choice char(32) |
Optional by schema | Unique identifier used to distinguish this record from other records. |
updated_by |
Number / Boolean bigint unsigned |
Required by schema | User or process that most recently updated the record. |
Access and safety
Restrict schema and database maintenance to authorized administrators. Back up the database before structural changes. Inferred field meanings are guidance, not a substitute for module source code or business-process documentation.