1 Definition Form

To define an object it is necessary to access the dictionary of the application and select: Objects / Definition / Objects

This takes you to the Object Definition Form:

This form is common for different objects, such as reports and forms, although not all options are valid for all object types. Fields marked with an asterisk (*) are mandatory.

  1. TABS: tabs allow you to navigate between forms, all related to object design. The current view corresponds to the highlighted tab.
    • Common tabs: Input, Variables, Output, Links, Languages, Metaquery and Alias.
    • Exclusive tabs for reports: Report Styles, Report tabs, Groups and Headers.
    • Exclusive tabs for forms: Form and TX Manager.
  2. IDENTIFICATION:
    • Object name*: it must be the unique identifier. Use conventional syntax, with lowercase letters and underscore between separate words. As usual, it is preferable to give a meaningful name to the object.
    • Tag name: it corresponds to the name that will be displayed in the object's tab. Capitalize the first letter of the tag name.
    • Title*: it is the text that appears in the object header. Use capital letters.
  3. ADDITIONAL INFO:
    • Area*: This field corresponds to the functional groups of objects and panels and serves two major functions. On the one hand, to assign role permissions through the wic_conf. On the other, to control some aspects related to the appearance and color of the object.
    • Render type*: select between report, singlerow form or multirow form.
    • Execution type*: select between read only (report), read mutable (special reports with capabilities for data change), read/write (transaction forms), process (makes transactions and performs a report) and not allow background (only for not to run processes in the background).
  4. STATUS:
    • Active: if the active box is enabled, then the object can be selected and executed. Deactivate if the object is being design or under revision.
    • Full output: by default the results of a report are paginated in as many pages as necessary. On the contrary, if the option Full output is enabled, all results will be displayed on a single page.
    • Print*: choose between Try Vertical or Always landscape.
  5. PERFORMANCE:
    • Forces reload: data is reloaded every time user accesses to any register. Recommended only for objects with a high concurrency of users, since it adversely affects performance.
    • Refresh: time, expressed is seconds, to perform a complete data reload.
  6. PERMISSIONS:
    • Reorder: the objects will show the standard options to reorder result set. Have in mind that processes should not allow reordering.
    • Query allowed: the object will show query icon.
  7. WEB SERVICES:
    • SOAP: allows accessing the object via this protocol.
  8. ORDER BY CRITERIA: it controls the initial order in which the Result Set of the SQL statement is displayed.
  9. SQL STATEMENT: SQL statements are used to retrieve data from the database. This would be the data the JRepObject uses to operate. This data is commonly referred to as Result Set or Cursor.
 

2 Definition of object

Through this option we access to the definition of system objects. From it, if the user has the required authorizations, it is possible to create, modify and delete such definitions. As well as information regarding identification and object parameters, it will be also possible to define:
  • SQL Statements. The syntax of the SQL statement that contains the object.
  • Information on the object. Information about the content and functions of the object.
  • Image. Image of an example of the object result.
  • Objects to which it is referenced to. List of objects that are hyperlinked to that given object.
Likewise, it is possible to access to consult and/or describe information attached to objects: As an additional function, it is also possible to perform the following ones:
  • Generating an object in XML format.
  • Copying objects to create similar ones or to transfer them to another repository database.
  • Automatically generating input and output fields for those objects which represent masters; that is, its code is equivalent to a database table name.
  • Delete an example image associated to an object.
   

3 Input fields (QBE)

Through this option we access to the definition of an object input fields. If the user has the required authorizations, it is possible to create, modify and delete such definitions. As an additional function, it is also possible to renumber input fields belonging to the object.
 

3.1 Use of all columns

To use all the columns of a table as input fields, it will only be necessary to enter the name of the table and an asterisk * in the Column field.

As a result, the report displays the query screen, which contains all columns of stipulated table.

IMPORTANT: the query screen includes all columns of the table, even those columns that haven't been selected in the SQL statements. Those columns will also work as filters.
 

3.2 QBE to SQL conversion

TO DO

This section is incomplete and will be concluded as soon as possible.
 

4 Input variables

Through this option we access to the definition of an object query variables. If the user has the required authorizations, it is possible to create, modify and delete such definitions. Likewise, it is possible to consult information attached to the object to which query variables belong to: As an additional function, it is also possible to renumber object query variables.
 

5 Meta query

Through this option you access the definition of the meta queries of an object. If the user has the necessary permissions, these definitions can be created, modified and deleted.

The meta queries consist of establishing selection criteria with fixed conditions associated with an object, in such a way that, when executing concerned object, the system will enable the meta queries of the object in question. This way the user, in addition to the indicated dynamic selection criteria, can (optionally) select one of the meta queries to set conditions for selecting it.

 

6 Output variables

Through this option we access to the definition of an object output fields. If the user has the required authorizations, it is possible create, modify and delete such definitions. Likewise, it is possible to consult information attached to the object to which output fields belong to: