API integration points wizard
For operations imported from AtomIQ, the API integration points action opens a 3-step dialog that helps you capture modernization intent (UI / Logic / Data / Files / Batch) and identify which resources from the saved AtomIQ tree are good API boundary candidates for that operation.
When the action is available
- The operation must have an
atomiqOperationIdand the parent business process must have a persisted AtomIQ snapshot (created when the spec was imported / refreshed from AtomIQ). - The wizard reads the snapshot stored on the spec — it does not call AtomIQ live. Refresh the import on the parent process if the snapshot looks stale.
- If the action button is missing, the operation hasn’t been linked to AtomIQ or the snapshot wasn’t saved on this spec yet.
Step 1 — Intro & snapshot status
Confirms that the persisted snapshot loaded for this operation. The footer shows how many root nodes were found in the tree. If the spec isn’t saved yet (no business process id), the wizard explains why it can’t load the snapshot; load errors from the server appear here too.
Step 2 — Modernization strategy
Pick what you intend to modernize for this operation. Only rows for resource types found in the tree are shown:
- Modernize UI only (SCREEN) — always checked and locked. Suggestions are always computed with the UI layer on; this is the minimum scope.
- Modernize Logic (PROGRAM) — opt-in.
- Modernize Data (TABLE) — requires Modernize Logic; ticking it auto-enables Logic. Unticking Logic clears Data.
- Modernize Files (FILE) — requires Modernize Logic; same auto-enable / clear behaviour as Data.
- Modernize Batch (JOB) — opt-in (independent).
A row is disabled when its layer isn’t available for this operation (server availability flags from the snapshot). When at least one applicable row exists you must tick something to continue. Pressing Next calls the server to compute integration-point suggestions — a short “Computing API integration points…” status appears while it runs.
Step 3 — Tree & suggested integration points
Shows the full snapshot tree with a checkbox per node. Boxes pre-checked by the server are the suggested API boundaries for your strategy; you can tick / untick any node to refine the selection.
- Hover a checkbox to see the server’s short reason for the suggestion (e.g. why a particular PROGRAM or TABLE was picked). Nodes added client-side use a built-in tooltip instead.
- SCREEN at the snapshot root is the entry UI — never an API boundary here, so its checkbox is locked.
- MAP nodes (BMS) are layout-only and never API boundaries; click the name to preview the green-screen map.
- PROGRAM at the snapshot root is automatically included and locked when Modernize Logic is off (it remains the API boundary).
- Drill down into a node by clicking its name: SCREEN / MAP → green-screen preview, PROGRAM → program documentation, TABLE → database table metadata. The app · category chip on the right shows the resource’s owning application.
- Use the chevron to collapse / expand branches; all branches start expanded.
Create Plan
The button at the bottom of the resource list panel counts your current selection. The wire-up to actually create a plan is not enabled yet — for now use the wizard to decide and document the integration boundaries; clicking the button is a no-op (the tooltip says “Not wired yet”).
Tip. The wizard always reads from the persisted snapshot, so you can iterate on strategy and selections without hitting AtomIQ. Back returns to the strategy step (selections aren’t lost on the same load); closing the dialog discards the in-progress selection.
3-step wizard to capture modernization intent and select API boundary candidates from an AtomIQ snapshot.