Manage Sales Lead Qualification Template Setup Task Guidance
Purpose
Exports the current Lead qualification-template baseline, validates a new
reference-derived package, reconciles duplicates from both the export and live
REST state, and hands a validated FSM archive to the mandatory Data Loader
approval and import lifecycle.
Setup Task Skill Contract
- task_code:
MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE
- task_name:
Manage Sales Lead Qualification Template
- parent_skill_id:
cx.sales.leads
- pillar:
CX
- offering:
Sales
- functional_area:
Leads
- functional_area_code:
ORA_LDS_LEADS
- available_flag:
Y
- export_import_supported_flag:
Y
- csv_export_import_supported_flag:
Y
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Manage Sales Lead Qualification Template under Leads.
Runtime Interface and Handoff
Apply the parent cx.sales.leads runtime-interface guidance. For the normal
workflow, prefer the declared export, validation, read-only lookup, and Data
Loader skill contracts before considering implementation or test source.
This task hands Data Loader only the task-context path, exact task name,
positive sequence, environment, final ZIP path and SHA-256, operation, template
identity and set, export identity/hash/release, duplicate evidence, row counts,
task-rule results, and finalData.archiveSha256. Data Loader owns its preview,
approval record, taskValidationEnvelope, authentication, upload, and
initiation structures. If a declared interface fails or differs from its
contract, follow the parent's scoped diagnostic escalation and reuse the
resolved interface for the rest of the run.
Setup Task Metadata
- Task name:
Manage Sales Lead Qualification Template
- Task code:
MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE
- Available:
Y
- Export/import supported:
Y
- CSV export/import supported:
Y
- CSV export/import routing:
supported
Mandatory Create Workflow
For Create, do not require the user to supply an existing ZIP. Export the
current task data automatically from the selected environment before generating
or approving a new qualification template.
- Preflight the target environment identity, task code, catalog flags,
authentication, export privilege, project destination, and import approval
state. Never print or persist credentials.
- Invoke
shared.setup-export.task-level-export in current-data mode for
MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE; do not use template/spec mode.
- Capture the export
ProcessId from either the collection form or
SetupTaskCSVExportProcess.items[0].ProcessId, poll that exact process, and
download the result from its enclosure/FileContent endpoint. Do not infer
completion from a collection response or download a collection resource.
- Validate the downloaded ZIP before use: ZIP signature and CRCs, the exact
required members below, metadata task code,
ObjectType=TASK,
ProcessType=EXPORT, ProcessStatus=COMPLETED, target ProcessEnv, target
Fusion release, and LEAD scope. Record its SHA-256 hash and export
ProcessId.
- Inventory every
LEAD template from both template CSVs and retain exact
name, AssessTemplateNumber, SetId, and StatusCode. Also run the
documented live exact-name lookup.
- Reconcile the proposed exact name against both sources. Continue only when
both return zero matches. One match in either source is a duplicate;
disagreement is stale or incomplete evidence and requires a fresh export;
multiple matches are ambiguous and block the operation.
- Use the validated ZIP only as the target environment's schema, column,
metadata, and relationship reference. Construct a new package containing
exactly one proposed Lead template and its dependency closure. Generate new
identifiers; never carry another template's rows, identifiers, audit values,
or unrelated setup records into the import package.
- Route the proposed package through
shared.validation.setup-data-validator
and shared.validation.reference-data-validator, then apply the task-local
graph through its data_loader_ready terminal. This validates the final
archive for handoff but does not create an import approval.
- Hand the final validated ZIP, task context, task name, sequence, and exact
package SHA-256 to
core.data-loader only when the task graph reaches
data_loader_ready. The task graph does not approve or execute the import.
- Let Data Loader invoke Task Hook
data-load, evaluate this task registry,
and build its immutable approval preview for the final archive. Include the
environment, release, export ProcessId/hash, inventory count, duplicate
evidence, package hash/rows, template design, set decision, and validation
results. Stop and require the user's later standalone approve message.
- After approval, let Data Loader revalidate the same archive, verify its
SHA-256, create the
taskValidationEnvelope, and pass that envelope to its
upload/initiation workflow. The archive contains
ASM_SETUP_CSV_METADATA.xml, so Data Loader must preserve it unchanged and
submit it with sourceType: FSM. Do not call a shared import script,
setupTaskCSVImports, UCM, or an initiation endpoint from this task skill.
- Treat accepted Data Loader initiation as terminal for that request. Do not
poll automatically. When the user later asks for status or results, use
Data Loader status handling to retrieve data-set errors and the FSM
ProcessLog, then verify the template with a new exact-name read or export.
Never retry an import automatically.
The export invocation must carry the selected project and target environment
through the shared authentication/export contracts. Its task arguments are:
--task-code MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE
--offering-name Sales
--functional-area-name Leads
--project-id {project_id}
Do not add --template-only. Treat an export created during the current Create,
Copy, or Review run as fresh. An older or user-supplied archive requires an
explicit offline/fallback decision and must still pass environment, release,
task, scope, integrity, and live-lookup checks.
The required current-data export contains exactly these members:
MOW_ASSESSMENT_TEMPLATE.csv
ORA_CRM_ASSESSMENT_TEMPLATE_FOR_RATING.csv
ORA_CRM_ASSESSMENT_TEMPLATE_RATING.csv
ORA_CRM_ASSESSMENT_ATTRIBUTE_GROUP.csv
ORA_CRM_ASSESSMENT_ATTRIBUTE.csv
ORA_CRM_ASSESSMENT_ATTRIBUTE_VALUE.csv
ORA_CRM_ASSESSMENT_SCORE_RANGE.csv
ASM_SETUP_CSV_METADATA.xml
The new package must retain those filenames and metadata structure. CSV header
order comes from the fresh export and must not be guessed or normalized.
User-Supplied ZIP Fallback
A user-supplied export is a fallback only when automatic export fails and the
user explicitly chooses offline continuation, or when the user explicitly asks
to work offline. Validate its task code, environment, release, LEAD scope,
member list, headers, integrity, and freshness before use. A ZIP from another
environment or release is not valid reference evidence without a new explicit
decision and validation; it never substitutes for the live duplicate lookup.
Other Supported Operations
Copy: export and resolve the source exactly, then create a new package with
new identifiers and a distinct name. Never modify a deployed source.
Review: export current data and reconcile it with the live exact-name result;
do not prepare or import a mutation package unless the user changes scope.
Deploy: provide read-only deployment-readiness review only. Actual
deployment is refused because this task does not yet have a validated FSM
package contract for the status transition; never substitute REST, browser,
or assisted Setup and Maintenance mutation.
Routing Metadata
CSVExportImportSupportedFlag is Y, so use these routes:
- Export with
shared.setup-export.task-level-export.
- Validate with
shared.validation.setup-data-validator.
- Validate reference data with
shared.validation.reference-data-validator.
- Gate and execute an approved import only through
core.data-loader.
Do not invoke shared.setup-import.task-level-import, its scripts,
setupTaskCSVImports, or a direct import endpoint. Data Loader is the mandatory
orchestrator and owns final-archive validation, Task Hook evaluation, immutable
preview, standalone approval, approval-envelope verification, upload, and FSM
initiation. Do not add task-local authentication or import code.
Use this task metadata when invoking those skills:
- Offering:
Sales
- Functional area / Setup Object:
Leads
- Setup task name:
Manage Sales Lead Qualification Template
- Setup task code:
MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE
Task-Local Rule Workflow
Use the task-local ora-resource/ rules after the fresh export is available and
before any preview or import handoff. The supported operations are Create,
Copy, Review, and Deploy.
- Validate the requested operation, template identity, reference-data set,
ratings, question groups, questions, weights, responses, and score ranges.
- Confirm the questionnaire design and reference-data-set scope are ready.
- Reconcile the exported inventory with the documented read-only assessment-
template lookup.
- Apply package-isolation, duplicate, deployed-template, score-model,
reference-data-set, and immutable-preview design gates.
- Route a validated Create or Copy package to the Data Loader approval gate,
return Review or Deploy-readiness results as read-only, and block any actual
Deploy mutation until an export-derived Data Loader contract is documented.
The task-local rule graph never authorizes a REST write, browser/assisted
deployment, or direct import.
It may orchestrate read-only export and lookup operations and return a validated
final FSM archive to Data Loader. A Create or Copy import executes only after
core.data-loader independently builds its preview, receives the later
standalone approval, verifies the unchanged archive, and produces the matching
Task Hook approval envelope. No task-local rule or implicit approval may bypass
that boundary.
Failure and Recovery
Load and apply ora-resource/ora_error_handling.md before export, preview, or
Data Loader handoff. Classify failures as input validation, catalog mismatch,
authentication or authorization, transport or environment, Fusion API,
process timeout, process failure, artifact persistence, approval blocker,
verification mismatch, or partial completion.
Allow only the owning shared/core client's documented single cached-token
refresh for an eligible read. Never retry or resubmit an export, upload,
import, deployment, POST, PATCH, or DELETE automatically. On timeout, stop and
report the environment, task code, ProcessId or request ID, last status,
elapsed wait, and exact resume path. Preserve successful outputs and list
failed or unattempted units instead of presenting partial work as complete.
Persist sanitized diagnostics and available ProcessLog or status evidence with
the failure class, stage, external identifiers, and one safe next action. Do
not issue automatic compensation. Redact and never print or persist
credentials, bearer tokens, authorization headers, client secrets, token-cache
content, private keys, full base64 payloads, or sensitive customer details.
Oracle Documentation Sources
Follow-On Scope
Assigning a deployed qualification template to lead profile options is outside
this task-local graph. Route that later work to MKL_MANAGE_SALES_LEAD_PROFILE_OPTIONS
when the Leads implementation is expanded; do not start that setup task from
this skill's rule registry.
Inputs
implementation_objective
project_context
setup_task_scope
setup_data_artifacts
fusion_environment_context: selected environment URL/identity and release;
credentials remain in the core authentication service
operation: Create, Copy, Review, or Deploy
template_identity: template name and, for Copy, the source and new names
reference_data_set: template set and intended business-unit coverage
ratings
question_groups
questions
question_weights
responses
score_ranges
task_template_associations_optional
execution_approval: absent until the user approves the immutable preview
Outputs
setup_task_plan
setup_data_routing
validation_checkpoints
current_template_reference_export: ZIP, ProcessId, SHA-256, environment,
release, and freshness evidence
lead_template_inventory
duplicate_reconciliation_result
validated_single_template_import_package: exact ZIP and SHA-256
immutable_import_preview
import_handoff_result
post_import_verification
skill_run_record
token_usage_record
Implementation Notes
Use the parent functional-area skill cx.sales.leads for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.
1---2skill_id: "cx.sales.leads.manage-sales-lead-qualification-template"3name: manage-sales-lead-qualification-template-setup-task-guidance4description: "Exports current Lead qualification templates, reconciles duplicate evidence, validates a reference-derived single-template FSM package, and hands the final archive to core.data-loader for its separate approval and import lifecycle."5layer: "pillar"6pillar: "CX"7offering: "Sales"8functional_area: "Leads"9functional_area_code: "ORA_LDS_LEADS"10task_code: "MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE"11task_name: "Manage Sales Lead Qualification Template"12parent_skill_id: "cx.sales.leads"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: "planning"20execution_mode: "hybrid"21owner_team: "CX sales pillar team"22version: "0.6.1"23inputs:24 - "implementation_objective"25 - "project_context"26 - "setup_task_scope"27 - "setup_data_artifacts"28 - "fusion_environment_context"29 - "operation"30 - "template_design"31 - "reference_data_set_decision"32 - "execution_approval"33 - "task_context_path"34 - "task_sequence"35outputs:36 - "setup_task_plan"37 - "setup_data_routing"38 - "validation_checkpoints"39 - "current_template_reference_export"40 - "lead_template_inventory"41 - "duplicate_reconciliation_result"42 - "validated_single_template_import_package"43 - "immutable_import_preview"44 - "data_loader_task_validation_result"45 - "data_loader_approval_preview"46 - "task_validation_envelope"47 - "data_load_initiation_result"48 - "import_handoff_result"49 - "post_import_verification"50 - "skill_run_record"51 - "token_usage_record"52depends_on:53 - "shared.setup-export.task-level-export"54 - "shared.validation.setup-data-validator"55 - "shared.validation.reference-data-validator"56 - "core.data-loader"57uses_core:58 - "core.project-mgmt.artifact-version-manager"59 - "core.project-mgmt.artifact-registry-manager"60 - "core.project-mgmt.project-state-manager"61persists_project_state: true62token_usage_tracking:63 enabled: true64 granularity: "per_skill_run"65 artifact_type: "token_usage_record"66 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"67 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"68 required_fields:69 - "activity_start_time"70 - "skill_id"71 - "task"72 - "trigger"73 - "artifacts_written"74 - "files_read"75 - "estimated_input_tokens"76 - "estimated_output_tokens"77 - "estimated_total_tokens"78 - "estimation_method"79 - "notes"80state_updates:81 - "setup_task_sequence"82 - "configuration_blueprints"83 - "validation_results"84 - "token_usage_records"85workspace_outputs:86 - artifact_type: "configuration_blueprint"87 default_location: "project/{project_id}/artifacts/pillars/cx/sales/leads/manage-sales-lead-qualification-template/current/"88 versioning_policy: "major-new-version-minor-confirm-update"89 - artifact_type: "validation_result"90 default_location: "project/{project_id}/artifacts/pillars/cx/sales/leads/manage-sales-lead-qualification-template/current/"91 versioning_policy: "major-new-version-minor-confirm-update"92 - artifact_type: "skill_run"93 default_location: "project/{project_id}/state/runs/"94 versioning_policy: "append-only"95 - artifact_type: "token_usage_record"96 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"97 versioning_policy: "append-only"98applicability:99 industries:100 - "All"101 countries:102 - "All"103 fusion_releases:104 - "Current Oracle Fusion Cloud release"105side_effects:106 - "Submits and downloads a read-only task-level CSV export from the selected Oracle Fusion environment."107 - "Reads the assessmentTemplatesLOV endpoint to reconcile exact Lead template-name matches."108 - "Persists reference exports, validation evidence, previews, and approved import results in the implementation project workspace."109 - "After the separate core.data-loader preview and approval lifecycle, uploads and initiates the unchanged FSM ZIP through core.data-loader."110required_privileges:111 - "Access to the selected Oracle Fusion environment and privileges to export setup task data."112 - "Privileges to read Assessment Templates list-of-values data."113 - "Privileges required by core.data-loader for an explicitly approved FSM import."114metadata:115 source: https://skillmd.com/skills/oracle/manage-sales-lead-qualification-template-setup-task-guidance116---117118# Manage Sales Lead Qualification Template Setup Task Guidance119120## Purpose121122Exports the current Lead qualification-template baseline, validates a new123reference-derived package, reconciles duplicates from both the export and live124REST state, and hands a validated FSM archive to the mandatory Data Loader125approval and import lifecycle.126127## Setup Task Skill Contract128129- task_code: `MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE`130- task_name: `Manage Sales Lead Qualification Template`131- parent_skill_id: `cx.sales.leads`132- pillar: `CX`133- offering: `Sales`134- functional_area: `Leads`135- functional_area_code: `ORA_LDS_LEADS`136- available_flag: `Y`137- export_import_supported_flag: `Y`138- csv_export_import_supported_flag: `Y`139- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`140141## Usage142143Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage Sales Lead Qualification Template` under `Leads`.144145## Runtime Interface and Handoff146147Apply the parent `cx.sales.leads` runtime-interface guidance. For the normal148workflow, prefer the declared export, validation, read-only lookup, and Data149Loader skill contracts before considering implementation or test source.150151This task hands Data Loader only the task-context path, exact task name,152positive sequence, environment, final ZIP path and SHA-256, operation, template153identity and set, export identity/hash/release, duplicate evidence, row counts,154task-rule results, and `finalData.archiveSha256`. Data Loader owns its preview,155approval record, `taskValidationEnvelope`, authentication, upload, and156initiation structures. If a declared interface fails or differs from its157contract, follow the parent's scoped diagnostic escalation and reuse the158resolved interface for the rest of the run.159160## Setup Task Metadata161162- Task name: `Manage Sales Lead Qualification Template`163- Task code: `MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE`164- Available: `Y`165- Export/import supported: `Y`166- CSV export/import supported: `Y`167- CSV export/import routing: `supported`168169## Mandatory Create Workflow170171For `Create`, do not require the user to supply an existing ZIP. Export the172current task data automatically from the selected environment before generating173or approving a new qualification template.1741751. Preflight the target environment identity, task code, catalog flags,176 authentication, export privilege, project destination, and import approval177 state. Never print or persist credentials.1782. Invoke `shared.setup-export.task-level-export` in current-data mode for179 `MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE`; do not use template/spec mode.1803. Capture the export `ProcessId` from either the collection form or181 `SetupTaskCSVExportProcess.items[0].ProcessId`, poll that exact process, and182 download the result from its `enclosure/FileContent` endpoint. Do not infer183 completion from a collection response or download a collection resource.1844. Validate the downloaded ZIP before use: ZIP signature and CRCs, the exact185 required members below, metadata task code, `ObjectType=TASK`,186 `ProcessType=EXPORT`, `ProcessStatus=COMPLETED`, target `ProcessEnv`, target187 Fusion release, and `LEAD` scope. Record its SHA-256 hash and export188 `ProcessId`.1895. Inventory every `LEAD` template from both template CSVs and retain exact190 name, `AssessTemplateNumber`, `SetId`, and `StatusCode`. Also run the191 documented live exact-name lookup.1926. Reconcile the proposed exact name against both sources. Continue only when193 both return zero matches. One match in either source is a duplicate;194 disagreement is stale or incomplete evidence and requires a fresh export;195 multiple matches are ambiguous and block the operation.1967. Use the validated ZIP only as the target environment's schema, column,197 metadata, and relationship reference. Construct a new package containing198 exactly one proposed Lead template and its dependency closure. Generate new199 identifiers; never carry another template's rows, identifiers, audit values,200 or unrelated setup records into the import package.2018. Route the proposed package through `shared.validation.setup-data-validator`202 and `shared.validation.reference-data-validator`, then apply the task-local203 graph through its `data_loader_ready` terminal. This validates the final204 archive for handoff but does not create an import approval.2059. Hand the final validated ZIP, task context, task name, sequence, and exact206 package SHA-256 to `core.data-loader` only when the task graph reaches207 `data_loader_ready`. The task graph does not approve or execute the import.20810. Let Data Loader invoke Task Hook `data-load`, evaluate this task registry,209 and build its immutable approval preview for the final archive. Include the210 environment, release, export ProcessId/hash, inventory count, duplicate211 evidence, package hash/rows, template design, set decision, and validation212 results. Stop and require the user's later standalone `approve` message.21311. After approval, let Data Loader revalidate the same archive, verify its214 SHA-256, create the `taskValidationEnvelope`, and pass that envelope to its215 upload/initiation workflow. The archive contains216 `ASM_SETUP_CSV_METADATA.xml`, so Data Loader must preserve it unchanged and217 submit it with `sourceType: FSM`. Do not call a shared import script,218 `setupTaskCSVImports`, UCM, or an initiation endpoint from this task skill.21912. Treat accepted Data Loader initiation as terminal for that request. Do not220 poll automatically. When the user later asks for status or results, use221 Data Loader status handling to retrieve data-set errors and the FSM222 ProcessLog, then verify the template with a new exact-name read or export.223 Never retry an import automatically.224225The export invocation must carry the selected project and target environment226through the shared authentication/export contracts. Its task arguments are:227228```text229--task-code MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE230--offering-name Sales231--functional-area-name Leads232--project-id {project_id}233```234235Do not add `--template-only`. Treat an export created during the current Create,236Copy, or Review run as fresh. An older or user-supplied archive requires an237explicit offline/fallback decision and must still pass environment, release,238task, scope, integrity, and live-lookup checks.239240The required current-data export contains exactly these members:241242- `MOW_ASSESSMENT_TEMPLATE.csv`243- `ORA_CRM_ASSESSMENT_TEMPLATE_FOR_RATING.csv`244- `ORA_CRM_ASSESSMENT_TEMPLATE_RATING.csv`245- `ORA_CRM_ASSESSMENT_ATTRIBUTE_GROUP.csv`246- `ORA_CRM_ASSESSMENT_ATTRIBUTE.csv`247- `ORA_CRM_ASSESSMENT_ATTRIBUTE_VALUE.csv`248- `ORA_CRM_ASSESSMENT_SCORE_RANGE.csv`249- `ASM_SETUP_CSV_METADATA.xml`250251The new package must retain those filenames and metadata structure. CSV header252order comes from the fresh export and must not be guessed or normalized.253254## User-Supplied ZIP Fallback255256A user-supplied export is a fallback only when automatic export fails and the257user explicitly chooses offline continuation, or when the user explicitly asks258to work offline. Validate its task code, environment, release, LEAD scope,259member list, headers, integrity, and freshness before use. A ZIP from another260environment or release is not valid reference evidence without a new explicit261decision and validation; it never substitutes for the live duplicate lookup.262263## Other Supported Operations264265- `Copy`: export and resolve the source exactly, then create a new package with266 new identifiers and a distinct name. Never modify a deployed source.267- `Review`: export current data and reconcile it with the live exact-name result;268 do not prepare or import a mutation package unless the user changes scope.269- `Deploy`: provide read-only deployment-readiness review only. Actual270 deployment is refused because this task does not yet have a validated FSM271 package contract for the status transition; never substitute REST, browser,272 or assisted Setup and Maintenance mutation.273274## Routing Metadata275276`CSVExportImportSupportedFlag` is `Y`, so use these routes:2772781. Export with `shared.setup-export.task-level-export`.2792. Validate with `shared.validation.setup-data-validator`.2803. Validate reference data with `shared.validation.reference-data-validator`.2814. Gate and execute an approved import only through `core.data-loader`.282283Do not invoke `shared.setup-import.task-level-import`, its scripts,284`setupTaskCSVImports`, or a direct import endpoint. Data Loader is the mandatory285orchestrator and owns final-archive validation, Task Hook evaluation, immutable286preview, standalone approval, approval-envelope verification, upload, and FSM287initiation. Do not add task-local authentication or import code.288289Use this task metadata when invoking those skills:290291- Offering: `Sales`292- Functional area / Setup Object: `Leads`293- Setup task name: `Manage Sales Lead Qualification Template`294- Setup task code: `MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE`295296## Task-Local Rule Workflow297298Use the task-local `ora-resource/` rules after the fresh export is available and299before any preview or import handoff. The supported operations are `Create`,300`Copy`, `Review`, and `Deploy`.3013021. Validate the requested operation, template identity, reference-data set,303 ratings, question groups, questions, weights, responses, and score ranges.3042. Confirm the questionnaire design and reference-data-set scope are ready.3053. Reconcile the exported inventory with the documented read-only assessment-306 template lookup.3074. Apply package-isolation, duplicate, deployed-template, score-model,308 reference-data-set, and immutable-preview design gates.3095. Route a validated Create or Copy package to the Data Loader approval gate,310 return Review or Deploy-readiness results as read-only, and block any actual311 Deploy mutation until an export-derived Data Loader contract is documented.312313The task-local rule graph never authorizes a REST write, browser/assisted314deployment, or direct import.315It may orchestrate read-only export and lookup operations and return a validated316final FSM archive to Data Loader. A Create or Copy import executes only after317`core.data-loader` independently builds its preview, receives the later318standalone approval, verifies the unchanged archive, and produces the matching319Task Hook approval envelope. No task-local rule or implicit approval may bypass320that boundary.321322## Failure and Recovery323324Load and apply `ora-resource/ora_error_handling.md` before export, preview, or325Data Loader handoff. Classify failures as input validation, catalog mismatch,326authentication or authorization, transport or environment, Fusion API,327process timeout, process failure, artifact persistence, approval blocker,328verification mismatch, or partial completion.329330Allow only the owning shared/core client's documented single cached-token331refresh for an eligible read. Never retry or resubmit an export, upload,332import, deployment, POST, PATCH, or DELETE automatically. On timeout, stop and333report the environment, task code, ProcessId or request ID, last status,334elapsed wait, and exact resume path. Preserve successful outputs and list335failed or unattempted units instead of presenting partial work as complete.336337Persist sanitized diagnostics and available ProcessLog or status evidence with338the failure class, stage, external identifiers, and one safe next action. Do339not issue automatic compensation. Redact and never print or persist340credentials, bearer tokens, authorization headers, client secrets, token-cache341content, private keys, full base64 payloads, or sensitive customer details.342343## Oracle Documentation Sources344345- [Create a Lead Qualification Template](https://docs.oracle.com/en/cloud/saas/sales/fadsi/create-a-lead-qualification-template.html)346- [Lead Qualification Templates](https://docs.oracle.com/en/cloud/saas/sales/oasal/lead-qualification-templates.html)347- [Assessment Templates REST Endpoints](https://docs.oracle.com/en/cloud/saas/sales/faaps/api-list-values-assessment-templates.html)348349## Follow-On Scope350351Assigning a deployed qualification template to lead profile options is outside352this task-local graph. Route that later work to `MKL_MANAGE_SALES_LEAD_PROFILE_OPTIONS`353when the Leads implementation is expanded; do not start that setup task from354this skill's rule registry.355356357## Inputs358359- `implementation_objective`360- `project_context`361- `setup_task_scope`362- `setup_data_artifacts`363- `fusion_environment_context`: selected environment URL/identity and release;364 credentials remain in the core authentication service365- `operation`: `Create`, `Copy`, `Review`, or `Deploy`366- `template_identity`: template name and, for `Copy`, the source and new names367- `reference_data_set`: template set and intended business-unit coverage368- `ratings`369- `question_groups`370- `questions`371- `question_weights`372- `responses`373- `score_ranges`374- `task_template_associations_optional`375- `execution_approval`: absent until the user approves the immutable preview376377## Outputs378379- `setup_task_plan`380- `setup_data_routing`381- `validation_checkpoints`382- `current_template_reference_export`: ZIP, ProcessId, SHA-256, environment,383 release, and freshness evidence384- `lead_template_inventory`385- `duplicate_reconciliation_result`386- `validated_single_template_import_package`: exact ZIP and SHA-256387- `immutable_import_preview`388- `import_handoff_result`389- `post_import_verification`390- `skill_run_record`391- `token_usage_record`392393## Implementation Notes394395Use the parent functional-area skill `cx.sales.leads` for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.