apex

分类: 测试与安全 | 上传者: avhrst | 下载: 0 | 版本: v1.0（最新）

通过 SQLcl CLI (Bash) 导出/修补/导入 Oracle APEX 组件。涵盖页面、区域、项目、按钮、流程、DA、验证、LOV、身份验证方案、模板、IR、IG、图表、地图、卡片和所有共享组件。

更新日志: Source: GitHub https://github.com/avhrst/apex-component-modifier

目录结构

当前层级: tree/main/.claude/skills/apex/

📁 app-patterns/
- 📄 .gitkeep 0 B
📁 evals/
- 📄 evals.json 1.1 KB
📁 global-patterns/
- 📄 .gitkeep 0 B
- 📄 authorization.md 9.4 KB
- 📄 automation.md 7.1 KB
- 📄 card_actions.md 4.2 KB
- 📄 card_component.md 5.5 KB
- 📄 card_icons.md 2.8 KB
- 📄 card_media.md 4.8 KB
- 📄 cards_region.md 4.9 KB
- 📄 classic_report.md 15.2 KB
- 📄 dynamic_actions.md 22.2 KB
- 📄 faceted_search.md 14.1 KB
- 📄 form_region.md 23.3 KB
- 📄 interactive_grid.md 25.4 KB
- 📄 interactive_report.md 28.5 KB
- 📄 jet_chart.md 26.9 KB
- 📄 lov.md 7.5 KB
- 📄 map_region.md 18.3 KB
- 📄 navigation.md 14.9 KB
- 📄 page_branch.md 7.6 KB
- 📄 page_computation.md 10.0 KB
- 📄 page_process.md 23.4 KB
- 📄 page_validation.md 12.5 KB
- 📄 web_source.md 15.6 KB
📁 references/
- 📁 apex_imp/
  - 📄 apex_imp.md 7.0 KB
  - 📄 app_install.md 2.6 KB
  - 📄 export_api.md 2.3 KB
  - 📄 imp_page.md 65.3 KB
  - 📄 imp_shared.md 44.7 KB
  - 📄 README.md 2.2 KB
  - 📄 valid_values.md 10.9 KB
- 📁 examples/
  - 📄 add_select_list_item.md 2.3 KB
📁 templates/
- 📄 patch_plan.md 799 B
- 📄 validation_checklist.md 2.1 KB
📁 tools/
- 📄 normalize_export_paths.md 2.2 KB
- 📄 patching_guidelines.md 3.4 KB
- 📄 validate_export.sh 3.1 KB
📄 SKILL.md 12.3 KB

SKILL.md

---
name: apex
description: Export/patch/import Oracle APEX components via SQLcl CLI (Bash). Covers pages, regions, items, buttons, processes, DAs, validations, LOVs, auth schemes, templates, IR, IG, charts, maps, cards, and all shared components.
argument-hint: "[conn|env] [app-id] [component] -- <change request>"
disable-model-invocation: false
---

# Oracle APEX Component Modifier (SQLcl CLI)

Export -> patch -> import APEX components via SQLcl CLI (Bash tool). Real side effects (DB + APEX).

## Settings

Env vars in `.claude/settings.json` (override in `.claude/settings.local.json`):
`SQLCL_CONNECTION`, `APEX_APP_ID`, `APEX_WORKSPACE` -- see CLAUDE.md.

## Inputs

- `$0`: connection alias (fallback: `$SQLCL_CONNECTION`)
- `$1`: app-id (fallback: `$APEX_APP_ID`)
- `$2`: component selector -- `PAGE:10`, `LOV:<id>`, `REGION:<id>`, or free-form
- Remaining args: change request

If inputs incomplete after defaults, resolve via `apex list` or APEX views.

## Preconditions

- `sql` CLI available on PATH (SQLcl 25.2.0+, Java 17+)
- Saved connection in `~/.dbtools` matching `$SQLCL_CONNECTION`
- `references/apex_imp/` docs present
- Filesystem write access

