Screens

Screens are dynamic html forms that allow database queries, inserts, updates, and deletes.  Screens also provide multiple ways of viewing the data returned by the database.  

See Also

Screen Templates

Adding Blocks to Screens

Modifying Blocks on Screens

Chart Blocks

Fields

Property Definitions

Creating Screens

  1. In the Explorer Tree, expand and select the Group Information object in which you wish to create a screen.

  2. There are options in creating a screen at this point.

  1. The Creating an Entity screen will be displayed.

  2. Select the Screen entity type by left-clicking on the Screen radio button.

  3. Click on the Next button on the bottom right of the screen.

  4. In the Entity Name field, enter the desired name for the screen.

  5. In the Datasource pop-list, select the desired datasource or (use default).

    Selecting (use default) will allow the screen or screen template to be used with any datasource, and data brought in will be determined by the user's datasource.

  6. In the Based On pop-list,select the template on which the new screen will be based.  

  7. In the Default Mode pop-list, select the view type that will be displayed by default for this screen.  Choices include QBE View, List View, Edit View, and New View.  

  8. In the Body Style pop-list, select the body style to be applied to the screen.  The default is (from parent) allowing the style to be determined from the selected template.

  9. In the Editable Field Style pop-list, select the style to be applied to the editable fields on this screen.  The default is (from parent) allowing the style to be determined from the Editable Field Style applied to the selected template.

  10. In the Non-Editable Field Style pop-list, select the style to be applied to the labels and display only fields on this screen.  The default is (from parent) allowing the style to be determined from the Non-Editable Field Style applied to the selected template.

  11. In the Lov Style pop-list, select the style to be applied to lists of values that are activated from fields on this screen.

  12. In the Link Style pop-list, select the link style that defines the styles that will be used for the hyperlinks on this screen.  The default is (from parent) allowing the style to be determined from the selected template.

  13. Click on the Next button on the bottom right of the screen.

  14. The Adding New Block screen will be displayed.

  15. See the Adding Blocks to Screens section for the next steps.

Modifying Screens

  1. In the Explorer Tree, expand the Group Information object and any sub-groups until you can select the screen that you wish to modify.

  2. Display the screen properties.  These will either be displayed in Alphabetical or Logically, depending on the setting of the [Sort Alphabetically/Logically] button.  The following instructions are assuming that the properties are sorted logically.

  3. In the Name property, the name that you entered when creating the screen will be displayed.  It can be changed, if desired.

  4. In the Description property, enter a user-defined description for this screen.  The default is the type of object followed by the screen name. (i.e. Screen:NEW_SCREEN)

  5. In the Title property, enter the title for the screen.  The title is displayed in the title bar of the browser when the screen is generated.

  6. In the Datasource pop-list, the datasource that you selected when creating the screen will be displayed.  It can be changed, if desired.

    If set to (default), the default for the user's log in will be used when this screen is displayed.

  7. In the Allow Anonymous pop-list, select true if anonymous users should have access to this screen.  Select false if anonymous users should not have access to this screen.

  8. The Inherits From pop-list displays the template from which this screen was created, grayed out.  This value cannot be changed.

  9. In the Display Only pop-list, select true if the data on this screen will be displayed as text only and cannot be modified.  Select false if the data on this screen will be displayed as fields by default, but block and field level settings can override this.

  10. In the Read Only pop-list, select true if the data on this screen will be displayed in editable fields, but cannot be modified.  Select false if the data on this screen will be displayed in editable fields and can be modified by default, but this setting can be overridden with the Editability property at the block or field level.

  11. In the Default Mode pop-list, select the view type that will be displayed by default for this screen.  Choices include QBE View, List View, Edit View, and New View.

  12. In the Editable Field Style pop-list, select the style to be applied to the editable fields on this screen.  

  13. In the Non-Editable Field Style pop-list, select the style to be applied to the labels and display only fields on this screen.  

  14. In the Lov Style pop-list, select the style to be applied to lists of values that are activated from fields on this screen.

  15. In the Link Style pop-list, select the link style that defines the styles that will be used for the hyperlinks on this screen.  

  16. In the Width property, enter the total width in pixels for this screen.

  17. In the Height property, enter the total height in pixels for this screen.

  18. In the Before Save property, enter any code that should be run before any queries are executed on this screen.  The code entered here should be written in SQL.

  19. In the After Save property, enter any code that should be run immediately after all queries are executed on this screen.  The code entered here should be written in SQL.

  20. In the On Load property, enter any javascript code that should be run when the screen is loaded.

  21. In the Required Roles property, select the roles that are required to run the entity.  When running this entity, the user must have at least one of the roles entered here, or the entity will not run, and the user will be returned to the log in screen.

    When you click on this field, a pop-up will be displayed with the available roles in the left side of the pop-up and the roles assigned to the entity on the right side.  

    To assign a role to the entity, select the desired role on the left side, and then click on the >> button to move it to the right side.  

    To unassign a role, select the desired role on the right side and then click on the << button to move it to the left side.  

    When all desired roles have been assigned, click on the Apply button.

    The Invalid Access Redirects To property will be displayed to allow you to define the entity that should be displayed for the user if the user does not have one of the required roles entered here.

  22. In the Required Globals property, list the global variables that are required to be set in order for the entity to run properly, separated by a line break.  If the entity is run, and some or all of these globals are missing, the entity will not be run.  The format is GLOBAL or, if desired, GLOBAL = VALUE.  

    For example, if the global variables ORG_UNIT_ID and EMPNO must be set for the page to run correctly, you would enter
    ORG_UNIT_ID
    EMPNO

    If the global variable ORG_UNIT_ID needed to have the value 100, but it didn't matter what the EMPNO value needed to be, you would enter
    ORG_UNIT_ID = 100
    EMPNO

  23. In the Accessed via property, enter the entity from which this screen is generated.  This is an optional property.  For example, if the screen has certain conditions that must be met on a report entity before it can be run, the name of the report entity should be entered here.  This prevents the screen from being improperly accessed.  

  24. In the Invalid Access Redirects To property, enter the entity to which the user will be redirected if this screen is improperly accessed.  This property is only displayed when the Accessed via property or Required Roles property is entered.  

    If a user accesses this screen from an entity other than the one entered in the Accessed via property, instead of opening the screen, the entity entered in this property will be opened.

    If a user that does not have one of the required roles accesses the entity, instead of opening the screen, the entity defined here is opened.

  25. Set the HTML Output Only property to the desired setting.  When this property is set to true, no javascript will be output in the entity source code and no scripted links should be used on the screen.  It is recommended that this property be set to true when creating a redirect entity for use when a non-supported browser is used to access an entity in the repository.

  26. In the Results Disposition property, only Return to Caller can be selected.  

  27. The Created on property displays the date and time on which the screen was created and cannot be changed.

  28. The Modified on property displays the date and time on which the screen was last changed and cannot be modified.

  29. When all changes have been made, press the [Save] button in the Main Toolbar.

Xephr is a registered trademark of NDS Systems, LC.

Copyright © 2007 NDS Systems LC.