RadixWare Programmer Guide/Definition Types

From RadixWiki
Jump to: navigation, search

Module Editor

The module editor can contain the General and Exported services pages. The editor looks as follows:

Module-editor.jpg


"General" Page

The page is used to define the common parameters of the module:

  • Description. The module description.
  • Test module. If the flag is set, the current module is the module for module tests. The module cannot depend on the module of module tests, only if it is a module of module tests itself.
  • Deprecated. If the flag is set, the module is considered deprecated. When compiling, the system will display a warning message each time such module is used.
  • Under construction. If the flag is set, the module will be included in the releases being created. If the particular module already exists and the flag is set, it will be copied from the previous release version while building release. The parameter displays only for the modules of the ADS segment.
  • This module is companion of. The module for which the current module is a companion. The parameter is displayed only for the ADS modules that were not overridden by another module.
  • Dependencies and used definitions. A list of module dependencies. If the flag is set in the Forced column, the module will not be deleted from the list of dependencies if it is not used. The following buttons are located to the right of the list:
Button Description
Add-button.jpg Adds a module to the list of dependencies.
Remove-button.jpg Removes the selected module from the list of dependencies if it is not used. It is not possible to remove the module from the list of dependencies if it is used.
Goto-button.jpg Opens the editor of the definition selected in the list of dependencies.
Find-usages.jpg Displays a list of usages in the current module of the definition selected in the list of dependencies. The list is displayed in the Usages pane.
Actualize.jpg Removes the unused definitions from the list and adds the used ones automatically.


"Exported Services" Page

The page is displayed only for the modules of the ADS segment. The page is used to define a list of service (interface) implementations in the current module. In the Environment parameter, specify the execution environment where the service implementations are used. Available values:

  • <all>. For all execution environments.
  • Desktop. The service can be used in the RadixWare Explorer environment.
  • Server. The service can be used in the RadixWare Server environment.
  • Common. The service can be used in any environment.
  • Client-Common. The service can be used in any client environment (Desktop or Web).
  • Web. The service can be used in the RadixWare Web Presentation Server environment.

The following table describes the buttons located to the right of the service list:

Button Description
Add-button.jpg Adds the service implementation to the list. When executing the operation, the dialog box opens for selecting the service (interface) and its implementation.
Remove-button.jpg Deletes the selected service.


Module Context Menu

For the description of the context menu items common for all definition types, refer to Definition Context Menu. The specific context menu items of the module are described in the following table:

Menu Item Description
Build Compiles all the definitions of the selected module.
Clean and Build Executes the Clean and Build operations in a sequence.
Clean Deletes the runtime files created during the last executed building or compiling.
Configure Images… Opens the editor of module images (refer to Set of Module Images).
Dependencies Shows the Module Dependencies panel displaying the list of module dependencies.
Hide Hides the module. The hidden modules are not displayed in the project tree. To manage the hidden modules, use the Hidden Nodes branch in the navigation tree.

Set of Module Images

The editor is used to manage images related to the module. These images can be used as icons and logos and displayed in the client application.

images-set-editor-1.png

The Find parameter is used to search through the set of images. Entering the text in the parameter displays the images with names that match the entered text. At that, the following flags are displayed under the Find parameter:

  • In name. Searches the text in the image names.
  • In keywords. Searches the text in the image keywords.
  • In description. Searches the text in the image descriptions.
  • Whole word. Searches the whole word.


The field in the main part of the editor displays a set of module images. If the Show names flag is set, the image name is displayed below each image. If the Original size flag is set, the images are displayed in their real size. Otherwise, all images are of standard size (64x64 pixels).

The following buttons are located to the right of the set of images:

Button

Description

edit-button.jpg

Opens the image in the program associated with the image type in the OS.

replace-button.jpg

Replaces the selected image. Clicking the button opens the dialog box for selecting the file with a new image.

properties-button.jpg

Opens the dialog box with image properties. The dialog box contains the following parameters:

  • Name. The image name. The parameter is mandatory.
  • Keywords. The image keywords. They can be used when searching for the images.
  • Description. The image description.

add-button-small.jpg

Adds an image. When clicking the button, the system requests the type of the image being created (supported the following formats: SVG, PNG, GIF, JPG). After that, the associated program opens the created image.

import-button.jpg

Imports an image. Clicking the button opens the dialog box for selecting the file with the image.

export-button.jpg

Exports an image. Clicking the button opens the dialog box for selecting the file where the image will be saved.

