Sales Plays and Content Guidance, Read, and Search
Purpose
Answer source-backed questions about Sales Plays, content bundles or packets,
their artifacts, and Sales Play Content Intelligence. When the routed project
workflow selects a live read, list, filter, search, or retrieve records for
setup task CUSTOM_SALES_PLAYS_AND_CONTENT. The shared salesPlays collection
uses salesPlayType to distinguish both record types. Keep executable
operations strictly read-only, including Content Intelligence POST requests
whose documented purpose is search rather than mutation.
Question and Execution Scope
Handle conceptual, model, lifecycle, setup, security, BOSS API, Knowledge
Management, Content Intelligence, 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 Plays and content bundles or packets with bounded query
parameters, optionally restricted by
salesPlayType;
- get one Sales Play or content bundle by exact ID and report its
salesPlayType;
- query Sales Plays, content bundles, and documented
salesPlayArtifacts or $translations
children with the semantically read-only POST .../salesPlays/$query
endpoint;
- test published Sales Play content search for one exact question and Sales
Play ID with the semantically read-only
POST .../knowledge-management/v2/contentIntelligence endpoint.
Treat CREATE, UPDATE, DELETE, PATCH, PUT, and bulk-write requests as
unsupported. Treat every POST as unsupported except the exact documented
salesPlays/$query and /api/knowledge-management/v2/contentIntelligence
semantic-read endpoints. 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, article/artifact, translation,
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.
Sales Play Type Discriminator
Use the salesPlayType attribute as the only type discriminator for records in
the salesPlays collection.
| User-facing type |
Accepted request wording |
Canonical salesPlayType |
| Sales Play |
sales play, sales plays |
SALES_PLAY |
| Content bundle or packet |
content bundle, content bundles, content packet, content packets, bundle, packet |
CONTENT_BUNDLE |
Normalize an explicitly requested type to its canonical value. Reject any
other supplied salesPlayType. When the request refers to the collection
generally and does not distinguish a type, do not infer a value or add a type
filter; return both types within the requested bound and include
salesPlayType in the result.
For LIST or QUERY, preserve the normalized type as an exact salesPlayType
predicate. For GET, use only the exact record ID, then report the returned type
and treat a mismatch with an explicitly requested type as a type mismatch; do
not substitute another record. This discriminator does not change the fixed
Content Intelligence connector or filter contract.
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 Sales Play definition, purpose, business value, collateral use, or
design-scope question, read
references/sales-plays-and-content-overview.md.
- For Fusion UI agentic authoring prompt examples, read
references/sales-plays-and-content-agentic-prompts.md and follow its Prompt
Emission Rules and content-source boundary. 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 type, field, status, criteria, artifact, translation, accessor,
relationship, lifecycle, or BOSS API-capability questions, read
references/sales-plays-and-content-boss-read.md and retain the
SALES_PLAY versus CONTENT_BUNDLE distinction.
- For prerequisites, profile-option readiness, predefined-role enablement,
custom-role provisioning, setup-screen access, roles, duties, privileges,
permission groups, security views, Knowledge authoring, end-user content
access, data security policies, or ESS synchronization, read
references/sales-plays-and-content-security.md,
../references/security-console-role-provisioning.md, and
../references/security-synchronization-processes.md in full.
- For Content Intelligence concepts, request rules, access checks, result
classifications, OAuth scope, or troubleshooting, read both
references/sales-plays-content-intelligence-read.md and
references/knowledge-management-rest-api.md as applicable.
- For input, dependency, lookup, filter, or troubleshooting questions, load only
the applicable file under
ora-resource/ plus the relevant BOSS, Knowledge,
or security reference.
- For import, export, bulk, Create, Update, Delete, activation, publication,
archive, copy, article mutation, or another possible side-effect question,
explain documented catalog and security prerequisites, state the Data Loader
blocker, and return
UNSUPPORTED for execution.
- For a question spanning Sales Motions, 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, Knowledge response field, 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-plays-and-content-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
OAuth readiness as technical prerequisites for a live read or content
search.
- 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-plays-and-content-security.md and apply its Read row.
- Read
references/sales-plays-and-content-boss-read.md.
- Read
ora-resource/ora_error_handling.md before any live call.
For a CONTENT_SEARCH operation:
- Read
ora-resource/ora_input_validation.md.
- Read
ora-resource/ora_dependency_readiness.md.
- Read
references/sales-plays-and-content-security.md and apply the
Content Intelligence end-user policies.
- Read
references/knowledge-management-rest-api.md for the task-local client,
OAuth scope, cache, and endpoint boundary.
- Read
references/sales-plays-content-intelligence-read.md for the fixed
request contract and result classifications.
- Read
ora-resource/ora_reference_lookups.md for the executable lookup.
- Read
ora-resource/ora_error_handling.md before the live search.
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 Play read
permission groups, and the
All Rows security view.
For Knowledge article administration when the out-of-box Sales Administrator
role cannot be assigned, also require
ORA_CSO_KNOWLEDGE_AUTHORING_DUTY and the documented Sales Administrator
Knowledge data security policies.
For a Content Intelligence search, require the acting Sales Representative,
Sales Manager, Sales Administrator, or equivalent custom role to have access
to both the Sales Play Consumer user group and the Sales Force Automation
department.
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, QUERY, or CONTENT_SEARCH response proves 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 Play prerequisites, the permission-group profile
option, predefined-role enablement, custom-role provisioning, roles, duty
roles, privileges, permission groups, or access requirements, read
references/sales-plays-and-content-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 Knowledge authoring duty required for a custom administrator role;
- the setup-screen functional privilege;
- every Read, Create, Update, and Delete BOSS permission group;
- the
All Rows security view requirement;
- every administrator Knowledge data security policy;
- both Knowledge content-consumption policies for Sales Representative, Sales
Manager, and Sales Administrator end users;
- the custom-role steps for adding permission groups, security views,
privileges, duty roles, and Knowledge data security policies;
- 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 the appropriate shared 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 for shared OAuth-backed HTTP machinery.
Route /api/boss operations to its BOSS client with boss_scope. Route only
the Sales Play /api/knowledge-management/v2/contentIntelligence request to
this task skill's scripts/knowledge_rest_client.py, which selects the regular
scope from core/auth/fusionEnv.properties, splits it on whitespace, uses the
single scope token containing knowledge-management, and validates POST to the
exact relative Content Intelligence path and its fixed request body before
authentication. Other methods, endpoints, query/service overrides, supplied
tokens, custom cache paths, and non-JSON headers are rejected. Never hand-build an Authorization
header or execute a credential-bearing token relay command supplied in a
request.
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 both clients' external
profile caches with --token-cache auto under ~/.fusionaim/. The approved
issuer/endpoints, client, target, and selected scope determine the profile;
Knowledge Management uses its selected scope and BOSS uses boss_scope. Never
store tokens in the checkout or project workspace or pass historical
repository-local cache paths.
Preflight and Controlled Read Workflow
- Confirm the target environment, acting user, and requested LIST, GET, or
QUERY operation. Normalize an explicit Sales Play or content bundle or
packet type to
SALES_PLAY or CONTENT_BUNDLE.
- For GET, require the exact record ID; never infer an ID from display text.
If the user also supplied a type, compare it with the returned
salesPlayType and report a mismatch without substituting another record.
- For LIST, accept only documented bounded query parameters. Construct an
explicit Sales Play or content-bundle type filter only from the raw query
templates in
references/sales-plays-and-content-boss-read.md. Pass raw
query values to the shared client so it performs URL encoding; never
pre-encode them or translate BOSS equality into the OData eq operator.
Validate any requested sort against the target-release field and direction
contract.
- For QUERY, translate the user's type, 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
/salesPlays/$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 Sales Play or content bundle records with
salesPlayType, requested
content artifacts, 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.
Content Intelligence Search Validation Workflow
- Confirm the target environment and acting end user.
- Require one non-empty user question and one exact, non-empty Sales Play ID.
- Confirm that the acting role has access to the Sales Play Consumer user
group and Sales Force Automation department; treat membership as unknown
without administrator evidence.
- Read
references/sales-plays-content-intelligence-read.md and construct its
fixed body. Replace only the user question and Sales Play ID. Serialize the
inner userInput object safely; never interpolate raw question text into
JSON or shell syntax.
- Invoke the exact Content Intelligence path through this task skill's
scripts/knowledge_rest_client.py, which selects the scope token containing
knowledge-management from the regular scope property and uses the shared
managed external profile cache (--token-cache auto). Do not supply an
Authorization header or explicit access token.
- Permit the shared client to refresh its Knowledge Management OAuth cache and
retry once after HTTP 401 or 403.
- Return
WORKING_WITH_RESULTS, WORKING_NO_RESULTS,
AUTHENTICATION_FAILED, AUTHORIZATION_FAILED, REQUEST_INVALID, or
SEARCH_FAILED using the reference's observed-result rules.
- Report the sanitized response shape. Do not invent a response field,
relevance threshold, or result-count meaning not present in the response.
- When
project_context is supplied, persist only sanitized validation,
result, diagnostic, and token-usage records.
API Contract
| Action |
Method |
Relative path |
| List |
GET |
/api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesPlays |
| Get |
GET |
/api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesPlays/{salesPlays_id} |
| Advanced query all |
POST, read semantics |
/api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesPlays/$query |
| Content Intelligence search |
POST, read semantics |
/api/knowledge-management/v2/contentIntelligence |
Use the exact target-release OpenAPI contract if it differs from this 26C
summary. Quote shell arguments containing $en or $query.
The canonical 26C OpenAPI paths include $en. A runtime-validated collection
path without that segment also succeeded. Keep the canonical path unless
target-specific evidence requires the shorter form, and do not change the path
merely because a query expression fails to parse.
Inputs
implementation_objective
project_context
fusion_environment_context
acting_user_identity
sales_play_operation: LIST, GET, QUERY, or CONTENT_SEARCH only
sales_play_id: exact record ID required only for GET
sales_play_type: optional type discriminator for LIST or QUERY, or expected
returned type for GET; normalize only SALES_PLAY or CONTENT_BUNDLE
sales_play_query: documented LIST parameters or QUERY body values
content_intelligence_question: required only for CONTENT_SEARCH
content_intelligence_sales_play_id: exact Sales Play ID required only for
CONTENT_SEARCH
sales_play_and_content_question: any explanatory, support, or execution
question about Sales Plays, content bundles or packets, artifacts, or Content
Intelligence
requested_answer_mode: EXPLAIN, READ, CLARIFY, ROUTE, GAP, or REFUSE
Outputs
question_classification
sales_play_and_content_answer
operation_support_status
source_gap
sales_play_list
sales_play_detail
sales_play_type_summary
content_intelligence_result
content_intelligence_status
security_prerequisite_summary
effective_read_access_result
diagnostics
skill_run_record
token_usage_record
Failure and Retry Rules
Classify failures as input validation, catalog mismatch, authentication,
authorization or privilege, transport or environment, Fusion API, artifact
persistence, or unsupported operation. Use catalog mismatch when documented or
generated LIST query grammar differs from a runtime-validated target contract.
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. For CONTENT_SEARCH,
allow the Knowledge Management wrapper to refresh and retry once. 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 .../salesPlays/$query or
POST /api/knowledge-management/v2/contentIntelligence semantic-read operation
as a mutation.
Help Sources
- Public Sales Play and collateral overview:
references/sales-plays-and-content-overview.md
- Fusion UI agentic authoring prompts:
references/sales-plays-and-content-agentic-prompts.md
- Complete prerequisite and security matrix:
references/sales-plays-and-content-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-plays-and-content-boss-read.md
- Content Intelligence request, security gate, and result classification:
references/sales-plays-content-intelligence-read.md
- Task-local Knowledge Management client, OAuth scope, and cache boundary:
references/knowledge-management-rest-api.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-plays-and-content"3name: sales-plays-and-content-guidance-read-and-search4description: "Answers source-backed questions about Sales Plays, content bundles or packets, salesPlayType, criteria, status, fields, content artifacts, translations, setup, lifecycle, agentic UI authoring prompts, Knowledge authoring and consumption, prerequisites, Security Console role provisioning, profile options, roles, privileges, permission groups, data security policies, BOSS API/query behavior, Content Intelligence, troubleshooting, import/export limits, write-support status, and help sources. Also lists, filters, classifies, and retrieves SALES_PLAY and CONTENT_BUNDLE records and performs the documented Content Intelligence semantic-read search with OAuth, authorization, retry, and diagnostic guardrails. Use for any Sales Plays and Content question, Fusion UI agentic-authoring prompt example, security-provisioning question, or read/search 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_PLAYS_AND_CONTENT"11task_name: "Sales Plays and Content"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.7.6"21inputs:22 - "implementation_objective"23 - "project_context"24 - "fusion_environment_context"25 - "acting_user_identity"26 - "sales_play_operation"27 - "sales_play_id"28 - "sales_play_type"29 - "sales_play_query"30 - "content_intelligence_question"31 - "content_intelligence_sales_play_id"32 - "sales_play_and_content_question"33 - "requested_answer_mode"34outputs:35 - "question_classification"36 - "sales_play_and_content_answer"37 - "operation_support_status"38 - "source_gap"39 - "sales_play_list"40 - "sales_play_detail"41 - "sales_play_type_summary"42 - "content_intelligence_result"43 - "content_intelligence_status"44 - "security_prerequisite_summary"45 - "effective_read_access_result"46 - "diagnostics"47 - "skill_run_record"48 - "token_usage_record"49depends_on:50 - "core.auth.fusion-oauth-authentication"51 - "core.fusion-api.rest-api-client"52uses_core:53 - "core.auth.fusion-oauth-authentication"54 - "core.fusion-api.rest-api-client"55 - "core.project-mgmt.artifact-version-manager"56 - "core.project-mgmt.artifact-registry-manager"57 - "core.project-mgmt.project-state-manager"58persists_project_state: true59token_usage_tracking:60 enabled: true61 granularity: "per_skill_run"62 artifact_type: "token_usage_record"63 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"64 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"65 required_fields:66 - "activity_start_time"67 - "skill_id"68 - "task"69 - "trigger"70 - "artifacts_written"71 - "files_read"72 - "estimated_input_tokens"73 - "estimated_output_tokens"74 - "estimated_total_tokens"75 - "estimation_method"76 - "notes"77state_updates:78 - "validation_results"79 - "token_usage_records"80workspace_outputs:81 - artifact_type: "validation_result"82 default_location: "project/{project_id}/artifacts/pillars/cx/sales/sales-orchestration/sales-plays-and-content/current/"83 versioning_policy: "major-new-version-minor-confirm-update"84 - artifact_type: "skill_run"85 default_location: "project/{project_id}/state/runs/"86 versioning_policy: "append-only"87 - artifact_type: "token_usage_record"88 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"89 versioning_policy: "append-only"90oracle_supplied_guidance_files:91 - purpose: "Sales Play and content bundle read-operation input validation"92 location: "ora-resource/ora_input_validation.md"93 - purpose: "Sales Play environment and OAuth readiness"94 location: "ora-resource/ora_dependency_readiness.md"95 - purpose: "Sales Play list, get, content-accessor, and advanced-query lookup contracts"96 location: "ora-resource/ora_reference_lookups.md"97 - purpose: "Sales Play and content bundle read error handling and refusal rules"98 location: "ora-resource/ora_error_handling.md"99oracle_supplied_guidance_status:100 access_verification: "Effective access is established only by the requested LIST, GET, QUERY, or CONTENT_SEARCH call; role, permission-group, and data-security-policy membership remain unknown without authorized administrator evidence"101 boss_read_contract: "Verified against the 26C internal BOSS OpenAPI source; LIST type-filter and descending creation-sort query syntax are runtime-validated"102 content_intelligence_contract: "Developer-provided semantic-read POST contract for /api/knowledge-management/v2/contentIntelligence with fixed Sales Play connector and published-content filters, using the task-local Knowledge Management wrapper with the knowledge-management scope token selected from the regular scope property"103 sales_play_type_contract: "The salesPlays collection contains SALES_PLAY and CONTENT_BUNDLE records, distinguished by the salesPlayType attribute; content bundle and content packet are equivalent user-facing terms"104 security_contract: "Complete guidance includes the site profile option, predefined-role enablement, custom-role Security Console steps, three custom-administrator duties, setup-screen privilege, read/create/update/delete permission groups, All Rows security view, Knowledge authoring and end-user content data policies, synchronization procedures, and effective-access verification boundaries; this skill executes read operations only"105applicability:106 industries:107 - "All"108 countries:109 - "All"110 fusion_releases:111 - "Oracle Fusion Cloud Applications 26C"112 - "Later releases after endpoint contract verification"113side_effects:114 - "Reads Sales Play and content-artifact setup data through Fusion BOSS REST APIs."115 - "Searches published Sales Play content through the Content Intelligence semantic-read POST endpoint."116 - "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."117 - "May refresh the managed external Knowledge Management OAuth profile cache once after a cache-managed 401 or 403 response to CONTENT_SEARCH."118required_privileges:119 - "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"120 - "The custom job role also needs the documented operation-specific Sales Play permission groups and All Rows security view"121 - "ZCA_VIEW_SALES_PLAYS_PRIV for access to the Sales Plays setup screen"122 - "ORA_CSO_KNOWLEDGE_AUTHORING_DUTY plus the documented Sales Administrator Knowledge data security policies when the out-of-box Sales Administrator role cannot be assigned to a Knowledge authoring administrator"123 - "The acting Content Intelligence end-user role needs the documented Sales Play Consumer user-group and Sales Force Automation department access policies"124metadata:125 source: https://skillmd.com/skills/oracle/sales-plays-and-content-guidance-read-and-search126---127128# Sales Plays and Content Guidance, Read, and Search129130## Purpose131132Answer source-backed questions about Sales Plays, content bundles or packets,133their artifacts, and Sales Play Content Intelligence. When the routed project134workflow selects a live read, list, filter, search, or retrieve records for135setup task `CUSTOM_SALES_PLAYS_AND_CONTENT`. The shared `salesPlays` collection136uses `salesPlayType` to distinguish both record types. Keep executable137operations strictly read-only, including Content Intelligence POST requests138whose documented purpose is search rather than mutation.139140## Question and Execution Scope141142Handle conceptual, model, lifecycle, setup, security, BOSS API, Knowledge143Management, Content Intelligence, live-read, troubleshooting, import/export,144write-support, and help-source questions. Use the response statuses in145`../references/sales-orchestration-question-routing.md` so every material part146is answered from source, clarified, routed, marked as a source gap, or refused147safely.148149An explanatory question does not authorize authentication or a Fusion call.150Only these live operations are executable:151152- list Sales Plays and content bundles or packets with bounded query153 parameters, optionally restricted by `salesPlayType`;154- get one Sales Play or content bundle by exact ID and report its155 `salesPlayType`;156- query Sales Plays, content bundles, and documented `salesPlayArtifacts` or `$translations`157 children with the semantically read-only `POST .../salesPlays/$query`158 endpoint;159- test published Sales Play content search for one exact question and Sales160 Play ID with the semantically read-only161 `POST .../knowledge-management/v2/contentIntelligence` endpoint.162163Treat `CREATE`, `UPDATE`, `DELETE`, `PATCH`, `PUT`, and bulk-write requests as164unsupported. Treat every `POST` as unsupported except the exact documented165`salesPlays/$query` and `/api/knowledge-management/v2/contentIntelligence`166semantic-read endpoints. Do not build a mutation preview, request mutation167approval, or invoke a write endpoint. Data Loader does not currently support168the applicable BOSS REST endpoints. Write support may be introduced only after169that dependency is available and payload, article/artifact, translation,170identity, concurrency, idempotency, approval, retry, diagnostic, and recovery171behavior has passed a reviewed skill revision.172173Do not route this task through FSM CSV export or import because both catalog174support flags are `N`.175176## Sales Play Type Discriminator177178Use the `salesPlayType` attribute as the only type discriminator for records in179the `salesPlays` collection.180181| User-facing type | Accepted request wording | Canonical `salesPlayType` |182|---|---|---|183| Sales Play | sales play, sales plays | `SALES_PLAY` |184| Content bundle or packet | content bundle, content bundles, content packet, content packets, bundle, packet | `CONTENT_BUNDLE` |185186Normalize an explicitly requested type to its canonical value. Reject any187other supplied `salesPlayType`. When the request refers to the collection188generally and does not distinguish a type, do not infer a value or add a type189filter; return both types within the requested bound and include190`salesPlayType` in the result.191192For LIST or QUERY, preserve the normalized type as an exact `salesPlayType`193predicate. For GET, use only the exact record ID, then report the returned type194and treat a mismatch with an explicitly requested type as a type mismatch; do195not substitute another record. This discriminator does not change the fixed196Content Intelligence connector or filter contract.197198## Required Read Order199200Choose the read path from the user's intent.201202For every question:2032041. Read `../references/sales-orchestration-question-routing.md`.2052. Classify the subject, question classes, and answer mode before loading OAuth206 or execution resources.2073. Continue with only the task sources required by the selected classes.208209## General Question Handling210211- For a Sales Play definition, purpose, business value, collateral use, or212 design-scope question, read213 `references/sales-plays-and-content-overview.md`.214- For Fusion UI agentic authoring prompt examples, read215 `references/sales-plays-and-content-agentic-prompts.md` and follow its Prompt216 Emission Rules and content-source boundary. Emit concrete, synthetic,217 copy-ready prompts without user-replacement placeholders; treat them as UI218 guidance, not authorization for this skill to write through BOSS or REST.219- For type, field, status, criteria, artifact, translation, accessor,220 relationship, lifecycle, or BOSS API-capability questions, read221 `references/sales-plays-and-content-boss-read.md` and retain the222 `SALES_PLAY` versus `CONTENT_BUNDLE` distinction.223- For prerequisites, profile-option readiness, predefined-role enablement,224 custom-role provisioning, setup-screen access, roles, duties, privileges,225 permission groups, security views, Knowledge authoring, end-user content226 access, data security policies, or ESS synchronization, read227 `references/sales-plays-and-content-security.md`,228 `../references/security-console-role-provisioning.md`, and229 `../references/security-synchronization-processes.md` in full.230- For Content Intelligence concepts, request rules, access checks, result231 classifications, OAuth scope, or troubleshooting, read both232 `references/sales-plays-content-intelligence-read.md` and233 `references/knowledge-management-rest-api.md` as applicable.234- For input, dependency, lookup, filter, or troubleshooting questions, load only235 the applicable file under `ora-resource/` plus the relevant BOSS, Knowledge,236 or security reference.237- For import, export, bulk, Create, Update, Delete, activation, publication,238 archive, copy, article mutation, or another possible side-effect question,239 explain documented catalog and security prerequisites, state the Data Loader240 blocker, and return `UNSUPPORTED` for execution.241- For a question spanning Sales Motions, Data Capture Rules, or the wider242 functional area, route to `cx.sales.sales-orchestration` and preserve this243 skill's execution boundary.244- If the loaded sources do not establish a business definition, transition,245 validation, UI step, integration behavior, Knowledge response field, or246 release-specific fact, return `SOURCE_GAP` and identify the exact Oracle247 source or SME confirmation needed. Do not infer the answer from field names248 or prior chat history.249250For a prerequisite, profile-option, predefined-role enablement, custom-role251provisioning, role, privilege, permission-group, or access question:2522531. Read `references/sales-plays-and-content-security.md` in full.2542. Read `../references/security-console-role-provisioning.md` in full.2553. Read `../references/security-synchronization-processes.md` in full.2564. Return the complete security contract plus target-environment and shared257 OAuth readiness as technical prerequisites for a live read or content258 search.2595. Do not load API execution resources, authenticate, call Fusion, persist a260 project artifact, or submit an ESS job unless the user separately requests261 an authorized operation.262263For a LIST, GET, or QUERY operation:2642651. Read `ora-resource/ora_input_validation.md`.2662. Read `ora-resource/ora_dependency_readiness.md`.2673. Read `ora-resource/ora_reference_lookups.md`.2684. Read `references/sales-plays-and-content-security.md` and apply its Read row.2695. Read `references/sales-plays-and-content-boss-read.md`.2706. Read `ora-resource/ora_error_handling.md` before any live call.271272For a CONTENT_SEARCH operation:2732741. Read `ora-resource/ora_input_validation.md`.2752. Read `ora-resource/ora_dependency_readiness.md`.2763. Read `references/sales-plays-and-content-security.md` and apply the277 Content Intelligence end-user policies.2784. Read `references/knowledge-management-rest-api.md` for the task-local client,279 OAuth scope, cache, and endpoint boundary.2805. Read `references/sales-plays-content-intelligence-read.md` for the fixed281 request contract and result classifications.2826. Read `ora-resource/ora_reference_lookups.md` for the executable lookup.2837. Read `ora-resource/ora_error_handling.md` before the live search.284285## Read Security Boundary286287Use either:288289- confirmed membership in `ORA_ZBS_SALES_ADMINISTRATOR_JOB`; or290- a custom job role containing both documented duty roles, the Sales Play read291 permission groups, and the `All Rows` security view.292293For Knowledge article administration when the out-of-box Sales Administrator294role cannot be assigned, also require295`ORA_CSO_KNOWLEDGE_AUTHORING_DUTY` and the documented Sales Administrator296Knowledge data security policies.297298For a Content Intelligence search, require the acting Sales Representative,299Sales Manager, Sales Administrator, or equivalent custom role to have access300to both the Sales Play Consumer user group and the Sales Force Automation301department.302303Treat the documented role and permission groups as prerequisites, not proof of304the acting user's membership. Do not claim membership without authorized305administrator evidence.306307A requested read operation may proceed as the effective access check. A308successful LIST, GET, QUERY, or CONTENT_SEARCH response proves access only for309that call.310HTTP 403 proves that the acting user lacks effective read authorization for311that request; it does not identify which role, privilege, permission group, or312security view is missing.313314The security reference also documents the Create, Update, and Delete permission315groups so implementers can prepare custom roles. Those grants do not expand316this skill's executable scope.317318## Security and Prerequisite Questions319320When the user asks for Sales Play prerequisites, the permission-group profile321option, predefined-role enablement, custom-role provisioning, roles, duty322roles, privileges, permission groups, or access requirements, read323`references/sales-plays-and-content-security.md`,324`../references/security-console-role-provisioning.md`, and325`../references/security-synchronization-processes.md` in full and return all326of the following:327328- the `ORA_ASE_SAS_INTEGRATION_ENABLED` Site profile-option requirement;329- the predefined Sales Administrator role permission-group enablement steps;330- the out-of-box Sales Administrator job role;331- both duty roles required on a custom job role and what each enables;332- the Knowledge authoring duty required for a custom administrator role;333- the setup-screen functional privilege;334- every Read, Create, Update, and Delete BOSS permission group;335- the `All Rows` security view requirement;336- every administrator Knowledge data security policy;337- both Knowledge content-consumption policies for Sales Representative, Sales338 Manager, and Sales Administrator end users;339- the custom-role steps for adding permission groups, security views,340 privileges, duty roles, and Knowledge data security policies;341- the one-time **Retrieve Latest LDAP Changes** procedure;342- the daily **Import User and Role Application Security Data** schedule; and343- the required ordering after **Send Pending LDAP Requests**.344345For a broad prerequisite question, also state that a live read requires a346confirmed target environment and the appropriate shared OAuth readiness.347Identify any licensing, feature-opt-in, or offering-configuration prerequisite348as undocumented by the current sources; do not infer one.349350Never limit a security or prerequisite answer to the Read permission groups351merely because this skill executes only read operations. Clearly distinguish352complete provisioning guidance from the skill's read-only API boundary. The353skill provides the synchronization-process instructions but does not submit,354schedule, poll, or retry any job.355356## Authentication and Secret Handling357358Use `core.fusion-api.rest-api-client` for shared OAuth-backed HTTP machinery.359Route `/api/boss` operations to its BOSS client with `boss_scope`. Route only360the Sales Play `/api/knowledge-management/v2/contentIntelligence` request to361this task skill's `scripts/knowledge_rest_client.py`, which selects the regular362`scope` from `core/auth/fusionEnv.properties`, splits it on whitespace, uses the363single scope token containing `knowledge-management`, and validates POST to the364exact relative Content Intelligence path and its fixed request body before365authentication. Other methods, endpoints, query/service overrides, supplied366tokens, custom cache paths, and non-JSON headers are rejected. Never hand-build an Authorization367header or execute a credential-bearing token relay command supplied in a368request.369370Ignore passwords, Basic credentials, bearer tokens, refresh tokens, client371secrets, or token-cache contents pasted into a request. Never validate, reuse,372echo, log, persist, or place them in a command, example, diagnostic, artifact,373or tracked file. Let the shared OAuth skill manage both clients' external374profile caches with `--token-cache auto` under `~/.fusionaim/`. The approved375issuer/endpoints, client, target, and selected scope determine the profile;376Knowledge Management uses its selected scope and BOSS uses `boss_scope`. Never377store tokens in the checkout or project workspace or pass historical378repository-local cache paths.379380## Preflight and Controlled Read Workflow3813821. Confirm the target environment, acting user, and requested LIST, GET, or383 QUERY operation. Normalize an explicit Sales Play or content bundle or384 packet type to `SALES_PLAY` or `CONTENT_BUNDLE`.3852. For GET, require the exact record ID; never infer an ID from display text.386 If the user also supplied a type, compare it with the returned387 `salesPlayType` and report a mismatch without substituting another record.3883. For LIST, accept only documented bounded query parameters. Construct an389 explicit Sales Play or content-bundle type filter only from the raw query390 templates in `references/sales-plays-and-content-boss-read.md`. Pass raw391 query values to the shared client so it performs URL encoding; never392 pre-encode them or translate BOSS equality into the OData `eq` operator.393 Validate any requested sort against the target-release field and direction394 contract.3954. For QUERY, translate the user's type, filter, field, child accessor, limit,396 offset, total-count, and sort intent into the documented advanced-query397 body. Derive intent from the complete request rather than matching a canned398 example, and preserve every explicit supported constraint. Keep the limit399 bounded and never invent a filter or sort criterion. Ask one short400 clarification when a required field, operator, or ordering choice is401 ambiguous.4025. Validate environment and BOSS OAuth configuration.4036. Invoke the selected read operation through the shared client. The QUERY404 operation uses POST but remains read-only because its exact path ends in405 `/salesPlays/$query`.4067. For LIST or GET, if a cache-managed token receives HTTP 401 or 403,407 allow the shared client to refresh once and retry once. For QUERY, the408 shared client does not automatically refresh or retry the POST; stop and409 report the sanitized authentication or authorization failure.4108. Permit a bounded retry only for a known transient read-only transport411 failure.4129. Return Sales Play or content bundle records with `salesPlayType`, requested413 content artifacts, `hasMore` and `totalItems` when present, effective-read414 status, and sanitized diagnostics.41510. When `project_context` is supplied, persist only sanitized read validation,416 result, diagnostic, and token-usage records.417418## Content Intelligence Search Validation Workflow4194201. Confirm the target environment and acting end user.4212. Require one non-empty user question and one exact, non-empty Sales Play ID.4223. Confirm that the acting role has access to the Sales Play Consumer user423 group and Sales Force Automation department; treat membership as unknown424 without administrator evidence.4254. Read `references/sales-plays-content-intelligence-read.md` and construct its426 fixed body. Replace only the user question and Sales Play ID. Serialize the427 inner `userInput` object safely; never interpolate raw question text into428 JSON or shell syntax.4295. Invoke the exact Content Intelligence path through this task skill's430 `scripts/knowledge_rest_client.py`, which selects the scope token containing431 `knowledge-management` from the regular `scope` property and uses the shared432 managed external profile cache (`--token-cache auto`). Do not supply an433 Authorization header or explicit access token.4346. Permit the shared client to refresh its Knowledge Management OAuth cache and435 retry once after HTTP 401 or 403.4367. Return `WORKING_WITH_RESULTS`, `WORKING_NO_RESULTS`,437 `AUTHENTICATION_FAILED`, `AUTHORIZATION_FAILED`, `REQUEST_INVALID`, or438 `SEARCH_FAILED` using the reference's observed-result rules.4398. Report the sanitized response shape. Do not invent a response field,440 relevance threshold, or result-count meaning not present in the response.4419. When `project_context` is supplied, persist only sanitized validation,442 result, diagnostic, and token-usage records.443444## API Contract445446| Action | Method | Relative path |447|---|---|---|448| List | GET | /api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesPlays |449| Get | GET | /api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesPlays/{salesPlays_id} |450| Advanced query all | POST, read semantics | /api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/salesPlays/$query |451| Content Intelligence search | POST, read semantics | /api/knowledge-management/v2/contentIntelligence |452453Use the exact target-release OpenAPI contract if it differs from this 26C454summary. Quote shell arguments containing `$en` or `$query`.455456The canonical 26C OpenAPI paths include `$en`. A runtime-validated collection457path without that segment also succeeded. Keep the canonical path unless458target-specific evidence requires the shorter form, and do not change the path459merely because a query expression fails to parse.460461## Inputs462463- `implementation_objective`464- `project_context`465- `fusion_environment_context`466- `acting_user_identity`467- `sales_play_operation`: LIST, GET, QUERY, or CONTENT_SEARCH only468- `sales_play_id`: exact record ID required only for GET469- `sales_play_type`: optional type discriminator for LIST or QUERY, or expected470 returned type for GET; normalize only `SALES_PLAY` or `CONTENT_BUNDLE`471- `sales_play_query`: documented LIST parameters or QUERY body values472- `content_intelligence_question`: required only for CONTENT_SEARCH473- `content_intelligence_sales_play_id`: exact Sales Play ID required only for474 CONTENT_SEARCH475- `sales_play_and_content_question`: any explanatory, support, or execution476 question about Sales Plays, content bundles or packets, artifacts, or Content477 Intelligence478- `requested_answer_mode`: EXPLAIN, READ, CLARIFY, ROUTE, GAP, or REFUSE479480## Outputs481482- `question_classification`483- `sales_play_and_content_answer`484- `operation_support_status`485- `source_gap`486- `sales_play_list`487- `sales_play_detail`488- `sales_play_type_summary`489- `content_intelligence_result`490- `content_intelligence_status`491- `security_prerequisite_summary`492- `effective_read_access_result`493- `diagnostics`494- `skill_run_record`495- `token_usage_record`496497## Failure and Retry Rules498499Classify failures as input validation, catalog mismatch, authentication,500authorization or privilege, transport or environment, Fusion API, artifact501persistence, or unsupported operation. Use catalog mismatch when documented or502generated LIST query grammar differs from a runtime-validated target contract.503504For LIST or GET, allow one cache-managed 401 or 403 refresh and retry through505the shared BOSS client. For QUERY, stop on 401 or 403 without automatically506refreshing or replaying the POST; a new requested read requires validation507after the authentication or authorization issue is resolved. For CONTENT_SEARCH,508allow the Knowledge Management wrapper to refresh and retry once. Retry a509known transient transport failure only within a bounded read-only retry policy.510Do not retry malformed requests or deterministic 4xx responses.511512For any mutation request, return `UNSUPPORTED`, state that this skill revision513is read-only, and stop without previewing or calling Fusion. Do not classify514the exact `POST .../salesPlays/$query` or515`POST /api/knowledge-management/v2/contentIntelligence` semantic-read operation516as a mutation.517518## Help Sources519520- Public Sales Play and collateral overview:521 `references/sales-plays-and-content-overview.md`522- Fusion UI agentic authoring prompts: `references/sales-plays-and-content-agentic-prompts.md`523- Complete prerequisite and security matrix:524 `references/sales-plays-and-content-security.md`525- Step-by-step Security Console role provisioning:526 `../references/security-console-role-provisioning.md`527- Step-by-step security synchronization processes:528 `../references/security-synchronization-processes.md`529- Read endpoint and command patterns:530 `references/sales-plays-and-content-boss-read.md`531- Content Intelligence request, security gate, and result classification:532 `references/sales-plays-content-intelligence-read.md`533- Task-local Knowledge Management client, OAuth scope, and cache boundary:534 `references/knowledge-management-rest-api.md`535- Cross-task question classification and response contract:536 `../references/sales-orchestration-question-routing.md`537538Use the parent skill `cx.sales.sales-orchestration` only for functional-area539scope and cross-task sequencing.