# Business Logic — KKW02510SFLogic.setInitsrv() [45 LOC]

| Field | Value |
|-------|-------|
| Fully Qualified Name | `eo.web.webview.KKW02510SF.KKW02510SFLogic` |
| Layer | Controller / WebView Logic (Web presentation layer — Java class in `eo.web.webview.KKW02510SF`) |
| Module | `KKW02510SF` (Package: `eo.web.webview.KKW02510SF`) |

## 1. Role

### KKW02510SFLogic.setInitsrv()

This method performs **pre-initialization data setup** (初期表示サービス呼出し前Data設定処理) for a customer contract information inquiry and update screen (KKW02510SF) in K-Opticom's telecom service management system. It prepares the DataBean with operational metadata — such as the current operation date, date-time stamp, and return message ID — before delegating to a series of service-component mappers that fetch and populate screen display data.

The method acts as a **shared initialization utility** called by two entry-point action methods on the same class: `actionClear()` (clear/reset flow) and `actionInit()` (initial display flow). It implements a **routing/dispatch pattern** based on the transaction division code (処理区分 — TRAN_DIV) retrieved from the DataBean. Four transaction divisions are supported: "00" (照会/Initial View), "03" (変更/Change), "05" (回復/Recovery), and "06" (予約取消/Reservation Cancel). Each division triggers different flag configurations that control whether the screen permits updates, requires password re-initialization, or suppresses change/cancellation operations.

After setting conditional flags, the method instantiates `KKSV0071_KKSV0071OPDBMapper` and delegates to six sequential service-component methods (`setKKSV007101SC` through `setKKSV007106SC`), each called with a specific function code (`FUNC_CD_1` or `FUNC_CD_2`). These mappers are responsible for reading customer contract and service data that the screen will display. The method plays the role of a **coordinator**: it does not perform business logic itself but orchestrates data preparation and service delegation, ensuring the screen's DataBean is fully initialized before rendering.

## 2. Processing Pattern (Detailed Business Logic)

```mermaid
flowchart TD
    START(["setInitsrv params"])
    A["getOpeDate from JCCWebCommon"] --> B["Set UNYO_YMD to paramBean[0]"]
    B --> C["getOpeDateTimeStamp from JCCWebCommon"]
    C --> D["Set UNYO_DTM to paramBean[0]"]
    D --> E["Set RTN_MSG_ID to empty string in paramBean[0]"]
    E --> F["Get TRAN_DIV from paramBean[0]"]
    F --> COND{trans_div == OP_TRAN_DIV_CHGE = 03 Change}
    COND -->|Yes| G1["Set UPD_MODE_FLG = true"]
    G1 --> H1["Set PWD_INIT_FLG = false"]
    H1 --> MAPPING["KKSV0071 Mapper Initialization"]
    COND -->|No| COND2{trans_div == OP_TRAN_DIV_SHOKAI = 00 InitialView}
    COND2 -->|Yes| G2["Set NON_UPD_DSL_FLG = true"]
    G2 --> MAPPING
    COND2 -->|No| COND3{trans_div == OP_TRAN_DIV_KAIHK = 05 Recovery OR OP_TRAN_DIV_RSV_CL = 06 ReservationCancel}
    COND3 -->|Yes| G3["Set KAIHK_CNSL_FLG = true"]
    G3 --> MAPPING
    COND3 -->|No| MAPPING
    MAPPING --> S1["setKKSV007101SC FUNC_CD_2"]
    S1 --> S2["setKKSV007102SC FUNC_CD_1"]
    S2 --> S3["setKKSV007103SC FUNC_CD_2"]
    S3 --> S4["setKKSV007104SC FUNC_CD_2"]
    S4 --> S5["setKKSV007105SC FUNC_CD_1"]
    S5 --> S6["setKKSV007106SC FUNC_CD_1"]
    S6 --> END(["Return Next"])
```

**Processing Flow:**

