This information applies to the use of the various files during a compilation, whatever their location (AS/400 or PC).
Message parameters
Data entry
Message file
Name of the file containing the error messages for the environment.
If the name is not defined at an application area level, this file will be used by default.
Default prefix
Prefix of error messages.
If the prefix is not defined at an application area level, this prefix will be used by default.
Crystal Reports
Radio buttons
Type of interface file (read only)
Specifies the interface file format used for data modeling:
XSD interface file |
The interface file for fields to include in the report is in XSD format (XML schema) → database type: ADO.NET(XML) |
TTX interface file (default) |
The interface file for fields to include in the report is in TTX format → database type: Field definition only |
TTX format is used by default. The CRFieldsOnlyToXSDutility must be used to migrate to XSD format (the only valid format when using a Crystal Reports 64-bit runtime).
Check boxes
Compatibility with Crystal Reports 2008 and later versions
Box checked |
Compatibility with Crystal Reports 2008 and later versions is guaranteed. This compatibility concerns the management of DATE and TIME Adelia types in the reports. If compatibility mode is activated, the Adelia types listed above are transposed into the same Crystal Reports type, and one only: the DATE/TIME type. The latter is the type that is already used for the transposition of the TIMESTAMP Adelia type. |
Box unchecked |
Compatibility not guaranteed. |
The use of only one Crystal Reports type for date/time data, means that the fields must be formatted appropriately during the layout design phase. Reports created with this compatibility mode are still compatible with older versions of Crystal Reports.
Note: the UpdCRDateFields tool enables you to convert all the reports present in an Adelia environment or in a Windows file management manager folder and make them compatible with Crystal Reports 2008 and later versions.
Size 50 exceeded warning
Box checked |
For descriptions that can be used when generating an AS/400 object, the text turns red when it exceeds 50 characters (description limit on AS/400 objects). |
Box unchecked |
No warning when the description size exceeds 50 characters. |
↑ Top of page
Level 2 and data flow generation parameters
Data entry
Replacing character
The default value is the character "$".
Lists
Generation type
Indicates how the management rules will be processed during level 2 generation.
The type is assigned to a program when the latter is created. It can be modified each time level 2 generation is requested.
Generating DB accesses
Initial value taken by a Visual or Web program when created.
Possible values:
Native access |
The data flow generation and the level 2 generation create 4GL instructions corresponding to database native accesses. |
SQL access |
The data flow generation and the level 2 generation create 4GL instructions corresponding to database SQL accesses. |
Click here for more details about the data flow and level 2 generation. ↑ Top of page
Bug manager
Data entry
Extension DLL
Extension DLL (plugin) making it possible to interface Adelia Studio with an external bug manager. Adelia is provided as standard with a JIRA interface (adeljira.dll) for managing JIRA forms via the product and mapping the Adelia correction manager lifecycle with the lifecycle of the JIRA forms associated with the corrections. Other bug managers may eventually be interfaced.
The plugin can add functionality to some Adelia applications (environment and application area parameters, software engineer parameters, session manager, correction manager, 4GL editor). See JIRA plugin documentation for more information.
Note: the plugin is loaded at start-up. If you change this parameter, you must close and re-open the Adelia applications and environment attributes to apply the change.
Source code repository
Data entry
Shared URL
URL giving access to the source code repository which is "https://server:port". You must type in this parameter if you want to use a source code repository shared by all users.
If this parameter is specified, it has priority over any "user" installations that may have existed previously.
Note: if the server was configured using the source code repository installation wizard, this parameter is indicated automatically.
Check boxes
Synchronize source code repository automatically
| Checked | Objects will be automatically exported, renamed, moved or deleted in the source code repository when they are changed in the environment (private object change, attachment or detachment, visibility change). Similarly, if source control is configured, objects will be automatically renamed or moved in the source manager if necessary (for example, in this case with SVN, you keep the change log). When this option is checked, the automatic backup or deletion options are no longer accessible in the 4GL editor as the export or deletion is taken into account by the synchronization. |
| Box unchecked | No automatic synchronization management. For example, a private object detached from an application area will keep its source in the repository. This can result in duplicates being displayed, for example if a private object is detached from the application area. |
Buttons
Undo
This button cancels the modifications made and restores the application to its previous state.
Default
This button cancels the modifications made and restores the application to the state it had when the environment was created.
Note: A click on the icon 
situated on the upper left-hand corner of the dialog box closes the box (keyboard shortcut: Alt+F4). If modifications were made, a confirmation screen appears.