Sales Motions Guidance and Read Operations
Purpose
Answer source-backed questions about Sales Motions and, when the routed project
workflow selects a live read, list, filter, or retrieve Sales Motions for setup
task CUSTOM_SALES_MOTIONS. Keep executable operations strictly read-only.
Question and Execution Scope
Handle conceptual, model, lifecycle, setup, security, API, live-read,
troubleshooting, import/export, write-support, and help-source questions. Use
the response statuses in
../references/sales-orchestration-question-routing.md so every material part
is answered from source, clarified, routed, marked as a source gap, or refused
safely.
An explanatory question does not authorize authentication or a Fusion call.
Only these live operations are executable:
- list Sales Motions with bounded query parameters;
- get one Sales Motion by exact ID;
- query Sales Motions with the semantically read-only
POST .../salesMotions/$query endpoint.
Treat CREATE, UPDATE, DELETE, PATCH, PUT, and bulk-write requests as
unsupported. Treat every POST as unsupported except the exact documented
salesMotions/$query read endpoint. Do not build a mutation preview, request
mutation approval, or invoke a write endpoint. Data Loader does not currently
support the applicable BOSS REST endpoints. Write support may be introduced
only after that dependency is available and payload, identity, concurrency,
idempotency, approval, retry, diagnostic, and recovery behavior has passed a
reviewed skill revision.
Do not route this task through FSM CSV export or import because both catalog
support flags are N.
Required Read Order
Choose the read path from the user's intent.
For every question:
- Read
../references/sales-orchestration-question-routing.md.
- Classify the subject, question classes, and answer mode before loading OAuth
or execution resources.
- Continue with only the task sources required by the selected classes.
General Question Handling
- For a definition, purpose, business value, use case, strategy scope,
objective, or high-value-activity question, read
references/sales-motions-overview.md.
- For Fusion UI agentic authoring prompt examples, read
references/sales-motions-agentic-prompts.md and follow its Prompt Emission
Rules. Emit concrete, synthetic, copy-ready prompts without user-replacement
placeholders; treat them as UI guidance, not authorization for this skill to
write through BOSS or REST.
- For object-model, field, status, accessor, relationship, lifecycle, or
API-capability questions, read
references/sales-motions-boss-read.md. Return only facts established by the
target-release contract.
- For prerequisites, profile-option readiness, predefined-role enablement,
custom-role provisioning, setup-screen access, roles, duties, privileges,
permission groups, security views, or ESS synchronization, read
references/sales-motions-security.md,
../references/security-console-role-provisioning.md, and
../references/security-synchronization-processes.md in full.
- For input, dependency, lookup, filter, or troubleshooting questions, load only
the applicable file under
ora-resource/ plus the relevant BOSS or security
reference.
- For import, export, bulk, Create, Update, Delete, activation, archive, or other
possible side-effect questions, explain the documented catalog and security
prerequisites, state the Data Loader blocker, and return
UNSUPPORTED for execution.
- For a question spanning Sales Plays, content, Data Capture Rules, or the wider
functional area, route to
cx.sales.sales-orchestration and preserve this
skill's execution boundary.
- If the loaded sources do not establish a business definition, transition,
validation, UI step, integration behavior, or release-specific fact, return
SOURCE_GAP and identify the exact Oracle source or SME confirmation needed.
Do not infer the answer from field names or prior chat history.
For a prerequisite, profile-option, predefined-role enablement, custom-role
provisioning, role, privilege, permission-group, or access question:
- Read
references/sales-motions-security.md in full.
- Read
../references/security-console-role-provisioning.md in full.
- Read
../references/security-synchronization-processes.md in full.
- Return the complete security contract plus target-environment and shared
BOSS OAuth readiness as technical prerequisites for a live read.
- Do not load API execution resources, authenticate, call Fusion, persist a
project artifact, or submit an ESS job unless the user separately requests
an authorized operation.
For a LIST, GET, or QUERY operation:
- Read
ora-resource/ora_input_validation.md.
- Read
ora-resource/ora_dependency_readiness.md.
- Read
ora-resource/ora_reference_lookups.md.
- Read
references/sales-motions-security.md and apply its Read row.
- Read
references/sales-motions-boss-read.md.
- Read
ora-resource/ora_error_handling.md before any live call.
Read Security Boundary
Use either:
- confirmed membership in
ORA_ZBS_SALES_ADMINISTRATOR_JOB; or
- a custom job role containing both documented duty roles, the Sales Motion
read permission groups, and the
All Rows security view.
Treat the documented role and permission groups as prerequisites, not proof of
the acting user's membership. Do not claim membership without authorized
administrator evidence.
A requested read operation may proceed as the effective access check. A
successful LIST, GET, or QUERY response proves read access only for that call.
HTTP 403 proves that the acting user lacks effective read authorization for
that request; it does not identify which role, privilege, permission group, or
security view is missing.
The security reference also documents the Create, Update, and Delete permission
groups so implementers can prepare custom roles. Those grants do not expand
this skill's executable scope.
Security and Prerequisite Questions
When the user asks for Sales Motion prerequisites, the permission-group profile
option, predefined-role enablement, custom-role provisioning, roles, duty
roles, privileges, permission groups, or access requirements, read
references/sales-motions-security.md,
../references/security-console-role-provisioning.md, and
../references/security-synchronization-processes.md in full and return all
of the following:
- the
ORA_ASE_SAS_INTEGRATION_ENABLED Site profile-option requirement;
- the predefined Sales Administrator role permission-group enablement steps;
- the out-of-box Sales Administrator job role;
- both duty roles required on a custom job role and what each enables;
- the setup-screen functional privilege;
- every Read, Create, Update, and Delete BOSS permission group;
- the
All Rows security view requirement;
- the custom-role steps for adding permission groups, security views,
privileges, and duty roles;
- the one-time Retrieve Latest LDAP Changes procedure;
- the daily Import User and Role Application Security Data schedule; and
- the required ordering after Send Pending LDAP Requests.
For a broad prerequisite question, also state that a live read requires a
confirmed target environment and shared BOSS OAuth readiness. Identify any
licensing, feature-opt-in, or offering-configuration prerequisite as
undocumented by the current sources; do not infer one.
Never limit a security or prerequisite answer to the Read permission groups
merely because this skill executes only read operations. Clearly distinguish
complete provisioning guidance from the skill's read-only API boundary. The
skill provides the synchronization-process instructions but does not submit,
schedule, poll, or retry any job.
Authentication and Secret Handling
Use core.fusion-api.rest-api-client and its BOSS client with boss_scope.
Never hand-build an Authorization header.
Ignore passwords, Basic credentials, bearer tokens, refresh tokens, client
secrets, or token-cache contents pasted into a request. Never validate, reuse,
echo, log, persist, or place them in a command, example, diagnostic, artifact,
or tracked file. Let the shared OAuth skill manage the external BOSS profile
cache with --token-cache auto. The cache is scoped to the selected OAuth
profile under ~/.fusionaim/; never store tokens in the checkout or project
workspace or pass a historical repository-local cache path.
Preflight and Controlled Read Workflow
- Confirm the target environment, acting user, and requested LIST, GET, or
QUERY operation.
- For GET, require the exact Sales Motion ID; never infer an ID from display
text.
- For LIST, accept only documented bounded query parameters.
- For QUERY, translate the user's filter, field, child accessor, limit,
offset, total-count, and sort intent into the documented advanced-query
body. Derive intent from the complete request rather than matching a canned
example, and preserve every explicit supported constraint. Keep the limit
bounded and never invent a filter or sort criterion. Ask one short
clarification when a required field, operator, or ordering choice is
ambiguous.
- Validate environment and BOSS OAuth configuration.
- Invoke the selected read operation through the shared client. The QUERY
operation uses POST but remains read-only because its exact path ends in
/salesMotions/$query.
- For LIST or GET, if a cache-managed token receives HTTP 401 or 403,
allow the shared client to refresh once and retry once. For QUERY, the
shared client does not automatically refresh or retry the POST; stop and
report the sanitized authentication or authorization failure.
- Permit a bounded retry only for a known transient read-only transport
failure.
- Return records,
hasMore and totalItems when present, effective-read
status, and sanitized diagnostics.
- When
project_context is supplied, persist only sanitized read validation,
result, diagnostic, and token-usage records.
API Contract
| Action |
Method |
Relative path |
| List |
GET |
/api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesMotions |
| Get |
GET |
/api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesMotions/{salesMotions_id} |
| Advanced query all |
POST, read semantics |
/api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesMotions/$query |
Use the exact target-release OpenAPI contract if it differs from this 26C
summary. Quote shell arguments containing $en or $query.
Inputs
implementation_objective
project_context
fusion_environment_context
acting_user_identity
sales_motion_operation: LIST, GET, or QUERY only
sales_motion_id: required only for GET
sales_motion_query: documented LIST parameters or QUERY body values
sales_motion_question: any explanatory, support, or execution question about
Sales Motions
requested_answer_mode: EXPLAIN, READ, CLARIFY, ROUTE, GAP, or REFUSE
Outputs
question_classification
sales_motion_answer
operation_support_status
source_gap
sales_motion_list
sales_motion_detail
security_prerequisite_summary
effective_read_access_result
diagnostics
skill_run_record
token_usage_record
Failure and Retry Rules
Classify failures as input validation, authentication, authorization or
privilege, transport or environment, Fusion API, artifact persistence, or
unsupported operation.
For LIST or GET, allow one cache-managed 401 or 403 refresh and retry through
the shared BOSS client. For QUERY, stop on 401 or 403 without automatically
refreshing or replaying the POST; a new requested read requires validation
after the authentication or authorization issue is resolved. Retry a
known transient transport failure only within a bounded read-only retry policy.
Do not retry malformed requests or deterministic 4xx responses.
For any mutation request, return UNSUPPORTED, state that this skill revision
is read-only, and stop without previewing or calling Fusion. Do not classify
the exact POST .../salesMotions/$query operation as a mutation.
Help Sources
- Public business overview and conceptual guidance:
references/sales-motions-overview.md
- Fusion UI agentic authoring prompts:
references/sales-motions-agentic-prompts.md
- Complete prerequisite and security matrix:
references/sales-motions-security.md
- Step-by-step Security Console role provisioning:
../references/security-console-role-provisioning.md
- Step-by-step security synchronization processes:
../references/security-synchronization-processes.md
- Read endpoint and command patterns:
references/sales-motions-boss-read.md
- Cross-task question classification and response contract:
../references/sales-orchestration-question-routing.md
Use the parent skill cx.sales.sales-orchestration only for functional-area
scope and cross-task sequencing.
1---2skill_id: "cx.sales.sales-orchestration.sales-motions"3name: sales-motions-guidance-and-read-operations4description: "Answers source-backed questions about Sales Motions, including purpose, setup, lifecycle and status, fields, objectives, high-value activities, agentic UI authoring prompts, relationships, prerequisites, Security Console role provisioning, profile options, roles, privileges, permission groups, API/query behavior, troubleshooting, import/export limits, write-support status, and help sources. Also lists, filters, and retrieves Sales Motions through read-only Fusion BOSS LIST, exact-ID GET, and semantic-read POST $query workflows with OAuth, authorization, retry, and diagnostic guardrails. Use for any Sales Motion question, Fusion UI agentic-authoring prompt example, security-provisioning question, or read request; explain or classify unsupported Create/Update/Delete requests without generating a mutation payload or bypassing the routed workflow."5layer: "pillar"6pillar: "CX"7offering: "Sales"8functional_area: "Sales Orchestration"9functional_area_code: "CUSTOM_SALES_ORCHESTRATION"10task_code: "CUSTOM_SALES_MOTIONS"11task_name: "Sales Motions"12parent_skill_id: "cx.sales.sales-orchestration"13available_flag: "Y"14export_import_supported_flag: "N"15csv_export_import_supported_flag: "N"16source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"17type: "verification"18execution_mode: "hybrid"19owner_team: "CX sales pillar team"20version: "0.8.3"21inputs:22 - "implementation_objective"23 - "project_context"24 - "fusion_environment_context"25 - "acting_user_identity"26 - "sales_motion_operation"27 - "sales_motion_id"28 - "sales_motion_query"29 - "sales_motion_question"30 - "requested_answer_mode"31outputs:32 - "question_classification"33 - "sales_motion_answer"34 - "operation_support_status"35 - "source_gap"36 - "sales_motion_list"37 - "sales_motion_detail"38 - "security_prerequisite_summary"39 - "effective_read_access_result"40 - "diagnostics"41 - "skill_run_record"42 - "token_usage_record"43depends_on:44 - "core.auth.fusion-oauth-authentication"45 - "core.fusion-api.rest-api-client"46uses_core:47 - "core.auth.fusion-oauth-authentication"48 - "core.fusion-api.rest-api-client"49 - "core.project-mgmt.artifact-version-manager"50 - "core.project-mgmt.artifact-registry-manager"51 - "core.project-mgmt.project-state-manager"52persists_project_state: true53token_usage_tracking:54 enabled: true55 granularity: "per_skill_run"56 artifact_type: "token_usage_record"57 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"58 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"59 required_fields:60 - "activity_start_time"61 - "skill_id"62 - "task"63 - "trigger"64 - "artifacts_written"65 - "files_read"66 - "estimated_input_tokens"67 - "estimated_output_tokens"68 - "estimated_total_tokens"69 - "estimation_method"70 - "notes"71state_updates:72 - "validation_results"73 - "token_usage_records"74workspace_outputs:75 - artifact_type: "validation_result"76 default_location: "project/{project_id}/artifacts/pillars/cx/sales/sales-orchestration/sales-motions/current/"77 versioning_policy: "major-new-version-minor-confirm-update"78 - artifact_type: "skill_run"79 default_location: "project/{project_id}/state/runs/"80 versioning_policy: "append-only"81 - artifact_type: "token_usage_record"82 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"83 versioning_policy: "append-only"84oracle_supplied_guidance_files:85 - purpose: "Sales Motion read-operation input validation"86 location: "ora-resource/ora_input_validation.md"87 - purpose: "Sales Motion environment and OAuth readiness"88 location: "ora-resource/ora_dependency_readiness.md"89 - purpose: "Sales Motion list, get, and advanced-query lookup contracts"90 location: "ora-resource/ora_reference_lookups.md"91 - purpose: "Sales Motion read error handling and refusal rules"92 location: "ora-resource/ora_error_handling.md"93oracle_supplied_guidance_status:94 access_verification: "Effective read access is established only by a successful requested LIST, GET, or QUERY; role and permission-group membership remain unknown without authorized administrator evidence"95 boss_read_contract: "Verified against the 26C internal BOSS OpenAPI source"96 security_contract: "Complete guidance includes the site profile option, predefined-role enablement, custom-role Security Console steps, two custom-job-role duties, setup-screen privilege, read/create/update/delete permission groups, All Rows security view, synchronization procedures, and effective-access verification boundaries; this skill executes read operations only"97applicability:98 industries:99 - "All"100 countries:101 - "All"102 fusion_releases:103 - "Oracle Fusion Cloud Applications 26C"104 - "Later releases after endpoint contract verification"105side_effects:106 - "Reads Sales Motion setup data through Fusion BOSS REST APIs."107 - "May refresh the managed external BOSS OAuth profile cache once after a cache-managed 401 or 403 response to LIST or GET; QUERY is not automatically retried."108required_privileges:109 - "ORA_ZBS_SALES_ADMINISTRATOR_JOB, or a custom job role with ORA_DR_FAI_GENERATIVE_AI_AGENT_RUNTIME_DUTY and ORA_ZCA_ACCESS_GROUPS_ENABLEMENT_DUTY"110 - "The custom job role also needs the documented operation-specific Sales Motion permission groups and All Rows security view"111 - "ZCA_VIEW_SALES_MOTIONS_PRIV for access to the Sales Motions setup screen"112metadata:113 source: https://skillmd.com/skills/oracle/sales-motions-guidance-and-read-operations114---115116# Sales Motions Guidance and Read Operations117118## Purpose119120Answer source-backed questions about Sales Motions and, when the routed project121workflow selects a live read, list, filter, or retrieve Sales Motions for setup122task `CUSTOM_SALES_MOTIONS`. Keep executable operations strictly read-only.123124## Question and Execution Scope125126Handle conceptual, model, lifecycle, setup, security, API, live-read,127troubleshooting, import/export, write-support, and help-source questions. Use128the response statuses in129`../references/sales-orchestration-question-routing.md` so every material part130is answered from source, clarified, routed, marked as a source gap, or refused131safely.132133An explanatory question does not authorize authentication or a Fusion call.134Only these live operations are executable:135136- list Sales Motions with bounded query parameters;137- get one Sales Motion by exact ID;138- query Sales Motions with the semantically read-only139 `POST .../salesMotions/$query` endpoint.140141Treat `CREATE`, `UPDATE`, `DELETE`, `PATCH`, `PUT`, and bulk-write requests as142unsupported. Treat every `POST` as unsupported except the exact documented143`salesMotions/$query` read endpoint. Do not build a mutation preview, request144mutation approval, or invoke a write endpoint. Data Loader does not currently145support the applicable BOSS REST endpoints. Write support may be introduced146only after that dependency is available and payload, identity, concurrency,147idempotency, approval, retry, diagnostic, and recovery behavior has passed a148reviewed skill revision.149150Do not route this task through FSM CSV export or import because both catalog151support flags are `N`.152153## Required Read Order154155Choose the read path from the user's intent.156157For every question:1581591. Read `../references/sales-orchestration-question-routing.md`.1602. Classify the subject, question classes, and answer mode before loading OAuth161 or execution resources.1623. Continue with only the task sources required by the selected classes.163164## General Question Handling165166- For a definition, purpose, business value, use case, strategy scope,167 objective, or high-value-activity question, read168 `references/sales-motions-overview.md`.169- For Fusion UI agentic authoring prompt examples, read170 `references/sales-motions-agentic-prompts.md` and follow its Prompt Emission171 Rules. Emit concrete, synthetic, copy-ready prompts without user-replacement172 placeholders; treat them as UI guidance, not authorization for this skill to173 write through BOSS or REST.174- For object-model, field, status, accessor, relationship, lifecycle, or175 API-capability questions, read176 `references/sales-motions-boss-read.md`. Return only facts established by the177 target-release contract.178- For prerequisites, profile-option readiness, predefined-role enablement,179 custom-role provisioning, setup-screen access, roles, duties, privileges,180 permission groups, security views, or ESS synchronization, read181 `references/sales-motions-security.md`,182 `../references/security-console-role-provisioning.md`, and183 `../references/security-synchronization-processes.md` in full.184- For input, dependency, lookup, filter, or troubleshooting questions, load only185 the applicable file under `ora-resource/` plus the relevant BOSS or security186 reference.187- For import, export, bulk, Create, Update, Delete, activation, archive, or other188 possible side-effect questions, explain the documented catalog and security189 prerequisites, state the Data Loader blocker, and return190 `UNSUPPORTED` for execution.191- For a question spanning Sales Plays, content, Data Capture Rules, or the wider192 functional area, route to `cx.sales.sales-orchestration` and preserve this193 skill's execution boundary.194- If the loaded sources do not establish a business definition, transition,195 validation, UI step, integration behavior, or release-specific fact, return196 `SOURCE_GAP` and identify the exact Oracle source or SME confirmation needed.197 Do not infer the answer from field names or prior chat history.198199For a prerequisite, profile-option, predefined-role enablement, custom-role200provisioning, role, privilege, permission-group, or access question:2012021. Read `references/sales-motions-security.md` in full.2032. Read `../references/security-console-role-provisioning.md` in full.2043. Read `../references/security-synchronization-processes.md` in full.2054. Return the complete security contract plus target-environment and shared206 BOSS OAuth readiness as technical prerequisites for a live read.2075. Do not load API execution resources, authenticate, call Fusion, persist a208 project artifact, or submit an ESS job unless the user separately requests209 an authorized operation.210211For a LIST, GET, or QUERY operation:2122131. Read `ora-resource/ora_input_validation.md`.2142. Read `ora-resource/ora_dependency_readiness.md`.2153. Read `ora-resource/ora_reference_lookups.md`.2164. Read `references/sales-motions-security.md` and apply its Read row.2175. Read `references/sales-motions-boss-read.md`.2186. Read `ora-resource/ora_error_handling.md` before any live call.219220## Read Security Boundary221222Use either:223224- confirmed membership in `ORA_ZBS_SALES_ADMINISTRATOR_JOB`; or225- a custom job role containing both documented duty roles, the Sales Motion226 read permission groups, and the `All Rows` security view.227228Treat the documented role and permission groups as prerequisites, not proof of229the acting user's membership. Do not claim membership without authorized230administrator evidence.231232A requested read operation may proceed as the effective access check. A233successful LIST, GET, or QUERY response proves read access only for that call.234HTTP 403 proves that the acting user lacks effective read authorization for235that request; it does not identify which role, privilege, permission group, or236security view is missing.237238The security reference also documents the Create, Update, and Delete permission239groups so implementers can prepare custom roles. Those grants do not expand240this skill's executable scope.241242## Security and Prerequisite Questions243244When the user asks for Sales Motion prerequisites, the permission-group profile245option, predefined-role enablement, custom-role provisioning, roles, duty246roles, privileges, permission groups, or access requirements, read247`references/sales-motions-security.md`,248`../references/security-console-role-provisioning.md`, and249`../references/security-synchronization-processes.md` in full and return all250of the following:251252- the `ORA_ASE_SAS_INTEGRATION_ENABLED` Site profile-option requirement;253- the predefined Sales Administrator role permission-group enablement steps;254- the out-of-box Sales Administrator job role;255- both duty roles required on a custom job role and what each enables;256- the setup-screen functional privilege;257- every Read, Create, Update, and Delete BOSS permission group;258- the `All Rows` security view requirement;259- the custom-role steps for adding permission groups, security views,260 privileges, and duty roles;261- the one-time **Retrieve Latest LDAP Changes** procedure;262- the daily **Import User and Role Application Security Data** schedule; and263- the required ordering after **Send Pending LDAP Requests**.264265For a broad prerequisite question, also state that a live read requires a266confirmed target environment and shared BOSS OAuth readiness. Identify any267licensing, feature-opt-in, or offering-configuration prerequisite as268undocumented by the current sources; do not infer one.269270Never limit a security or prerequisite answer to the Read permission groups271merely because this skill executes only read operations. Clearly distinguish272complete provisioning guidance from the skill's read-only API boundary. The273skill provides the synchronization-process instructions but does not submit,274schedule, poll, or retry any job.275276## Authentication and Secret Handling277278Use `core.fusion-api.rest-api-client` and its BOSS client with `boss_scope`.279Never hand-build an Authorization header.280281Ignore passwords, Basic credentials, bearer tokens, refresh tokens, client282secrets, or token-cache contents pasted into a request. Never validate, reuse,283echo, log, persist, or place them in a command, example, diagnostic, artifact,284or tracked file. Let the shared OAuth skill manage the external BOSS profile285cache with `--token-cache auto`. The cache is scoped to the selected OAuth286profile under `~/.fusionaim/`; never store tokens in the checkout or project287workspace or pass a historical repository-local cache path.288289## Preflight and Controlled Read Workflow2902911. Confirm the target environment, acting user, and requested LIST, GET, or292 QUERY operation.2932. For GET, require the exact Sales Motion ID; never infer an ID from display294 text.2953. For LIST, accept only documented bounded query parameters.2964. For QUERY, translate the user's filter, field, child accessor, limit,297 offset, total-count, and sort intent into the documented advanced-query298 body. Derive intent from the complete request rather than matching a canned299 example, and preserve every explicit supported constraint. Keep the limit300 bounded and never invent a filter or sort criterion. Ask one short301 clarification when a required field, operator, or ordering choice is302 ambiguous.3035. Validate environment and BOSS OAuth configuration.3046. Invoke the selected read operation through the shared client. The QUERY305 operation uses POST but remains read-only because its exact path ends in306 `/salesMotions/$query`.3077. For LIST or GET, if a cache-managed token receives HTTP 401 or 403,308 allow the shared client to refresh once and retry once. For QUERY, the309 shared client does not automatically refresh or retry the POST; stop and310 report the sanitized authentication or authorization failure.3118. Permit a bounded retry only for a known transient read-only transport312 failure.3139. Return records, `hasMore` and `totalItems` when present, effective-read314 status, and sanitized diagnostics.31510. When `project_context` is supplied, persist only sanitized read validation,316 result, diagnostic, and token-usage records.317318## API Contract319320| Action | Method | Relative path |321|---|---|---|322| List | GET | /api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesMotions |323| Get | GET | /api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesMotions/{salesMotions_id} |324| Advanced query all | POST, read semantics | /api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesMotions/$query |325326Use the exact target-release OpenAPI contract if it differs from this 26C327summary. Quote shell arguments containing `$en` or `$query`.328329## Inputs330331- `implementation_objective`332- `project_context`333- `fusion_environment_context`334- `acting_user_identity`335- `sales_motion_operation`: LIST, GET, or QUERY only336- `sales_motion_id`: required only for GET337- `sales_motion_query`: documented LIST parameters or QUERY body values338- `sales_motion_question`: any explanatory, support, or execution question about339 Sales Motions340- `requested_answer_mode`: EXPLAIN, READ, CLARIFY, ROUTE, GAP, or REFUSE341342## Outputs343344- `question_classification`345- `sales_motion_answer`346- `operation_support_status`347- `source_gap`348- `sales_motion_list`349- `sales_motion_detail`350- `security_prerequisite_summary`351- `effective_read_access_result`352- `diagnostics`353- `skill_run_record`354- `token_usage_record`355356## Failure and Retry Rules357358Classify failures as input validation, authentication, authorization or359privilege, transport or environment, Fusion API, artifact persistence, or360unsupported operation.361362For LIST or GET, allow one cache-managed 401 or 403 refresh and retry through363the shared BOSS client. For QUERY, stop on 401 or 403 without automatically364refreshing or replaying the POST; a new requested read requires validation365after the authentication or authorization issue is resolved. Retry a366known transient transport failure only within a bounded read-only retry policy.367Do not retry malformed requests or deterministic 4xx responses.368369For any mutation request, return `UNSUPPORTED`, state that this skill revision370is read-only, and stop without previewing or calling Fusion. Do not classify371the exact `POST .../salesMotions/$query` operation as a mutation.372373## Help Sources374375- Public business overview and conceptual guidance:376 `references/sales-motions-overview.md`377- Fusion UI agentic authoring prompts: `references/sales-motions-agentic-prompts.md`378- Complete prerequisite and security matrix:379 `references/sales-motions-security.md`380- Step-by-step Security Console role provisioning:381 `../references/security-console-role-provisioning.md`382- Step-by-step security synchronization processes:383 `../references/security-synchronization-processes.md`384- Read endpoint and command patterns: `references/sales-motions-boss-read.md`385- Cross-task question classification and response contract:386 `../references/sales-orchestration-question-routing.md`387388Use the parent skill `cx.sales.sales-orchestration` only for functional-area389scope and cross-task sequencing.