remove-small-button.jpg

Removes an image from the set. The user is asked to confirm the action.

used-by-button.jpg

Finds all places where the selected image is used.

Merge changes.jpg

Merges changes between the SVN repository version and local working copy.

Database Definition Segment

The Database Definition Segment (DDS) is used to define the structure and logic of data storage.

The DDS module can contain:

  • The parameters of creating the objects in the database:
    • Prefix of object names in the database.
    • The default tablespace for the tables.
    • The default tablespace for the indexes.
  • Pre- and Post- Installation Scripts.
  • Tables.
  • Views.
  • References between Tables.
  • Sequences.
  • PL/SQL Packages.
  • PL/SQL Types.

Modifying DDS Module

To change any definitions in the DDS module, it is required to capture this module. For this purpose, select the Capture structure item from the module context menu in RadixWare Designer navigation tree. The captured modules are marked with bold font in RadixWare Designer navigation tree. When updating the work copies, other developers will see that the module is captured. To finish the session of modifying the module, it is required to select one of the two items of the module context menu in RadixWare Designer navigation tree:

  • Commit structure. Commits the changes in the module.
  • Cancel capture. Cancels the capture of the module. All changes will be canceled.

When committing the changes, the script of the database modification is generated. The script is displayed in the dialog box of committing the changes:

Fix-structure.jpg

The generated script can be changed in this dialog box if required.

In the Backward compatible area, select one of the options indicating whether the change requires the applications server restart when installing the update:

  • Compatible. The applications server restart is not required.
  • Incompatible. The applications server restart is required.

Note.jpgThe change does not require the applications server restart if the database structure is compatible during all the stages of the script work. For example, the script that deletes a table and then creates it again will require the application server restart since there is a state when the applications server cannot work in the course of script work (there is no necessary table in the database).

In the process of committing the DDS module, the SVN Commit operation is executed. It commits the changes to the SVN repository.

SQL Scripts

SQL scripts changing the database structure according to the changes made in the DDS segment by the developer are automatically generated by RadixWare Designer. The automatically generated scripts are displayed to the developer when fixing the DDS module. The developer can correct the automatically generated scripts if required.

The DDS module is also used to define the SQL scripts that must be executed before and after the automatically generated scripts.

Pre-processor Directives

In addition to PL/SQL instructions, it is allowed to use pre-processor directives. The constructions of the following type are supported:

Example.jpg 
#if isDefined("ORA_EDITION") and ORA_EDITION == "STD" then
...
#else
...
#endif

Where ORA_EDITION is a script parameter. Over the script parameters, the following is supported:

  • isDefined() function - checks if the value for this parameter is specified
  • == operations (equality test), + and - (summation and subtraction for numeric parameters), and ! (negation of conditional).

The PL/SQL instructions between the #if and the #else directives will be executed if the specified condition is fulfilled; otherwise, the instructions between the #else and the #endif directives will be executed.

The script parameters are defined by the system administrator when installing or upgrading the software products using RadixWare Manager. Moreover, the values of parameters can be defined in the scripts by means of the string of the following type:

Example.jpg!TABLE_ROWS=1000

Data Types in Database and RadixWare Types

A standard set of database basic data types does not match the set of basic types in RadixWare (they are based on Java types). For example, to store integer values in Oracle, the NUMBER type is used, while in Java, Int type is used. In the DDS definitions, the type used in JML is specified for table rows, views, etc. The data type used in the database is selected automatically on the basis of JML type selected by developer. The developer can refine the automatically selected type by defining the length and accuracy. The platform is responsible for the data conversion.

Diagram

The tables, views, references and sequences are provided on the database diagram. To edit the diagram, use the visual editor.

The tables, views and sequences are shown on the database diagram as rectangles with the list of columns and other attributes. The references between the tables are shown as arrows.

The diagram editor looks as follows:

Diagram-window-small.png

To add an element to the diagram, select the Add <object type> item from the context menu of the blank space of the diagram.

To add a reference between the tables to the diagram, left-click the parent table while holding the Alt key (or two keys Ctrl and Alt), move the mouse pointer to the child table and release the button. At that, the reference editor is opened (refer to References between Tables).

To delete an element from the diagram, select the Delete item from the context menu.

To open the editor of a table, view, sequence or reference, double-click the element or select the Edit item from its context menu.

Tables

The table definition in the DDS defines the following:

  • a set of columns
  • indexes
  • triggers
  • database parameters
  • initial data
  • audit parameters

