Manage HCM Role Provisioning Rules
Purpose
Provide a controlled, cross-pillar method to export, validate, and
approval-gate the import of the Manage HCM Role Provisioning Rules FSM
setup task. Delegate transport and live import execution to the declared shared
and core dependencies. Prepare user-requested rule changes against the supported template.
Export and move the FSM setup task Manage HCM Role Provisioning Rules only
through the declared dependency workflows. The catalog identity is task code
PER_MANAGE_HCM_ROLE_PROVISIONING_RULES; require a current catalog or live-task
lookup to confirm that its export/import flags remain supported before execution.
Scope and boundaries
- Support a task-level FSM CSV export and the subsequent import of either the
exact export, a user-supplied fresh FSM archive for this task, or a modified
copy of an export or a verified-template candidate. Revalidate every change.
- This task governs HCM role-provisioning rules. Do not substitute a Manage
Job Roles archive or use this skill to create, update, or redesign job,
abstract, duty, or data roles, role memberships, security profiles, or data
security policies. Route individual role changes to Manage Job Roles or
Manage Duties, and policy changes to Manage Data Security Policies. This skill
accepts create, update, delete and redesign operations for provisioning rules.
- Do not call Fusion, OAuth, UCM, REST, FSM, or loader commands directly.
shared.setup-export.task-level-export owns export; core.data-loader
owns every import preflight, upload, initiation, and monitoring route.
- Treat a changed archive, source scope, target environment, or validation
result as a new request that must pass all gates again.
Required preflight
- Resolve the project workspace, requested operation, source and target
environments, and the exact role-provisioning-rule scope. Require source and
target to be distinct for a migration request; require explicit confirmation
for a same-environment restore.
- Confirm the exact task name and code with
shared.setup-export.task-level-export and verify its current
CSVExportImportSupportedFlag is Y. If the task is ambiguous, unavailable,
or unsupported, record a catalog-mismatch diagnostic and stop.
- Confirm the operator has Functional Setup Manager export access in the
source and Data Loader import privileges in the target. Do not request or
expose credentials, access tokens, or tenant secrets.
- Record the source/target identities, task code, scope, and a redacted
execution plan in the project workspace before any side effect.
Export Manage HCM Role Provisioning Rules
- Route the export to
shared.setup-export.task-level-export with task name
Manage HCM Role Provisioning Rules, task code
PER_MANAGE_HCM_ROLE_PROVISIONING_RULES, the source environment, and
project ID.
- Let that skill perform task lookup, support-flag validation, export process
creation, polling, download, and project export persistence. Do not
substitute a template export for a data export.
- Preserve the returned ZIP unchanged. Register its path, SHA-256, process ID,
task identity, source environment, and export timestamp as the export record.
- On an export timeout or failure, preserve the task code, process ID, last
status, process-log reference, elapsed wait, and next-check path. Do not
start another export process automatically.
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 a fresh or modified archive for import
- Require a supplied archive to be a non-empty, readable FSM ZIP. Bind its
SHA-256 to task code
PER_MANAGE_HCM_ROLE_PROVISIONING_RULES, source
provenance when known, and target environment. A modified export is a new
source artifact, not a continuation of the original export validation.
- Route setup-data validation to
shared.validation.setup-data-validator and
preserve the resulting validation evidence. Fail closed on archive-shape,
task-identity, scope, catalog, environment, or privilege mismatch.
- Do not alter, unpack-and-repack, merge, or otherwise transform the archive
after validation. Any change invalidates the evidence and approval preview.
Import the validated archive
- Route the immutable validated archive to
core.data-loader as an FSM,
task-routed import. Provide the task context, target environment, archive
SHA-256, and validation evidence.
- Let
core.data-loader complete its required source and API validation and
produce its immutable approval preview. This skill must not bypass or replace
the Data Loader route with a direct FSM API, UCM upload, REST call, CSV
utility, or browser action.
- Present the exact target environment, task code, archive name and SHA-256,
validation result, and expected impact. Stop before the first POST.
- Proceed only after the user gives a separate, immediate approval for that
immutable preview.
core.data-loader revalidates the archive and owns the
upload, initiation, process monitoring, and diagnostics.
- Do not retry an upload, initiation, import, overwrite, or replacement
process without a fresh approval. Preserve returned request IDs,
process-log references, and redacted diagnostics in the project workspace.
Failure handling
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 security configuration. For any ambiguity or unsafe path, record
the blocker and recommended next action, then stop.
1---2skill_id: "common.security-console.manage-hcm-role-provisioning-rules"3name: manage-hcm-role-provisioning-rules4description: "Prepare HCM role-provisioning-rule creation, updates, deletion and redesign from user requirements or FSM templates; validate and import supported changes through Data Loader."5layer: "pillar"6pillar: "Common"7task_code: "PER_MANAGE_HCM_ROLE_PROVISIONING_RULES"8task_name: "Manage HCM Role Provisioning Rules"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.0"20inputs:21 - "project_id"22 - "source_environment"23 - "target_environment"24 - "requested_operation"25 - "hcm_role_provisioning_rule_scope"26 - "setup_archive"27 - "user_input_file"28 - "execution_approval"29outputs:30 - "manage-hcm-role-provisioning-rules-export"31 - "import-template-export"32 - "input-file-conformance-result"33 - "corrected-input-file"34 - "archive-validation-result"35 - "import-approval-preview"36 - "data-load-execution-result"37 - "diagnostics"38 - "skill-run-record"39 - "token-usage-record"40depends_on:41 - "shared.setup-export.task-level-export"42 - "shared.validation.setup-data-validator"43 - "core.data-loader"44 - "core.project-mgmt.artifact-registry-manager"45 - "core.project-mgmt.project-state-manager"46uses_core:47 - "core.data-loader"48 - "core.project-mgmt.artifact-registry-manager"49 - "core.project-mgmt.project-state-manager"50persists_project_state: true51state_updates:52 - "scope"53 - "exports"54 - "validation_results"55 - "token_usage_records"56token_usage_tracking:57 enabled: true58 granularity: "per_skill_run"59 artifact_type: "token_usage_record"60 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"61 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"62 required_fields:63 - "activity_start_time"64 - "skill_id"65 - "task"66 - "trigger"67 - "artifacts_written"68 - "files_read"69 - "estimated_input_tokens"70 - "estimated_output_tokens"71 - "estimated_total_tokens"72 - "estimation_method"73 - "notes"74workspace_outputs:75 - artifact_type: "configuration_export"76 default_location: "project/{project_id}/exports/common/security-console/manage-hcm-role-provisioning-rules/"77 versioning_policy: "major-new-version-minor-confirm-update"78 - artifact_type: "validation_result"79 default_location: "project/{project_id}/artifacts/pillars/common/security-console/manage-hcm-role-provisioning-rules/current/"80 versioning_policy: "major-new-version-minor-confirm-update"81 - artifact_type: "skill_run"82 default_location: "project/{project_id}/state/runs/"83 versioning_policy: "append-only"84 - artifact_type: "token_usage_record"85 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"86 versioning_policy: "append-only"87oracle_supplied_guidance_files:88 - purpose: "FSM archive and task identity validation"89 location: "ora-resource/ora_input_validation.md"90 - purpose: "Import dependency and same-environment restore checks"91 location: "ora-resource/ora_dependency_readiness.md"92 - purpose: "Immutable preview and Data Loader route enforcement"93 location: "ora-resource/ora_design_enforcement.md"94 - purpose: "Approval, retry, and diagnostic controls"95 location: "ora-resource/ora_error_handling.md"96oracle_supplied_guidance_status: "Repository-authored task validation guidance; current Oracle documentation and the active Fusion contract remain authoritative."97applicability:98 industries:99 - "All"100 countries:101 - "All"102 fusion_releases:103 - "Current Oracle Fusion Cloud release"104side_effects:105 - "May route an approved task-level export to the shared export skill."106 - "May route an approved immutable FSM archive to core.data-loader for upload and import."107required_privileges:108 - "Verified Functional Setup Manager privileges to export the Manage HCM Role Provisioning Rules setup task."109 - "Verified target-environment privileges to upload and initiate the approved FSM archive through Data Loader."110metadata:111 source: https://skillmd.com/skills/oracle/manage-hcm-role-provisioning-rules112---113114# Manage HCM Role Provisioning Rules115116## Purpose117118Provide a controlled, cross-pillar method to export, validate, and119approval-gate the import of the **Manage HCM Role Provisioning Rules** FSM120setup task. Delegate transport and live import execution to the declared shared121and core dependencies. Prepare user-requested rule changes against the supported template.122123Export and move the FSM setup task **Manage HCM Role Provisioning Rules** only124through the declared dependency workflows. The catalog identity is task code125`PER_MANAGE_HCM_ROLE_PROVISIONING_RULES`; require a current catalog or live-task126lookup to confirm that its export/import flags remain supported before execution.127128## Scope and boundaries129130- Support a task-level FSM CSV export and the subsequent import of either the131 exact export, a user-supplied fresh FSM archive for this task, or a modified132 copy of an export or a verified-template candidate. Revalidate every change.133- This task governs HCM role-provisioning rules. Do not substitute a **Manage134 Job Roles** archive or use this skill to create, update, or redesign job,135 abstract, duty, or data roles, role memberships, security profiles, or data136 security policies. Route individual role changes to Manage Job Roles or137 Manage Duties, and policy changes to Manage Data Security Policies. This skill138 accepts create, update, delete and redesign operations for provisioning rules.139- Do not call Fusion, OAuth, UCM, REST, FSM, or loader commands directly.140 `shared.setup-export.task-level-export` owns export; `core.data-loader`141 owns every import preflight, upload, initiation, and monitoring route.142- Treat a changed archive, source scope, target environment, or validation143 result as a new request that must pass all gates again.144145## Required preflight1461471. Resolve the project workspace, requested operation, source and target148 environments, and the exact role-provisioning-rule scope. Require source and149 target to be distinct for a migration request; require explicit confirmation150 for a same-environment restore.1512. Confirm the exact task name and code with152 `shared.setup-export.task-level-export` and verify its current153 `CSVExportImportSupportedFlag` is `Y`. If the task is ambiguous, unavailable,154 or unsupported, record a catalog-mismatch diagnostic and stop.1553. Confirm the operator has Functional Setup Manager export access in the156 source and Data Loader import privileges in the target. Do not request or157 expose credentials, access tokens, or tenant secrets.1584. Record the source/target identities, task code, scope, and a redacted159 execution plan in the project workspace before any side effect.160161## Export Manage HCM Role Provisioning Rules1621631. Route the export to `shared.setup-export.task-level-export` with task name164 `Manage HCM Role Provisioning Rules`, task code165 `PER_MANAGE_HCM_ROLE_PROVISIONING_RULES`, the source environment, and166 project ID.1672. Let that skill perform task lookup, support-flag validation, export process168 creation, polling, download, and project export persistence. Do not169 substitute a template export for a data export.1703. Preserve the returned ZIP unchanged. Register its path, SHA-256, process ID,171 task identity, source environment, and export timestamp as the export record.1724. On an export timeout or failure, preserve the task code, process ID, last173 status, process-log reference, elapsed wait, and next-check path. Do not174 start another export process automatically.175176## Create, update, delete and redesign177178Accept these operation requests for this task's own setup objects, including179user-specified individual changes. Prepare supported changes using the target's180FSM template and execute them through `core.data-loader`; do not reject a181request merely because the user does not already have an input archive.182183Read [FSM input preparation](../references/fsm-input-preparation.md) when preparing a change or helping a user184understand the input. Obtain and safely extract the template, explain its files185and required columns, map supplied business values, and prepare a separate186candidate. Automatically authorize only the necessary template/spec export;187retain Data Loader's validation and actual import approval workflow.188189For deletion, verify the explicit supported action for the exact object or190relationship. An omitted CSV row, blank value or unrelated REMOVE action is191not whole-object deletion. If the task has no supported deletion contract,192record that specific operation gap; do not impose a blanket prohibition on all193individual changes or invent a browser/API execution route.194195For update or redesign, establish existing keys, preserve unrelated values and196show the intended changes. Intentional changes in the selected target are not197same-environment restores. Apply restore confirmation only to an actual restore.198199## Template-first import preparation2002011. Unless the user explicitly overrides this sequence, export the task first202 and provide that export as the import template before asking for import203 content. Explain that the template establishes the supported archive and204 file structure; it is not approval to import.2052. When the user provides an input file, compare it with the export template206 for file names, headers, column order, encoding, required values, and207 task-specific references. Help correct structural defects in a separate208 candidate file; preserve the supplied original and do not silently alter209 business values.2103. Give the user a concise change summary and identify any unresolved values211 or references. Use the corrected file only after it conforms to the export212 structure and has been assembled into a new candidate archive using the213 supported archive shape. That candidate is a new artifact and must pass the214 validation and approval gates below.2154. The user may override the export-first sequence, template choice, or216 proposed file corrections at any time. Honor that direction, while retaining217 the required task-identity, validation, and immediate import-approval gates.218219## Validate a fresh or modified archive for import2202211. Require a supplied archive to be a non-empty, readable FSM ZIP. Bind its222 SHA-256 to task code `PER_MANAGE_HCM_ROLE_PROVISIONING_RULES`, source223 provenance when known, and target environment. A modified export is a new224 source artifact, not a continuation of the original export validation.2252. Route setup-data validation to `shared.validation.setup-data-validator` and226 preserve the resulting validation evidence. Fail closed on archive-shape,227 task-identity, scope, catalog, environment, or privilege mismatch.2283. Do not alter, unpack-and-repack, merge, or otherwise transform the archive229 after validation. Any change invalidates the evidence and approval preview.230231## Import the validated archive2322331. Route the immutable validated archive to `core.data-loader` as an FSM,234 task-routed import. Provide the task context, target environment, archive235 SHA-256, and validation evidence.2362. Let `core.data-loader` complete its required source and API validation and237 produce its immutable approval preview. This skill must not bypass or replace238 the Data Loader route with a direct FSM API, UCM upload, REST call, CSV239 utility, or browser action.2403. Present the exact target environment, task code, archive name and SHA-256,241 validation result, and expected impact. Stop before the first POST.2424. Proceed only after the user gives a separate, immediate approval for that243 immutable preview. `core.data-loader` revalidates the archive and owns the244 upload, initiation, process monitoring, and diagnostics.2455. Do not retry an upload, initiation, import, overwrite, or replacement246 process without a fresh approval. Preserve returned request IDs,247 process-log references, and redacted diagnostics in the project workspace.248249## Failure handling250251Classify failures as input validation, catalog mismatch, authorization,252transport/environment, Fusion API, process timeout, process failed, artifact253persistence, or approval blocker. Redact credentials, tokens, customer data,254and sensitive security configuration. For any ambiguity or unsafe path, record255the blocker and recommended next action, then stop.