Manage Duties
Purpose
Provide a controlled, cross-pillar method to export, validate, and
approval-gate the import of the Manage Duties FSM setup task. Delegate
transport and live import execution to the declared shared and core
dependencies. Prepare user-requested custom-duty changes using supported FSM fields.
Export and move FSM task Manage Duties only through declared dependencies.
Its catalog identity is ASXS_MANAGE_DUTIES; before execution, confirm a
current catalog or live-task lookup reports CSVExportImportSupportedFlag=Y.
Boundaries
- Support a task-level CSV export and import of the exact export, a verified-template
candidate or a user-supplied modified derivative. A modified archive is a new artifact:
validate, hash, preview, and approve it separately.
- Cover duty-role groupings and their provisioning to abstract, job, or other
duty roles. Accept creation, updates, deletion and hierarchy redesign for
this task's supported duty objects; route changes to other setup objects
through their dedicated skills.
- Do not call Fusion, OAuth, UCM, REST, FSM, or loader commands directly.
Task Level Export owns export; Data Loader owns import preflight, upload,
initiation, monitoring, and diagnostics.
Preflight
- Resolve project, operation, source and target environments, and duty scope.
Require separate environments for migration or explicit confirmation for a
same-environment restore.
- Confirm
Manage Duties / ASXS_MANAGE_DUTIES and current CSV support with
shared.setup-export.task-level-export. On ambiguity or unsupported status,
record a catalog-mismatch diagnostic and stop.
- Confirm source export and target import privileges. Never request or expose
credentials, tokens, or tenant secrets.
- Persist source/target identity, task code, scope, and a redacted plan before
any side effect.
Export
- Route to
shared.setup-export.task-level-export with task name Manage Duties, code ASXS_MANAGE_DUTIES, source environment, and project ID.
- Let that skill discover the task, validate support, create/poll/download the
export, and persist it. Do not substitute a template export for setup data.
- Preserve the returned ZIP unchanged and register its path, SHA-256, process
ID, task identity, source environment, and timestamp.
- On timeout/failure preserve task code, process ID, last status, process-log
reference, elapsed wait, and next-check path; do not automatically re-export.
Create, update, delete and redesign
Accept these operation requests for this task's own setup objects, including
user-specified individual changes. Prepare supported changes using the target's
FSM template and execute them through core.data-loader; do not reject a
request merely because the user does not already have an input archive.
Read FSM input preparation when preparing a change or helping a user
understand the input. Obtain and safely extract the template, explain its files
and required columns, map supplied business values, and prepare a separate
candidate. Automatically authorize only the necessary template/spec export;
retain Data Loader's validation and actual import approval workflow.
For deletion, verify the explicit supported action for the exact object or
relationship. An omitted CSV row, blank value or unrelated REMOVE action is
not whole-object deletion. If the task has no supported deletion contract,
record that specific operation gap; do not impose a blanket prohibition on all
individual changes or invent a browser/API execution route.
For update or redesign, establish existing keys, preserve unrelated values and
show the intended changes. Intentional changes in the selected target are not
same-environment restores. Apply restore confirmation only to an actual restore.
Template-first import preparation
- Unless the user explicitly overrides this sequence, export the task first
and provide that export as the import template before asking for import
content. Explain that the template establishes the supported archive and
file structure; it is not approval to import.
- When the user provides an input file, compare it with the export template
for file names, headers, column order, encoding, required values, and
task-specific references. Help correct structural defects in a separate
candidate file; preserve the supplied original and do not silently alter
business values.
- Give the user a concise change summary and identify any unresolved values
or references. Use the corrected file only after it conforms to the export
structure and has been assembled into a new candidate archive using the
supported archive shape. That candidate is a new artifact and must pass the
validation and approval gates below.
- The user may override the export-first sequence, template choice, or
proposed file corrections at any time. Honor that direction, while retaining
the required task-identity, validation, and immediate import-approval gates.
Validate and import
- Accept a non-empty export ZIP or a user-modified derivative. Bind its
SHA-256 to
ASXS_MANAGE_DUTIES, source, and target. Never call it a Manage
Job Roles archive.
- Route validation to
shared.validation.setup-data-validator; fail closed on
archive shape, task identity, scope, catalog, environment, or privilege
mismatch. Preserve validation evidence.
- Do not alter, unpack/repack, merge, or transform the archive after
validation. Any modification starts a new validation cycle.
- Route the immutable validated archive to
core.data-loader as an FSM,
task-routed import with target identity, SHA-256, and validation evidence.
- Let Data Loader build its immutable approval preview. Do not substitute a
direct FSM API, UCM upload, REST call, CSV utility, or browser action.
- Present target, task code, archive name/SHA-256, validation result, and
expected impact; stop before the first POST. Proceed only after separate,
immediate approval. Data Loader revalidates and owns execution thereafter.
- Do not retry upload, import, overwrite, or replacement without fresh
approval. Persist returned IDs, process-log references, and redacted
diagnostics in the project workspace.
Failures
Classify failures as input validation, catalog mismatch, authorization,
transport/environment, Fusion API, process timeout, process failed, artifact
persistence, or approval blocker. Redact credentials, tokens, customer data,
and sensitive duty or role configuration; record the blocker and safe next step.
1---2skill_id: "common.security-console.manage-duties"3name: manage-duties4description: "Prepare custom duty creation, updates, deletion and redesign requests from user requirements or FSM templates; validate and execute supported Manage Duties changes through approval-gated Data Loader imports."5layer: "pillar"6pillar: "Common"7task_code: "ASXS_MANAGE_DUTIES"8task_name: "Manage Duties"9parent_skill_id: "common.security-console"10available_flag: "Y"11export_import_supported_flag: "Y"12csv_export_import_supported_flag: "Y"13dataloader_import_mode: "FSM"14businessObject: ""15source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"16type: "orchestration"17execution_mode: "hybrid"18owner_team: "FSCR Security team"19version: "0.2.1"20inputs: ["project_id", "source_environment", "target_environment", "requested_operation", "duty_scope", "setup_archive", "user_input_file", "execution_approval"]21outputs: ["manage-duties-export", "import-template-export", "input-file-conformance-result", "corrected-input-file", "archive-validation-result", "import-approval-preview", "data-load-execution-result", "diagnostics", "skill-run-record", "token-usage-record"]22depends_on: ["shared.setup-export.task-level-export", "shared.validation.setup-data-validator", "core.data-loader", "core.project-mgmt.artifact-registry-manager", "core.project-mgmt.project-state-manager"]23uses_core: ["core.data-loader", "core.project-mgmt.artifact-registry-manager", "core.project-mgmt.project-state-manager"]24persists_project_state: true25state_updates: ["scope", "exports", "validation_results", "token_usage_records"]26token_usage_tracking:27 enabled: true28 granularity: "per_skill_run"29 artifact_type: "token_usage_record"30 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"31 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"32 required_fields: ["activity_start_time", "skill_id", "task", "trigger", "artifacts_written", "files_read", "estimated_input_tokens", "estimated_output_tokens", "estimated_total_tokens", "estimation_method", "notes"]33workspace_outputs:34 - artifact_type: "configuration_export"35 default_location: "project/{project_id}/exports/common/security-console/manage-duties/"36 versioning_policy: "major-new-version-minor-confirm-update"37 - artifact_type: "validation_result"38 default_location: "project/{project_id}/artifacts/pillars/common/security-console/manage-duties/current/"39 versioning_policy: "major-new-version-minor-confirm-update"40 - artifact_type: "skill_run"41 default_location: "project/{project_id}/state/runs/"42 versioning_policy: "append-only"43 - artifact_type: "token_usage_record"44 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"45 versioning_policy: "append-only"46applicability:47 industries: ["All"]48 countries: ["All"]49 fusion_releases: ["Current Oracle Fusion Cloud release"]50side_effects: ["May route an approved task-level export to shared.setup-export.task-level-export.", "May route an approved immutable FSM archive to core.data-loader for upload and import."]51required_privileges: ["Functional Setup Manager privileges to export Manage Duties.", "Target-environment privileges to upload and initiate the approved FSM archive through Data Loader."]52metadata:53 source: https://skillmd.com/skills/oracle/manage-duties54---5556# Manage Duties5758## Purpose5960Provide a controlled, cross-pillar method to export, validate, and61approval-gate the import of the **Manage Duties** FSM setup task. Delegate62transport and live import execution to the declared shared and core63dependencies. Prepare user-requested custom-duty changes using supported FSM fields.6465Export and move FSM task **Manage Duties** only through declared dependencies.66Its catalog identity is `ASXS_MANAGE_DUTIES`; before execution, confirm a67current catalog or live-task lookup reports `CSVExportImportSupportedFlag=Y`.6869## Boundaries7071- Support a task-level CSV export and import of the exact export, a verified-template72 candidate or a user-supplied modified derivative. A modified archive is a new artifact:73 validate, hash, preview, and approve it separately.74- Cover duty-role groupings and their provisioning to abstract, job, or other75 duty roles. Accept creation, updates, deletion and hierarchy redesign for76 this task's supported duty objects; route changes to other setup objects77 through their dedicated skills.78- Do not call Fusion, OAuth, UCM, REST, FSM, or loader commands directly.79 Task Level Export owns export; Data Loader owns import preflight, upload,80 initiation, monitoring, and diagnostics.8182## Preflight83841. Resolve project, operation, source and target environments, and duty scope.85 Require separate environments for migration or explicit confirmation for a86 same-environment restore.872. Confirm `Manage Duties` / `ASXS_MANAGE_DUTIES` and current CSV support with88 `shared.setup-export.task-level-export`. On ambiguity or unsupported status,89 record a catalog-mismatch diagnostic and stop.903. Confirm source export and target import privileges. Never request or expose91 credentials, tokens, or tenant secrets.924. Persist source/target identity, task code, scope, and a redacted plan before93 any side effect.9495## Export96971. Route to `shared.setup-export.task-level-export` with task name `Manage98 Duties`, code `ASXS_MANAGE_DUTIES`, source environment, and project ID.992. Let that skill discover the task, validate support, create/poll/download the100 export, and persist it. Do not substitute a template export for setup data.1013. Preserve the returned ZIP unchanged and register its path, SHA-256, process102 ID, task identity, source environment, and timestamp.1034. On timeout/failure preserve task code, process ID, last status, process-log104 reference, elapsed wait, and next-check path; do not automatically re-export.105106## Create, update, delete and redesign107108Accept these operation requests for this task's own setup objects, including109user-specified individual changes. Prepare supported changes using the target's110FSM template and execute them through `core.data-loader`; do not reject a111request merely because the user does not already have an input archive.112113Read [FSM input preparation](../references/fsm-input-preparation.md) when preparing a change or helping a user114understand the input. Obtain and safely extract the template, explain its files115and required columns, map supplied business values, and prepare a separate116candidate. Automatically authorize only the necessary template/spec export;117retain Data Loader's validation and actual import approval workflow.118119For deletion, verify the explicit supported action for the exact object or120relationship. An omitted CSV row, blank value or unrelated REMOVE action is121not whole-object deletion. If the task has no supported deletion contract,122record that specific operation gap; do not impose a blanket prohibition on all123individual changes or invent a browser/API execution route.124125For update or redesign, establish existing keys, preserve unrelated values and126show the intended changes. Intentional changes in the selected target are not127same-environment restores. Apply restore confirmation only to an actual restore.128129## Template-first import preparation1301311. Unless the user explicitly overrides this sequence, export the task first132 and provide that export as the import template before asking for import133 content. Explain that the template establishes the supported archive and134 file structure; it is not approval to import.1352. When the user provides an input file, compare it with the export template136 for file names, headers, column order, encoding, required values, and137 task-specific references. Help correct structural defects in a separate138 candidate file; preserve the supplied original and do not silently alter139 business values.1403. Give the user a concise change summary and identify any unresolved values141 or references. Use the corrected file only after it conforms to the export142 structure and has been assembled into a new candidate archive using the143 supported archive shape. That candidate is a new artifact and must pass the144 validation and approval gates below.1454. The user may override the export-first sequence, template choice, or146 proposed file corrections at any time. Honor that direction, while retaining147 the required task-identity, validation, and immediate import-approval gates.148149## Validate and import1501511. Accept a non-empty export ZIP or a user-modified derivative. Bind its152 SHA-256 to `ASXS_MANAGE_DUTIES`, source, and target. Never call it a Manage153 Job Roles archive.1542. Route validation to `shared.validation.setup-data-validator`; fail closed on155 archive shape, task identity, scope, catalog, environment, or privilege156 mismatch. Preserve validation evidence.1573. Do not alter, unpack/repack, merge, or transform the archive after158 validation. Any modification starts a new validation cycle.1594. Route the immutable validated archive to `core.data-loader` as an FSM,160 task-routed import with target identity, SHA-256, and validation evidence.1615. Let Data Loader build its immutable approval preview. Do not substitute a162 direct FSM API, UCM upload, REST call, CSV utility, or browser action.1636. Present target, task code, archive name/SHA-256, validation result, and164 expected impact; stop before the first POST. Proceed only after separate,165 immediate approval. Data Loader revalidates and owns execution thereafter.1667. Do not retry upload, import, overwrite, or replacement without fresh167 approval. Persist returned IDs, process-log references, and redacted168 diagnostics in the project workspace.169170## Failures171172Classify failures as input validation, catalog mismatch, authorization,173transport/environment, Fusion API, process timeout, process failed, artifact174persistence, or approval blocker. Redact credentials, tokens, customer data,175and sensitive duty or role configuration; record the blocker and safe next step.