Accelerated development process
- Pre-defined structures are available for EDI formats
- Built-in validation for mandatory properties
- Serialization of EDI 270 structure
- De-serialization of EDI 271 structure
- Serialization of EDI 276 structure
- Deserialization of EDI 277 structure
- Serialization of EDI 278 structure
- Deserialization of EDI 278 structure.
User can construct/generate EDI 270 structure by calling a serialization action which takes pre-defined Edi270 outsystems structure and convert it into EDI structure and returns output in string format and binary data format.
User can convert EDI structure into pre-defined EDI 271 Outsystems structure by passing EDI structure as a string or binary data to the de-serialization action.
User can construct/generate EDI 276 structure by calling a serialization action which takes pre-defined Edi276 outsystems structure and convert it into EDI structure and returns output in string format and binary data format.
User can convert EDI structure into pre-defined Edi277 Outsystems structure by passing EDI structure as a string or binary data to the de-serialization action.
User can construct/generate EDI 278 structure by calling a serialization action which takes pre-defined Edi278 outsystems structure and convert it into EDI structure and returns output in string format and binary data format.
User can convert EDI structure into pre-defined Edi278 outsystems structure by passing EDI structure as a string or binary data to the de-serialization action.
The component will check whether all the mandatory fields which are required in the EDI structure are available or not, if not available then error messages will be returned
Not in forge