Welcome
Samples
Rich UI access to LDAP
To customize a Rich UI project to access an LDAP-compliant server, use the Rich UI LDAP access sample. The sample contains instructions to gain this access and provides files containing code you can use in your projects.
Special considerations for JSON support on IBM i:

Overview
Getting started
Installing
Upgrading and migrating
EGL Code Accelerator for IBD
Developing
Samples
- EGL Text User Interface sample
  These sample programs use a text user interface to maintain the Employee table in the DB2® Sample database.
- EGL Dojo widgets
  You can use samples to practice working with the EGL Dojo widgets.
- EGL Dojo mobile widgets
  You can use samples to practice working with the EGL Dojo mobile widgets.
- EGL bootstrap widgets
  You can use samples to practice working with the EGL bootstrap widgets.
- EGL ionic widgets
  You can use samples to practice working with the EGL ionic widgets.
- EGL Rich UI technical sample
  This sample is a collection of EGL Rich UI technical samples.
- EGL Cordova sample
  You can use samples to practice working with the EGL Cordova.
- Rich UI access to LDAP
  To customize a Rich UI project to access an LDAP-compliant server, use the Rich UI LDAP access sample. The sample contains instructions to gain this access and provides files containing code you can use in your projects.
  - Setup for Rich UI access to LDAP
    Configuring this project takes approximately 5 minutes.
  - Special considerations for JSON support on IBM i:
- EGL access to LDAP
  To customize an EGL project to access an LDAP-compliant server, use the EGL LDAP access sample. The sample contains instruction to gain access and provides files containing code that you can use in your projects. The files are listed at the end of this topic.
Troubleshooting and support
EGL runtime error messages
Reference
Glossary
Using the help
Notices for IBM Business Developer documentation

Special considerations for JSON support on IBM i:

Here are the few considerations while using the JSON parse and generate functions for IBM i as the target environment.

Error handling while parsing JSON on IBM i will be limited and would list down errors on following category:

Table 1.
Seq No.	Error Message ID	Message	Description
1	GEN0350	Function convertFromJSON found an error in JSON string	Generic error statement.
2	GEN0351	Syntax Error. Offset=<Displacement in input JSON String> expected=<Expected char/string> found=<Char/String found in the input JSON String>	Issued when Syntax error is detected.
3	GEN0352	Non-nullable field <FFF> not found in the JSON string	Field (defined as non-nullable) not present in the input JSON string.
4	GEN0353	Non-nullable field <FFF> found to be to null	Value found to be NULL in input JSON string for a non-null field.
5	GEN0354	Value <NNN> would be truncated when copying to field <FFF>	Target field capacity not adequate to store the received value.
6	GEN0355	Iconv conversion error. Character <SSS> cannot be converted to codepage <NNNN>	Code page conversion error.

Below are the return codes which will be provided by JSON Processor to the JSON error handler:

0 - No issues
8 - Non-recoverable error

The JSON string to be processed should not exceed 32767 number of bytes.
Following EGL data types will be included in upcoming releases:
1. Dictionary
2. NUM
3. BIN