1. **Retrieve and set operation date** (運用年月日): Calls `JCCWebCommon.getOpeDate(this, null)` to obtain the current operational date (based on the system's configured business date, which may differ from the actual calendar date). Sets it into `paramBean[0]` under the key `UNYO_YMD` ("運用年月日").

2. **Retrieve and set operation date-time stamp**: Calls `JCCWebCommon.getOpeDateTimeStamp(this, null)` to obtain the current operational date-time in timestamp format. Sets it into `paramBean[0]` under the key `UNYO_DTM` ("運用年月日時分秒"). A commented-out alternative using `JCCWebCommon.getSysDateTime()` exists, indicating a previous design choice between business date and system clock.

3. **Clear return message ID**: Sets the return message ID key `RTN_MSG_ID` ("返却メッセージID") to an empty string, ensuring no residual error or confirmation message from a prior operation is displayed.

4. **Read transaction division (処理区分)**: Retrieves the `TRAN_DIV` ("処理区分") value from `paramBean[0]` to determine which business mode the screen is operating in.

5. **Branch on transaction division:**
   - **"03" (変更/Change)**: Sets `UPD_MODE_FLG` ("更新表示フラグ") to `true` (enabling update-mode UI), and `PWD_INIT_FLG` ("パスワード初期化フラグ") to `false` (no password re-initialization needed).
   - **"00" (照会/Initial View)**: Sets `NON_UPD_DSL_FLG` ("変更解約不可フラグ") to `true` (disabling change and cancellation operations — read-only mode).
   - **"05" (回復/Recovery) or "06" (予約取消/Reservation Cancel)**: Sets `KAIHK_CNSL_FLG` ("回復取消表示フラグ") to `true` (enabling recovery/cancellation display flags).
   - **Any other value**: No flags are set; the screen uses default behavior.

6. **Initialize KKSV0071 mapper and call six service-component methods** (上りマッピング — upstream mapping): Creates a new `KKSV0071_KKSV0071OPDBMapper` instance and sequentially calls six SC methods, each passing the `paramBean`, `inputMap`, and a function code. These methods fetch and populate screen display data from the backend.

7. **Return**: No explicit return value (void method). Control passes to the caller (`actionClear()` or `actionInit()`).

## 3. Parameter Analysis

| No | Parameter Name | Type | Business Description |
|----|---------------|------|---------------------|
| 1 | `paramBean` | `X31SDataBeanAccess[]` | Array of DataBean accessors used to read/write screen data. `paramBean[0]` is the primary DataBean for the KKW02510SF screen, carrying operational metadata (date, date-time stamp, return message ID) and flags (update mode, password init, non-updatable DSL, recovery/cancel). This is the bridge between the web layer and the presentation model. |
| 2 | `inputMap` | `HashMap<String, Object>` | Input data map passed to the KKSV0071 mapper service methods. Contains contextual information needed by the upstream service components to fetch screen display data (e.g., customer ID, contract reference). The Javadoc explicitly marks it as Not null. |

**Instance fields / external state read:**

| Source | Description |
|--------|-------------|
| `this` (KKW02510SFLogic instance) | Passed to `JCCWebCommon.getOpeDate()` and `JCCWebCommon.getOpeDateTimeStamp()` — used to resolve the operational date in the context of the current web session/business date configuration. |

## 4. CRUD Operations / Called Services

### Pre-computed evidence from code analysis graph:

| CRUD | SC / CBS | SC Code | Entity / DB | Operation Description |
|------|----------|---------|-------------|----------------------|
| R | `JCCWebCommon.getOpeDate` | - | - | Retrieves the current operational date (運用年月日) from the system's business date configuration. Used for date display on the screen. |
| R | `JCCWebCommon.getOpeDateTimeStamp` | - | - | Retrieves the current operational date-time stamp (運用年月日時分秒) from the system's business date configuration. Used for audit/tracking metadata. |
| - | `OneStopDataBeanAccess.sendMessageString` (for UNYO_YMD) | - | - | Sets the operation date value into the DataBean at key `UNYO_YMD` ("運用年月日"). |
| - | `OneStopDataBeanAccess.sendMessageString` (for UNYO_DTM) | - | - | Sets the operation date-time stamp value into the DataBean at key `UNYO_DTM` ("運用年月日時分秒"). |
| - | `OneStopDataBeanAccess.sendMessageString` (for RTN_MSG_ID) | - | - | Clears the return message ID by setting it to an empty string. |
| - | `OneStopDataBeanAccess.sendMessageString` (for TRAN_DIV) | - | - | Reads the transaction division (処理区分) value from the DataBean to determine the screen mode. |
| - | `OneStopDataBeanAccess.sendMessageBoolean` (for UPD_MODE_FLG) | - | - | Sets the update display flag (更新表示フラグ) to true, enabling update-mode UI elements. |
| - | `OneStopDataBeanAccess.sendMessageBoolean` (for PWD_INIT_FLG) | - | - | Sets the password initialization flag (パスワード初期化フラグ) to false when in change mode. |
| - | `OneStopDataBeanAccess.sendMessageBoolean` (for NON_UPD_DSL_FLG) | - | - | Sets the change/cancellation-inhibitable flag (変更解約不可フラグ) to true when in initial-view mode, making the screen read-only. |
| - | `OneStopDataBeanAccess.sendMessageBoolean` (for KAIHK_CNSL_FLG) | - | - | Sets the recovery/cancellation display flag (回復取消表示フラグ) to true when in recovery or reservation-cancel mode. |
| R | `KKSV0071_KKSV0071OPDBMapper.setKKSV007101SC` | - | - | Upstream mapping service call — initializes first set of screen data via KKSV0071 module. Called with `FUNC_CD_2`. |
| R | `KKSV0071_KKSV0071OPDBMapper.setKKSV007102SC` | - | - | Upstream mapping service call — initializes second set of screen data via KKSV0071 module. Called with `FUNC_CD_1`. |
| R | `KKSV0071_KKSV0071OPDBMapper.setKKSV007103SC` | - | - | Upstream mapping service call — initializes third set of screen data via KKSV0071 module. Called with `FUNC_CD_2`. |
| R | `KKSV0071_KKSV0071OPDBMapper.setKKSV007104SC` | - | - | Upstream mapping service call — initializes fourth set of screen data via KKSV0071 module. Called with `FUNC_CD_2`. |
| R | `KKSV0071_KKSV0071OPDBMapper.setKKSV007105SC` | - | - | Upstream mapping service call — initializes fifth set of screen data via KKSV0071 module. Called with `FUNC_CD_1`. |
| R | `KKSV0071_KKSV0071OPDBMapper.setKKSV007106SC` | - | - | Upstream mapping service call — initializes sixth set of screen data via KKSV0071 module. Called with `FUNC_CD_1`. |

**Classification notes:**
- All six `setKKSV0071xxSC` methods are classified as **R (Read)** because they are data-initialization/mapping methods that fetch screen display data from the backend. The naming convention `setKKSVxxxxSC` indicates a service-component-level data population method (the `set` prefix in the method name refers to "setting up screen data," not database update).
- `JCCWebCommon.getOpeDate` and `JCCWebCommon.getOpeDateTimeStamp` are **R (Read)** operations — they read the operational date from the system's business date configuration.

## 5. Dependency Trace

### Pre-computed evidence from code analysis graph:

No screen/batch entry points found within 8 hops. Direct callers found: 2 methods.
Terminal operations from this method: `getOpeDateTimeStamp` [R], `setKKSV007106SC` [-], `setKKSV007106SC` [-], `setKKSV007105SC` [-], `setKKSV007105SC` [-], `setKKSV007104SC` [-], `setKKSV007104SC` [-], `setKKSV007103SC` [-], `setKKSV007103SC` [-], `setKKSV007102SC` [-], `setKKSV007102SC` [-], `setKKSV007101SC` [-], `setKKSV007101SC` [-], `sendMessageString` [-], `sendMessageString` [-], `sendMessageString` [-], `sendMessageString` [-], `sendMessageString` [-], `sendMessageString` [-], `getOpeDateTimeStamp` [R]

| # | Caller (Screen/Batch) | Call Chain (Full Path to this Method) | Terminal (SC / CRUD / Entity) |
|---|----------------------|--------------------------------------|-------------------------------|
| 1 | Logic:KKW02510SFLogic.actionClear() | `KKW02510SFLogic.actionClear()` -> `setInitsrv` | `setKKSV007101SC` [R], `setKKSV007102SC` [R], `setKKSV007103SC` [R], `setKKSV007104SC` [R], `setKKSV007105SC` [R], `setKKSV007106SC` [R] |
| 2 | Logic:KKW02510SFLogic.actionInit() | `KKW02510SFLogic.actionInit()` -> `setInitsrv` | `setKKSV007101SC` [R], `setKKSV007102SC` [R], `setKKSV007103SC` [R], `setKKSV007104SC` [R], `setKKSV007105SC` [R], `setKKSV007106SC` [R] |

**Notes:**
- Both callers (`actionClear()` and `actionInit()`) are private methods on the same `KKW02510SFLogic` class, indicating this is an internal utility method, not a public API.
- `actionClear()` is invoked during a clear/reset operation on the screen, while `actionInit()` is invoked during the initial screen display. Both require the same pre-initialization data setup.
- The KKSV0071 module ( accessed via `KKSV0071_KKSV0071OPDBMapper`) is a shared upstream service component used across multiple screens for fetching customer contract and service data.

## 6. Per-Branch Detail Blocks

**Block 1** — [SET] `(Operation date retrieval)` (L708)

> Retrieves the operational date from the system and sets it into the DataBean. Also sets the date-time stamp and clears the return message ID.

| # | Type | Code |
|---|------|------|
| 1 | CALL | `opeDate = JCCWebCommon.getOpeDate(this, null)` // Get current operational date (運用年月日) |
| 2 | SET | `opeDate = String` // Variable holding the operational date value |
| 3 | EXEC | `paramBean[0].sendMessageString(KKW02510SFConst.UNYO_YMD, X31CWebConst.DATABEAN_SET_VALUE, opeDate)` // Set operation date into paramBean[0] at key UNYO_YMD="運用年月日" [-> KKW02510SFConst.UNYO_YMD="運用年月日"] |
| 4 | EXEC | `paramBean[0].sendMessageString(KKW02510SFConst.UNYO_DTM, X31CWebConst.DATABEAN_SET_VALUE, JCCWebCommon.getOpeDateTimeStamp(this, null))` // Set operation date-time stamp (運用年月日時分秒) into paramBean[0] [-> KKW02510SFConst.UNYO_DTM="運用年月日時分秒"] |
| 5 | SET | *(commented)* `paramBean[0].sendMessageString(KKW02510SFConst.UNYO_DTM, ..., JCCWebCommon.getSysDateTime())` // Alternate: use system clock instead of operational date — not active |
| 6 | EXEC | `paramBean[0].sendMessageString(KKW02510SFConst.RTN_MSG_ID, X31CWebConst.DATABEAN_SET_VALUE, "")` // Clear return message ID by setting to empty string [-> KKW02510SFConst.RTN_MSG_ID="返却メッセージID"] |

**Block 2** — [SET] `(Transaction division retrieval)` (L716)

> Reads the transaction division code from the DataBean to determine the screen mode.

| # | Type | Code |
|---|------|------|
| 1 | EXEC | `trans_div = paramBean[0].sendMessageString(KKW02510SFConst.TRAN_DIV, X31CWebConst.DATABEAN_GET_VALUE)` // Retrieve transaction division (処理区分) from paramBean[0] [-> KKW02510SFConst.TRAN_DIV="処理区分"] |
| 2 | SET | `trans_div = String` // Variable holding the division code (e.g., "00", "03", "05", "06") |

**Block 3** — [IF] `(trans_div == JKKCommonConst.OP_TRAN_DIV_CHGE = "03" (Change))` (L718)

> When the transaction division is "03" (変更/Change), this block enables update mode on the screen and disables password re-initialization. The user is modifying existing service data.

| # | Type | Code |
|---|------|------|
| 1 | COMMENT | `// 処理区分"更新"` // Transaction division: "Update" (Note: comment says "更新" (update), while the constant is "変更" (change) — likely the same mode with slightly different comment wording) |
| 2 | EXEC | `paramBean[0].sendMessageBoolean(KKW02510SFConst.UPD_MODE_FLG, X31CWebConst.DATABEAN_SET_VALUE, true)` // Set update display flag (更新表示フラグ) to true [-> KKW02510SFConst.UPD_MODE_FLG="更新表示フラグ"] |
| 3 | EXEC | `paramBean[0].sendMessageBoolean(KKW02510SFConst.PWD_INIT_FLG, X31CWebConst.DATABEAN_SET_VALUE, false)` // Set password initialization flag (パスワード初期化フラグ) to false [-> KKW02510SFConst.PWD_INIT_FLG="パスワード初期化フラグ"] |

**Block 4** — [ELSE-IF] `(trans_div == JKKCommonConst.OP_TRAN_DIV_SHOKAI = "00" (Initial View))` (L723)

> When the transaction division is "00" (照会/Initial View), this block sets the non-update DSL flag, making the screen read-only. The user is viewing existing data without modification capability.

| # | Type | Code |
|---|------|------|
| 1 | COMMENT | `// 処理区分"照会"` // Transaction division: "Initial View" (照会 = inquiry/view) |
| 2 | EXEC | `paramBean[0].sendMessageBoolean(KKW02510SFConst.NON_UPD_DSL_FLG, X31CWebConst.DATABEAN_SET_VALUE, true)` // Set change/cancellation-inhibitable flag (変更解約不可フラグ) to true [-> KKW02510SFConst.NON_UPD_DSL_FLG="変更解約不可フラグ"] |

**Block 5** — [ELSE-IF] `(trans_div == JKKCommonConst.OP_TRAN_DIV_KAIHK = "05" (Recovery) OR trans_div == JKKCommonConst.OP_TRAN_DIV_RSV_CL = "06" (Reservation Cancel))` (L728)

> When the transaction division is "05" (回復/Recovery) or "06" (予約取消/Reservation Cancel), this block sets the recovery/cancellation display flag. This flag likely enables UI elements related to service recovery or cancellation workflows.

| # | Type | Code |
|---|------|------|
| 1 | COMMENT | `// 処理区分"回復" or "予約取消"` // Transaction division: "Recovery" or "Reservation Cancel" |
| 2 | EXEC | `paramBean[0].sendMessageBoolean(KKW02510SFConst.KAIHK_CNSL_FLG, X31CWebConst.DATABEAN_SET_VALUE, true)` // Set recovery/cancellation display flag (回復取消表示フラグ) to true [-> KKW02510SFConst.KAIHK_CNSL_FLG="回復取消表示フラグ"] |

**Block 6** — [ELSE] `(no explicit else clause)` (L734)

> If the transaction division is none of the recognized values ("00", "03", "05", "06"), no flag is set. The screen proceeds with default behavior, which may be determined by other initialization logic or the caller.

| # | Type | Code |
|---|------|------|
| 1 | COMMENT | `// 上りマッピング` // Upstream mapping — the KKSV0071 service component methods are called regardless of which branch was taken |
| 2 | SET | `mapper = new KKSV0071_KKSV0071OPDBMapper()` // Instantiate the KKSV0071 mapper for upstream data mapping |

**Block 6.1** — [CALL SEQUENCE] `(KKSV0071 mapper method chain)` (L736–L741)

> Six sequential service-component calls that populate the screen's DataBean with customer contract and service data from the backend. Each call passes the same `paramBean` and `inputMap` but with a different function code (`FUNC_CD_1` or `FUNC_CD_2`), which likely determines the type of data to fetch (e.g., basic info vs. detailed info).

| # | Type | Code |
|---|------|------|
| 1 | CALL | `mapper.setKKSV007101SC(paramBean, inputMap, JPCModelConstant.FUNC_CD_2)` // Initialize screen data via KKSV0071 module — function code FUNC_CD_2 [-> JPCModelConstant.FUNC_CD_2] |
| 2 | CALL | `mapper.setKKSV007102SC(paramBean, inputMap, JPCModelConstant.FUNC_CD_1)` // Initialize screen data via KKSV0071 module — function code FUNC_CD_1 [-> JPCModelConstant.FUNC_CD_1] |
| 3 | CALL | `mapper.setKKSV007103SC(paramBean, inputMap, JPCModelConstant.FUNC_CD_2)` // Initialize screen data via KKSV0071 module — function code FUNC_CD_2 |
| 4 | CALL | `mapper.setKKSV007104SC(paramBean, inputMap, JPCModelConstant.FUNC_CD_2)` // Initialize screen data via KKSV0071 module — function code FUNC_CD_2 |
| 5 | CALL | `mapper.setKKSV007105SC(paramBean, inputMap, JPCModelConstant.FUNC_CD_1)` // Initialize screen data via KKSV0071 module — function code FUNC_CD_1 |
| 6 | CALL | `mapper.setKKSV007106SC(paramBean, inputMap, JPCModelConstant.FUNC_CD_1)` // Initialize screen data via KKSV0071 module — function code FUNC_CD_1 |

## 7. Glossary

| Term | Type | Business Meaning |
|------|------|------------------|
| `UNYO_YMD` | Field | Operation date (運用年月日) — the current business date used across the system. May differ from the actual calendar date if the business date is configured differently (e.g., for end-of-day batch processing). |
| `UNYO_DTM` | Field | Operation date-time stamp (運用年月日時分秒) — the full date-time value including year, month, day, hour, minute, and second. Used for audit trail and timestamp metadata. |
| `RTN_MSG_ID` | Field | Return message ID (返却メッセージID) — an identifier for messages returned to the user (e.g., success/failure notifications). Cleared during initialization to prevent stale messages from being displayed. |
| `TRAN_DIV` | Field | Transaction division (処理区分) — a classification code that determines the screen's operating mode (initial view, change, recovery, reservation cancel, etc.). Values: "00"=Initial View, "03"=Change, "05"=Recovery, "06"=Reservation Cancel. |
| `UPD_MODE_FLG` | Field | Update display flag (更新表示フラグ) — when true, enables update-mode UI elements allowing the user to modify data. Set to true in Change mode ("03"). |
| `PWD_INIT_FLG` | Field | Password initialization flag (パスワード初期化フラグ) — when true, triggers password re-initialization on the screen. Set to false in Change mode (no re-initialization needed). |
| `NON_UPD_DSL_FLG` | Field | Change/cancellation-inhibitable flag (変更解約不可フラグ) — when true, disables change and cancellation operations, making the screen read-only. Set to true in Initial View mode ("00"). |
| `KAIHK_CNSL_FLG` | Field | Recovery/cancellation display flag (回復取消表示フラグ) — when true, enables UI elements for recovery and cancellation workflows. Set to true in Recovery ("05") and Reservation Cancel ("06") modes. |
| `CUST_KEI_HKTGI_LIST` | Field | Customer contract continuation list (顧客契約引継リスト) — reference to a list of customer contracts being continued/ported. |
| `OP_TRAN_DIV_CHGE` | Constant | Transaction division code "03" — 変更 (Change/Modify). Indicates the user is modifying existing service data. |
| `OP_TRAN_DIV_SHOKAI` | Constant | Transaction division code "00" — 照会 (Inquiry/Initial View). Indicates the user is viewing data in read-only mode. |
| `OP_TRAN_DIV_KAIHK` | Constant | Transaction division code "05" — 回復 (Recovery). Indicates a service recovery operation. |
| `OP_TRAN_DIV_RSV_CL` | Constant | Transaction division code "06" — 予約取消 (Reservation Cancel). Indicates a reservation cancellation operation. |
| `FUNC_CD_1` | Constant | Function code 1 — passed to KKSV0071 mapper methods. Likely represents a standard data retrieval mode. |
| `FUNC_CD_2` | Constant | Function code 2 — passed to KKSV0071 mapper methods. Likely represents an extended or detailed data retrieval mode. |
| `X31SDataBeanAccess` | Class | DataBean accessor class — the interface for reading/writing screen data in the K-Opticom web framework. Methods like `sendMessageString` and `sendMessageBoolean` are used to manipulate DataBean values. |
| `KKSV0071_KKSV0071OPDBMapper` | Class | Database mapper for the KKSV0071 service component module. Provides six service methods (`setKKSV007101SC` through `setKKSV007106SC`) that populate screen data from the backend. |
| KKSV0071 | Module | A shared service component module (likely related to customer contract/service information display) used across multiple screens for data initialization. |
| KKW02510SF | Module | The screen module being documented. A customer contract information inquiry/update screen in the K-Opticom telecom service management system. |
| JCCWebCommon | Class | A common utility class in the web layer providing methods for operational date handling (`getOpeDate`, `getOpeDateTimeStamp`) and other web-wide shared functionality. |
| JKKCommonConst | Class | A shared constants class containing transaction division codes and other common configuration values used across the web application. |
| KKW02510SFConst | Class | Screen-specific constants class defining keys for the DataBean (e.g., `UNYO_YMD`, `TRAN_DIV`, `UPD_MODE_FLG`). |
| FTTH | Business term | Fiber To The Home — a fiber-optic broadband internet service offered by K-Opticom. |
| 照会 (Shokai) | Japanese term | Inquiry/Initial View mode — the user is viewing existing service data without modification capability. |
| 変更 (Henkou) | Japanese term | Change/Modify mode — the user is modifying existing service data. |
| 回復 (Kaihou) | Japanese term | Recovery mode — a service recovery operation is being performed. |
| 予約取消 (Yoyaku Torikeshi) | Japanese term | Reservation Cancel mode — an existing reservation is being cancelled. |
| 更新 (Koushin) | Japanese term | Update — refers to the update operation mode. Appears in a Japanese comment within the source code. |
| 初期表示 (Shoki Hyouji) | Japanese term | Initial display — the first-time screen rendering before any user interaction. |