Platform RCP — Integration

Overview

Call EngagementHub operations over Velaxe RCP with trusted application provenance and the same canonical authorization/runtime used by Handler.

Capabilities

• Provides POST RCP paths for runtime-enabled operations

• Uses Core InterAppRequestContext for caller and workspace provenance

• Supports system capability discovery before grant configuration

• Enforces operation grants for business calls

• Converges into the same runtime as Handler and Bridge

1. 1

   Step 1

   Inspect EngagementHub capabilities.

   Back to top
2. 2

   Step 2

   Choose the required operation identifier.

   Back to top
3. 3

   Step 3

   Configure the caller application grant.

   Back to top
4. 4

   Step 4

   Call the EngagementHub RCP operation through Core AppRpcService.

   Back to top
5. 5

   Step 5

   Allow operation and resource authorization to run.

   Back to top
6. 6

   Step 6

   Process the canonical response in the caller application.

   Back to top

Limitations

• RCP calls require platform-established caller identity.

• Mutating operations use the same domain services as other trusted transports.

• Resource policies distinguish workspace-owned and caller-owned resources.

FAQs

Pricing