Manage Party Usage Filter Rules Setup Task Guidance
Purpose and Boundary
Use this skill only to export or import the complete FSM setup package for
Manage Party Usage Filter Rules. Fix the task identity to HZ_MANAGE_PARTY_USAGE_FILTER_RULES under
Trading Community Foundation.
Do not use this skill for planning, sequencing, standalone validation, template
generation, filtered exports, or individual party-usage-filter-rule 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.
Single-Approval User Experience
For each export or import operation, complete all safe, read-only preparation
before asking the user to approve anything. Intake questions, authentication,
validation, preview generation, and corrections are preparation steps, not
approval gates.
When preparation 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, and side effect. Ask the user 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.
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.
Fixed Task Context
- Pillar:
CX
- Offering:
Customer Data Management
- Functional area:
Trading Community Foundation
- Functional area code:
ORA_HZ_CDM_FOUNDATION
- Task name:
Manage Party Usage Filter Rules
- Task code:
HZ_MANAGE_PARTY_USAGE_FILTER_RULES
- 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. Complete
authentication, environment identity, privilege, live exact-task lookup,
CSVExportImportSupportedFlag=Y, destination-path, and overwrite checks
as read-only preflight; fail closed on a mismatch or blocker.
Fix template_only=false and export_criteria=[]. Refuse every filter,
business-object subset, and template/specification request.
Build the single execution summary with the source environment, task
name/code, unfiltered whole-task scope, output directory, 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_PARTY_USAGE_FILTER_RULES \
--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-party-usage-filter-rules/ \
--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. Complete authentication, target identity, privilege, route, and
source-path checks as read-only preflight. 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_PARTY_USAGE_FILTER_RULES. 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 prompting the user. 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
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.
- 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 party-usage-filter-rule 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 Party Usage Filter Rules 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 |
| Export only one party-usage-filter-rule |
Refuse partial scope without making a Fusion call |
| Create or edit a party-usage-filter-rule |
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-party-usage-filter-rules"3name: manage-party-usage-filter-rules-setup-task-guidance4description: "Exports or imports the complete Manage Party Usage Filter Rules 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_PARTY_USAGE_FILTER_RULES"11task_name: "Manage Party Usage Filter Rules"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.3.0"23inputs:24 - "operation"25 - "project_id"26 - "fusion_environment_context"27 - "setup_data_zip_path"28 - "execution_options"29 - "execution_approval"30outputs:31 - "configuration_export"32 - "export_submission_record"33 - "data_load_execution_result"34 - "diagnostics"35 - "skill_run_record"36 - "token_usage_record"37depends_on:38 - "shared.setup-export.task-level-export"39 - "core.data-loader"40uses_core:41 - "core.auth.fusion-oauth-authentication"42 - "core.project-mgmt.artifact-registry-manager"43 - "core.project-mgmt.project-state-manager"44persists_project_state: true45token_usage_tracking:46 enabled: true47 granularity: "per_skill_run"48 artifact_type: "token_usage_record"49 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"50 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"51 required_fields:52 - "activity_start_time"53 - "skill_id"54 - "task"55 - "trigger"56 - "artifacts_written"57 - "files_read"58 - "estimated_input_tokens"59 - "estimated_output_tokens"60 - "estimated_total_tokens"61 - "estimation_method"62 - "notes"63state_updates:64 - "exports"65 - "reports"66 - "token_usage_records"67workspace_outputs:68 - artifact_type: "configuration_export"69 default_location: "project/{project_id}/exports/customer-data-management/trading-community-foundation/manage-party-usage-filter-rules/"70 versioning_policy: "append-only"71 - artifact_type: "report"72 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-party-usage-filter-rules/current/"73 versioning_policy: "append-only"74 - artifact_type: "skill_run"75 default_location: "project/{project_id}/state/runs/"76 versioning_policy: "append-only"77 - artifact_type: "token_usage_record"78 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"79 versioning_policy: "append-only"80applicability:81 industries:82 - "All"83 countries:84 - "All"85 fusion_releases:86 - "Current Oracle Fusion Cloud release"87side_effects:88 - "After explicit approval, creates and polls one whole-task FSM export process and writes its ZIP or process log to the project workspace."89 - "After the skill's single import approval gate, imports one immutable whole-task FSM ZIP and can change configuration owned by Manage Party Usage Filter Rules in the target Fusion environment."90 - "Writes redacted execution, diagnostic, run, artifact-registry, state, and token-usage records under the selected project workspace."91required_privileges:92 - "Fusion privileges to discover the setup task and run setup task CSV exports."93 - "Fusion privileges to submit, inspect, and retrieve logs for setup task CSV imports."94metadata:95 source: https://skillmd.com/skills/oracle/manage-party-usage-filter-rules-setup-task-guidance96---9798# Manage Party Usage Filter Rules Setup Task Guidance99100## Purpose and Boundary101102Use this skill only to export or import the complete FSM setup package for103`Manage Party Usage Filter Rules`. Fix the task identity to `HZ_MANAGE_PARTY_USAGE_FILTER_RULES` under104`Trading Community Foundation`.105106Do not use this skill for planning, sequencing, standalone validation, template107generation, filtered exports, or individual party-usage-filter-rule inspection or108maintenance. Validation is permitted only as a mandatory preflight for an109export or import.110111## Supported Operations1121131. `export`: export every setup-data object owned by the fixed task as one114 unfiltered, non-template FSM package through115 `shared.setup-export.task-level-export`.1162. `import`: import one complete, unchanged FSM ZIP for the fixed task through117 the mandatory `core.data-loader` workflow.118119Treat a migration request as these two operations in sequence. Finish and120persist the source export before starting a separate target import preflight121and approval.122123## Single-Approval User Experience124125For each export or import operation, complete all safe, read-only preparation126before asking the user to approve anything. Intake questions, authentication,127validation, preview generation, and corrections are preparation steps, not128approval gates.129130When preparation passes, present one compact execution summary containing the131environment, operation, fixed task name/code, exact scope, artifact path and132SHA-256 when applicable, output path, and side effect. Ask the user to reply133exactly `approve`. That one approval authorizes the one immutable operation134shown in the summary:135136- for export, one FSM export submission plus polling and result retrieval;137- for import, one upload and initiation of the validated FSM ZIP.138139Pass that approval through the selected shared or core workflow. Do not ask140again at a task-local, Task Hook, adapter, upload, or initiation boundary.141Downstream approval records are internal representations of the same user142approval, not new prompts.143144If input is missing, validation fails, the environment is ambiguous, or an145explicit exception is required, stop with a friendly correction or blocker.146Do not label the correction as an approval request. Any change to the approved147environment, task, scope, archive bytes, hash, output path, or execution options148invalidates the approval and requires a new prepared summary.149150## Fixed Task Context151152- Pillar: `CX`153- Offering: `Customer Data Management`154- Functional area: `Trading Community Foundation`155- Functional area code: `ORA_HZ_CDM_FOUNDATION`156- Task name: `Manage Party Usage Filter Rules`157- Task code: `HZ_MANAGE_PARTY_USAGE_FILTER_RULES`158- CSV export/import supported: `Y`159- Data Loader import mode: `FSM`160161Never accept a task-code, offering, or functional-area override.162163## Whole-Task FSM Export1641651. Require `project_id` and the named source Fusion environment. Complete166 authentication, environment identity, privilege, live exact-task lookup,167 `CSVExportImportSupportedFlag=Y`, destination-path, and overwrite checks168 as read-only preflight; fail closed on a mismatch or blocker.1692. Fix `template_only=false` and `export_criteria=[]`. Refuse every filter,170 business-object subset, and template/specification request.1713. Build the single execution summary with the source environment, task172 name/code, unfiltered whole-task scope, output directory, and one-process173 impact. Ask exactly once for `approve`; do not ask for approval during174 discovery, authentication, validation, or output preparation.1754. Invoke `shared.setup-export.task-level-export` exactly once with the fixed176 context. Use its shared FSM engine for submission, polling, ZIP or177 `ProcessLog` retrieval, and packaging; do not implement task-local REST.178 Run the approved command with unbuffered output:179180 ~~~bash181 python3 -u shared/setup-export/task-level-export/scripts/export_setup_task_csv.py \182 --data \183 --task-code HZ_MANAGE_PARTY_USAGE_FILTER_RULES \184 --offering-name "Customer Data Management" \185 --functional-area-name "Trading Community Foundation" \186 --project-id "{project_id}" \187 --output-dir project/{project_id}/exports/customer-data-management/trading-community-foundation/manage-party-usage-filter-rules/ \188 --token-cache auto \189 --wait-seconds 300 \190 --poll-interval 10191 ~~~192193 If the command runner yields a session or cell identifier, wait on that same194 process until it exits. The `-u` option exposes the shared exporter's195 `Started ... process: <ProcessId>` line without changing shared code.196 Capture that identifier in the task skill's run record. Empty initial output197 is not failure and must not trigger a replacement export.1985. Persist the `ProcessId` as soon as it is returned. On success, verify the ZIP,199 calculate SHA-256, store it in the declared export directory, register it,200 and update project state.2016. On timeout, preserve the same `ProcessId`, last status, and elapsed time.202 Resume only that process after a later request; never submit a replacement203 export automatically.204205## Whole-Task FSM Import Through Data Loader2062071. Require `project_id`, the named target Fusion environment, and one explicit208 ZIP path. Complete authentication, target identity, privilege, route, and209 source-path checks as read-only preflight. Reject loose CSV files, multiple210 archives, and directory scans.2112. Verify that the file is a readable ZIP containing exactly one member whose212 basename is `ASM_SETUP_CSV_METADATA.xml`, and require its single213 `ObjectShortName` to equal `HZ_MANAGE_PARTY_USAGE_FILTER_RULES`. Preserve the archive214 byte for byte and calculate its SHA-256.2153. Invoke `core.data-loader` with the fixed task context and216 `dataloader_import_mode=FSM`. Let Data Loader own source review, task217 validation, FSM adapter selection, immutable preview creation,218 upload/initiation, and user-friendly reporting. Run its non-mutating219 preflight first:220221 ~~~bash222 python3 core/data-loader/scripts/upload_and_initiate.py "{setup_data_zip_path}"223 ~~~224225 Complete Task Hook validation and build the task-routed immutable preview226 before prompting the user. Require the preview and later approval envelope to retain227 `executionRoute=data-loader`, `sourceType=FSM`, the exact task code/name,228 absolute archive path, archive SHA-256, and `wholeTask=true`.2294. After every preflight check passes, display one user-friendly execution230 summary with the exact target, fixed task name/code, ZIP path and hash,231 whole-task scope, validation status, and configuration-changing impact.232 Ask exactly once for the separate message `approve`; stop before the first233 POST. On that message, record Task Hook approval for the displayed preview,234 verify the archive hash again, create the approval envelope, and immediately235 use Data Loader's approved task-routed command without another prompt:236237 ~~~bash238 python3 core/data-loader/scripts/upload_and_initiate.py "{setup_data_zip_path}" \239 --task-routed \240 --task-validation-envelope "{task_validation_envelope_path}" \241 --approve-upload242 ~~~2435. Do not invoke `setupTaskCSVImports`, a shared import script, UCM upload, or a244 product adapter directly from this skill. Do not use an approval prompt to245 waive a validation problem: resolve it or report a blocker before the246 single execution summary. Any changed target, archive bytes, task context,247 or execution option invalidates approval and restarts Data Loader preflight.2486. Persist the accepted execution result and available redacted diagnostics in249 the declared report path. Check status only when the user asks, and never250 resubmit an import while its outcome is uncertain.251252## Error and Retry Contract253254Classify failures as `input_validation`, `catalog_or_metadata_mismatch`,255`auth_expired_or_invalid`, `authorization_or_privilege`,256`transport_or_environment`, `fusion_api_error`, `process_timeout`,257`process_failed`, `artifact_persistence`, or `approval_blocker`.258259- Refresh a cache-managed token once after a read-only 401 or 403. A second260 authentication response blocks execution.261- Never retry an export or import POST automatically. Require a new immutable262 preview and explicit approval before any new submission.263- On timeout or failure, report the environment, operation, task code,264 `ProcessId` or request ID when available, last status, elapsed time,265 diagnostic artifact, and recommended next action.266- Never print or persist tokens, secrets, authorization headers, token-cache267 contents, full Base64 payloads, or sensitive customer data.268269## Result Contract270271For export, report the source environment, fixed task name/code, `ProcessId`,272status, ZIP or log path, enclosure type, and ZIP SHA-256 when available. For273import, return the complete `core.data-loader` Markdown result and report the274target environment, fixed task name/code, immutable ZIP path and hash, status,275and available process log. Record the skill run and token usage for every276durable project activity.277278## Refusal Rules279280- Refuse individual party-usage-filter-rule creation, editing, deletion, or inspection.281- Refuse filtered, partial, criteria-based, and template/specification exports.282- Refuse task-code overrides, loose CSV files, edited or repacked ZIPs, and283 packages that Data Loader cannot confirm as the fixed FSM task.284- Refuse direct endpoint, script, or adapter execution that bypasses the285 required approval workflow.286287## Golden Scenarios288289| Request | Expected route |290|---|---|291| Export all Manage Party Usage Filter Rules setup data from TEST | Approve and run one unfiltered FSM task export; persist the ZIP, hash, and process result |292| 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 |293| Export only one party-usage-filter-rule | Refuse partial scope without making a Fusion call |294| Create or edit a party-usage-filter-rule | Refuse record-level maintenance without making a Fusion call |295296## Sources297298- `knowledge/setup-task-catalog/effective/setupTasksAll.json`299- `shared/setup-export/task-level-export/SKILL.md`300- `core/data-loader/SKILL.md`