## SQLcl CLI Usage

All database and APEX operations use the `sql` CLI via the **Bash tool**. Do NOT use SQLcl MCP tools.

**Pattern — run SQL or SQLcl commands:**
```bash
sql -S -name $SQLCL_CONNECTION <<'EOF'
<commands here>
exit;
EOF
```

- `-S` = silent mode (suppresses banner)
- `-name` = required flag for saved connections (e.g. `-name ai`, `-name DEV`)
- Always end with `exit;` to ensure the process terminates
- Use heredoc (`<<'EOF'`) to pass multi-line commands
- For single commands: `sql -S -name $SQLCL_CONNECTION <<< "SELECT 1 FROM dual; exit;"`

---

## Change Tiers

Classify the request **before loading any references**. This determines which docs to read and how many workflow steps to execute.

| Tier | When | Examples | Docs to load |
|------|------|----------|--------------|
| **T1 — Modify** | Change parameter(s) on existing component(s) | Rename label, change item type, update SQL source, toggle condition | Export file only. `valid_values.md` only if setting an enumerated type value. |
| **T2 — Add/Remove** | Add or remove a component within an existing page or shared component file | Add item, add DA, add button, remove process, add region | `imp_page.md` or `imp_shared.md` (relevant section only) + matching `global-patterns/` file + `valid_values.md` |
| **T3 — Complex** | Multi-file changes, new shared components, cross-component wiring | Add IR with columns + saved report, add LOV + select list + DA, add form page | `references/apex_imp/README.md` for orientation, then specific files as needed per sub-task. Each sub-task follows T1 or T2 rules. |

When unsure, start at T1 — escalate only if the export file doesn't contain enough info.

---

## Workflow

### 1) Setup
Confirm `sql` CLI is available (`sql -V`). Create timestamped working folder. If git repo: branch + baseline commit.

### 2) Identify & Export
Normalize selector (e.g., "page 10" -> `PAGE:10`). For named shared components, use `apex list` to resolve IDs.
```bash
sql -S -name $SQLCL_CONNECTION <<'EOF'
apex export -applicationid <APP_ID> -split -dir <workdir> -expComponents "<...>"
exit;
EOF
```
**Note:** Export creates `<workdir>/f<APP_ID>/application/...` — the `f<APP_ID>` subdirectory is auto-created. So `-dir apex-export` produces `apex-export/f129/application/...`.

Confirm `install_component.sql` (partial) or `install.sql` (full) or `install_page.sql` (page export) exists.

### 3) Read export file, classify tier
Read the exported file(s). Classify the change per the tier table above. Then load only the docs that tier requires.

**Reference loading decision tree:**

```
Is this a parameter change on an existing component?
├─ YES (T1): Do you know the valid value?
│   ├─ YES: No docs needed — patch directly
│   └─ NO: Read `valid_values.md` for the relevant section only
└─ NO: Are you adding/removing a component?
    ├─ YES (T2): What component type?
    │   ├─ Page component → Read relevant section of `imp_page.md` + matching `global-patterns/` file
    │   └─ Shared component → Read relevant section of `imp_shared.md` + matching `global-patterns/` file
    └─ NO (T3): Multiple sub-tasks → Read `references/apex_imp/README.md`, then apply T1/T2 per sub-task
```

**Global pattern file lookup** (T2/T3 only — load the ONE file matching the component):

| Component type | Pattern file |
|---|---|
| Interactive Report | `interactive_report.md` |
| Interactive Grid | `interactive_grid.md` |
| Form region | `form_region.md` |
| Classic Report | `classic_report.md` |
| Cards region | `cards_region.md` (+ `card_component.md`, `card_media.md`, `card_actions.md`, `card_icons.md` as needed) |
| JET Chart | `jet_chart.md` |
| Map region | `map_region.md` |
| Dynamic Action | `dynamic_actions.md` |
| Faceted Search | `faceted_search.md` |
| Process | `page_process.md` |
| Validation | `page_validation.md` |
| Computation | `page_computation.md` |
| Branch | `page_branch.md` |
| Navigation | `navigation.md` |
| LOV | `lov.md` |
| Authorization | `authorization.md` |
| Web Source | `web_source.md` |
| Automation | `automation.md` |

