Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


There are several reasons why “compatibility” mode is necessary (especially when converting existing RPG applications): 

  • Field names in DDS-converted Rich Display Files are not case sensitive by default because Rich Displays work with a variety of back-ends, some of which are not case sensitive. Validation rules in the Visual Designer treat bound fields with the same name but a different case as the same field. The Visual Designer's Field List Tab normalizes all bound fields to the same case. 
  • The displays made with Visual Designer for RPG OA are not case sensitive, because RPG is not a case sensitive language. So, in order to reuse the same displays for RPG and Node.js without having to recreate and/or adjust everything for Node.js usage, we use “compatibility” mode.
  • It is not uncommon to have the same field name appear in different types of declarations. The same field can appear in a declared physical file, a declared display file, and/or declared as a global field in a data structure – it is often important that all of these occurrences are treated as the same field.