This tutorial is to explain the Inbound V3 processing. The Inbound V3 processing is based on the Message type. Please refer to the admin guide( What is Message Type)and the tutorial ( How to use Message type ) to understand the concept of the message type. Inbound V3 is very powerful than Inbound V2 because it supports hierarchical data which can be designed by the message type directly. For example when using with V2 and when we have a hierarchical data (Account and contact) we need to create two Interfaces and use IChain for building the relationship between the parent and child. However, Inbound V3 we don’t need to create two interfaces separately and use IChain. We just need one Interface with Message Type to do mapping. This means that with the new version V3 the design and processing of hierarchical data is enormous simplify and easier (follow this guide The new Inbound processing with version v3 ) to detail more. In addition, Inbound V3 support different processing mode like can normal integration, Batch, Bulk Mode, and Auto-Switch Mode. Follow this tutorial to understand what are the different modes and when we use their mode ( When to use synchronous, batch or bulk interface? and when to use Auto-Switch Mode? ).
Enhance new Inbound V3 processing
There are two techniques in new Inbound V3 for flexible way to enhance the process of flow among with Plug-In block and Replacement block.
- Plug-In block is the technique that gives the ability for solving user requirement. this means that the user can extend our existing class or can add their class to existing Skyvva classes. A custom class can be apex class, flow or a process.
We have the following plug-in block which could make sense:
- Before processing
- Before Mapping
- Before Workflow
- Before Operation
- After Processing
- Replacement block is the technique that the user can use a custom class to override our SKyvva Classes. User can replacement block to 4 standards Skyvva processing:
- Create Message
Here’s the picture of Inbound V3 processing
As the picture above we can see two Inbound processing such as old and new. In old Inbound processing work with Skyvva 4 steps, first of all, When we import the data, the data will create a message and then go to check the workflow that we use. next is checking the Mapping and final step it will do Operation (Upsert, Insert, Update, and delete). So this old Inbound V3 is not flexible because it cannot make us use our own logic. That why SKYVVA has to enhance the new one Inbound V3. The new Inbound V3 has the same SKYVVA flow as the old but we add more features which have Custom replacement and Custom Plug-in to help User do own business logic.
So as we know the processing of inbound V3 work base one Message Type, we can assume that Inbound V3 is more useful than Inbound V2 because Inbound V3 can help the user to do plug-in block or replace block. Also, When we use Inbound V3 we don’t need two Interfaces like Inbound V2 to import hierarchical data because Inbound V3 is work base on Message Type that can help create a hierarchical structure to do mapping. Follow this link How to create Custom class?