The document object model consisted of the following naming conventions:
2.x: document.bodyform.EO__Name__STR and document.forms['bodyform'].EO__Name__STR
3.x: document.forms['mainForm'].EO__Name__STR
which must be renamed to for 4.x and 5.x
document.forms['mainForm'].elements
Binding to system fields and usage of system fields in Javascript will require edits. For example,
EO__NumberString__STR
must become
enterpriseEntity.idNumber
Also, you must check for changes in field names in the object model. For example the version 2.x field numberString became idNumber in later versions.
In 2.x custom field names were formatted as: EO__Detail_{category}__{fieldType}_{fieldName}__{paramType}
In 4.x these must be formatted as:
command_categories[category]_customFields[fieldName]_value
So in the example below, custom field name
EO__Detail_OPPS__DetailNumbValue_PlAcOCReserveChange__DBL
will become
command_categories[OPPS]_customFields[PlAcOCReserveChange]_value
Access to elements in a form, in Javascript, must be rewritten like this:
document.bodyform.EO__Name__STR.value
becomes
document.forms['mainForm'].elements['applicationEntity.name'].value
i.e. document.bodyform becomes document.forms['mainForm']
Another example:
document.forms['bodyform'].EO__Detail_LITP_OUTC__DetailTextValue_InvAccrual5__STR.value
becomes
document.forms['mainForm'].elements['command_categories[LITP_OUTC]_customFields[InvAccrual5]_value'].value