What Happens to my Existing EAE Model?

Outwardly, after migration your model looks substantially different due to the change in developer interface to Visual Studio and the change to more common Object-Oriented terminology. However the basic structure of your model actually remains almost exactly the same.

When you load an existing LCIF model file into Agile Business Suite, its elements are immediately mapped onto the new Agile Business Suite constructs. The model initially has the same structure and form as it did in EA Developer, the elements of the model simply have different names.

Many of the changes in Agile Business Suite are based on the use of Object-Oriented (OO) and component technologies. This allows users to adopt industry-standard design concepts and incorporate the benefits of OO design and development with the traditional strengths of EAE. The changes affect not just the naming, but the implementation and generation of the elements within your model.

Other changes are based on the close integration with Microsoft Windows technologies and the use of Visual Studio as the interface.

These factors combine to enable Agile Business Suite applications to interact more effectively with other systems, and make them easier to customize and maintain.

Refer to Recognizing the Model Elements for more information.

 Caution

  • In EAE, Global Setup Data items become locally scoped during the execution of a Callable GLG. Callable GLGs are migrated to AB Suite as methods. Since GSDs (segment attributes in Agile Business Suite) are not locally scoped within methods, this can result in a change in runtime behavior if the GLG modifies the value of a GSD, or relies on local scoping to initialize the GSD.

  • In EAE, the documentation warned:

    “Do not use a Data Item brought into memory by a DETERMINE; command as a key over its own structure.

    “For example, if the Profile having the key of NAME is over a Component CUST, you can not specify CUST.NAME as a key. If you need to do this, move the value to a Setup Data Item and specify the Setup Data Item as the key.”

    In Agile Business Suite this construct is not permitted, and causes the following validation error:

    Error #2113 Source key ’CUST.NAME’ cannot be used in the key list