feat(integrations): add Oracle Fusion Cloud HCM - #7415
feat(integrations): add Oracle Fusion Cloud HCM#7415BillLeoutsakosvl346 wants to merge 4 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Greptile SummaryAdds a read-only Oracle Fusion Cloud HCM integration with guarded server-side transport, explicit output projection, selectors, documentation, and generated tool metadata.
Confidence Score: 5/5The PR appears safe to merge because no blocking failure remains. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| apps/sim/lib/internal/oracle-fusion-hcm/client.ts | Implements tenant validation, guarded transport, retries, response limits, and exact-token JSON parsing; the previously reported precision concern was withdrawn. |
| apps/sim/lib/internal/oracle-fusion-hcm/operations.ts | Defines bounded read-only Oracle resource operations and projects responses through explicit output schemas. |
| apps/sim/lib/internal/oracle-fusion-hcm/validation.test.ts | Covers tenant, identifier, paging, search, and date validation boundaries. |
| apps/sim/blocks/blocks/oracle_fusion_hcm.ts | Registers the 18 Oracle HCM actions and their operation-specific workflow inputs and outputs. |
| apps/sim/lib/selectors/server/providers/oracle-fusion-hcm.ts | Provides server-side worker, assignment, absence, and absence-type selection. |
| apps/sim/tools/oracle_fusion_hcm/definitions.ts | Declares Oracle tool parameters and credential handling; no follow-up-eligible finding was accepted. |
Sequence Diagram
sequenceDiagram
participant User as Workflow user
participant Block as Oracle HCM block
participant Tool as Server-side tool dispatcher
participant Client as Guarded Oracle client
participant Oracle as Oracle Fusion HCM
User->>Block: Configure read operation and credentials
Block->>Tool: Execute validated tool input
Tool->>Client: Dispatch read-only operation
Client->>Client: Validate tenant and resolve DNS
Client->>Oracle: Pinned-IP HTTPS GET with Basic auth
Oracle-->>Client: Bounded JSON response
Client->>Client: Preserve IDs and project allowlisted fields
Client-->>Tool: Sanitized operation result
Tool-->>Block: Structured output
Reviews (5): Last reviewed commit: "refactor(integrations): align Oracle HCM..." | Re-trigger Greptile
6350f0b to
b477451
Compare
b477451 to
151a5fa
Compare
151a5fa to
8b79d3c
Compare
8b79d3c to
20724c1
Compare
|
@greptile-apps @cubic-dev-ai please re-review the latest commit (20724c1), including the fixes and dispositions on the prior review threads. |
@BillLeoutsakosvl346 Incremental reviews are turned off for this repository. Comment |
|
@cubic-dev-ai review this PR |
@BillLeoutsakosvl346 I have started the AI code review. It will take a few minutes to complete. |
83e7bcb to
1c2968f
Compare
|
@cubic-dev-ai review this PR |
@BillLeoutsakosvl346 I have started the AI code review. It will take a few minutes to complete. |
|
@cubic-dev-ai review this PR |
@BillLeoutsakosvl346 I have started the AI code review. It will take a few minutes to complete. |
Summary
Adds a strictly read-only Oracle Fusion Cloud HCM integration using Oracle's versioned
11.13.18.05REST resources and Basic authentication over TLS.The block exposes 18 actions:
It also adds four server-side selectors for workers, assignments, absences, and absence types, plus eight templates and seven grounded integration skills.
Security and data handling
https://<environment>.fa.<region>.oraclecloud.com/.fa.ocs.oraclecloud.comoriginsNo mutation tools, triggers, OAuth configuration, API routes, dependencies, lockfile changes, database changes, or new icon artwork are included. The block reuses the existing red Oracle oval (
NetSuiteIcon).Oracle references
Verification
A fresh independent reviewer ran
.agents/skills/validate-integration/SKILL.md, reopened current Oracle documentation, checked repository precedents, and completed a fix/revalidation loop. Final result: no unresolved Critical, Warning, or Suggestion findings.The generated integration MDX retains the shared generator's existing trailing-space/EOF convention (also present in existing integration pages).
docs:checkis green; this is not integration-specific.V1 limitations