|Code||Code identifying the database in the application|
|Physical name||Physical database name on server. It should only be informed if it is different from logical code.|
|Title||Description that appears in application objects (menu, tools...).|
|DB Server code||Database server code where the database is located|
|Isolation level||Users visibility level of transaction integrity
Options of the connection URL to the database. The connection URL is formed with the data indicated on the BD server. These options will be added to that URL. One example of options for an Informix instance could be: DB_LOCALE and CLIENT_LOCALE.
|Version||Allow to determine the nature of database (Master only, VNext only, Both) if database is not the currrent enviloment then the database application is displayed disabled.
|Rest app||If true, system will look in all database dictionaries to search for embebed REST applications that are marked to be shown in lateral menu. This flag will be automatically set to 0 if system detects no application.
|OLAP client||Enable this flag to allow using this database with OLAP client.
|Portal templates||Indicates if it contains portal templates. Applicable only to dictionary DB.
|Insert||When enabled, insert statements are allowed on this database.
|Delete||When disabled, delete statements are not allowed for this database.
|Update||When flag is checked, update statements are allowed to the database.
|Processes||Indicates if the database accepts process executions regardless of whether the insertion, deletion, and modification indicators are active.
|Requires transactions||When checked, the system veryfies that the database has the transaction mode enabled.
If database is not compliant with this requirement, the database is accessible only in read mode.
|Verification of integrity||
Indicates whether it is necessary to verify certain resources in the database.
When checked, several DB features are verified for integrity:
If any of these resources is not found, the database will be accessible only in read mode.
|Extranet access||This flag allow or decline the access to the database via Axional Studio.
If this parameter is enabled, database will be visible to users who connect to the system via Extranet.
In order for the system to detect if a user connects via Intranet or Extranet, it is essential to correctly configure the localAddress and proxyAddress variables of the JASConfig system configuration file.
|Locked||Flag to enable or disable users access to this database. Generally used for maintenance.
|Initial SQL||These SQL statements (semicolon separated) are executed the first time the connection to the database is established.
They are executed after the Initial SQL defined at the database server.
|Description||Free text describing the database.|
|Web logo||Logo used globally throughout application.|
|Documents logo||File containing the logo of the database for the generated documents. This logo will be used automatically for all print-outs, except otherwise specified.|
|Date created||Date of registering
|Date updated||Date of the last update
|BUT_SCHEMA_MODEL||Build schema||// JSQL.getLinkURL: // The dictionary of wic_conf is wic_admin. The object schema_model is in the wic db // so, this URL must be opened in the wic db to found the object (forced).|
|BUT_SCHEMA_CODE||Compile code||// JSQL.getLinkURL: // The dictionary of wic_conf is wic_admin. The object schema_model is in the wic db // so, this URL must be opened in the wic db to found the object (forced).|