The table definition also specifies whether entity classes and application classes based on this table can have user-defined properties.

The table of the top layer can overwrite the table of the lower layer. At that, it can add the columns (with the null property or default property to provide the migration) and define indexes, triggers, records (data) and database parameters.

Table Editor

The table editor looks as follows:

Table-editor.png

The table definition editor contains several pages:

"Main" Page

The page is used to define the common parameters of the database table:

  • Name. The name of the table definition.
  • Deprecated. If the flag is set, the table is considered to be deprecated. When compiling, the warning will be displayed each time the table is used.
  • Overwrite. The definition of the table that is overwritten by the current one. The parameter is not available if the current table does not overwrite another one.
  • DB Name. The table name in the database.
  • Description. The description of the purpose of a table.
  • Generate in database. If the flag is not set, the table will not be created in the database by the generated scripts.
  • Additional database attributes. The parameters define the table properties specific for the database being used.
    • Tablespace. The tablespace where the table must be created.
    • Partitioning. The fragment of SQML query that defines partitioning for the table.
    • Global temporary. If the flag is set, the table will be temporary.
    • On commit preserve row. If the flag is set, the ON COMMIT PRESERVE ROW statement will be added to the table definition. The parameter is available, if the Global Temporary flag is set.
  • Audit. The parameters define the audit settings for the current table.
    • Insert, Update, Delete. The flags enable audit of the respective actions with the table.
    • Reference. The reference between tables that is used to select the audit scheme for the current table.
  • Extensions options. The parameters define behavior of the object-relational mapping (ORM):
    • Support user properties. If the flag is set, the classes based on the table can use the user properties.
    • Use as user properties object. If the flag is set, the current table will store the user properties of the Object type for other classes.
    • Enable application classes. If the flag is set, the application classes based on this table can be created.


"Columns" Page

The page is used to define the properties of certain table columns. On the left side of the page, there is a list of columns. The items to the right manage the properties of the selected column in the list.

The following parameters are displayed in the list of columns for each column:

  • T. The column type displayed as an icon.
  • Name. The name of the column.
  • Type. The column type.
  • P. If the flag is set, the column is included in the primary key.
  • M. If the flag is set, the NULL value is prohibited in the column.
  • F. If the flag is set, the external key is related to this column.

Below the list of columns, there is a set of buttons to manage the list.

The right side of the Columns page contains the Main and Values pages.


"Columns | Main" Page

The page contains the following basic parameters of the column:

  • Name. The name of the column.
  • Column template. The template used by the column. If the parameter value is defined, the Value type, DB type, Length, Precision parameters are not available.
  • Value type. RadixWare data type used to view the values in the column.
  • Length. The data length in the column. The parameter is available only for some data types.
  • Precision. The data precision in the column. The parameter is available only for some data types.
  • DB type. The data type used for the column in the database. It is set automatically on the basis of the Value type, Length, Precision parameter values. The parameter is not editable.
  • Description. The description of the column purpose.
  • Generate in DB. If the flag is set, the generated scripts will create this column.
  • DB name. The name of the table in the database.
  • SQL expression. If the flag is set, the SQL expression is defined in the SQML editor to calculate the values in the column.


"Columns | Values" Page

The page is used to define the rules of filling the column with values:

  • Sequence. The sequence that must be used to receive the column values.
  • Audit. The Insert, Update, Delete flags enable audit of the respective operations for the column.
  • Use default value. If the flag is set, the radio button below defines the default value for the column. Available values:
    • Value. The default value is specified in the parameter to the right side.
    • Current system date and time. The default value is the current date and time (the sysdate() function) (it is available only for the columns containing the date and time value).
    • Current system date and exact time. The default value is the current date and time (the systimestamp() function) (it is available only for the columns containing the date and time value).
    • Expression. The default value is defined by the expression specified in the parameter below.
  • Generate check constraint. If the flag is set, the current column in the database will be related to the constraint defined in the Validation rule SQML editor. The DB name parameter defines the name of the constraint used in the database.


"Indices" Page

The page is used to define the indices related to the table. On the left pane of the dialog box, there is a list of indices and a set of buttons to manage the list. On the right pane, there are two pages: Main and Database Options with the items managing the selected index.


"Indices | Main" Page

The page contains the following parameters:

  • Name. The index name.
  • DB Name. The index name in the database.
  • Generate in database. If the flag is set, the generated scripts will create the current index.

