View Maintenance Help

View Definition records contain the parameters, directory paths and filenames which together define the view (or look and feel) that a user will experience through the browser. Once a View is defined it can be referenced by Organizations in the Organization definitions. Hence all users within that Organization would receive that View definition. Any number of views can be defined and any number of Organizations can reference a view.

The default predefined view ID is 'dxstd'.

To add a new View enter the new unique View ID and click the Add button.  The View Maintenance form will display. Complete the form and click Save to save the new View.

To search for a View, enter an exact or partial match of the View ID to search for and click Search.

To view, change or delete an existing View on the search list click the View's ID.  You can then modify the View's definition and click Save or you can click Delete to remove the View if it is not in use by an Organization.

View file field definitions : 
View ID
The View ID can be up to 8 characters in length and can consist of alphanumeric characters, comma, period, dash and underscore only. The ID is the unique identifier of the View and is case sensitive.

Option Directory 
The Option Directory defines where to find the HTML, images and icons to be used for menu option presentation and some other DynamicXport standard pages such as logoff.html and msg.html. The default Option Directory is dx/dxstd/, which is defined in the view file as relative to the dx directory, or dxstd/
To create a new Options look and feel you can create a new Options theme directory by copying the dx/dxstd directory to another directory under dx/ and then modify the options files. For example copy dx/dxstd/* to dx/siteabc/*. Then reference the new Option Directory in the View definition as siteabc/
Images and icons directories are subdirectories within the option directory. 

Option Type 
The Option Type indicated which type of menu option presentation to use. There are several pre-configured types that can be used and modified or you can create your own and reference it as Option Type x. Option Type 1 will utilize option1.html, type 2 option2.html, etc and Option Type x will utilize optionx.html 

Option Type 1 - Top Frame/Drop down box Uses a Top Frame with drop down list of options. Top frame has smalllogo.gif with an Alt/Link to Exit URL. Background can be changed in .css class= OptionTopFrame and class=OptionTopFrameSub and class=OptionBody. (By default, main page has the largelogo.gif centered. )
(It is recommended that Option Descriptions be kept below 18-20 characters for proper display.)

Type 2 - Left Frame/Vertical list Uses a left frame with a list of options. Left frame has smalllogo.gif with an Alt/Link to Exit URL. Background and fonts can be changed in .css class= OptionLeftFrame and class=OptionLeftFrameSub and class=OptionBody (By default, main page has the largelogo.gif centered. ) 

Type 3 - No frame/Full page Uses the full screen to display options (typically as large icons). Uses top3.gif for a heading with an Alt/Link to Exit URL and left3.gif for side image. Background of page can be changed in .css class=OptionBody 

Type 4 - Top frame/Horizontal tabs Uses a Top Frame with foldertabs of options. Background can be changed in .css class=OptionTopFrame and class=OptionBody 

Type x - Custom Custom defined/designed HTML options page 

Menu show type 
This indicator defines how each menu option is presented to the user. 
Choices are : 
1. Display Option Description
2. Display Option ICON image
If displaying ICONs for options, an icon image file must be created for each menu option and placed in the Option Directory icons subdirectory. 

Merge Directory 
The merge directory defines where to find the html pages to merge to for all the custom applications. The Merge directory field is available to the application as an S. field (S.VIEW.MergeDIR) to facilitate the application merging to the correct html page. The Merge directory automatically precedes an Option's Input page and Output page. The Merge Directory allows for the flexiblility of defining different View definitions and HTML pages to facilitate different stores, locations and language variations all using the same DynamicXport platform and same applications. The Merge Directory should be defined relative to the dx/ directory and should be at the same directory level as the dx/cgi-bin directory. For example, the directory could be /dx/custom/ and referenced in the View definition as custom/ 

Stylesheet filename 
The stylesheet filename defines the stylesheet .css filename to use for this view. The stylesheet file is a centralized file on the web server which defines various web presentation parameters such as fonts, colors and backgrounds. The default stylesheet file is dx/styles/dxstd.css and is referenced as styles/dxstd.css To create another scheme or template copy the dxstd.css to another filename, modify the definition and then reference it in the view definition.

Messages filename 
The message filename defines the message text filename to use for this view.
The message file is a centralized file on the application server which defines the message text to display for associated message numbers. These are typically used but not limited to error messages.
The format of the file is message #, colon, message text. Message text is limited to 74 characters. Message numbers 0-10000 are reserved for DynamicXport. Message numbers above 10000 are available for your application's use.
The message file MUST reside in the same directory as the dx listener program. The default message file is dx/dxmsg.txt and is referenced as simply dxmsg.txt in the View definition.
To create another message file for different languages, etc. copy the dxmsg.txt to another filename in the same directory, modify the messages in the file and then reference it in the View definition.