Skip to content

Custom Action

Overview

Custom Actions are used to enable communication between two Kelvin SmartApps™, whether on the same cluster or across different clusters.

They allow developers to create a dedicated Kelvin SmartApp™ to perform specific tasks that are commonly needed by other Kelvin SmartApps™.

Example

For example, you can create a Kelvin SmartApp™ to send emails or perform specific conversion calculations before saving data to the Kelvin Platform.

The tasks that can be performed are flexible and depend on the developer’s objectives.

Other Kelvin SmartApps™ can then send data to this Kelvin SmartApp™ for processing.

This approach allows you to centralize common tasks or isolate sensitive information, such as email login credentials, within a single Kelvin SmartApp™.

Structure

Custom Actions require two different types of Applications (Kelvin SmartApps™) to be properly setup;

  • Publisher Application: Any Kelvin SmartApp™ that packages and sends the custom action either directly or via a Recommendation
  • Consumer Application (Executor): A specific Kelvin SmartApp™ that will receive the custom action and performs predefined actions on the payload data

Warning

For each Type declared in any Publisher App, only ONE Consumer App (Executor) can be deployed on the Kelvin Platform to receive that Type.

Custom Actions are sent from a Publisher to a Consumer Application.

It can also be packaged into a Recommendation for approval by Operations before the Custom Action is sent to the Consumer App (Executor).

Note

This functionality will work even when there is no internet connectivity as long as the two Applications are on the same Cluster network.

Custom Actions has a robust fault tolerant protocol to ensure all custom actions are traceable and will report failures back to the sending Application.