Below, there are two lists. The left list contains the columns included in the index, the right one contains all other columns. To move the columns between the lists, use the buttons with arrows.


"Indices | Database Options" Page

The page contains the following parameters that refine the use of index in the database:

  • Generate unique constraint (secondary key). If the flag is set, the unique constraint (secondary key) will be generated for the current index in the database. At that, the control elements further in the list will be available.
  • DB name. The name of the database used in the database. The parameter is available if the Generate unique constraint (secondary key) flag is set.

The following flags correspond to SQL clauses of the same name used when creating the constraints:

  • Rely
  • Disable
  • Novalidate
  • Deferrable
  • Initially deferred
  • Additional. The additional index parameters:
  • Tablespace. The tablespace where it is required to locate index.
The following flags correspond to SQL clauses of the same name used when creating indexes:
  • Bitmap
  • Local
  • Nologging
  • Invisible
  • Unique


"Triggers" Page

The page enables to define triggers connected with this table. On the left pane of the dialog box, there is a list of triggers and a set of buttons to manage the list. The items on the right pane define the parameters of the selected trigger:

  • Name. The name of the trigger.
  • DB name. The name of the trigger in the database.
  • For each row. If the flag is set, the trigger will be executed for each row.
  • Disabled. If the flag is set, the trigger will be generated when it is disabled.
  • Actuation time. The time when the trigger is activated. Available values:
    • Before. The trigger will be activated before the operation.
    • After. The trigger will be activated after the operation.
    • Instead of. The trigger will be operated instead of the operation.
  • Triggernig events. The parameters define the events when the trigger must be activated:
    • Insert. If the flag is set, the trigger will be activated when adding the data to the table.
    • Update. If the flag is set, the trigger will be activated only when the table is changed.
    • For columns. A list of table columns that will cause the trigger activation when changed. The parameter is displayed when the Update flag is set.
    • Delete. If the flag is set, the trigger will be activated when the records are deleted from the table.
  • Type. The purpose of the trigger. Available values:
    • For audit. The trigger is automatically generated to support the audit.
    • For user properties. The trigger is automatically generated to support user-defined properties.
    • None. The trigger is defined by the user.

The parameter is not editable.

The SQML editor located below is used to define the trigger code.


"Initial Values" Page

The page defines the data added to the table when it is created. The table that occupies the major part of the page contains the data to be filled in. The buttons on the right pane are described in the following table:

Button Name Description
Add-column2.png Add Column Adds the column from the table.
Del-column2.png Remove Column Removes the selected column.
Add-row.png Add Row Adds the row of initial values.
Del-row.png Remove Row Removes the row.
Remove-all.png Clear Clears the list of initial values.
Move-up.png Raise Selected Row Moves the selected row up.
Move-down.png Lower Selected Row Moves the selected row down.

Views

The definitions of views in RadixWare provide the interface to the views defined in the database. The view defines the same parameters as the table does. In addition to it, it defines SQML query.


View Editor

The view editor contains the same elements as the table editor (refer to Table Editor) and the Query additional page.

The Main page contains the following parameters:

  • Check option, Read only. The flags correspond to SQL clauses of the same name used when creating the view.
  • Distinct. If the flag is set, all the select queries from the view will be executed using the DISTINCT clause that combines the same records.

The Query page is used to define SQML query that selects the data for the view.

References between Tables

Two types of the references between the database tables are supported:

  • Link. The "one-to-many" reference between the tables.
  • Master-detail. A special reference "one-to (-one or -zero)" that is used to organize polymorphic tables.


Editor of References between Tables

The editor looks as follows:

Table-link-editor.jpg

The editor contains the following parameters:

  • Name. The name of the reference. It is generated automatically. The parameter is not editable.
  • Type. The reference type. Available values: Link, Master-detail.
  • Auto DB name. The name of the reference in the database.
  • Generate in database. If the flag is not set, the scripts being generated will not create the current reference in the database.
  • Database options. The flags correspond to SQL clause of the same name used when defining the reference.
  • On parent deletion. The parameter defines what must be done when the record is deleted from the parent table. Available values:
    • Prohibit if children exist. Deletion is prohibited if the child records exist.
    • Delete cascade. The records are deleted in cascade (corresponds to the ON DELETE CASCADE SQL statement).
    • Set all child reference columns to NULL. The child reference column is set to NULL (corresponds to the ON DELETE SET NULL SQL statement).
    • Do not modify children. Does not modify the child records.
  • EAS checks if children exist. The parameter defines when the applications server must check if child records exist. Available values:
    • Always. Always check.
    • Never. Never check.
    • Only for single object. Check only when deleting a single object.

