Archive for March 30, 2012

Interview Question 2 Answer

What are the 5 relation types and describe each one?

August Poll Results

TopicResults
General 2E navigation.9%
Create a web page from 2E.27%
Web services in 2E.27%
Triggers in 2E.9%
New features in 2E 8.6.27%

•The ‘Known by’ relation defines a primary key field or identifying key field.  You can have as many of these identifying keys defined as required for a unique record key.
•A ‘Qualified by’ relation is another identifying key field.  These are used in situations where you may have data with the same unique primary keys and an additional qualification of a date or quantity field for instance.  (An effective date or a quantity level break)
•The ‘Has’ relation is a simple attribute
•The ‘Owned by’ relation indicates a parent-child relationship between the two files.  This is an identifying key field and is the key from the parent file (all the identifying key fields).
     •Enforces referential integrity in the database
     •Allows for Virtualization of fields (creating a Join Logical)
     •Provides for automatic code generation of record selection capabilities (F4     or ? processing)
•The ‘Refers to’ relation is also a foreign key stored in the record, but it is not an identifying key field to the record.
     •Enforces referential integrity in the database
     •Allows for Virtualization of fields (creating a Join Logical)
     •Provides for automatic code generation of record selection capabilities (F4 or ? processing
•The ‘Includes’ relation allows you to include a specified group of fields in the file.
     •This group of fields is defined as a structure file
•The ‘Extended by’ relation is a relation intended to signify that a file has additional related data in another file. The extension file must still be entered using the ‘Owned by’ relation.
     •This relation doesn’t add any attributes to the file (by default)
     •Enforces referential integrity in the database (interactive functions will need to be ‘told’ to ignore this validation!)
     •Indicates a one to one file relation.
     •Allows for Virtualization
     •Provides for automatic code generation of record selection capabilities (F4 or ? processing)

Multiple Line Entry

In the old days of 2E prior to 8.1, 2E fields longer than the screen width could be a bit of a problem. In order to get them to work you had to use function fields on the screen and pass the values from the function fields back and forth between the actual field and the multiple function fields. You would have to substring the long field into multiple functions fields on the screen to display the field. Then you would have to concatenate the function fields together in order to place them into the database field.

This problem was solved a while ago with 2E 8.1.  You simply have to go to Edit Screen Entry Details for the field that needs to display on multiple lines and select display on multiple lines = Y.  2E will calculate the length of the input field based on the Height attribute.  The Height corresponds to the number of lines to display for the field.

In this example I have a 100 character field.  That will display on 2 lines of 50 characters for each line.

The Web Option Flow

Sometimes it helps to see a diagram of a process.  I have created a basic flow of how Web Option processes the 2E screen as an HTML page.  This will help in understanding how the different parts of Web Option fit together in the Web Option web application.

WebOption Macros and Scripting

Support for user defined macros was added in version 8.5 of WebOption.  The use of macros  scripting will allow the developer to record and plan keystrokes within the generated screen.  By using macros and scripting you can simulate flowing through a series of screens, actually skipping the screens visually and simply moving on the web from one screen to the next.  So in effect, you can reorganize some of the actual flow of your application and make it more web friendly.

 

 

 
 
© 2013 CM First Group - All rights reserved