Configure Oracle Sales to Quoting Integration
Purpose
Configure CPQ Integration Center connections using the registered IntegrationVendors Data Loader business object. This task replaces direct CPQ REST calls so authorization, payload validation, archive handling, and execution use the repository-standard Data Loader controls.
Dependency
When Fusion Sales and CPQ are in scope, invoke cx.sales.integrations.manage-oracle-cx-sales-to-oracle-cpq-cloud-integration in its read-only verification path before preparing a connection load. Record its readiness result in the project workspace. Do not use this task to change Fusion Sales instances or actions.
Preflight
Before generating a source artifact or opening Fusion:
- Resolve the project workspace and require an active Run Book binding. The selected task must be
Oracle Sales to Quoting Integrationwith task codeCUSTOM_ORACLE_SALES_TO_QUOTING_INTEGRATION. - Confirm that the selected Fusion environment matches the active Run Book environment and that
IntegrationVendorsis visible in Data Loader. - Treat the active Run Book Fusion environment base URL as the endpoint source for both staged profiles. Do not use a different host unless the user explicitly changes the Run Book environment.
- Require exactly one connection profile per artifact:
fusion-crmorgeneric-integration. The standard sequence is CRM staging first, followed by Generic Integration staging only after the user confirms the CRM connection is enabled. - Use the literal
FDOS_CREDENTIAL_REQUIREDfor both username and password in a staging artifact. Never place credentials, bearer tokens, or CPQ OAuth-scope values in a workbook, DAT, ZIP, project artifact, diagnostic, or chat response. - Set every staged connection's
enableditem tofalse. Enabling and credential entry are user-managed CPQ UI actions. - Stop on an ambiguous Business Object, missing
propertieschild, or missingitemschild. Do not reconstruct a direct REST request as a fallback.
Data Loader source model
Generate the workbook from live IntegrationVendors metadata through core.data-loader. The artifact must preserve this hierarchy:
IntegrationVendors (integrationVendorsKey)
└── properties (propertyId, integrationVendorsKey)
└── items (propertyId, name, value)
Use a different integrationVendorsKey and propertyId for each connection. Every items row must carry the same propertyId as its properties parent. The Data Loader metadata column order is authoritative; values must follow the order in that section's METADATA line.
Fusion CRM profile — stage first
Populate the parent with integrationType=CRM and vendorName=fusion. Populate items with:
| Item name | Staged value |
|---|---|
name |
FusionSales |
variableName |
FusionSales |
endPointURI |
Active Run Book Fusion environment base URL |
username |
FDOS_CREDENTIAL_REQUIRED |
password |
FDOS_CREDENTIAL_REQUIRED |
enabled |
false |
After the CRM archive succeeds, stop for the user to enter the real credentials, enable the connection, and save it in CPQ Admin > Integrations > Integration Center. Use the declared read-only UI verification step to confirm the enabled state. Do not proceed to Generic Integration staging until the user confirms this step.
Generic Integration profile — stage second
Populate the parent with integrationType=genericIntegration and vendorName=genericIntegration. Populate items with:
| Item name | Staged value |
|---|---|
name |
Fusion Account Integration |
requestUrl |
Active Run Book Fusion environment base URL |
username |
FDOS_CREDENTIAL_REQUIRED |
password |
FDOS_CREDENTIAL_REQUIRED |
enabled |
false |
Use a literal HTTPS URL, not Markdown link syntax. After the archive succeeds, stop again for the user to replace the placeholders, enable the connection, save it, and confirm the enabled state in Integration Center.
Workflow
- Generate and validate a Fusion CRM XLSX/archive through
core.data-loaderfrom liveIntegrationVendorsmetadata, using the staged CRM values above. - Invoke
core.data-loader.task-hookfor the selected Run Book task. Complete its declared read-only validation rules and build the required Data Loader preview. A missing or failed Task Hook envelope blocks upload. - Present the exact target environment, immutable CRM archive,
FDOS_CREDENTIAL_REQUIREDstaging values, andenabled=false. Upload and initiate only after explicit approval of that exact validated archive. - After the CRM initiation is accepted, return the Data Loader initiation result and stop. Do not poll automatically. On a later explicit user request for status, use the
core.data-loaderstatus workflow. Proceed to CPQ Admin > Integrations > Integration Center only after a successful load outcome is confirmed. The user replaces the placeholders, enables the CRM connection, saves, and confirms it is enabled. Do not enter or retain credentials. End this stage with an explicit outcome: eitherCRM connection configured and enabled, orCRM Data Loader succeeded; user credential and enablement action remains. - Only after that confirmation, generate and validate a separate Generic Integration XLSX/archive with the staged Generic values above; repeat Task Hook validation and obtain a new explicit approval for that exact archive.
- After the Generic initiation is accepted, return the Data Loader initiation result and stop. Do not poll automatically. On a later explicit user request for status, use the
core.data-loaderstatus workflow. Proceed to user-managed credential entry, enablement, save, and read-only enabled-state confirmation only after a successful load outcome is confirmed. End the skill with an explicit outcome: eitherFusion CRM and Fusion Account Integration connections are configured and enabled, or the exact remaining user-managed credential or enablement action.
Approval and security boundaries
- Do not call
/cpq/rest/*/integrationVendorsdirectly. - Do not retain or reintroduce scripts that make direct CPQ Integration Vendor GET, POST, or PATCH requests.
- Do not upload or initiate a Data Loader request without the immutable preflight, approved Task Hook envelope, and explicit approval for the exact archive.
- Never retry a live Data Loader initiation, REST mutation, or UI save without a new explicit approval.
Diagnostics and recovery
Classify failures as input_validation, catalog_mismatch, auth_or_authorization, transport_or_environment, fusion_api, process_failed, artifact_persistence, or approval_blocker.
- For metadata or hierarchy mismatches, regenerate from live
IntegrationVendorsmetadata and revalidate. - For Task Hook failures, preserve the redacted validation result and stop; resolve the selected Run Book task context before creating another archive.
- When the user explicitly asks for a failed Data Loader request's status or errors, retrieve them through
core.data-loader; do not issue a compensating direct CPQ REST call. - Redact credentials, tokens, authorization headers, and sensitive payload values from all workspace artifacts and diagnostics.
Validation
python3 core/data-loader/scripts/generate_sample_dat.py --help
python3 core/data-loader/scripts/validate_data_load_file.py --help
python3 -m unittest discover -s core/data-loader/task-hook/tests -v