The parameter is available only if the Forbid if children exist value is selected in the On parent deletion parameter.

  • Confirm children deletion/modification. If the flag is set, the user is asked to confirm the deletion of parent records.
  • Based on. The parameters define what columns the reference must be based on:
    • Primary key. If the flag is set, the primary key of the parent table will be used.
    • Secondary key (index). If the flag is set, the specified secondary key will be used.

The Fill Parent Columns button (Move-down.png) fills the list of columns in the parent table. The reference must be based on these columns.

The list in the lower part of the dialog box contains column pairs from the parent and child table. These pairs are used for the reference.

Sequences

The sequence definition is the sequence defined in the database.

Sequence Editor The sequence editor contains the following parameters:

  • Name. The name of the sequence.
  • DB name. The name of the sequence in the database.
  • Minimum value, Maximum value. The minimum and maximum value of the sequence.
  • Start with. The value of the sequence to start with.
  • Increment by. The increment by which the sequence ascends.
  • Cache. A number of the values of the sequence the database calculates in advance (the CACHE clause in the definition of sequence).
  • Cycle. If the flag is set, the sequence will be cyclic (the CYCLE clause in the definition of sequence).
  • Order. If the flag is set, it guarantees that sequence numbers are generated in order of request in case the database cluster is used. (the ORDER clause in the definition of sequence).

Column Templates

Sometimes, when developing the database structure, it is required to have columns with identical settings (the name, type, etc.). To simplify the support of equal settings of such columns, RadixWare enables to define the column templates.


Column Templates Editor

The column templates editor contains the following parameters:

  • Name. The name of the template.
  • Value type. The data type in the column.
  • DB type. The data type used to store the values in the database. It is set automatically and based on the values of the Value type, Length, Precision parameters. If the value selected in the Value type parameter is different from the DB Type, the parameter is not editable. Otherwise, the value is selected from the PL/SQL types available in the current scope.
  • Length. The maximum data length in the column.
  • Precision. The number of decimal places to be stored for fractions.
  • Description. The description of the template purpose.

PL/SQL Types

The type definitions allow creating types of data to be defined in DB. RadixWare Designer enables to change the structure of type fields using a special editor or define it explicitly in the SQML editor.


PL/SQL Type Editor

The editor looks as follows:

Db-type-editor.jpg

The editor contains the following parameters:

  • Name. The name of the type.
  • Type. The base type.
  • Fields. A list of the fields included in the type. Clicking the parameter or Dots.jpg next to it opens the dialog box for editing a set of fields.
  • Description. The type description.
  • Purity level. The flags correspond to the clauses of the same name used with the PRAGMA RESTRICT_REFERENCES when defining the package.

The SQML editor below displays the generated code of type definition.

PL/SQL Packages

PL/SQL definitions describe PL/SQL packages stored on the database server. The package definitions can contain the procedures used in other definitions.

PL/SQL package includes a header and a body. The package body contains the definitions of PL/SQL procedures and fragments of PL/SQL free text. The header can contain the prototypes of some procedures defined in the package body. Out of package, it is possible to use only those procedures prototypes of which are included in the package header.


PL/SQL Package Editor

The editor looks as follows:

Dds-package-editor.jpg

The editor contains the following parameters:

  • Name. The name of the package.
  • Deprecated. If the flag is set, the package is considered to be deprecated. When compiling, the system displays a warning message each time the procedure of such package is used.
  • Description. The package description.
  • Purity level. The flags correspond to the clauses of the same name used with the PRAGMA RESTRICT_REFERENCES when defining the package.

The SQML editor below displays the generated package code.


PL/SQL Procedure Editor

The editor looks as follows:

Dds-procedure-editor.jpg

The editor contains the following parameters:

  • Profile. The procedure profile. Clicking the field or Dots.jpg next to it opens the dialog box for editing the profile.
  • Deprecated. If the flag is set, the procedure is considered to be deprecated. When compiling, the system displays a warning message each time such procedure is used.
  • Description. The procedure description.
  • Public. If the flag is set, the procedure can be used by other PL/SQL packages or called from ADS.
  • Deterministic. If the flag is set, the DETERMINISTIC clause will be used when defining the procedure.
  • Cache result. If the flag is set, the caching of the procedure result is allowed
  • Relies on. A set of tables the procedure result depends on. The parameter is available if the Cache result flag is set.
  • Generate in DB. If the flag is set, the scripts being generated will create the current procedure in the database.
  • Purity level. The flags correspond to the clauses of the same name used with the PRAGMA RESTRICT_REFERENCES when defining the procedure.
  • The procedure code. The SQML editor toolbar enables to execute the procedure.


