Manage Additional Name Types Setup Task Guidance
Purpose and Boundary
Use this skill only to export or import the complete FSM setup package for
Manage Additional Name Types. Fix the task identity to
HZ_MANAGE_ADDITIONAL_NAME_TYPES under Trading Community Foundation.
Do not use this skill for planning, sequencing, standalone validation, template
generation, filtered exports, or individual additional-name-type inspection or
maintenance. Validation is permitted only as a mandatory preflight for an
export or import.
Supported Operations
export: export every setup-data object owned by the fixed task as one
unfiltered, non-template FSM package through
shared.setup-export.task-level-export.
import: import one complete, unchanged FSM ZIP for the fixed task through
the mandatory core.data-loader workflow.
Treat a migration request as these two operations in sequence. Finish and
persist the source export before starting a separate target import preflight
and approval.
One Consolidated Approval
Use exactly one conversational approval point for each export or import
operation. Gather and validate every detail first. Never ask the user to
approve project creation, local Run Book artifact refresh, task-context
creation, authentication, browser sign-in, source review, metadata checks,
preview generation, Task Hook validation, or approval-envelope creation.
Those are preparation steps.
Complete the preparation bundle before mentioning approval:
Resolve the project, environment, fixed task, operation, source or output
path, scope, execution options, and overwrite state from supplied inputs and
durable project context. Ask concise factual questions only for values that
cannot be resolved safely; do not frame them as approvals.
If no implementation project exists, create the repository-prescribed draft
project and inform the user. If the selected project lacks a current local
task context, run the project workspace initializer's artifact-only refresh:
python3 core/project-mgmt/project-workspace-initializer/scripts/create_project_runbook.py \
--project-root project/{project_id} \
--refresh-artifacts
This command must not create or update a live Oracle Run Book. Do not stop to
ask the user to authorize this local, non-mutating prerequisite.
Complete OAuth authentication and target/source identity checks before
building the approval summary. Open the configured OAuth URL in the default
browser when interactive sign-in is required and wait for the callback.
Treat browser sign-in as authentication, not as an execution approval.
Finish catalog, privilege, path, ZIP, task metadata, Data Loader, Task Hook,
destination, overwrite, and immutable-preview checks. Persist the exact
preview that downstream approval records will reference.
Only after the complete bundle passes, present one compact execution summary
containing the environment, operation, fixed task name/code, exact scope,
artifact path and SHA-256 when applicable, output path, execution options, and
side effect. Ask the user once to reply exactly approve. That one approval
authorizes the one immutable operation shown in the summary:
- for export, one FSM export submission plus polling and result retrieval;
- for import, one upload and initiation of the validated FSM ZIP.
Pass that approval through the selected shared or core workflow. Do not ask
again at a task-local, Task Hook, adapter, upload, or initiation boundary.
Downstream approval records are internal representations of the same user
approval, not new prompts. Never bypass host security controls; satisfy any
platform-required login or tool permission during preparation when possible
and do not reinterpret it as another business-operation approval.
If input is missing, validation fails, the environment is ambiguous, or an
explicit exception is required, stop with a friendly correction or blocker.
Do not label the correction as an approval request. Any change to the approved
environment, task, scope, archive bytes, hash, output path, or execution options
invalidates the approval and requires a new prepared summary.
An approval is not consumed by a failure that provably occurs before the first
live POST, such as a local browser-launch, token-cache access, file-permission,
or approval-envelope persistence failure. Correct that preparation failure and
resume the exact approved operation without asking again, but only when the
environment, task, scope, archive bytes and hash, output path, execution
options, and preview fingerprint are unchanged and audit evidence confirms
that no live POST was attempted. Permit at most one bounded recovery for that
pre-POST failure. If a POST was attempted, accepted, timed out, or has an
uncertain outcome, the approval is consumed; never resubmit automatically.
Direct Export Trigger and Resume
Treat export fsm task Manage Additional Name Types and equivalent whole-task
export wording as a complete export request. Infer operation=export, the
fixed task identity, template_only=false, export_criteria=[], the standard
300-second wait, and the 10-second poll interval. Resolve the project and the
single configured Fusion environment from durable context. Ask a factual
question only when more than one viable environment or project remains, or an
overwrite conflict cannot be resolved safely.
Run every preparation step in the same turn, then persist the redacted ready
preview at:
project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-additional-name-types/current/export-approval-preview.json
Set status=ready_for_approval and bind the preview fingerprint to the project,
source environment, operation, task name/code, whole-task scope, output
directory, adapter, template flag, empty export criteria, wait seconds, poll
interval, and live lookup artifact. Include no token, secret, authorization
header, or token-cache content. Present the same bound values to the user and
ask exactly for approve; do not finish the turn with a plan when preparation
has succeeded.
When the next user message is exactly approve, load the persisted ready
preview, verify its fingerprint and bound values are unchanged, and immediately
run the one shared export command in this skill. Do not repeat discovery, ask
another business approval, or stop after process submission: capture the
ProcessId, poll it, retrieve FileContent or ProcessLog, verify and register
the artifact, update project state, append token usage, and report the result.
If no valid ready preview exists, complete or repair preflight and present a new
summary; never reinterpret an unbound approval as permission for a POST.
Fixed Task Context
- Pillar:
CX
- Offering:
Customer Data Management
- Offering code:
ZCH_CDM
- Functional area:
Trading Community Foundation
- Functional area code:
ORA_HZ_CDM_FOUNDATION
- Task name:
Manage Additional Name Types
- Task code:
HZ_MANAGE_ADDITIONAL_NAME_TYPES
- CSV export/import supported:
Y
- Data Loader import mode:
FSM
Never accept a task-code, offering, or functional-area override.
Whole-Task FSM Export
Resolve or create project_id, refresh missing local task-context artifacts,
and resolve the named source Fusion environment without an approval prompt.
Complete authentication, environment identity, privilege, destination-path,
and overwrite checks as read-only preflight. Use the existing shared
task-name lookup without hierarchy filters, then select the one result whose
TaskCode and TaskName exactly match the fixed task identity:
python3 shared/setup-export/task-level-export/scripts/find_setup_task_code.py \
--task-name "Manage Additional Name Types" \
--token-cache auto \
--output project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-additional-name-types/current/setup-task-search.json \
--json \
--print
From the returned rows, require exactly one live row with
TaskCode=HZ_MANAGE_ADDITIONAL_NAME_TYPES, the exact task name,
AvailableFlag=Y, and CSVExportImportSupportedFlag=Y. The documented
setupTasks response may omit OfferingName, OfferingCode,
FunctionalAreaName, and FunctionalAreaCode; validate that hierarchy from
the effective catalog and persisted task context, and do not reject the task
merely because those live fields are absent or blank. If Fusion returns a
nonblank hierarchy value on the exact row that contradicts the
catalog-backed context, or if zero or multiple rows have the exact fixed
code and name, fail closed before approval or POST. Ignore non-exact search
results; never select the first row merely because it was returned first.
Fix template_only=false and export_criteria=[]. Refuse every filter,
business-object subset, and template/specification request.
Write export-approval-preview.json with status=ready_for_approval, the
immutable bound fields and preview fingerprint defined above. Build the
single execution summary from that artifact with the source environment,
task name/code, unfiltered whole-task scope, output directory, polling
options, and one-process impact. Ask exactly once for approve; do not ask
for approval during discovery, authentication, validation, or output
preparation.
Invoke shared.setup-export.task-level-export exactly once with the fixed
context. Use its shared FSM engine for submission, polling, ZIP or
ProcessLog retrieval, and packaging; do not implement task-local REST.
Run the approved command with unbuffered output:
python3 -u shared/setup-export/task-level-export/scripts/export_setup_task_csv.py \
--data \
--task-code HZ_MANAGE_ADDITIONAL_NAME_TYPES \
--offering-name "Customer Data Management" \
--functional-area-name "Trading Community Foundation" \
--project-id "{project_id}" \
--output-dir project/{project_id}/exports/customer-data-management/trading-community-foundation/manage-additional-name-types/ \
--token-cache auto \
--wait-seconds 300 \
--poll-interval 10
If the command runner yields a session or cell identifier, wait on that same
process until it exits. The -u option exposes the shared exporter's
Started ... process: <ProcessId> line without changing shared code.
Capture that identifier in the task skill's run record. Empty initial output
is not failure and must not trigger a replacement export.
Persist the ProcessId as soon as it is returned. On success, verify the ZIP,
calculate SHA-256, store it in the declared export directory, register it,
and update project state.
On timeout, preserve the same ProcessId, last status, and elapsed time.
Resume only that process after a later request; never submit a replacement
export automatically.
Whole-Task FSM Import Through Data Loader
Resolve or create project_id, the named target Fusion environment, and one
explicit ZIP path. Reuse durable project inputs instead of asking the user
to restate them. Reject loose CSV files, multiple archives, and directory
scans.
Ensure that the project contains a current task-context entry resolving
sequence, exact task name/code, and this skill path. If it is missing or
stale, run the local --refresh-artifacts command from the consolidated
preparation bundle and continue automatically. Never ask for separate Run
Book artifact authorization and never create a live Oracle Run Book as an
import prerequisite.
Complete OAuth authentication, browser callback when required, target
identity, required privilege, route, and source-path checks before creating
the approval preview. Confirm that the same cached authentication mechanism
is available to the eventual Data Loader command; do not defer first-time
login until after approval.
Verify that the file is a readable ZIP containing exactly one member whose
basename is ASM_SETUP_CSV_METADATA.xml, and require its single
ObjectShortName to equal HZ_MANAGE_ADDITIONAL_NAME_TYPES. Preserve the
archive byte for byte and calculate its SHA-256.
Invoke core.data-loader with the fixed task context and
dataloader_import_mode=FSM. Let Data Loader own source review, task
validation, FSM adapter selection, immutable preview creation,
upload/initiation, and user-friendly reporting. Run its non-mutating
preflight first:
python3 core/data-loader/scripts/upload_and_initiate.py "{setup_data_zip_path}"
Complete Task Hook validation and build the task-routed immutable preview
before mentioning approval. Require the preview and later approval envelope
to retain executionRoute=data-loader, sourceType=FSM, the exact task
code/name, absolute archive path, archive SHA-256, and wholeTask=true.
After every preflight check passes, display one user-friendly execution
summary with the exact target, fixed task name/code, ZIP path and hash,
whole-task scope, validation status, and configuration-changing impact.
Ask exactly once for the separate message approve; stop before the first
POST. On that message, record Task Hook approval for the displayed preview,
verify the archive hash again, create the approval envelope, and immediately
use Data Loader's approved task-routed command without another prompt:
python3 core/data-loader/scripts/upload_and_initiate.py "{setup_data_zip_path}" \
--task-routed \
--task-validation-envelope "{task_validation_envelope_path}" \
--approve-upload
Treat Task Hook preview approval, archive verification, approval-envelope
persistence, command authorization, upload authorization, and initiation
authorization as internal representations of the one user approval. Do not
expose them as additional user approval points. If an authentication or
local-permission failure occurs before the first POST, apply the bounded
pre-POST recovery rule and reuse the same approval only when the immutable
preview fingerprint is unchanged.
Do not invoke setupTaskCSVImports, a shared import script, UCM upload, or a
product adapter directly from this skill. Do not use an approval prompt to
waive a validation problem: resolve it or report a blocker before the
single execution summary. Any changed target, archive bytes, task context,
or execution option invalidates approval and restarts Data Loader preflight.
Persist the accepted execution result and available redacted diagnostics in
the declared report path. Check status only when the user asks, and never
resubmit an import while its outcome is uncertain.
Error and Retry Contract
Classify failures as input_validation, catalog_or_metadata_mismatch,
auth_expired_or_invalid, authorization_or_privilege,
transport_or_environment, fusion_api_error, process_timeout,
process_failed, artifact_persistence, or approval_blocker.
- Refresh a cache-managed token once after a read-only 401 or 403. A second
authentication response blocks execution.
- Permit one recovery of an unchanged approved operation only when audit
evidence proves the failure occurred before the first live POST. This is a
continuation of the same approved operation, not a new submission.
- Never retry an export or import POST automatically. After a POST attempt or
uncertain response, require a new immutable preview and explicit approval
before any new submission.
- On timeout or failure, report the environment, operation, task code,
ProcessId or request ID when available, last status, elapsed time,
diagnostic artifact, and recommended next action.
- Never print or persist tokens, secrets, authorization headers, token-cache
contents, full Base64 payloads, or sensitive customer data.
Result Contract
For export, report the source environment, fixed task name/code, ProcessId,
status, ZIP or log path, enclosure type, and ZIP SHA-256 when available. For
import, return the complete core.data-loader Markdown result and report the
target environment, fixed task name/code, immutable ZIP path and hash, status,
and available process log. Record the skill run and token usage for every
durable project activity.
Refusal Rules
- Refuse individual additional-name-type creation, editing, deletion, or inspection.
- Refuse filtered, partial, criteria-based, and template/specification exports.
- Refuse task-code overrides, loose CSV files, edited or repacked ZIPs, and
packages that Data Loader cannot confirm as the fixed FSM task.
- Refuse direct endpoint, script, or adapter execution that bypasses the
required approval workflow.
Golden Scenarios
| Request |
Expected route |
| Export all Manage Additional Name Types setup data from TEST |
Approve and run one unfiltered FSM task export; persist the ZIP, hash, and process result |
| Import the complete exported ZIP into UAT |
Finish Data Loader and Task Hook preflight, show one immutable-operation summary, request one approval, and submit one FSM import |
| Import when local task context is missing |
Refresh local artifact-only Run Book context automatically, finish authentication and validation, then ask once for the consolidated import approval |
| Authentication cache is inaccessible after approval but before any POST |
Repair authentication once and continue the unchanged approved operation without another user approval |
| Export only one additional-name-type |
Refuse partial scope without making a Fusion call |
| Create or edit an additional-name-type |
Refuse record-level maintenance without making a Fusion call |
Sources
knowledge/setup-task-catalog/effective/setupTasksAll.json
shared/setup-export/task-level-export/SKILL.md
core/data-loader/SKILL.md
https://docs.oracle.com/en/cloud/saas/applications-common/26b/farca/Find_SetupTask_Code.html
1---2skill_id: "cx.customer-data-management.trading-community-foundation.manage-additional-name-types"3name: manage-additional-name-types-setup-task-guidance4description: "Exports or imports the complete Manage Additional Name Types setup-task data as an unfiltered Oracle Fusion FSM package, gathering project context, authentication, validation, and the immutable preview before one consolidated approval. Use only for whole-task FSM export/import; route every import through core.data-loader and refuse record-level maintenance, filtered or template exports, and direct REST or loader execution."5layer: "pillar"6pillar: "CX"7offering: "Customer Data Management"8functional_area: "Trading Community Foundation"9functional_area_code: "ORA_HZ_CDM_FOUNDATION"10task_code: "HZ_MANAGE_ADDITIONAL_NAME_TYPES"11task_name: "Manage Additional Name Types"12parent_skill_id: "cx.customer-data-management.trading-community-foundation"13available_flag: "Y"14export_import_supported_flag: "Y"15csv_export_import_supported_flag: "Y"16dataloader_import_mode: "FSM"17businessObject: ""18source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"19type: "orchestration"20execution_mode: "hybrid"21owner_team: "CX customer data management pillar team"22version: "0.5.1"23inputs:24 - "operation"25 - "project_id"26 - "fusion_environment_context"27 - "setup_data_zip_path"28 - "execution_options"29 - "execution_approval"30outputs:31 - "consolidated_approval_preview"32 - "configuration_export"33 - "export_submission_record"34 - "data_load_execution_result"35 - "diagnostics"36 - "skill_run_record"37 - "token_usage_record"38depends_on:39 - "shared.setup-export.task-level-export"40 - "core.data-loader"41uses_core:42 - "core.auth.fusion-oauth-authentication"43 - "core.project-mgmt.project-workspace-initializer"44 - "core.project-mgmt.artifact-registry-manager"45 - "core.project-mgmt.project-state-manager"46persists_project_state: true47token_usage_tracking:48 enabled: true49 granularity: "per_skill_run"50 artifact_type: "token_usage_record"51 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"52 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"53 required_fields:54 - "activity_start_time"55 - "skill_id"56 - "task"57 - "trigger"58 - "artifacts_written"59 - "files_read"60 - "estimated_input_tokens"61 - "estimated_output_tokens"62 - "estimated_total_tokens"63 - "estimation_method"64 - "notes"65oracle_supplied_guidance_files:66 - purpose: "Validate the fixed whole-task operation contract before export or import."67 location: "ora-resource/ora_input_validation.md"68 - purpose: "Search the live task by its fixed name, then select and validate the exact fixed TaskCode without requiring hierarchy fields that the setupTasks resource may omit."69 location: "ora-resource/ora_reference_lookups.md"70 - purpose: "Classify failures, preserve identifiers, and prevent unsafe resubmission."71 location: "ora-resource/ora_error_handling.md"72oracle_supplied_guidance_status: "Task-local validation, live lookup, and error-handling rules are compiled and ready."73state_updates:74 - "exports"75 - "reports"76 - "token_usage_records"77workspace_outputs:78 - artifact_type: "configuration_export"79 default_location: "project/{project_id}/exports/customer-data-management/trading-community-foundation/manage-additional-name-types/"80 versioning_policy: "append-only"81 - artifact_type: "report"82 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-additional-name-types/current/"83 versioning_policy: "append-only"84 - artifact_type: "skill_run"85 default_location: "project/{project_id}/state/runs/"86 versioning_policy: "append-only"87 - artifact_type: "token_usage_record"88 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"89 versioning_policy: "append-only"90applicability:91 industries:92 - "All"93 countries:94 - "All"95 fusion_releases:96 - "Current Oracle Fusion Cloud release"97side_effects:98 - "After explicit approval, creates and polls one whole-task FSM export process and writes its ZIP or process log to the project workspace."99 - "After the skill's single import approval gate, imports one immutable whole-task FSM ZIP and can change configuration owned by Manage Additional Name Types in the target Fusion environment."100 - "Writes redacted execution, diagnostic, run, artifact-registry, state, and token-usage records under the selected project workspace."101required_privileges:102 - "Fusion privileges to discover the setup task and run setup task CSV exports."103 - "Fusion privileges to submit, inspect, and retrieve logs for setup task CSV imports."104metadata:105 source: https://skillmd.com/skills/oracle/manage-additional-name-types-setup-task-guidance106---107108# Manage Additional Name Types Setup Task Guidance109110## Purpose and Boundary111112Use this skill only to export or import the complete FSM setup package for113`Manage Additional Name Types`. Fix the task identity to114`HZ_MANAGE_ADDITIONAL_NAME_TYPES` under `Trading Community Foundation`.115116Do not use this skill for planning, sequencing, standalone validation, template117generation, filtered exports, or individual additional-name-type inspection or118maintenance. Validation is permitted only as a mandatory preflight for an119export or import.120121## Supported Operations1221231. `export`: export every setup-data object owned by the fixed task as one124 unfiltered, non-template FSM package through125 `shared.setup-export.task-level-export`.1262. `import`: import one complete, unchanged FSM ZIP for the fixed task through127 the mandatory `core.data-loader` workflow.128129Treat a migration request as these two operations in sequence. Finish and130persist the source export before starting a separate target import preflight131and approval.132133## One Consolidated Approval134135Use exactly one conversational approval point for each export or import136operation. Gather and validate every detail first. Never ask the user to137approve project creation, local Run Book artifact refresh, task-context138creation, authentication, browser sign-in, source review, metadata checks,139preview generation, Task Hook validation, or approval-envelope creation.140Those are preparation steps.141142Complete the preparation bundle before mentioning approval:1431441. Resolve the project, environment, fixed task, operation, source or output145 path, scope, execution options, and overwrite state from supplied inputs and146 durable project context. Ask concise factual questions only for values that147 cannot be resolved safely; do not frame them as approvals.1482. If no implementation project exists, create the repository-prescribed draft149 project and inform the user. If the selected project lacks a current local150 task context, run the project workspace initializer's artifact-only refresh:151152 ~~~bash153 python3 core/project-mgmt/project-workspace-initializer/scripts/create_project_runbook.py \154 --project-root project/{project_id} \155 --refresh-artifacts156 ~~~157158 This command must not create or update a live Oracle Run Book. Do not stop to159 ask the user to authorize this local, non-mutating prerequisite.1603. Complete OAuth authentication and target/source identity checks before161 building the approval summary. Open the configured OAuth URL in the default162 browser when interactive sign-in is required and wait for the callback.163 Treat browser sign-in as authentication, not as an execution approval.1644. Finish catalog, privilege, path, ZIP, task metadata, Data Loader, Task Hook,165 destination, overwrite, and immutable-preview checks. Persist the exact166 preview that downstream approval records will reference.167168Only after the complete bundle passes, present one compact execution summary169containing the environment, operation, fixed task name/code, exact scope,170artifact path and SHA-256 when applicable, output path, execution options, and171side effect. Ask the user once to reply exactly `approve`. That one approval172authorizes the one immutable operation shown in the summary:173174- for export, one FSM export submission plus polling and result retrieval;175- for import, one upload and initiation of the validated FSM ZIP.176177Pass that approval through the selected shared or core workflow. Do not ask178again at a task-local, Task Hook, adapter, upload, or initiation boundary.179Downstream approval records are internal representations of the same user180approval, not new prompts. Never bypass host security controls; satisfy any181platform-required login or tool permission during preparation when possible182and do not reinterpret it as another business-operation approval.183184If input is missing, validation fails, the environment is ambiguous, or an185explicit exception is required, stop with a friendly correction or blocker.186Do not label the correction as an approval request. Any change to the approved187environment, task, scope, archive bytes, hash, output path, or execution options188invalidates the approval and requires a new prepared summary.189190An approval is not consumed by a failure that provably occurs before the first191live POST, such as a local browser-launch, token-cache access, file-permission,192or approval-envelope persistence failure. Correct that preparation failure and193resume the exact approved operation without asking again, but only when the194environment, task, scope, archive bytes and hash, output path, execution195options, and preview fingerprint are unchanged and audit evidence confirms196that no live POST was attempted. Permit at most one bounded recovery for that197pre-POST failure. If a POST was attempted, accepted, timed out, or has an198uncertain outcome, the approval is consumed; never resubmit automatically.199200## Direct Export Trigger and Resume201202Treat `export fsm task Manage Additional Name Types` and equivalent whole-task203export wording as a complete export request. Infer `operation=export`, the204fixed task identity, `template_only=false`, `export_criteria=[]`, the standard205300-second wait, and the 10-second poll interval. Resolve the project and the206single configured Fusion environment from durable context. Ask a factual207question only when more than one viable environment or project remains, or an208overwrite conflict cannot be resolved safely.209210Run every preparation step in the same turn, then persist the redacted ready211preview at:212213```text214project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-additional-name-types/current/export-approval-preview.json215```216217Set `status=ready_for_approval` and bind the preview fingerprint to the project,218source environment, operation, task name/code, whole-task scope, output219directory, adapter, template flag, empty export criteria, wait seconds, poll220interval, and live lookup artifact. Include no token, secret, authorization221header, or token-cache content. Present the same bound values to the user and222ask exactly for `approve`; do not finish the turn with a plan when preparation223has succeeded.224225When the next user message is exactly `approve`, load the persisted ready226preview, verify its fingerprint and bound values are unchanged, and immediately227run the one shared export command in this skill. Do not repeat discovery, ask228another business approval, or stop after process submission: capture the229`ProcessId`, poll it, retrieve `FileContent` or `ProcessLog`, verify and register230the artifact, update project state, append token usage, and report the result.231If no valid ready preview exists, complete or repair preflight and present a new232summary; never reinterpret an unbound approval as permission for a POST.233234## Fixed Task Context235236- Pillar: `CX`237- Offering: `Customer Data Management`238- Offering code: `ZCH_CDM`239- Functional area: `Trading Community Foundation`240- Functional area code: `ORA_HZ_CDM_FOUNDATION`241- Task name: `Manage Additional Name Types`242- Task code: `HZ_MANAGE_ADDITIONAL_NAME_TYPES`243- CSV export/import supported: `Y`244- Data Loader import mode: `FSM`245246Never accept a task-code, offering, or functional-area override.247248## Whole-Task FSM Export2492501. Resolve or create `project_id`, refresh missing local task-context artifacts,251 and resolve the named source Fusion environment without an approval prompt.252 Complete authentication, environment identity, privilege, destination-path,253 and overwrite checks as read-only preflight. Use the existing shared254 task-name lookup without hierarchy filters, then select the one result whose255 `TaskCode` and `TaskName` exactly match the fixed task identity:256257 ~~~bash258 python3 shared/setup-export/task-level-export/scripts/find_setup_task_code.py \259 --task-name "Manage Additional Name Types" \260 --token-cache auto \261 --output project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-additional-name-types/current/setup-task-search.json \262 --json \263 --print264 ~~~265266 From the returned rows, require exactly one live row with267 `TaskCode=HZ_MANAGE_ADDITIONAL_NAME_TYPES`, the exact task name,268 `AvailableFlag=Y`, and `CSVExportImportSupportedFlag=Y`. The documented269 `setupTasks` response may omit `OfferingName`, `OfferingCode`,270 `FunctionalAreaName`, and `FunctionalAreaCode`; validate that hierarchy from271 the effective catalog and persisted task context, and do not reject the task272 merely because those live fields are absent or blank. If Fusion returns a273 nonblank hierarchy value on the exact row that contradicts the274 catalog-backed context, or if zero or multiple rows have the exact fixed275 code and name, fail closed before approval or POST. Ignore non-exact search276 results; never select the first row merely because it was returned first.2772. Fix `template_only=false` and `export_criteria=[]`. Refuse every filter,278 business-object subset, and template/specification request.2793. Write `export-approval-preview.json` with `status=ready_for_approval`, the280 immutable bound fields and preview fingerprint defined above. Build the281 single execution summary from that artifact with the source environment,282 task name/code, unfiltered whole-task scope, output directory, polling283 options, and one-process impact. Ask exactly once for `approve`; do not ask284 for approval during discovery, authentication, validation, or output285 preparation.2864. Invoke `shared.setup-export.task-level-export` exactly once with the fixed287 context. Use its shared FSM engine for submission, polling, ZIP or288 `ProcessLog` retrieval, and packaging; do not implement task-local REST.289 Run the approved command with unbuffered output:290291 ~~~bash292 python3 -u shared/setup-export/task-level-export/scripts/export_setup_task_csv.py \293 --data \294 --task-code HZ_MANAGE_ADDITIONAL_NAME_TYPES \295 --offering-name "Customer Data Management" \296 --functional-area-name "Trading Community Foundation" \297 --project-id "{project_id}" \298 --output-dir project/{project_id}/exports/customer-data-management/trading-community-foundation/manage-additional-name-types/ \299 --token-cache auto \300 --wait-seconds 300 \301 --poll-interval 10302 ~~~303304 If the command runner yields a session or cell identifier, wait on that same305 process until it exits. The `-u` option exposes the shared exporter's306 `Started ... process: <ProcessId>` line without changing shared code.307 Capture that identifier in the task skill's run record. Empty initial output308 is not failure and must not trigger a replacement export.3095. Persist the `ProcessId` as soon as it is returned. On success, verify the ZIP,310 calculate SHA-256, store it in the declared export directory, register it,311 and update project state.3126. On timeout, preserve the same `ProcessId`, last status, and elapsed time.313 Resume only that process after a later request; never submit a replacement314 export automatically.315316## Whole-Task FSM Import Through Data Loader3173181. Resolve or create `project_id`, the named target Fusion environment, and one319 explicit ZIP path. Reuse durable project inputs instead of asking the user320 to restate them. Reject loose CSV files, multiple archives, and directory321 scans.3222. Ensure that the project contains a current task-context entry resolving323 sequence, exact task name/code, and this skill path. If it is missing or324 stale, run the local `--refresh-artifacts` command from the consolidated325 preparation bundle and continue automatically. Never ask for separate Run326 Book artifact authorization and never create a live Oracle Run Book as an327 import prerequisite.3283. Complete OAuth authentication, browser callback when required, target329 identity, required privilege, route, and source-path checks before creating330 the approval preview. Confirm that the same cached authentication mechanism331 is available to the eventual Data Loader command; do not defer first-time332 login until after approval.3334. Verify that the file is a readable ZIP containing exactly one member whose334 basename is `ASM_SETUP_CSV_METADATA.xml`, and require its single335 `ObjectShortName` to equal `HZ_MANAGE_ADDITIONAL_NAME_TYPES`. Preserve the336 archive byte for byte and calculate its SHA-256.3375. Invoke `core.data-loader` with the fixed task context and338 `dataloader_import_mode=FSM`. Let Data Loader own source review, task339 validation, FSM adapter selection, immutable preview creation,340 upload/initiation, and user-friendly reporting. Run its non-mutating341 preflight first:342343 ~~~bash344 python3 core/data-loader/scripts/upload_and_initiate.py "{setup_data_zip_path}"345 ~~~346347 Complete Task Hook validation and build the task-routed immutable preview348 before mentioning approval. Require the preview and later approval envelope349 to retain `executionRoute=data-loader`, `sourceType=FSM`, the exact task350 code/name, absolute archive path, archive SHA-256, and `wholeTask=true`.3516. After every preflight check passes, display one user-friendly execution352 summary with the exact target, fixed task name/code, ZIP path and hash,353 whole-task scope, validation status, and configuration-changing impact.354 Ask exactly once for the separate message `approve`; stop before the first355 POST. On that message, record Task Hook approval for the displayed preview,356 verify the archive hash again, create the approval envelope, and immediately357 use Data Loader's approved task-routed command without another prompt:358359 ~~~bash360 python3 core/data-loader/scripts/upload_and_initiate.py "{setup_data_zip_path}" \361 --task-routed \362 --task-validation-envelope "{task_validation_envelope_path}" \363 --approve-upload364 ~~~3657. Treat Task Hook preview approval, archive verification, approval-envelope366 persistence, command authorization, upload authorization, and initiation367 authorization as internal representations of the one user approval. Do not368 expose them as additional user approval points. If an authentication or369 local-permission failure occurs before the first POST, apply the bounded370 pre-POST recovery rule and reuse the same approval only when the immutable371 preview fingerprint is unchanged.3728. Do not invoke `setupTaskCSVImports`, a shared import script, UCM upload, or a373 product adapter directly from this skill. Do not use an approval prompt to374 waive a validation problem: resolve it or report a blocker before the375 single execution summary. Any changed target, archive bytes, task context,376 or execution option invalidates approval and restarts Data Loader preflight.3779. Persist the accepted execution result and available redacted diagnostics in378 the declared report path. Check status only when the user asks, and never379 resubmit an import while its outcome is uncertain.380381## Error and Retry Contract382383Classify failures as `input_validation`, `catalog_or_metadata_mismatch`,384`auth_expired_or_invalid`, `authorization_or_privilege`,385`transport_or_environment`, `fusion_api_error`, `process_timeout`,386`process_failed`, `artifact_persistence`, or `approval_blocker`.387388- Refresh a cache-managed token once after a read-only 401 or 403. A second389 authentication response blocks execution.390- Permit one recovery of an unchanged approved operation only when audit391 evidence proves the failure occurred before the first live POST. This is a392 continuation of the same approved operation, not a new submission.393- Never retry an export or import POST automatically. After a POST attempt or394 uncertain response, require a new immutable preview and explicit approval395 before any new submission.396- On timeout or failure, report the environment, operation, task code,397 `ProcessId` or request ID when available, last status, elapsed time,398 diagnostic artifact, and recommended next action.399- Never print or persist tokens, secrets, authorization headers, token-cache400 contents, full Base64 payloads, or sensitive customer data.401402## Result Contract403404For export, report the source environment, fixed task name/code, `ProcessId`,405status, ZIP or log path, enclosure type, and ZIP SHA-256 when available. For406import, return the complete `core.data-loader` Markdown result and report the407target environment, fixed task name/code, immutable ZIP path and hash, status,408and available process log. Record the skill run and token usage for every409durable project activity.410411## Refusal Rules412413- Refuse individual additional-name-type creation, editing, deletion, or inspection.414- Refuse filtered, partial, criteria-based, and template/specification exports.415- Refuse task-code overrides, loose CSV files, edited or repacked ZIPs, and416 packages that Data Loader cannot confirm as the fixed FSM task.417- Refuse direct endpoint, script, or adapter execution that bypasses the418 required approval workflow.419420## Golden Scenarios421422| Request | Expected route |423|---|---|424| Export all Manage Additional Name Types setup data from TEST | Approve and run one unfiltered FSM task export; persist the ZIP, hash, and process result |425| Import the complete exported ZIP into UAT | Finish Data Loader and Task Hook preflight, show one immutable-operation summary, request one approval, and submit one FSM import |426| Import when local task context is missing | Refresh local artifact-only Run Book context automatically, finish authentication and validation, then ask once for the consolidated import approval |427| Authentication cache is inaccessible after approval but before any POST | Repair authentication once and continue the unchanged approved operation without another user approval |428| Export only one additional-name-type | Refuse partial scope without making a Fusion call |429| Create or edit an additional-name-type | Refuse record-level maintenance without making a Fusion call |430431## Sources432433- `knowledge/setup-task-catalog/effective/setupTasksAll.json`434- `shared/setup-export/task-level-export/SKILL.md`435- `core/data-loader/SKILL.md`436- `https://docs.oracle.com/en/cloud/saas/applications-common/26b/farca/Find_SetupTask_Code.html`