![]() PROIV Developer Glossary |
![]() DEVELOPER |
![]() |
A glossary of terms used in PROIV Developer:
Alternate Index Map - Available for CISAM and relational database files. The alternate map allows you to access a file via alternative key field(s). In the case of relational database files, the maps should be used to reference views.
Comm Variable - A variable that is available to any function. Current contents of all comm variables can be displayed in System view.
Dynamic View - Shows all the objects in the function that have a dynamic effect on the PROIV timing cycle.
Error Link - The function to be executed when the current function is exited in error. Specified on the Events tab of the function definition.
Events View - Shows every permissible event point for every object in the function.
Exit Link - The function to be executed when the current function is exited. Specified on the Events tab of the function definition.
File Definition - Also known as a logical file. Defines the format of the data fields in a file. Each physical file used by PROIV must have at least one logical file definition, but may have more depending upon the application.
File Variable - The name associated with a data field in a file. File variables are defined in the file definition window.
File View - Provides information on all File Accessors in the function– their access modes and read/return objects.
File View - The term ‘function’ in PROIV is used in the same way that the term ‘program’ is used in third generation languages. As a developer using PROIV, you will create numerous functions that operate together to accomplish a series of related operations, such as data entry, storage and update, or report production.
Fragment - Any function developed in PROIV Developer is built up from, and can be broken down into, fragments. A fragment can be anything from a single screen component or single file accessor, through a set of screen components, to a complete cycle, to a set of several nested cycles.
Global Function - A function that can be called by another function.
Interface Map - Parameters to be supplied to a Global Function are specified on the parameters tab of the function definition. For each call to a Global Function, an interface map is used to indicate the variable to be mapped to each parameter.
Linkage view - Provides analysis of all functions calling or called by the current function.
Logical File - Also known as a file definition. Defines the format of the data fields within a file. Each physical file used by PROIV must have at least one logical file definition, but may have more depending upon the application.
Object - Within PROIV Developer, all components of your application can be thought of as objects – from an individual variable to a complete file definition, from a on a screen, to a cycle within a function, to the complete function. An object is a physical entity that has values or attributes assigned to it. You assign these values and attributes via the property sheet associated with the object.
Each object is identified by its unique tag name. Using meaningful tag names will greatly improve the readability of your functions.
Managed objects are those that you can open via the Open Object Dialogue: file definitions, functions, tasks and global logics.
Object Types
box |
|
|
|
control break |
|
combo box |
|
dummy field |
|
editbox |
|
file accessor |
|
function |
|
header |
|
holding field |
|
icon |
|
chart |
|
slider |
|
spinner |
|
listbox |
|
line |
|
many time paging screen/report cycle |
|
many time paging window cycle |
|
many time screen/report cycle |
|
many time window cycle |
|
menu cycle |
|
one time paging screen/report cycle |
|
one time paging window cycle |
|
one time screen/report cycle |
|
one time window cycle |
|
radio group |
|
selection cycle |
|
text |
|
update cycle |
|
variable |
|
Parameters - Allow information to be passed into a function. The information may be from another PROIV function (the called function must be a Global Function) or, if the called function is included in a task, the information may be from an external program.
Process Point - A point in a function at which logic may be called.
Promote - Convert a specified fragment or function to a template which is stored in a central library available to all developers.
Property Sheet - Every object in PROIV Developer has an associated property sheet, which is used to assign values and properties to the object.
Statics View - Shows all static objects in the function, such as static text and s on a screen or headings on a report.
Structure View - Gives a complete outline picture of all the cycles within a function.
Tag Name - Each object is identified by its unique tag name. Using meaningful tag names will greatly improve the readability of your functions.
Task - Tasks allow you to call sections of PROIV code from a third party program – for example, from a Visual Basic program.
Template - Functions and fragments that may be of use to other developers can be promoted to templates and stored in a central library.
Topic ID: 500258