This page (revision-50) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
50 26-Nov-2021 10:22 1 KB kparrott to previous HOW_DO_I_ADD_A_HEADER_OR_FOOTER_TO_A_SCREEN ==> HOW TO ADD A HEADER OR FOOTER TO A SCREEN
49 26-Nov-2021 10:22 1 KB jmyers to previous | to last
48 26-Nov-2021 10:22 3 KB jmyers to previous | to last
47 26-Nov-2021 10:22 4 KB jmyers to previous | to last
46 26-Nov-2021 10:22 5 KB jmyers to previous | to last
45 26-Nov-2021 10:22 5 KB jmyers to previous | to last
44 26-Nov-2021 10:22 6 KB jmyers to previous | to last
43 26-Nov-2021 10:22 7 KB jmyers to previous | to last
42 26-Nov-2021 10:22 9 KB jmyers to previous | to last
41 26-Nov-2021 10:22 10 KB jmyers to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 73 added 42 lines
High Line has created various sample screen headers and footers throughout Self Service. These headers and footers are either HTML or JSP files which are saved in the "docs" folder under selfService on your 9ias server.
The headers and footers provided can be edited to your requirements. It is recommended, however, that you follow High Line's naming conventions for these files.
;Header:
Each header is named as follows:
FUNCTION_Header.html or FUNCTION_Header.jsp, where FUNCTION is the name of the function to which you will be applying this header (e.g. WEEPP_Header.html).
;Footer:
Each footer is named as follows:
FUNCTION_Footer.html or FUNCTION_Footer.jsp, where FUNCTION is the name of the function to which you will be applying this footer (e.g. WEEP_Footer.html).
A header and/or footer will only appear on a screen if the Header Info and/or Footer Info preferences have been properly setup via the Maintain Functions ([IMFN]) screen in Self Service Administration module to call the appropriate HTML or JSP document
from the "docs" directory.
Whenever Self Service software updates are provided by High Line that all of the documents in the "docs" folder will be overwritten. To avoid losing any newly created documents or changes made to the delivered documents, we recommend that you keep
a master copy of ALL required headers and footers outside of the server environment.
!Q: HOW DO I CREATE A MENU?
A:
# Access the Create Menus form through the Web Site Administrator main menu, or through the Navigation tree. You will be presented with a list of menus.
# Click the Add icon found at the bottom of this list. A blank row will now appear in the list.
# Ensure your cursor is on that row. Directly beneath the list, there are a series of fields allowing you to define the new menu.
# Fill in the name of the menu in the Menu Code field.
# Complete the Sequence, Code and Type fields to identify the menu items (functions or menus) that will compose your menu and the order in which they should appear.
# Complete either the Call Function or Call Menu field for each menu item. A menu item may only call either a function or a menu, so you will fill in only one of these two fields.
# Complete the Label field and if desired, the Icon Name field.
# Set the Menu Action Usage must be User Defined. This must be completed.
# Once you are satisfied with the data you have provided, click the Save button.
!Q:HOW DO I CREATE A USER NAME?
A:
# Access the Create User (IMUS) form through the Web Site Administrator main menu, or through the Navigation tree. You will be presented with a list of users.
# Click the Add icon found at the bottom of this list. A blank row will now appear in the list;
# A ensure your cursor is on that row. Directly beneath the list are the fields that allow you to define the user you wish to enter.
# Enter the user’s ID/Name and Description in the appropriate fields.
# If the user should have access for a limited time period, you may define that time period through the Start Date and End Date fields.
# You may provide an Email Address and Password in the appropriate fields
# Define the general execution rights for this user through the Create Allowed, Retrieve Allowed, Update Allowed and Delete Allowed booleans.
# Define execution rights to a specific function for this user through the Execution Rights tab at the bottom of the form.
# At this point you may also define the role’s Preferences and assign Roles.
# Once you are satisfied with the data you have provided, click the Save button.