Time Slots Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Time Slots under Scheduling and Dispatch.
Setup Task Skill Contract
- task_code:
ORA_FFS_TS_TIME_SLOTS - task_name:
Time Slots - parent_skill_id:
cx.field-service.scheduling-and-dispatch - pillar:
CX - offering:
Field Service - functional_area:
Scheduling and Dispatch - functional_area_code:
ORA_FFS_FA_SCHEDULING_AND_DISPATCH - available_flag:
Y - export_import_supported_flag:
UNKNOWN - csv_export_import_supported_flag:
UNKNOWN - source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Time Slots under Scheduling and Dispatch.
Execution Direction
execution_direction is optional and defaults to core.data-loader.task-rest.
That Core route may execute only the operation methods it supports after its
own task-validation gate. It must reject the Time Slots PUT operation rather
than silently changing route or method.
Set execution_direction=ora_rest_execution only when explicitly selecting
the task-owned Time Slots REST workflow. That route requires read-only
preflight, describe-backed payload mapping, an immutable preview, and approval
bound to that preview immediately before the PUT. A failed or unsupported
default route is not permission to fall back automatically to direct REST.
The contract in ora-resource/ora_rest_execution.md is the source of truth for
route selection, supported operations, endpoint paths, refusal behavior, and
verification. It does not authorize a live call by itself.
Time Slots REST Execution Contract
| Requested direction | Result | Constraint |
|---|---|---|
Omitted or core.data-loader.task-rest |
Use the Core Task REST executor | It permits GET, POST, and PATCH only. It must reject the Time Slots PUT and must not substitute a route. |
ora_rest_execution |
Use the pillar-owned direct REST workflow | This is the only selected route for a Time Slots PUT; it is not a fallback. |
| Data Loader archive/import | Block | CSV support is UNKNOWN; a configuration workbook is not a Data Loader artifact. |
The direct workflow uses the implementation API: search with
GET /api/field-service/configuration/v1/timeSlots/, read with
GET /api/field-service/configuration/v1/timeSlots/{itemId}, and create or
update with PUT /api/field-service/configuration/v1/timeSlots/{itemId}. The
public GET /rest/ofscMetadata/v1/timeSlots endpoint is discovery-only.
A 404 item read is a create candidate and a 200 item read is an update
candidate; both use the same implementation item PUT. Reject POST, PATCH,
DELETE, metadata-item write paths, and endpoint substitution. Every PUT uses
FS-IDENTIFY-BY: label always. Send If-None-Match: {label} only for a 404
create candidate; omit it for a 200 update candidate, otherwise the API
returns a create-only 409 Conflict.
The writable body maps Label, Name, Status, Start Time, and End Time to
label, name, active, timeStart, and timeEnd. isAllDay appears only
in the documented response and is not written; all-day rows are therefore
rejected as unsupported by this direct contract. Activity Types and Capacity
Categories are not execution payload fields. The association APIs are never called.
Warehouse Visits has no mapped writable field and is rejected.
For an executable direct operation:
- Complete environment preflight and list/read the current Time Slots state.
- Resolve a 404 only as a create candidate; treat a 200 as an update, enable, or disable candidate. Stop on any other read result.
- Produce an immutable preview containing environment identity, method, path, current-state summary, mapped body, field-level diff, and SHA-256 digest.
- Obtain explicit approval bound to that exact digest immediately before PUT.
Do not retry, roll back, or substitute a write method. If an independent
slot write fails, retain its diagnostic and continue the remaining approved
independent slots; return
partial_failed, nevercompleted. - Read the same item with GET after a successful PUT and compare saved fields with the approved request. Persist only redacted diagnostics and artifact references.
Error Handling
Apply the task-local failure contract in
ora-resource/ora_error_handling.md before preview and execution. Preflight,
workbook validation, design-enforcement, dependency, lookup, and payload
mapping failures block the preview and no write is attempted. Do not retry a
PUT automatically, substitute an endpoint or execution route, or make a write
without approval bound to the immutable preview. Persist only sanitized,
redacted diagnostics. When an approved independent slot PUT fails, retain its
failure diagnostic, continue only the remaining approved independent slots,
and return partial_failed; verify each successful PUT with a same-item GET.
Setup Task Metadata
- Task name:
Time Slots - Task code:
ORA_FFS_TS_TIME_SLOTS - Available:
Y - Export/import supported:
UNKNOWN - CSV export/import supported:
UNKNOWN - CSV export/import routing:
not supported
CSV Export, Import, and Validation Workflow
CSVExportImportSupportedFlag is UNKNOWN, 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.
Inputs
implementation_objectiveproject_contextsetup_task_scopesetup_data_artifactsexecution_direction— optional; defaults tocore.data-loader.task-rest. Set toora_rest_executiononly with an explicit task-owned REST selection.
Outputs
setup_task_plansetup_data_routingvalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
Use the parent functional-area skill cx.field-service.scheduling-and-dispatch for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.