Data used by ispecs, or other classes, are called attributes. Transient attributes of ispecs or report methods are equivalent to Setup Data Items defined in EAE. They can also be variables in a business segment class method. Segment attributes are equivalent to Global Setup Data Items defined in EAE.
Note: Single character Setup Data Items and Global Setup Data Items (for example, “A”) are renamed to “Migrated_”<single char SD> (for example, “Migrated_A”), to avoid possible conflict with shadow report names.
System-defined attributes were known as System Data Items in EA Developer. They are now built-in attributes of the segment, and can be referenced in method logic anywhere within their scope.
Note: The Glb.Product read-only built-in segment attribute is no longer relevant, and should be replaced by Glb.IsDebug, a read-only boolean flag ('true' when debugging, otherwise 'false'). On migration, Glb.Product is replaced with Glb.IsDebug where the intent is clear: for example, DW; GLB.PRODUCT = (LINC) is migrated to If NOT GLB.IsDebug. Otherwise, no change is made to the segment attribute on migration: for example MV; GLB.PRODUCT DA20 is migrated as-is to Move GLB.PRODUCT DA20.
Attributes have properties that describe the data, such as the size and kind of data they need to store, and whether the data is written to the runtime database or not.
An attribute has a number of properties which describe its role and the kind of data it needs to store.
Attribute properties are described in detail in the Agile Business Suite Developer Online Help.
Mapping between Agile Business Suite Attributes and Enterprise Application Environment Usage Types
AB Suite <<ispec>> Class Attribute Properties | EAE Usage Equivalents | |
|---|---|---|
| Direction | Persistence |
|
| InOut | No | Input |
| InOut | Yes | Input-Output |
| In | No | Input, but cleared |
| In | Yes | Input-Output, but cleared |
| Out | No | Inquiry |
| None | Yes | Out |
| None | No | Setup Data Item |