If you have developed a custom client application for Component Enabler in EAE 3.3,
note the following differences in data item names between EAE and AB Suite:
Two data item names have been changed to accommodate AB Suite requirements. These changes occur on every Ispec and require updates to the custom client application.
MAINT -> _UserMAINT ACTMTH -> _ACTMTH
Note: You will not need to make any changes in the custom application immediately, since the Component Enabler Runtime environment automatically translates between the EAE and AB Suite names in these cases. However, you should plan to apply the changes to your custom client application as soon as possible.
Ispecs that insert Insertables (GLGs) will have the names of the inserted data items qualified with the name of the insertable class that it originates from:
<glg-data> -> <glg>$<glg>$<glg-data>
For example, Changes on "DATA1" inserted by "GLG1" is:
DATA1 -> GLG1$GLG1$DATA1
This allows you to have multiple fields on an ispec with the same name, qualified with their originating insertable name and the instance name (in the example above, the instance name is the same as the insertable name - GLG1). For Component Enabler client applications, the fully qualified field names is used in Agile Business Suite.
Customers that use the supplied generators to create their client applications are not impacted by this difference, since the new qualified names is used to generate the client application modules. However, for custom client applications, the field names in the custom client code need to be updated to the new qualified names.
In some cases, the name changes required to the custom client code might be extensive. Consequently, the Component Enabler Runtime environment has been enhanced to automatically map requests for the old style EAE names, to the new qualified names. This is done automatically for you. However, it is not a final solution, and it is recommended that the required changes to the custom client code be applied as soon as possible, to avoid potential problems when duplicate field names are inserted into an Ispec (which is possible in Agile Business Suite because they are qualified by the name of their insertable).
If the Component Enabler log file has been activated, a message warning of the name substitution is logged. These log messages can also serve as a useful indicator of which fields need to be updated in the custom client code.