Overview
| Feature Details | |
| Introduced in Version | 9.20 |
| Modified in Version | 9.20 |
| Location | Public < Integrations < gRPC |
This feature will allow for developers inside the platform to expose flows to be enabled for use with the gRPC protocol. This method of integration is typically used in microservice style infrastructure. It sends over the data in the payload as binary serialized to increase the speed of the completion of the call in compared to REST methods.
Example
Here is an example of setting up a flow to be configured as a gRPC endpoint.
- Create a gRPC Flow
This is a specific flow behavior made to specifically be used for gRPC endpoints. This contains restrictions inside the flow designer to ensure that was you are following the standards needed for the gRPC protocol.
- No Capital Letters, Special Characters, or Spaces in the Flow Name
- Inputs/Outpus Must be Composite Objects
If this criteria is not met then you will get an issue when downloading the protobuf file.
A good tip here is to look at the flow validations. If your gRPC flow has validations, then it will not download correctly.
2. Download Protobuf File
There is an action on the gRPC folder (Public<Integration<gRPC) called Download Proto Files to allow the end user to download the protobuf file. This file is needed for external applications to interact with the exposed services.
3. Use Service
Once you have the protobuf file, you will be able to use the file to call the flows that are configured in the Decisions application over the gRPC Service.