Text Fragment Editor

The text fragment editor contains the Name parameter that defines the name of the text fragment and the SQML editor. The text entered in the SQML editor will be inserted into a respective place of PL/SQL package.

Access Partition Family

Access partition family is an attribute by which the instances of entity classes and application classes are classified. The access partition family includes several access partitions.

The access partition family can be based on the enumeration or a table.


Editor of Access Partition Family

The editor contains the following parameters:

  • Head. The definition on which the access partition family must be based on. It is possible to specify a table or an enumeration.
  • Parent family. Parent access partition family.


Application Definition Segment

Main title: Application Definition Segment


User Definitions Segment

The UDS segment can contain:

  • the user-defined functions and user-defined reports sent by the customer for the vendor support
  • the random files to be delivered to the customer in the product distribution kit

The user-defined functions in the UDS segment can use the definitions of the lower layers.


Sending User-Defined Functions for Maintenance

The user-defined functions developed by customer can be sent to the developer for maintenance. For this purpose, the user-defined functions are exported to XML files by the respective command in RadixWare Explorer and the obtained files are sent to the developer.

The developer loads the files received from the customer to the module of the UDS segment by the respective command in RadixWare Designer.

RadixWare Designer does not allow to change API employed by the user-defined functions of the UDS segment. The developer can mark the API definitions as deprecated. When compiling, the system displays the warning message each time the deprecated definition is used.


Sending User-Defined Reports for Maintenance

The user-defined reports developed by customer (in the RadixWare User Extensions Designer application) can be also sent to the developer for maintenance. For this purpose, the user-defined reports are exported to XML files by the respective command in RadixWare User Extensions Designer and the obtained files are sent to the developer.

The developer loads the files received from the customer to the module of the UDS segment by the respective command of the context menu of Import User Definitions unit. At that the report definition is created in the unit.

The context menu of the report definition located in the UDS segment contains the Export specific item. When selecting this menu item, the report is exported to the XML file.

UDS Module Context Menu

For the description of the context menu items common for all definition types, refer to Definition Context Menu. The specific context menu items of the modules of the UDS segment are described in the following table:

Menu Item Description
Import User Definitions... Imports the user-defined function / report from XML file.
Create File Storage Creates the file storage in the module.

User-Defined Functions

The user-defined function editor contains the following parameters:

  • Storage Property. The application class property whose value can be this user-defined function. The parameter is editable only when creating the definition.
  • Function class. The application class whose instance is this user-defined function. The parameter coincides with the property type specified in the Storage Property parameter. The parameter is filled automatically and is not editable.
  • Method. The profile of the user-defined function. The parameter is filled automatically and is not editable.

The JML editor is located below the mentioned parameters. It defines the source text of the user-defined function.


Definition Context Menu

For the description of the context menu items common for all definition types, refer to Definition Context Menu.

The specific menu items of the user-defined functions of the UDS segment are described in the following table:

Menu Item Description
Import... Imports the user-defined function from XML file.
Export... Exports the user-defined function to XML file.

Import User-Defined Function

To import the user-defined function from XML file, select the Import item from the context menu of the user-defined function or the Import User Definitions item from the UDS module context menu. At that, the dialog box for selecting the file is opened.

When importing the user-defined functions, the following actions are executed:

  1. The user is asked if the existing definitions in the definition module must be deleted. If the user confirms the action, all definitions are deleted from the module.
  2. The definition of the user-defined function is loaded from the specified file.
  3. The module dependencies are automatically actualized in such a way that all the definitions used by a new one are available for it.

File Storage

The module of UDS segment can contain the storage with a set of random files. To create a storage in the module, select the Create File Storage item from the module context menu in RadixWare Designer navigation tree. At that, the Files child definition is displayed for the module.

To create a file or directory in the file storage, select New | Other item from the Files context menu. At that, the NetBeans standard wizard for creating files is opened.

To edit the files in the storage, use the NetBeans standard editor.

For the description of NetBeans file creation wizard and the NetBeans standard editor, refer to NetBeans documentation.