Also check: `app-patterns/catalog.md` + `conventions.md` — if present, load to match app-specific template IDs, naming, and conventions.

### 4) Plan (T2/T3 only)
For T1, skip planning — go straight to patching. For T2/T3: split into DB changes (DDL/DML/PLSQL) and APEX patches. Order: DB first -> patch export -> import.

**Incremental import strategy (T2/T3 — REQUIRED):**

Because `set_environment.sql` uses `whenever sqlerror exit rollback`, **any single error rolls back the entire import**. Do NOT patch all components into one file and import once. Instead, add components one at a time:

1. Export page → add **one** component (e.g. a region) → import → verify it worked
2. Re-export page → add **next** component → import → verify
3. Repeat until all components are in place

This catches errors early — a bad parameter on one item won't destroy 20 previously-good regions. Each re-export captures APEX's canonical format for what you already imported, so you're always patching a known-good baseline.

**When to batch:** Simple, low-risk components of the same type (e.g. multiple IR columns, multiple DA actions on the same event) can be added together in one pass. But mix component types (regions + items + DAs) incrementally.

### 5) Apply DB changes (if any)
Generate idempotent scripts. Execute via `sql` CLI (Bash tool). Validate compilation.
```bash
sql -S -name $SQLCL_CONNECTION <<'EOF'
-- DDL/DML/PLSQL here
show errors;
exit;
EOF
```

### 6) Patch exported file(s)

#### Patching rules (follow these exactly)

**Structure:**
- Every procedure call wrapped in `begin...end;` terminated by `/` on its own line
- **CRITICAL — PL/SQL block boundaries:** Each `begin...end;/` is a separate SQL*Plus anonymous block. The `/` terminates the block and sends it for execution. **Never nest** `begin...end;/` inside another `begin...end;/` — the inner `/` will terminate the outer block and cause `ORA-06550`.
- **Page file block layout:**
  ```
  begin                           -- Block 1: component_begin + create_page
  wwv_flow_imp.component_begin(...);
  wwv_flow_imp_page.create_page(...);
  end;
  /
  begin                           -- Block 2..N: one per component
  wwv_flow_imp_page.create_page_plug(...);
  end;
  /
  begin                           -- Block N+1: component_end
  wwv_flow_imp.component_end;
  end;
  /
  ```
- Never modify `component_begin`/`component_end` blocks
- Comma-first style: `,p_name=>'...'`
- Multi-line strings: `wwv_flow_string.join(wwv_flow_t_varchar2('line1','line2'))`
- Single quotes doubled inside strings: `'it''s'`

**Hidden items set by JavaScript (DAs):**
- Hidden items set via `$s()` from a DA work fine with `p_protection_level=>'S'` and `value_protected=>'Y'` because `$s()` uses AJAX (not URL parameters), so session state protection checksums don't apply.
- **DO NOT** use `p_protection_level=>'N'` or `value_protected=>'N'` with `NATIVE_HIDDEN` — this violates the `WWV_VALID_FSITEM_IDT` check constraint and the import will fail with `ORA-02290`.
- Chart/region refresh via `p_ajax_items_to_submit` submits the item value via AJAX POST, which works correctly with the default protection settings.

**Item attributes format (APEX 24.2+):**
- Use `wwv_flow_t_plugin_attributes(wwv_flow_t_varchar2('key','value',...)).to_clob` — NOT bare `wwv_flow_t_varchar2(...)`.
- Example: `,p_attributes=>wwv_flow_t_plugin_attributes(wwv_flow_t_varchar2('value_protected', 'Y')).to_clob`
- When unsure of the format, export a reference page containing that item type from any app and copy the exact syntax.

