An internal custom step can be used in a project data or master data flows, and can be limited to an integration between specific provider applications. Internal custom steps must be coded in Java and can be used anywhere in a flow step sequence. For example, use an internal custom step to transfer project data from a Sample to File integration.
The flow steps are organized as follows:
- Load from Source: This step loads the data from the source application into the Gateway framework so that it can be processed.
- (Optional) <Internal Custom Step Name>: This step can be used anywhere in the flow sequence. In this case, this step loads the internal custom step to the source data.
- Convert from Source to Gateway Format: This step converts the source data to the Gateway format.
- Convert to Destination Format: This step converts the data from Gateway format to the destination format.
- (Optional) <Internal Custom Step Name>: This step can be used anywhere in the flow sequence. In this case, this step loads the internal custom step to the destination data.
- Update Destination: This step saves the data into the destination application's database.
- (Optional) <Internal Custom Step Name>: This step can be used anywhere in the flow sequence. In this case, this step loads the internal custom step to the destination data.