Manage Data Styles Setup Task Guidance
Purpose and Boundary
Use this skill only to export or import the complete FSM setup package for
Manage Data Styles. Fix the task identity to HZ_MANAGE_DATA_STYLES under
Trading Community Foundation.
Do not use this skill for planning, sequencing, standalone validation, template
generation, filtered exports, or individual data-style 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.
Fixed Task Context
- Pillar:
CX
- Offering:
Customer Data Management
- Functional area:
Trading Community Foundation
- Functional area code:
ORA_HZ_CDM_FOUNDATION
- Task name:
Manage Data Styles
- Task code:
HZ_MANAGE_DATA_STYLES
- CSV export/import supported:
Y
- Data Loader import mode:
FSM
Never accept a task-code, offering, or functional-area override.
Whole-Task FSM Export
Require project_id and the named source Fusion environment. Resolve the
live task by the exact fixed task code and confirm
CSVExportImportSupportedFlag=Y; fail closed on a mismatch.
Fix template_only=false and export_criteria=[]. Refuse every filter,
business-object subset, and template/specification request.
Show the source environment, task name/code, unfiltered whole-task scope,
output directory, and one-process impact. Obtain explicit approval
immediately before the export POST.
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_DATA_STYLES \
--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-data-styles/ \
--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
Require project_id, the named target Fusion environment, and one explicit
ZIP path. Reject loose CSV files, multiple archives, and directory scans.
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_DATA_STYLES. 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, approval,
upload/initiation, and user-friendly reporting. Start with:
python3 core/data-loader/scripts/upload_and_initiate.py "{setup_data_zip_path}"
Require the task-routed preview and approval envelope to retain
executionRoute=data-loader, sourceType=FSM, the exact task code/name,
absolute archive path, archive SHA-256, and wholeTask=true.
Treat the initial import request as validation only. Display the exact target,
fixed task code, ZIP path and hash, and impact statement; stop before the
first POST. Continue only after the separate user message required by
core.data-loader approves that immutable artifact. Then use Data Loader's
approved task-routed command with the envelope returned by Task Hook:
python3 core/data-loader/scripts/upload_and_initiate.py "{setup_data_zip_path}" \
--task-routed \
--task-validation-envelope "{task_validation_envelope_path}" \
--approve-upload
Do not invoke setupTaskCSVImports, a shared import script, UCM upload, or a
product adapter directly from this skill. 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.
- Never retry an export or import POST automatically. 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 data-style 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 data styles from TEST |
Approve and run one unfiltered FSM task export; persist the ZIP, hash, and process result |
| Import the complete exported ZIP into UAT |
Run core.data-loader preflight, require its separate immutable-artifact approval, and submit one FSM import |
| Export only one data style |
Refuse partial scope without making a Fusion call |
| Create or edit a data style |
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
1---2skill_id: "cx.customer-data-management.trading-community-foundation.manage-data-styles"3name: manage-data-styles-setup-task-guidance4description: "Exports or imports the complete Manage Data Styles setup-task data as an unfiltered Oracle Fusion FSM package. 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_DATA_STYLES"11task_name: "Manage Data Styles"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"17source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"18type: "orchestration"19execution_mode: "hybrid"20owner_team: "CX customer data management pillar team"21version: "0.2.0"22inputs:23 - "operation"24 - "project_id"25 - "fusion_environment_context"26 - "setup_data_zip_path"27 - "execution_options"28 - "execution_approval"29outputs:30 - "configuration_export"31 - "export_submission_record"32 - "data_load_execution_result"33 - "diagnostics"34 - "skill_run_record"35 - "token_usage_record"36depends_on:37 - "shared.setup-export.task-level-export"38 - "core.data-loader"39uses_core:40 - "core.auth.fusion-oauth-authentication"41 - "core.project-mgmt.artifact-registry-manager"42 - "core.project-mgmt.project-state-manager"43persists_project_state: true44token_usage_tracking:45 enabled: true46 granularity: "per_skill_run"47 artifact_type: "token_usage_record"48 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"49 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"50 required_fields:51 - "activity_start_time"52 - "skill_id"53 - "task"54 - "trigger"55 - "artifacts_written"56 - "files_read"57 - "estimated_input_tokens"58 - "estimated_output_tokens"59 - "estimated_total_tokens"60 - "estimation_method"61 - "notes"62state_updates:63 - "exports"64 - "reports"65 - "token_usage_records"66workspace_outputs:67 - artifact_type: "configuration_export"68 default_location: "project/{project_id}/exports/customer-data-management/trading-community-foundation/manage-data-styles/"69 versioning_policy: "append-only"70 - artifact_type: "report"71 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-data-styles/current/"72 versioning_policy: "append-only"73 - artifact_type: "skill_run"74 default_location: "project/{project_id}/state/runs/"75 versioning_policy: "append-only"76 - artifact_type: "token_usage_record"77 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"78 versioning_policy: "append-only"79applicability:80 industries:81 - "All"82 countries:83 - "All"84 fusion_releases:85 - "Current Oracle Fusion Cloud release"86side_effects:87 - "After explicit approval, creates and polls one whole-task FSM export process and writes its ZIP or process log to the project workspace."88 - "After the separate core.data-loader approval gate, imports one immutable whole-task FSM ZIP and can change data-style configuration in the target Fusion environment."89 - "Writes redacted execution, diagnostic, run, artifact-registry, state, and token-usage records under the selected project workspace."90required_privileges:91 - "Fusion privileges to discover the setup task and run setup task CSV exports."92 - "Fusion privileges to submit, inspect, and retrieve logs for setup task CSV imports."93metadata:94 source: https://skillmd.com/skills/oracle/manage-data-styles-setup-task-guidance95---9697# Manage Data Styles Setup Task Guidance9899## Purpose and Boundary100101Use this skill only to export or import the complete FSM setup package for102`Manage Data Styles`. Fix the task identity to `HZ_MANAGE_DATA_STYLES` under103`Trading Community Foundation`.104105Do not use this skill for planning, sequencing, standalone validation, template106generation, filtered exports, or individual data-style inspection or107maintenance. Validation is permitted only as a mandatory preflight for an108export or import.109110## Supported Operations1111121. `export`: export every setup-data object owned by the fixed task as one113 unfiltered, non-template FSM package through114 `shared.setup-export.task-level-export`.1152. `import`: import one complete, unchanged FSM ZIP for the fixed task through116 the mandatory `core.data-loader` workflow.117118Treat a migration request as these two operations in sequence. Finish and119persist the source export before starting a separate target import preflight120and approval.121122## Fixed Task Context123124- Pillar: `CX`125- Offering: `Customer Data Management`126- Functional area: `Trading Community Foundation`127- Functional area code: `ORA_HZ_CDM_FOUNDATION`128- Task name: `Manage Data Styles`129- Task code: `HZ_MANAGE_DATA_STYLES`130- CSV export/import supported: `Y`131- Data Loader import mode: `FSM`132133Never accept a task-code, offering, or functional-area override.134135## Whole-Task FSM Export1361371. Require `project_id` and the named source Fusion environment. Resolve the138 live task by the exact fixed task code and confirm139 `CSVExportImportSupportedFlag=Y`; fail closed on a mismatch.1402. Fix `template_only=false` and `export_criteria=[]`. Refuse every filter,141 business-object subset, and template/specification request.1423. Show the source environment, task name/code, unfiltered whole-task scope,143 output directory, and one-process impact. Obtain explicit approval144 immediately before the export POST.1454. Invoke `shared.setup-export.task-level-export` exactly once with the fixed146 context. Use its shared FSM engine for submission, polling, ZIP or147 `ProcessLog` retrieval, and packaging; do not implement task-local REST.148 Run the approved command with unbuffered output:149150 ```bash151 python3 -u shared/setup-export/task-level-export/scripts/export_setup_task_csv.py \152 --data \153 --task-code HZ_MANAGE_DATA_STYLES \154 --offering-name "Customer Data Management" \155 --functional-area-name "Trading Community Foundation" \156 --project-id "{project_id}" \157 --output-dir project/{project_id}/exports/customer-data-management/trading-community-foundation/manage-data-styles/ \158 --token-cache auto \159 --wait-seconds 300 \160 --poll-interval 10161 ```162163 If the command runner yields a session or cell identifier, wait on that same164 process until it exits. The `-u` option exposes the shared exporter's165 `Started ... process: <ProcessId>` line without changing shared code.166 Capture that identifier in the task skill's run record. Empty initial output167 is not failure, and must not trigger a replacement export.1685. Persist the `ProcessId` as soon as it is returned. On success, verify the ZIP,169 calculate SHA-256, store it in the declared export directory, register it,170 and update project state.1716. On timeout, preserve the same `ProcessId`, last status, and elapsed time.172 Resume only that process after a later request; never submit a replacement173 export automatically.174175## Whole-Task FSM Import Through Data Loader1761771. Require `project_id`, the named target Fusion environment, and one explicit178 ZIP path. Reject loose CSV files, multiple archives, and directory scans.1792. Verify that the file is a readable ZIP containing exactly one member whose180 basename is `ASM_SETUP_CSV_METADATA.xml`, and require its single181 `ObjectShortName` to equal `HZ_MANAGE_DATA_STYLES`. Preserve the archive182 byte for byte and calculate its SHA-256.1833. Invoke `core.data-loader` with the fixed task context and184 `dataloader_import_mode=FSM`. Let Data Loader own source review, task185 validation, FSM adapter selection, immutable preview creation, approval,186 upload/initiation, and user-friendly reporting. Start with:187188 ```bash189 python3 core/data-loader/scripts/upload_and_initiate.py "{setup_data_zip_path}"190 ```191192 Require the task-routed preview and approval envelope to retain193 `executionRoute=data-loader`, `sourceType=FSM`, the exact task code/name,194 absolute archive path, archive SHA-256, and `wholeTask=true`.1954. Treat the initial import request as validation only. Display the exact target,196 fixed task code, ZIP path and hash, and impact statement; stop before the197 first POST. Continue only after the separate user message required by198 `core.data-loader` approves that immutable artifact. Then use Data Loader's199 approved task-routed command with the envelope returned by Task Hook:200201 ```bash202 python3 core/data-loader/scripts/upload_and_initiate.py "{setup_data_zip_path}" \203 --task-routed \204 --task-validation-envelope "{task_validation_envelope_path}" \205 --approve-upload206 ```2075. Do not invoke `setupTaskCSVImports`, a shared import script, UCM upload, or a208 product adapter directly from this skill. Any changed target, archive bytes,209 task context, or execution option invalidates approval and restarts Data210 Loader preflight.2116. Persist the accepted execution result and available redacted diagnostics in212 the declared report path. Check status only when the user asks, and never213 resubmit an import while its outcome is uncertain.214215## Error and Retry Contract216217Classify failures as `input_validation`, `catalog_or_metadata_mismatch`,218`auth_expired_or_invalid`, `authorization_or_privilege`,219`transport_or_environment`, `fusion_api_error`, `process_timeout`,220`process_failed`, `artifact_persistence`, or `approval_blocker`.221222- Refresh a cache-managed token once after a read-only 401 or 403. A second223 authentication response blocks execution.224- Never retry an export or import POST automatically. Require a new immutable225 preview and explicit approval before any new submission.226- On timeout or failure, report the environment, operation, task code,227 `ProcessId` or request ID when available, last status, elapsed time,228 diagnostic artifact, and recommended next action.229- Never print or persist tokens, secrets, authorization headers, token-cache230 contents, full Base64 payloads, or sensitive customer data.231232## Result Contract233234For export, report the source environment, fixed task name/code, `ProcessId`,235status, ZIP or log path, enclosure type, and ZIP SHA-256 when available. For236import, return the complete `core.data-loader` Markdown result and report the237target environment, fixed task name/code, immutable ZIP path and hash, status,238and available process log. Record the skill run and token usage for every239durable project activity.240241## Refusal Rules242243- Refuse individual data-style creation, editing, deletion, or inspection.244- Refuse filtered, partial, criteria-based, and template/specification exports.245- Refuse task-code overrides, loose CSV files, edited or repacked ZIPs, and246 packages that Data Loader cannot confirm as the fixed FSM task.247- Refuse direct endpoint, script, or adapter execution that bypasses the248 required approval workflow.249250## Golden Scenarios251252| Request | Expected route |253|---|---|254| Export all data styles from TEST | Approve and run one unfiltered FSM task export; persist the ZIP, hash, and process result |255| Import the complete exported ZIP into UAT | Run `core.data-loader` preflight, require its separate immutable-artifact approval, and submit one FSM import |256| Export only one data style | Refuse partial scope without making a Fusion call |257| Create or edit a data style | Refuse record-level maintenance without making a Fusion call |258259## Sources260261- `knowledge/setup-task-catalog/effective/setupTasksAll.json`262- `shared/setup-export/task-level-export/SKILL.md`263- `core/data-loader/SKILL.md`