**Item defaults:**
- Use `p_item_default=>'value'` only — do NOT include `p_item_default_type`. APEX exports omit it; including it (e.g. `'STATIC'`) causes `ORA-02290` constraint violations.

**IDs:**
- Scan all `wwv_flow_imp.id(...)` values in the file
- New ID = max existing + 1 (or +100 for spacing)
- Never use random IDs
- All cross-references must use matching raw IDs in `wwv_flow_imp.id(...)`
- Exception: `p_id` in `create_page` = raw page number (NOT wrapped)

**Sequences:**
- Use gaps of 10. Insert between 10 and 20 -> use 15.

**Ordering within page file:**
1. Manifest → `create_page` → regions → report/worksheet columns → buttons → branches → items → computations → validations → DA events + actions → processes

**File paths** (split export `<workdir>/f<APP_ID>/`):
- `PAGE:N` -> `application/pages/page_%05d.sql` (zero-padded)
- Shared components -> `application/shared_components/...` (use Glob if name unknown)
- New shared component files: add `@@` reference in `install_component.sql` before dependent pages

#### Post-patch validation
Run `bash tools/validate_export.sh <file>` to check begin/end balance, ID uniqueness, and syntax.

### 7) Import via SQLcl CLI
```bash
cd <workdir>/f<APP_ID>
sql -S -name $SQLCL_CONNECTION <<'EOF'
@install_component.sql
exit;
EOF
```
**Important:** `cd` into the export directory before running the install script — it uses relative `@@` paths to reference page/component files.
If different environment: prepend `apex_application_install` context block (read `app_install.md`).

### 8) Verify
Re-export + diff. Deliver: change summary, modified files, patch diff, import log.

---

## Error Recovery

**Before changes:** git baseline commit + export snapshot.

| Failure | Recovery |
|---------|----------|
| Export missing files | Verify `-dir`, permissions, APP_ID, connection (`sql -V` to confirm CLI works) |
| DB script fails | Fix + re-run; reverse with DROP/ALTER |
| Invalid patched file | `git checkout -- <file>`, re-patch |
| Import ORA-06550 (PLS-00103) | Nested `begin...end;/` blocks — fix block boundaries per structure rules above |
| Import ORA-02290 (`WWV_VALID_FSITEM_IDT`) | Invalid item parameter combination. Common causes: (1) `p_protection_level=>'N'` or `value_protected=>'N'` on `NATIVE_HIDDEN` — use `'S'`/`'Y'` instead; (2) `p_item_default_type` included — remove it, use only `p_item_default`; (3) wrong `p_attributes` format — must be `wwv_flow_t_plugin_attributes(...).to_clob`. Export a working item of the same type from any app as reference. |
| Import rolls back all changes | `set_environment.sql` contains `whenever sqlerror exit rollback`. **Any** error in the page file aborts the entire import and rolls back all components. Fix the failing call first, then reimport — partial imports are not possible. |
| Import ID collision | Revisit ID rules; regenerate |
| Import compilation error | `show errors`; fix DB objects; re-import |
| Component broken | Re-import baseline export |
| Unknown parameter format | Export a reference page from any app containing that component type (`apex export -applicationid <N> -split -dir /tmp/ref -expComponents "PAGE:<N>"`), then grep for the parameter to see the exact syntax APEX uses. |

Rollback: git -> `git checkout` + re-import. No git -> re-export from APEX.

## Examples

- `/apex PAGE:10 -- Add item P10_STATUS (select list) based on LOV STATUS_LOV, create table APP_STATUS if missing.`
- `/apex DEV 113 PAGE:10 -- Add item P10_STATUS (select list) based on LOV STATUS_LOV.`
- `/apex STG 113 LOV:23618973754424510000 -- Rename LOV display column and update dependent items on Page 3.`

登录后下载/点赞/收藏 ❤ 16 | ★ 0

apex

目录结构

SKILL.md

举报内容

提示