Data Capture Rules Guidance and Read Operations
Purpose
Answer source-backed questions about Data Capture Rules and, when the routed
project workflow selects a live read, list, filter, or retrieve Data Capture
Rules for setup task CUSTOM_DATA_CAPTURE_RULES. 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 Data Capture Rules with bounded query parameters;
- get one Data Capture Rule by exact ID;
- query Data Capture Rules with the semantically read-only
POST .../dataCaptureRules/$query endpoint.
Treat CREATE, UPDATE, DELETE, PATCH, PUT, and bulk-write requests as
unsupported. This includes requests to create, generate, draft, or sample a
Data Capture Rule, even when the user asks only for a local blueprint or
example. Return UNSUPPORTED from this skill and stop. Do not route the
request to the parent Sales Orchestration skill or another skill, and do not
produce a blueprint, payload, preview, project artifact, approval request, or
write call.
A request for copy-ready text to enter in the Fusion Data Capture Rules UI is
an EXPLAIN request, not a mutation request. It is allowed only as prompt
guidance under references/data-capture-rules-agentic-prompts.md; stop at the
prompt text and do not turn it into a rule blueprint, payload, preview, or live
Fusion operation.
Treat every POST as unsupported except the exact documented
dataCaptureRules/$query semantic-read endpoint. Questions about documented
Create, Update, or Delete security prerequisites remain guidance requests, not
mutation authorization. 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, setup concept, or documented
attribute example, read
references/data-capture-rules-overview.md.
- For Fusion UI agentic authoring prompt examples, read
references/data-capture-rules-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, criteria, rank, rule-attribute, translation,
accessor, relationship, lifecycle, or API-capability questions, read
references/data-capture-rules-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/data-capture-rules-security.md,
../references/security-console-role-provisioning.md, and
../references/security-synchronization-processes.md in full.
- For input, dependency, lookup, BOSS filter, query-body, 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. Preserve the existing refusal of local
mutation blueprints and sample write payloads.
- For a question spanning Sales Motions, Sales Plays, content, 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.
Before loading another skill, authenticating, or creating an artifact,
classify whether the objective requests a Data Capture Rule mutation. If it
does, return UNSUPPORTED within this skill and stop. Do not route a
task-level Data Capture Rule request to the parent skill.
For a prerequisite, profile-option, predefined-role enablement, custom-role
provisioning, role, privilege, permission-group, or access question:
- Read
references/data-capture-rules-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/data-capture-rules-security.md and apply its Read row.
- Read
references/data-capture-rules-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 Data Capture
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 Data Capture prerequisites, the permission-group profile
option, predefined-role enablement, custom-role provisioning, roles, duty
roles, privileges, permission groups, or access requirements, read
references/data-capture-rules-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 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 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 Data Capture Rule 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.
- For LIST and QUERY equality predicates, use the raw BOSS expression
((field = 'value')). Do not use OData eq, double-quoted string literals,
or pre-encoded filter text. For one active rule, use
((statusCode = 'ACTIVE')) and a bound of 1.
- For QUERY, send one top-level JSON object with
collection.filter and
collection.limit; place optional fields, accessors, subTypes, and
parameters only at their documented levels. Do not wrap the body in a
query, payload, or data object.
- 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
/dataCaptureRules/$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/dataCaptureRules |
| Get |
GET |
/api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/dataCaptureRules/{dataCaptureRules_id} |
| Advanced query all |
POST, read semantics |
/api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/dataCaptureRules/$query |
Use the exact target-release OpenAPI contract if it differs from this 26C
summary. Quote shell arguments containing $en or $query.
The validated active-rule QUERY body is:
{
"fields": ["id", "name", "statusCode"],
"collection": {
"filter": "((statusCode = 'ACTIVE'))",
"limit": 1
}
}
Read references/data-capture-rules-boss-read.md for the executable shared
client command and additional supported body fields.
Inputs
implementation_objective
project_context
fusion_environment_context
acting_user_identity
data_capture_rule_operation: LIST, GET, or QUERY only
data_capture_rule_id: required only for GET
data_capture_rule_query: documented LIST parameters or QUERY body values
data_capture_rule_question: any explanatory, support, or execution question
about Data Capture Rules
requested_answer_mode: EXPLAIN, READ, CLARIFY, ROUTE, GAP, or REFUSE
Outputs
question_classification
data_capture_rule_answer
operation_support_status
source_gap
data_capture_rule_list
data_capture_rule_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, including a request to create or generate a sample
Data Capture Rule or local blueprint, return UNSUPPORTED, state that this
skill revision is read-only, and stop without routing, artifact generation,
previewing, approval, or a Fusion call. Do not classify the exact
POST .../dataCaptureRules/$query semantic-read operation as a mutation.
Help Sources
- Public Data Capture overview, setup concept, and release-specific limits:
references/data-capture-rules-overview.md
- Fusion UI agentic authoring prompts:
references/data-capture-rules-agentic-prompts.md
- Complete prerequisite and security matrix:
references/data-capture-rules-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/data-capture-rules-boss-read.md
- Cross-task question classification and response contract:
../references/sales-orchestration-question-routing.md
Do not route a task-level Data Capture Rule request to the parent skill. The
parent skill is relevant only when the user explicitly requests broader
functional-area scope or cross-task sequencing, not as a fallback for an
unsupported Data Capture Rule operation.
1---2skill_id: "cx.sales.sales-orchestration.data-capture-rules"3name: data-capture-rules-guidance-and-read-operations4description: "Answers source-backed questions about Data Capture Rules, including purpose, setup, lifecycle and status, fields, criteria, rank, rule attributes, translations, agentic UI authoring prompts, relationships, prerequisites, Security Console role provisioning, profile options, roles, privileges, permission groups, API/filter/query behavior, troubleshooting, import/export limits, write-support status, and help sources. Also lists, filters, and retrieves Data Capture Rules 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 Data Capture Rule question, Fusion UI agentic-authoring prompt example, security-provisioning question, or read request; explain or classify unsupported Create/Update/Delete requests without routing to a mutation blueprint or bypassing the routed workflow."5layer: "pillar"6pillar: "CX"7offering: "Sales"8functional_area: "Sales Orchestration"9functional_area_code: "CUSTOM_SALES_ORCHESTRATION"10task_code: "CUSTOM_DATA_CAPTURE_RULES"11task_name: "Data Capture Rules"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.6.3"21inputs:22 - "implementation_objective"23 - "project_context"24 - "fusion_environment_context"25 - "acting_user_identity"26 - "data_capture_rule_operation"27 - "data_capture_rule_id"28 - "data_capture_rule_query"29 - "data_capture_rule_question"30 - "requested_answer_mode"31outputs:32 - "question_classification"33 - "data_capture_rule_answer"34 - "operation_support_status"35 - "source_gap"36 - "data_capture_rule_list"37 - "data_capture_rule_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/data-capture-rules/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: "Data Capture Rule read-operation input validation"86 location: "ora-resource/ora_input_validation.md"87 - purpose: "Data Capture Rule environment and OAuth readiness"88 location: "ora-resource/ora_dependency_readiness.md"89 - purpose: "Data Capture Rule list, get, and advanced-query lookup contracts"90 location: "ora-resource/ora_reference_lookups.md"91 - purpose: "Data Capture Rule 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 Data Capture Rule 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 Data Capture permission groups and All Rows security view"111 - "ZCA_VIEW_DATA_CAPTURE_RULES_PRIV for access to the Data Capture setup screen"112metadata:113 source: https://skillmd.com/skills/oracle/data-capture-rules-guidance-and-read-operations114---115116# Data Capture Rules Guidance and Read Operations117118## Purpose119120Answer source-backed questions about Data Capture Rules and, when the routed121project workflow selects a live read, list, filter, or retrieve Data Capture122Rules for setup task `CUSTOM_DATA_CAPTURE_RULES`. Keep executable operations123strictly read-only.124125## Question and Execution Scope126127Handle conceptual, model, lifecycle, setup, security, API, live-read,128troubleshooting, import/export, write-support, and help-source questions. Use129the response statuses in130`../references/sales-orchestration-question-routing.md` so every material part131is answered from source, clarified, routed, marked as a source gap, or refused132safely.133134An explanatory question does not authorize authentication or a Fusion call.135Only these live operations are executable:136137- list Data Capture Rules with bounded query parameters;138- get one Data Capture Rule by exact ID;139- query Data Capture Rules with the semantically read-only140 `POST .../dataCaptureRules/$query` endpoint.141142Treat `CREATE`, `UPDATE`, `DELETE`, `PATCH`, `PUT`, and bulk-write requests as143unsupported. This includes requests to create, generate, draft, or sample a144Data Capture Rule, even when the user asks only for a local blueprint or145example. Return `UNSUPPORTED` from this skill and stop. Do not route the146request to the parent Sales Orchestration skill or another skill, and do not147produce a blueprint, payload, preview, project artifact, approval request, or148write call.149150A request for copy-ready text to enter in the Fusion Data Capture Rules UI is151an `EXPLAIN` request, not a mutation request. It is allowed only as prompt152guidance under `references/data-capture-rules-agentic-prompts.md`; stop at the153prompt text and do not turn it into a rule blueprint, payload, preview, or live154Fusion operation.155156Treat every `POST` as unsupported except the exact documented157`dataCaptureRules/$query` semantic-read endpoint. Questions about documented158Create, Update, or Delete security prerequisites remain guidance requests, not159mutation authorization. Data Loader does not currently support the applicable160BOSS REST endpoints. Write support may be introduced only after that dependency161is available and payload, identity, concurrency, idempotency, approval, retry,162diagnostic, and recovery behavior has passed a reviewed skill revision.163164Do not route this task through FSM CSV export or import because both catalog165support flags are `N`.166167## Required Read Order168169Choose the read path from the user's intent.170171For every question:1721731. Read `../references/sales-orchestration-question-routing.md`.1742. Classify the subject, question classes, and answer mode before loading OAuth175 or execution resources.1763. Continue with only the task sources required by the selected classes.177178## General Question Handling179180- For a definition, purpose, business value, setup concept, or documented181 attribute example, read `references/data-capture-rules-overview.md`.182- For Fusion UI agentic authoring prompt examples, read183 `references/data-capture-rules-agentic-prompts.md` and follow its Prompt184 Emission Rules. Emit concrete, synthetic, copy-ready prompts without185 user-replacement placeholders; treat them as UI guidance, not authorization186 for this skill to write through BOSS or REST.187- For object-model, field, status, criteria, rank, rule-attribute, translation,188 accessor, relationship, lifecycle, or API-capability questions, read189 `references/data-capture-rules-boss-read.md`. Return only facts established190 by the target-release contract.191- For prerequisites, profile-option readiness, predefined-role enablement,192 custom-role provisioning, setup-screen access, roles, duties, privileges,193 permission groups, security views, or ESS synchronization, read194 `references/data-capture-rules-security.md`,195 `../references/security-console-role-provisioning.md`, and196 `../references/security-synchronization-processes.md` in full.197- For input, dependency, lookup, BOSS filter, query-body, or troubleshooting198 questions, load only the applicable file under `ora-resource/` plus the199 relevant BOSS or security reference.200- For import, export, bulk, Create, Update, Delete, activation, archive, or other201 possible side-effect questions, explain the documented catalog and security202 prerequisites, state the Data Loader blocker, and return203 `UNSUPPORTED` for execution. Preserve the existing refusal of local204 mutation blueprints and sample write payloads.205- For a question spanning Sales Motions, Sales Plays, content, or the wider206 functional area, route to `cx.sales.sales-orchestration` and preserve this207 skill's execution boundary.208- If the loaded sources do not establish a business definition, transition,209 validation, UI step, integration behavior, or release-specific fact, return210 `SOURCE_GAP` and identify the exact Oracle source or SME confirmation needed.211 Do not infer the answer from field names or prior chat history.212213Before loading another skill, authenticating, or creating an artifact,214classify whether the objective requests a Data Capture Rule mutation. If it215does, return `UNSUPPORTED` within this skill and stop. Do not route a216task-level Data Capture Rule request to the parent skill.217218For a prerequisite, profile-option, predefined-role enablement, custom-role219provisioning, role, privilege, permission-group, or access question:2202211. Read `references/data-capture-rules-security.md` in full.2222. Read `../references/security-console-role-provisioning.md` in full.2233. Read `../references/security-synchronization-processes.md` in full.2244. Return the complete security contract plus target-environment and shared225 BOSS OAuth readiness as technical prerequisites for a live read.2265. Do not load API execution resources, authenticate, call Fusion, persist a227 project artifact, or submit an ESS job unless the user separately requests228 an authorized operation.229230For a LIST, GET, or QUERY operation:2312321. Read `ora-resource/ora_input_validation.md`.2332. Read `ora-resource/ora_dependency_readiness.md`.2343. Read `ora-resource/ora_reference_lookups.md`.2354. Read `references/data-capture-rules-security.md` and apply its Read row.2365. Read `references/data-capture-rules-boss-read.md`.2376. Read `ora-resource/ora_error_handling.md` before any live call.238239## Read Security Boundary240241Use either:242243- confirmed membership in `ORA_ZBS_SALES_ADMINISTRATOR_JOB`; or244- a custom job role containing both documented duty roles, the Data Capture245 read permission groups, and the `All Rows` security view.246247Treat the documented role and permission groups as prerequisites, not proof of248the acting user's membership. Do not claim membership without authorized249administrator evidence.250251A requested read operation may proceed as the effective access check. A252successful LIST, GET, or QUERY response proves read access only for that call.253HTTP 403 proves that the acting user lacks effective read authorization for254that request; it does not identify which role, privilege, permission group, or255security view is missing.256257The security reference also documents the Create, Update, and Delete permission258groups so implementers can prepare custom roles. Those grants do not expand259this skill's executable scope.260261## Security and Prerequisite Questions262263When the user asks for Data Capture prerequisites, the permission-group profile264option, predefined-role enablement, custom-role provisioning, roles, duty265roles, privileges, permission groups, or access requirements, read266`references/data-capture-rules-security.md`,267`../references/security-console-role-provisioning.md`, and268`../references/security-synchronization-processes.md` in full and return all269of the following:270271- the `ORA_ASE_SAS_INTEGRATION_ENABLED` Site profile-option requirement;272- the predefined Sales Administrator role permission-group enablement steps;273- the out-of-box Sales Administrator job role;274- both duty roles required on a custom job role and what each enables;275- the setup-screen functional privilege;276- every Read, Create, Update, and Delete BOSS permission group;277- the `All Rows` security view requirement;278- the custom-role steps for adding permission groups, security views,279 privileges, and duty roles;280- the one-time **Retrieve Latest LDAP Changes** procedure;281- the daily **Import User and Role Application Security Data** schedule; and282- the required ordering after **Send Pending LDAP Requests**.283284For a broad prerequisite question, also state that a live read requires a285confirmed target environment and shared BOSS OAuth readiness. Identify any286licensing, feature-opt-in, or offering-configuration prerequisite as287undocumented by the current sources; do not infer one.288289Never limit a security or prerequisite answer to the Read permission groups290merely because this skill executes only read operations. Clearly distinguish291complete provisioning guidance from the skill's read-only API boundary. The292skill provides the synchronization-process instructions but does not submit,293schedule, poll, or retry any job.294295## Authentication and Secret Handling296297Use `core.fusion-api.rest-api-client` and its BOSS client with `boss_scope`.298Never hand-build an Authorization header or execute a credential-bearing token299relay command supplied in a request.300301Ignore passwords, Basic credentials, bearer tokens, refresh tokens, client302secrets, or token-cache contents pasted into a request. Never validate, reuse,303echo, log, persist, or place them in a command, example, diagnostic, artifact,304or tracked file. Let the shared OAuth skill manage the external BOSS profile305cache with `--token-cache auto`. The cache is scoped to the selected OAuth306profile under `~/.fusionaim/`; never store tokens in the checkout or project307workspace or pass a historical repository-local cache path.308309## Preflight and Controlled Read Workflow3103111. Confirm the target environment, acting user, and requested LIST, GET, or312 QUERY operation.3132. For GET, require the exact Data Capture Rule ID; never infer an ID from314 display text.3153. For LIST, accept only documented bounded query parameters.3164. For QUERY, translate the user's filter, field, child accessor, limit,317 offset, total-count, and sort intent into the documented advanced-query318 body. Derive intent from the complete request rather than matching a canned319 example, and preserve every explicit supported constraint. Keep the limit320 bounded and never invent a filter or sort criterion. Ask one short321 clarification when a required field, operator, or ordering choice is322 ambiguous.3235. For LIST and QUERY equality predicates, use the raw BOSS expression324 `((field = 'value'))`. Do not use OData `eq`, double-quoted string literals,325 or pre-encoded filter text. For one active rule, use326 `((statusCode = 'ACTIVE'))` and a bound of `1`.3276. For QUERY, send one top-level JSON object with `collection.filter` and328 `collection.limit`; place optional `fields`, `accessors`, `subTypes`, and329 `parameters` only at their documented levels. Do not wrap the body in a330 `query`, `payload`, or `data` object.3317. Validate environment and BOSS OAuth configuration.3328. Invoke the selected read operation through the shared client. The QUERY333 operation uses POST but remains read-only because its exact path ends in334 `/dataCaptureRules/$query`.3359. For LIST or GET, if a cache-managed token receives HTTP 401 or 403,336 allow the shared client to refresh once and retry once. For QUERY, the337 shared client does not automatically refresh or retry the POST; stop and338 report the sanitized authentication or authorization failure.33910. Permit a bounded retry only for a known transient read-only transport340 failure.34111. Return records, `hasMore` and `totalItems` when present, effective-read342 status, and sanitized diagnostics.34312. When `project_context` is supplied, persist only sanitized read validation,344 result, diagnostic, and token-usage records.345346## API Contract347348| Action | Method | Relative path |349|---|---|---|350| List | GET | /api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/dataCaptureRules |351| Get | GET | /api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/dataCaptureRules/{dataCaptureRules_id} |352| Advanced query all | POST, read semantics | /api/boss/data/objects/ora/cxSalesCommon/engagements/v1/$en/dataCaptureRules/$query |353354Use the exact target-release OpenAPI contract if it differs from this 26C355summary. Quote shell arguments containing `$en` or `$query`.356357The validated active-rule QUERY body is:358359```json360{361 "fields": ["id", "name", "statusCode"],362 "collection": {363 "filter": "((statusCode = 'ACTIVE'))",364 "limit": 1365 }366}367```368369Read `references/data-capture-rules-boss-read.md` for the executable shared370client command and additional supported body fields.371372## Inputs373374- `implementation_objective`375- `project_context`376- `fusion_environment_context`377- `acting_user_identity`378- `data_capture_rule_operation`: LIST, GET, or QUERY only379- `data_capture_rule_id`: required only for GET380- `data_capture_rule_query`: documented LIST parameters or QUERY body values381- `data_capture_rule_question`: any explanatory, support, or execution question382 about Data Capture Rules383- `requested_answer_mode`: EXPLAIN, READ, CLARIFY, ROUTE, GAP, or REFUSE384385## Outputs386387- `question_classification`388- `data_capture_rule_answer`389- `operation_support_status`390- `source_gap`391- `data_capture_rule_list`392- `data_capture_rule_detail`393- `security_prerequisite_summary`394- `effective_read_access_result`395- `diagnostics`396- `skill_run_record`397- `token_usage_record`398399## Failure and Retry Rules400401Classify failures as input validation, authentication, authorization or402privilege, transport or environment, Fusion API, artifact persistence, or403unsupported operation.404405For LIST or GET, allow one cache-managed 401 or 403 refresh and retry through406the shared BOSS client. For QUERY, stop on 401 or 403 without automatically407refreshing or replaying the POST; a new requested read requires validation408after the authentication or authorization issue is resolved. Retry a409known transient transport failure only within a bounded read-only retry policy.410Do not retry malformed requests or deterministic 4xx responses.411412For any mutation request, including a request to create or generate a sample413Data Capture Rule or local blueprint, return `UNSUPPORTED`, state that this414skill revision is read-only, and stop without routing, artifact generation,415previewing, approval, or a Fusion call. Do not classify the exact416`POST .../dataCaptureRules/$query` semantic-read operation as a mutation.417418## Help Sources419420- Public Data Capture overview, setup concept, and release-specific limits:421 `references/data-capture-rules-overview.md`422- Fusion UI agentic authoring prompts: `references/data-capture-rules-agentic-prompts.md`423- Complete prerequisite and security matrix:424 `references/data-capture-rules-security.md`425- Step-by-step Security Console role provisioning:426 `../references/security-console-role-provisioning.md`427- Step-by-step security synchronization processes:428 `../references/security-synchronization-processes.md`429- Read endpoint and command patterns:430 `references/data-capture-rules-boss-read.md`431- Cross-task question classification and response contract:432 `../references/sales-orchestration-question-routing.md`433434Do not route a task-level Data Capture Rule request to the parent skill. The435parent skill is relevant only when the user explicitly requests broader436functional-area scope or cross-task sequencing, not as a fallback for an437unsupported Data Capture Rule operation.