Invantive Estate

Based on a minimum of data input, the function autocomplete of Invantive Producer, will produce and add the necessary requirements to run the application. This usually saves a factor five to ten in volume of work.

The necessary data for autocomplete are:

•Application.

•Tables.

•Table columns with the exception of system columns, but including referential ID columns.

•Natural key indexes and columns.

•Image Function for the view name to the alias via the Invantive Producer code domain ‘<application code>_lov_view_name_to_code’.

•Names of business views.

•Reporting views.

•Business rules.

•Possible extra view elements which cannot be determined automatically. For these views, use serial numbers of 900 or higher.

The autocomplete subsequently performs the following actions:

Cleanup:

•Remove remains of data in the repository that were created previously with the autocomplete function for the selected application.

Add technical fields:

•Create for each table a column ‘ID’ that will be used as primary key if it does not exist already.

•Each table gets a primary key named ‘<application code>_<table alias>_pk’ with the column ‘ID’.

•Create for each table the following audit columns if these do not exist already: creation date, created by, created in, transaction creation, date last updated, last updated by, last updated in, transaction last updated, date created by interface, date updated by interface, initial system group, unique original system reference, free column type and ten free-columns.

•A unique index named ‘<application code>_<table alias>_uk_orig’ is created for the original unique system reference.

LOV-views:

•LOV views for each column in the data model with a name ending with the code column postfix as set in the application (usually ‘ind’). The name of the view is based on the application setting View name, in which the occurrences of ‘:tcn_name’ will be replaced by the name of the column, without the code column postfix. The alias of the LOV view will be retrieved from the description of the code value in the code ‘<application code>_lov_view_name_to_code’ in Invantive Producer. The definition of the view is based on the application setting View template, in which the occurrences of ‘:tcn_name’ are being replaced by the name of the column, without the code column postfix.
For example: The column ‘gender_ind’ results to a LOV view named ‘<application code>_lov_gender_r’.
No LOV view is added if a view with this name already exists.

•For each LOV view an artificial table will be rendered, so LOV views can also be used to establish relationships.

•For each LOV view also a referential constraint will be created between the artificial table and the related column.

Referential constraints and related indexes:

•A referential constraint is added for each column that begins with three letters and ends in ‘_id’ of ‘_id_’. The three letters are used to determine the appropriate table.

•Referential indexes are added for each column that refers to a different table.

Business Objects

•For each table a business object will be created which contains all the tables to which this table refers directly or indirectly.