Run Resource Type Preparation Process for Field Service Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Run Resource Type Preparation Process for Field Service under Users and Security.
Canonical ESS Delegation Contract
Use only schemas/ess-delegation-contract.schema.json version 1.0. This
skill validates a complete approved_submission envelope before calling the
core submitter. Its request_payload is the exact approved Scheduler body;
ess_request_payload is retired. The job contract, approval hash, target
environment, and polling options must be present in the same envelope.
Setup Task Skill Contract
- task_code:
ORA_FFS_RUN_RESOURCE_TYPE_PREPARATION_PROCESS - task_name:
Run Resource Type Preparation Process for Field Service - parent_skill_id:
cx.field-service.users-and-security - pillar:
CX - offering:
Field Service - functional_area:
Users and Security - functional_area_code:
ORA_ASK_USERS_AND_SECURITY - available_flag:
Y - export_import_supported_flag:
N - csv_export_import_supported_flag:
N - dataloader_import_mode:
ESS - businessObject: ``
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Run Resource Type Preparation Process for Field Service under Users and Security.
Setup Task Metadata
- Task name:
Run Resource Type Preparation Process for Field Service - Task code:
ORA_FFS_RUN_RESOURCE_TYPE_PREPARATION_PROCESS - Available:
Y - Export/import supported:
N - CSV export/import supported:
N - CSV export/import routing:
not supported - Data Loader import mode:
ESS - Business Object: ``
CSV Export, Import, and Validation Workflow
CSVExportImportSupportedFlag is N, so this task is not marked as CSV export/import supported in the effective setup-task catalog.
Do not route CSV export work to shared.setup-export.task-level-export or CSV import work to core.data-loader unless live Fusion metadata or Oracle guidance confirms support. Use shared.validation.setup-data-validator only when a setup data artifact is available for review. Use shared.validation.reference-data-validator when the task depends on cross-pillar reference data.
Preflight Checks
Load ora-resource/ora_error_handling.md before preview or live execution and
apply its disclosure and stop-before-retry rules alongside this skill's
preflight checks.
Before calling core.fusion-api.ess-job-submitter or any other side-effecting
operation, complete and persist these preflight checks under the active project
workspace:
- Confirm the target Fusion environment identity, required ESS privileges, OAuth scopes, and usable session or token-cache state. Classify missing or invalid authentication as
auth_expired_or_invalid; classify a rejected refreshed session or missing privilege asauthorization_or_privilege. - Confirm this task's catalog identity (
ORA_FFS_RUN_RESOURCE_TYPE_PREPARATION_PROCESS) and the exactCrmEssjob contract. Treat a missing or ambiguous task, application, or job definition asinput_validationorcatalog_or_metadata_mismatchand stop before invoking the submitter. - Validate the default or user-edited payload as JSON. Require one resolved IANA timezone, the
FREQ=HOURLY;INTERVAL=6;recurrence, an offset-bearing start timestamp, an end timestamp exactly ten calendar years after the start timestamp, and valid polling options. - Confirm that payload previews, execution plans, diagnostics, and result files resolve beneath this task's declared project artifact directory. Classify an unsafe or unwritable destination as
artifact_persistenceand make no Fusion call. - Identify whether the requested action is preview or live execution. For live execution, display the final immutable payload and exact target environment, then require explicit approval immediately before the first ESS submission. Without approval, classify the stop as
approval_blocker.
Persist redacted diagnostics for authentication, authorization, transport, Fusion API, timeout, and process failures. For transport_or_environment failures, retry only read-only checks with bounded attempts. For process_timeout, preserve the request ID, last status, elapsed wait, and next-check path. Do not retry a live ESS submission after any failure or indeterminate outcome without fresh explicit approval.
ESS Execution Workflow
When the implementation objective is to run Run Resource Type Preparation Process for Field Service, delegate the ESS operation to core.fusion-api.ess-job-submitter. Do not call Fusion Scheduler REST APIs, handle OAuth tokens, or implement polling directly in this skill.
- Generate the Default ESS Request Payload below when the caller does not supply a reviewed
ess_request_payload. Resolvecurrent_iana_timezoneto the target environment's current IANA time zone, set both timestamps in that zone with their UTC offset, and calculate the end timestamp as exactly ten calendar years after the start timestamp. A caller-provided payload is an editable replacement and must be fully revalidated. - Display the fully resolved payload as JSON and let the user modify it. Revalidate the edited payload, target environment, schedule, and polling options; persist the redacted immutable approval payload as
payload_preview. - Immediately before submission, present the exact target environment and approved immutable payload and obtain explicit approval to submit the mutating ESS request.
- After approval, call
core.fusion-api.ess-job-submitterwith the approved payload, configured polling options, and managed external token-cache reference. Persist the returned request ID, status summary, and diagnostics in the project workspace. On a polling timeout, report the request ID, last status, elapsed wait, and the read-only next-check path. Do not retry a submission after an uncertain or failed request without fresh explicit approval.
core.fusion-api.ess-job-submitter owns OAuth refresh, REST submission, polling, and redaction of credentials. This skill owns Field Service task sequencing, exact job-contract validation, approval gating, and project-level audit artifacts.
Default ESS Request Payload
Unless the user supplies a reviewed replacement payload, call
core.fusion-api.ess-job-submitter with this resolved template:
{
"description": "Run Resource Type Preparation Process for Field Service - Every 6 hours",
"jobDefinitionId": "JobDefinition://oracle/apps/ess/crm/fieldservice/core/FfsCorePrepareResourceTypesJob",
"application": "CrmEss",
"schedule": {
"timezone": "{current_iana_timezone}",
"recurrences": [
{
"icalString": "FREQ=HOURLY;INTERVAL=6;",
"startDate": "{current_timestamp_in_current_timezone}",
"endDate": "{current_timestamp_in_current_timezone_plus_10_calendar_years}"
}
]
}
}
The payload shown to the user for editing and approval must contain the actual resolved IANA time zone and timestamps, not these placeholders. Do not submit the template itself.
Inputs
implementation_objectiveproject_contextsetup_task_scopesetup_data_artifactsess_delegation_contract
Outputs
setup_task_plansetup_data_routingvalidation_checkpointspayload_previewexecution_resultdiagnosticsaudit_summaryskill_run_recordtoken_usage_record
Implementation Notes
Use the parent functional-area skill cx.field-service.users-and-security for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.
Failure Handling and Recovery
- Classify missing job fields or an ambiguous catalog match as
input validationorcatalog mismatch; do not invoke the submitter. - Classify authentication, authorization, transport, Fusion API, timeout, and process failures using the submitter's diagnostics. Persist only redacted diagnostics and returned external identifiers.
- The submitter may refresh a rejected cached token once. Do not retry an ESS submission, import, or other mutation after a failure or indeterminate outcome without explicit user approval.
- For a timeout, retain the request ID and use the submitter's read-only tracking route for the next check. For a terminal failure, retain the status payload or process log when available and present the recommended recovery action.